BSOD (Past 2 Days)
Are you overclocking your system? Might want to back it down/retune if you are. I would also make sure your graphics driver is up to date and make sure that your CPU and GPU are not overheating. If you don’t already have software the monitors these temperatures then I would recommend HWMonitor which can be found here:
http://www.cpuid.com/downloads/hwmonitor/1.22-setup.exe
Chloe (Version 3):
[i7 930 @ 4.1Ghz (1.3875V) w/Cooler Master 120M][Gigabyte G1 Gaming GTX 970 (stock)]
(edited by Ilithis Mithilander.3265)
I have MSI Afterburner, it can monitor temps, but I do not overclock my system, it is too problematic for this rig
temps are fine, under 40 idle, under 80 stressed.
Drivers are up to date, Nvidia, done several clean installs, don’t normally opt for beta drivers either.
Perhaps try using memtest to test your RAM. I had a bad stick last year when Guild Wars 2 launched and I got blue screens when the RAM was being used/stressed by the game. You can find memtest here:
http://www.memtest.org/
Then for kittens and giggles, I would run a check disk scan on the hard drive that has Guild Wars 2. Simply go to ‘My Computer’ and right click on the hard drive and go to ‘Properties’. Then, head to the ‘Tools’ tab and hit the ‘Check now…’ button in the ‘Error Checking’ section.
Chloe (Version 3):
[i7 930 @ 4.1Ghz (1.3875V) w/Cooler Master 120M][Gigabyte G1 Gaming GTX 970 (stock)]
(edited by Ilithis Mithilander.3265)
I remember how long it took when running a memtest and chkdsk a long time ago, I will have to try that when I can leave my computer idle.
-Ran a memtest, RAM is fine
-Ran Chkdsk (qued from windows), was ok
-Bought a new heatsink and thermal paste (thought it may be a CPU overheat issue, i may need to check voltages) temps are good (even though Speedfan tricked me and told me they are running at 80+ degrees)
- Cleared out any dust from my GPU (its a 570, so that brick can hide some dust in its casing)
Had a BSOD prior to installing the new heatsink (so hopefully this fixes it)
If not, I will post a recent minidump, because that would be so infuriating -.-
I’ve started to have BSODs lately too, memory is fine, no harddrive errors either. I’m not sure but since the game’s been running fine up until say a two weeks ago, and I haven’t made any changes to my system or installed any new software or anything, I’m starting to wonder.
Not sure if your link is down or what, but the link just goes to the hosts main page and not a file DL page. Check that and reupload it. If your temps were in spec, the new HS will not change anything. What is your system spec? Can you list all parts and model numbers?
Does it BSOD any other time or just GW2?
Not sure if your link is down or what, but the link just goes to the hosts main page and not a file DL page. Check that and reupload it. If your temps were in spec, the new HS will not change anything. What is your system spec? Can you list all parts and model numbers?
Does it BSOD any other time or just GW2?
Were you referring to the memtest link? If so, I have no control over that website since I have nothing to do with memtest besides being a consumer of their product. The download is about halfway down the page.
Chloe (Version 3):
[i7 930 @ 4.1Ghz (1.3875V) w/Cooler Master 120M][Gigabyte G1 Gaming GTX 970 (stock)]
Not sure if your link is down or what, but the link just goes to the hosts main page and not a file DL page. Check that and reupload it. If your temps were in spec, the new HS will not change anything. What is your system spec? Can you list all parts and model numbers?
Does it BSOD any other time or just GW2?
Were you referring to the memtest link? If so, I have no control over that website since I have nothing to do with memtest besides being a consumer of their product. The download is about halfway down the page.
Talking to the OP who posted a dump file of the BSODs.
Well it was posted about a week ago, so I will probably need to re-upload since it was most likely removed.
As for specs:
Win7 x64
i5-2500k
EVGA GTX 570
Raidmax 680w PSU
12Gb RAM (2×2 / 2×4, 1066×2 1600×2)
It used to only BSOD with GW2, but now it seems to be occurring in other graphically intensive games as well.
both GPU and CPU are at stock defaults.
https://www.dropbox.com/s/36y36em6ukl6tzk/052713-44600-01.dmp
(edited by Zietlogik.6208)
First thing that stands out is the PSU, Raidmax is know for being crap and causing all kinds of problems, if you have a multimeter I would hook it up to the PSU and check all the rails to see if they are in spec. Next is the RAM, not only are you running odd sized RAM you are also running mismatched speeds and most likely timings and possibly brands. Run memtest86+, when running it you should run a few passes on each stick, that being when you run memtest there should only be ONE stick of RAM in the system. please also post temps from coretemp and afterburner, both should be load temps, use IBT to load the CPU and something like kombustor for the GPU.
What mobo are you using? What are the brands and models of RAM you have in the system? Which model PSU is that? The BSOD is being caused by the NV driver, however the 5xx line is very picky about RAM speeds and types, so the mix match could be the cause (so I would take out the 2×2 set and just leave in the 2×4 for now and see what happens) assuming the card it self is good and no bad RAM or out of spec power. You should also follow the NV guide on doing a clean uninstall and reinstall of the driver just to make sure.
Also, open a cmd window and type in “sfc /scannow” without the quotes and see if it finds any errors, if it does and can’t fix them, follow the info to the log file and upload it.
(edited by TinkTinkPOOF.9201)
Ive had the same system setup for well over a year, and the issues have just propped up within the last week. I’ve already ran memtest, but not individually, but TBH, I will not dedicate that much time to it.
Hopefully it is not hardware related at all, I don’t have easy access to a credible parts store nearby, so this is simply a pain in the kitten to deal with.
Iv’e re-installed and driversweeped them out multiple times, no change
re-seated any connections, no change
ran that memtest (but not individually) no errors (and the speed difference just downclocks my 1600 to 1066)
temps are fine, it was just speedfan giving me false readings.
the board is an asus P8P67 LE
Ram is 2×2 Corsair DDR3 1600 (if i were to run 1 channel, these would be the ones i would use)
-2×4 G.Skill DDR3 1066 (higher capacity, lower frequency/speeds)
There are still some non-hardware tests I would like to go through (older NV drivers etc.)
But GHA!, is this ever irritating!
Ive had the same system setup for well over a year, and the issues have just propped up within the last week. I’ve already ran memtest, but not individually, but TBH, I will not dedicate that much time to it.
Testing one stick at a time is needed, many times RAM will not show bad unless tested as single sticks, same can be said for sets, and all sockets should be tested also. Tests should also be run for 8+ hours, many times marginal RAM will not flip bits until its been heated up well or used for long times.
Hopefully it is not hardware related at all, I don’t have easy access to a credible parts store nearby, so this is simply a pain in the kitten to deal with.
Where do you live? There are many online places to buy PC parts in most countries.
ran that memtest (but not individually) no errors (and the speed difference just downclocks my 1600 to 1066)
It is not about downclocking the RAM, or even being able to match up the timings, it is mismatched RAM, which can cause many problems, just different brands with the same speeds and timings in a system can cause problems, it is always best to use paired sticks.
temps are fine, it was just speedfan giving me false readings.
And they are?
Ram is 2×2 Corsair DDR3 1600 (if i were to run 1 channel, these would be the ones i would use)
-2×4 G.Skill DDR3 1066 (higher capacity, lower frequency/speeds)
Running any 2 sticks is dual channel, not single channel. Which ever you chose to keep, take out the other set and be sure to set the defaults for the RAM you leave in, run the system and see if you still get BSODs.
Testing one stick at a time is needed, many times RAM will not show bad unless tested as single sticks, same can be said for sets, and all sockets should be tested also. Tests should also be run for 8+ hours, many times marginal RAM will not flip bits until its been heated up well or used for long times.
Ya, I understand that, I just don’t really have that kind of time to run the tests.
Where do you live? There are many online places to buy PC parts in most countries.
There is a place I normally go to for parts across town, im in a large city, but I don’t have alot of time to do that, as well as don’t drive which makes it more difficult. And I have ordered plenty of parts online as well, but that tends to take more time to arrive than me just going to a parts store.
It is not about downclocking the RAM, or even being able to match up the timings, it is mismatched RAM, which can cause many problems, just different brands with the same speeds and timings in a system can cause problems, it is always best to use paired sticks.
Ya, maybe it just took alot of time to manifest, but it never gave me problems until about a week ago, and I have had it set up for a long time…but I am becoming more suspicious of my PSU over my RAM honestly.
And they are?
Under Prime95
Min: 36
Max: 69
Running any 2 sticks is dual channel, not single channel. Which ever you chose to keep, take out the other set and be sure to set the defaults for the RAM you leave in, run the system and see if you still get BSODs.
I know, i meant a single DIMM, not channel, A1, B1
Additional Notes: My event log shows some strange errors as well, it used to only be the nv errors, but now i am getting:
-Session “Microsoft Security Client OOBE” stopped due to the following error: 0xC000000D
That is linked to the Microsoft Essentials, which I removed and uninstalled, as well as removed registry traces of…
-The driver \Driver\WUDFRd failed to load for the device USB\VID_04E8&PID_5091\7f9ee40c000000f0.
Not sure about that one though
(edited by Zietlogik.6208)
You never said if you have a multimeter or not, so checking the PSU might not be an option, only other thing is having access to another PSU, as I said in my first post, it was the first thing to stand out to me.
I do not have a multimeter, and currently don’t have another PSU that I could swap to test :/
T.T I may just have to bite the bullet here and throw some money at a new PSU, and maybe upgrade my GPU (just cuz) this is so annoying
https://www.dropbox.com/s/nzxfoksk8yul2g3/060213-20248-01.dmp