Random BSOD's - mostly while playing games.

[RacketLord]

So a short while back I had a completely random BSOD while just using Google Chrome. I thought nothing of it, since it's been a long time since i've had a BSOD. However, at that point I started receiving constant and random BSOD's, and most of the time they appear while i'm playing video games.

Every time I get a blue screen, it gives me a random error, such as: BAD_POOL_HEADER, SYSTEM_EXIT_OWNED_MUTEX, and IRQL_NOT_LESS_OR_EQUAL. After running Memtest86 and recieving over 250k reported errors - and that number was rising very quickly - I thought it was the RAM that was the culprit. However, after doing a full reformat of my primary HDD drive, and buying brand new RAM, the BSOD's are still present.

Just today, I had 4 of them in less than an hour - and one of them happened because I emptied the recycle bin! I have no idea where to go from here, so hopefully someone here can assist me with this. If RAM isn't the issue, could it be a bad mobo? Power supply acting up? Some random driver I don't know about, messing everything up? I'm sure you guys know better than I do.

I'm attaching the Seven Forums .zip in hopes that'll assist in the troubleshooting process. I quite literally have no idea what could possibly be causing this. Appreciate any help I can get!

 

[Jonathan_King]

Hello,

It seems as if your network adapter drivers were the cause of at least some of the BSODs. Start by giving them an update: Realtek

Rt64win7.sys    Fri May 22 10:52:30 2009 (4A16BC2E)

You might also run Memtest86 again, just for the heck of it.

...Summary of the dumps:

[font=lucida console]
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Sat Jul 28 20:45:24.122 2012 (UTC - 4:00)
System Uptime: 0 days 0:07:06.605
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : ntkrnlmp.exe ( nt!KiProcessExpiredTimerList+110 )
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xA_nt!KiProcessExpiredTimerList+110
BiosReleaseDate = 06/17/2010
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Sat Jul 28 15:38:20.467 2012 (UTC - 4:00)
System Uptime: 0 days 2:36:01.685
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for ndis.sys - 
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : ndis.sys ( ndis!NdisFRegisterFilterDriver+1f3c0 )
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0x109
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x109_1_ndis!NdisFRegisterFilterDriver+1f3c0
BiosReleaseDate = 06/17/2010
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Sat Jul 28 21:07:05.715 2012 (UTC - 4:00)
System Uptime: 0 days 0:05:50.198
*** ERROR: Module load completed but symbols could not be loaded for nsiproxy.sys
Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+a53 )
BUGCHECK_STR:  0x19_3
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  wmpnetwk.exe
FAILURE_BUCKET_ID:  X64_0x19_3_nt!ExDeferredFreePool+a53
BiosReleaseDate = 06/17/2010
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Sat Jul 28 20:36:21.783 2012 (UTC - 4:00)
System Uptime: 0 days 0:01:32.016
Probably caused by : ntkrnlmp.exe ( nt!PfSnEndTraceWorkerThreadRoutine+0 )
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0x39
FAILURE_BUCKET_ID:  X64_0x39_nt!PfSnEndTraceWorkerThreadRoutine+0
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Sat Jul 28 20:26:04.603 2012 (UTC - 4:00)
System Uptime: 0 days 2:14:46.101
Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  chrome.exe
FAILURE_BUCKET_ID:  X64_0xA_nt!KiPageFault+260
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
[/font]

 

[RacketLord]

Ok, i'll give that an update, and i'll run Memtest while I sleep tonight. I'll post back any results I may or may not get from that test.

 

[RacketLord]

Ok, time for an update. I'm posting this from another computer, because my computer now refuses to even start up. However, I was able to get some results from running Memtest before that happened.

After 6 hours and about 6 passes, I came back to find over 350,000 errors reported. Now, I just put in some new RAM yesterday, so it can't be the RAM going bad already, I don't think. Add that to the fact that my computer doesn't want to start up, could it perhaps be a bad motherboard? Could a failing hard drive cause these kinds of blue screens and stuff?

If anyone could provide some further assistance as soon as they can, i'd really appreciate it.

 

[Jonathan_King]

A failing hard drive could cause BSODs, but it can't account for the Memtest86 errors. Bear in mind RAM does sometimes ship faulty, so try taking out all but one stick and running Memtest86 again; repeat with all sticks, and if you see no errors, add two sticks, etc.

 

[RacketLord]

So, another update for ya. I took out one stick of ram (I have only two in total) and tested that one. No errors. I removed it and replaced it with the other stick. No errors. I placed both sticks back in the computer and ran another test for 6 and a half hours. No errors.

I haven't had a blue screen yet, but that's because I haven't played a game or stressed my system. I will attempt to make it blue screen later today, and post the dump file. But my question is this: why would memtest go haywire with error reports that one time, then not again after so many hours of testing? Surely if the RAM was bad, it would have reported errors during all that time, no?

Well, i'll report back as soon as I get another blue screen, and we'll see what the dump file has to say for itself.