Random BSOD

[WolvenAncestor]

Hey guys,

I built my PC in early summer and have been having random BSODs ever since. Was running XP originally and noticed that since I've installed Windows 7 the BSODs have gotten worse. I updated my BIOS and that seems to have helped. I don't seem to be getting BSODs while my PC is idling anymore. The last few days I've noticed it's been happening while gaming. Playing certain games I will crash after playing about 5-10 minutes. Other games seem just fine. I've been browsing forums for months about this problem and haven't seemed to find any help. Any help would be appreciated.

 

[wallyinnc]

Hi W.A., welcome to the forums
Have you checked the temperatures for your CPU and Video card. Win7 is known to run a little hotter than its predecessors, it might be pushing you to BSODs if your cooling is not ideal.

 

[WolvenAncestor]

Thank you for the response.

I haven't thought about monitoring the temperature of my CPU and GPU. I just installed SpeedFan (although am not quite sure how good it is, I used it on my old PC). As Windows 7 is idling everything appears okay or cool. I'll fire up a few games over the next few hours and report back with what I find.

 

[WolvenAncestor]

Just tried running L4D2. The game crashed after about the same amount of time as it has been lately before the BSOD (which is about 5 minutes). The temperature of my GPU was around 62/63 degrees. From looking up information on my card those temps shouldn't be a problem at all. Going to research some possible BIOS settings for the card to see if that may remedy the situation. If anyone else has any ideas I'm all ears.

 

[usasma]

A very interesting set of dump files (to include STOP 0x24 and 0x23) - along with a STOP 0x124
Gonna take a bit of time to make new files to run all 50 dump files - please be patient....

 

[usasma]

Gut feeling is that there's a hardware issue here - video, network, hard drive, file system, antivirus, usb errors, with a smattering of Windows drivers thrown in just to confuse things.

I would start by updating this driver - as the 2005 version is known to cause issues in Win7: ASACPI.sys Sun Mar 27 22:30:36 2005 This is the Asus ATK0110 ACPI Utility and is available from the Asus Support website.

Just FYI - there have been a lot of memory issues noticed with Asus P5 series of motherboards and Windows 7. So I'd suggest checking with both the Asus and the OCZ folks to ensure that the settings for your RAM are correct.

Once you've addressed the previous 2 issues, monitor for further BSOD's. If you get one, upload it here and follow the directions in the next paragraph (if you don't get another BSOD, then don't follow it).

