BSOD - A real good one :\

[joshykins]

OK, so I've just built this new system from scratch. I've had it for about a week and a half now and this has been going on for about 4 or 5 days. Id get a BSOD every second day or so, and sometimes 2 in close intervals. Seems to hit at random, im trying to find a pattern, its never happened while gaming, usualy while the computer is under light load, small multitasking ect.

I have did what the BSOD stickie thread advised and post the following results. It's very annoying and hits when I least expect it to. Any help would be greatly appreciated. The error report screen that pops up after the computers reboots itself points to this location:

C:\Users\Joshykins\AppData\Local\Temp\WER-46020-0.sysdata.xml
or \WER-43617-0.sysdata.xml

Ive reinstalled the OS from the OEM disc 2 days ago. I thought that AVG may have been the culprit, their automated torjan scanner perhaps, Ive uninstalled AVG, but the BSOD hit me again two hours later.

 

[Anak]

Hi! joshykins, welcome to 7F

Just doing a quick search

C:\Users\Joshykins\AppData\Local\Temp\WER-46020-0.sysdata.xml
or \WER-43617-0.sysdata.xml

Points to a memory problem.
Did the OS offer to run a memory diagnostic after the BSOD?

If not you can run this: http://www.sevenforums.com/tutorials/715-memory-diagnostics-tool.html Let us know any results good or bad, please.

And if that does not show anything you can try this: Memtest86+ - Advanced Memory Diagnostic Tool It needs to run at least 4 passes, and some members here will suggest to let it run overnight. Again please let us know the results if you run it.

Meanwhile I will go ahead and see what I can find in your attached file.

 

[joshykins]

Thank you very much for the help! I will post the results as soon as I'm able, around 2-3 hours, thanks again!

Windows Memory diagnostic came up clean. I will run Memtest86+ and report back.

 

[Anak]

Your welcome!

If I am reading your post right, those 4 or more memtest runs should take more than 2 to 3 hrs.

 

[Anak]

I thought that AVG may have been the culprit, their automated torjan scanner perhaps, Ive uninstalled AVG, but the BSOD hit me again two hours later.

Your thoughts may be correct. I am seeing multiple instances of Avg trying to reload, and msi installer faults (DETAIL - 1 user registry handles leaked) because msiexec.exe tried to open a key which may be related to the AVG un-install.

Lets run a disk check: http://www.sevenforums.com/tutorials/433-disk-check.html follow to step #5 for now, just to see if there are any errors.
Omit steps #6, 7, & 8, and pick it back up again at step #10.
Disk Check has to run un-interrupted so you will have to plan to run this when you are not using your machine. Otherwise go to step #11, and schedule it to run at a later time.

Let us know any results good or bad please.

 

[joshykins]

Ok so Disk Check scanned and reported no problems. Memtest86 however caught 14 errors in three passes. So i would assume RAM is the culprit! Im going to replace all 4 sticks of this kingstin value ram rubish and report back tomorrow if succesful. Thanks Anak!

 

[Anak]

Your welcome Josh.

Don't be too hasty about that ram, it could be a bad slot also. There is a way to check each stick, and each slot.

See: FAQ : please read before posting - Canardpc.com 'bout half way down.

About The Errors Reported
-------------------------

- How many errors are acceptable?

No errors are acceptable. Even if there is just one error, something is
amiss which can cause your system to crash. Of course what the cause of the
errors is you will still have to determine.

- What do I do when I get errors?

If you are well stocked, have a few other machines at your disposal, or
just want to spend the cash for some new modules the best way to test if
the cause is in your memory modules is just to replace them and test again.
If you are less fortunate and do not have such modules at your disposal the
only viable way to get the system further diagnosed is to bring it in to a
computer repair shop, though there is still something you can do.

If you have more then one module in your system, test them one by one, if
one is consistently giving errors and another is consistently showing no
errors it's a pretty good bet that the module giving the errors is simply
defective. To exclude the possibility that a defective slot is throwing
your results, use the same slot to test each different module.