Try running Driver Verifier according to the following directions (I don't expect it to give us significant data, but we have to look):

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out.

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.
If that doesn't work, post back and we'll have to see about fixing the registry entry off-line.

More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users

After this we'll run Driver Verifier again (to verify ALL drivers), then I'll suggest reinstalling Windows with a clean install and no additions to see if that fixes things. And, after all that, if it's still not fixed, then we can assume that there's a hardware issue - and start tracking that down.

Summary of the BSOD's:

BugCheck 1E, {0, 0, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
BugCheck 1000007E, {ffffffffc0000005, fffff880019baad3, fffff88002fd2688, fffff88002fd1ee0}
Probably caused by : aswTdi.SYS ( aswTdi+5ad3 )
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
BugCheck D1, {fffffa7f90e7067b, 2, 1, fffff88003c48527}
Probably caused by : usbuhci.sys ( usbuhci!UhciGetEndpointStatus+17 )
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
BugCheck 1000007E, {ffffffffc0000005, fffff8800141453a, fffff88002dd2918, fffff88002dd2170}
Probably caused by : NETIO.SYS ( NETIO!FreeSomeCacheBucketEntries+4a )
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
BugCheck 50, {fffffab8150ace00, 1, fffff800028966f5, 5}
Probably caused by : ntkrnlmp.exe ( nt!PoIdle+1f5 )
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
BugCheck D1, {6500000078, 2, 0, fffff88002d0db4e}
Probably caused by : afd.sys ( afd!AfdEnqueueTpSendIrp+4e )
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
BugCheck 3B, {c0000005, fffff8000287a4dc, fffff880091fb800, 0}
Probably caused by : ntkrnlmp.exe ( nt!KeWaitForMultipleObjects+202 )
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
BugCheck 1E, {0, 0, 0, 0}
Probably caused by : Rt64win7.sys ( Rt64win7+148d5 )
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
BugCheck 3B, {c0000005, fffff880014f7b40, fffff88007ca0550, 0}
Probably caused by : NETIO.SYS ( NETIO!memcmp+50 )
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
BugCheck 3B, {c0000005, fffff88001083280, fffff88009c4af10, 0}
Probably caused by : fltmgr.sys ( fltmgr!FltpPurgeVolumeNameCache+50 )
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
BugCheck 1000007E, {ffffffffc0000005, fffff880014a1aee, fffff88002ff4f58, fffff88002ff47b0}
Probably caused by : pacer.sys ( pacer!PcFilterSendNetBufferLists+29 )
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
BugCheck A, {fffffa000506e350, 2, 1, fffff800028a786e}
Probably caused by : CLFS.SYS ( CLFS!CClfsLogCcb::`scalar deleting destructor'+cd )
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
BugCheck 124, {0, fffffa8004c5d038, 0, 0}
Probably caused by : hardware
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
BugCheck D1, {1, 2, 1, fffff88002abb15c}
Probably caused by : LV302V64.SYS ( LV302V64+22299 )
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
BugCheck 23, {e0107, fffff880039d9b38, fffff880039d9390, fffff8000288cc60}
Probably caused by : fvevol.sys ( fvevol!FveFilterDeviceControl+57b )
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
BugCheck D1, {2, b, 1, fffff88005393f9a}
Probably caused by : hardware ( Rt64win7+32f9a )
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
BugCheck 34, {50830, fffff88002faf398, fffff88002faebf0, fffff80002896c60}
Probably caused by : ntkrnlmp.exe ( nt!IofCallDriver+50 )
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
BugCheck 7F, {8, 80050031, 6f8, fffff80002b93c96}
Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
BugCheck 3B, {c0000005, fffff96000093b20, fffff88009ad41e0, 0}
Probably caused by : win32k.sys ( win32k!MapDesktopObject+20 )
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
BugCheck 50, {ffffdd03c80da340, 1, fffff96000128fb7, 7}
Probably caused by : win32k.sys ( win32k!GreGetDeviceCaps+247 )
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
BugCheck 1000007E, {ffffffffc0000005, fffff800028f4b7c, fffff88002fd8ee8, fffff88002fd8740}
Probably caused by : cng.sys ( cng!GatherRandomKey+22c )
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
BugCheck 1E, {0, 0, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
BugCheck 3B, {c0000005, fffff88003c1b507, fffff88009d2dc30, 0}
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+17f )
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
BugCheck 3B, {c000001d, fffff8000305018d, fffff880093bd0b0, 0}
Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceHandler+7c )
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
BugCheck 3B, {c0000005, fffff80002a55a22, fffff88009983ff0, 0}
Probably caused by : ntkrnlmp.exe ( nt!ExpCheckForIoPriorityBoost+e2 )
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
BugCheck 3B, {c0000005, fffff80002a88baf, fffff88007f54830, 0}
Probably caused by : ntkrnlmp.exe ( nt!IoIs32bitProcess+1f )
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
BugCheck 1E, {ffffffffc0000005, fffff88002f19db0, 0, 0}
Probably caused by : Rt64win7.sys ( Rt64win7+157c1 )
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
BugCheck 3B, {c0000005, fffff80002a5f80b, fffff880086ebec0, 0}
Probably caused by : memory_corruption ( nt!MmLocateSubsectionNode+23 )
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
BugCheck 1000007E, {ffffffffc0000005, fffff8800192cba9, fffff88002fd9898, fffff88002fd90f0}
Probably caused by : hardware ( cdrom!RequestSetupMcnRequest+215 )
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
BugCheck A, {fffff6ffffff8000, 0, 0, fffff80002a98c9e}
Probably caused by : memory_corruption ( nt!MiDispatchFault+de )
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
BugCheck D1, {fffff800100c6710, 5, 8, fffff800100c6710}
Probably caused by : nvlddmkm.sys ( nvlddmkm+181a24 )
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
BugCheck 1E, {0, 0, 0, 0}
Probably caused by : nvlddmkm.sys ( nvlddmkm+184dde )
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
BugCheck 19, {3, fffffa800403e4c0, fffffa800403e4c0, fffa800403e4c0}
Probably caused by : Pool_Corruption ( nt!ExFreePool+780 )
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
BugCheck 1E, {ffffffffc0000005, fffff80002d704ef, 0, ffffffffffffffff}
Probably caused by : win32k.sys ( win32k!NtUserSetInformationThread+f4 )
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
BugCheck A, {fffff6fc00050980, 2, 0, fffff80002a527b3}
Probably caused by : memory_corruption ( nt!MiTryLockProtoPoolPageAtDpc+23 )
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
BugCheck 1E, {ffffffffc0000005, fffff880077b8950, 0, 0}
Probably caused by : rdyboost.sys ( rdyboost!SmdProcessReadWrite+c8d )
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
BugCheck 1A, {41287, 17d9, 0, 0}
Probably caused by : hardware ( nt! ?? ::FNODOBFM::`string'+42c75 )
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
BugCheck 3B, {c0000005, fffff80002bbf5cc, fffff88006013de0, 0}
Probably caused by : memory_corruption ( nt!MmFreePagesFromMdl+bc )
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
BugCheck 1E, {0, 0, 0, 0}
Probably caused by : Rt64win7.sys ( Rt64win7+1561d )
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
BugCheck 3B, {c0000005, fffff960000b1d03, fffff8800809df50, 0}
Probably caused by : win32k.sys ( win32k!GreExtTextOutWInternal+10f )
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
BugCheck 24, {1904fb, fffff88002fbcfa0, fffff88002fbd040, fffff80002b037f8}
Probably caused by : Ntfs.sys ( Ntfs! ?? ::FNODOBFM::`string'+2dab )
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
BugCheck 3B, {c0000005, fffff960001376f9, fffff880080aa170, 0}
Probably caused by : win32k.sys ( win32k!SearchIconCache+39 )
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
BugCheck 24, {1904fb, fffff8800698ad38, fffff8800698a590, fffff80002ad44ec}
Probably caused by : Ntfs.sys ( Ntfs! ?? ::FNODOBFM::`string'+2cc9 )
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
BugCheck 1E, {0, 0, 0, 0}
Probably caused by : USBPORT.SYS ( USBPORT!USBPORT_Core_iIrpCsqCompleteDoneTransfer+1c8 )
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
BugCheck 50, {ffffffffe4854d27, 1, fffff8800ff0e99f, 2}
Probably caused by : nvlddmkm.sys ( nvlddmkm+dc99f )
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
BugCheck 1000007E, {ffffffffc0000005, fffff88003c20cee, fffff88002e686a8, fffff88002e67f00}
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+22 )
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
BugCheck 1E, {ffffffffc0000005, fffff880096571d0, 0, 0}
Probably caused by : Rt64win7.sys ( Rt64win7+11939 )
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
BugCheck 3B, {c0000005, fffff96000093b20, fffff88009ad41e0, 0}
Probably caused by : win32k.sys ( win32k!MapDesktopObject+20 )
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
BugCheck 3B, {c000001d, fffff88001938721, fffff88008a2bee0, 0}
Probably caused by : hardware ( Npfs!NpWriteDataQueue+251 )

 

[WolvenAncestor]

Okay so I tried a bit of everything mentioned here. Nothing seemed to work. So I opened up my case and disconnected some things and looked around. As embarrassing as this is it seems as though it was my own fault. The power cable I plugged into my GPU wasn't meant for the PCI-E slot. So I changed that around and haven't seemed to have a BSOD since. If it does come back I'll definitely respond to this post though. Thank you for the help everyone!

 

[zigzag3143]

Okay so I tried a bit of everything mentioned here. Nothing seemed to work. So I opened up my case and disconnected some things and looked around. As embarrassing as this is it seems as though it was my own fault. The power cable I plugged into my GPU wasn't meant for the PCI-E slot. So I changed that around and haven't seemed to have a BSOD since. If it does come back I'll definitely respond to this post though. Thank you for the help everyone!

WA

the crux of the matter is usually the user finds and fixes it. We al have had our Doh, moments. My first problem was so much more my fault and I wa hounded for days. If you are fixed thats all that matters.

Ken