Constant BSODs, mostly 0x50 really need help!

jmil23 · 25 Mar 2012

So I'm at my wits end here as I really have no idea what's wrong with my computer. I've been getting tons of bsods the past few days when playing games and sometimes within minutes of booting my computer. Sometimes it also takes a few restarts to boot properly.

Things I've done
-Updated the bios and drivers
-Driver sweeped and updated to the newest Nvidia drivers, 285.62, 275.33, and currently 266.58 to no avail
-Tried each ram slot individually (still bsoded)
-Reset all OC to default in the bios
-Ran chkdsk nothing found
-Ran antimalware/rootkit shit nothing found
-Driver verifier just kept insta crashing my computer because of my habu drivers so I turned it off
-Plugged computer directly into wall
-Took side off case and put a fan there

Setup:
Windows 7 Ultimate x64
Amd x4 960t (no unlocked cores)
Asus M4N68T M V2 (refurbished)
Galaxy 460GTX 768mb
2x2GB G SKILL DDR3 1333 (F3-10666CL9D)
CM 500W ATX12V v2.3 (RS500-PCARD3)

Any help would be greatly appreciated!!!!

usasma · 25 Mar 2012

SP1 isn't installed, please do the following:

Installing Windows 7 Service Pack 1
1. Visit the PC manufacturer's website and update ALL drivers. DO NOT use Windows Update or the "Update drivers" function of Device Manager.
2. Check Device Manager for any unknown/disabled devices - if there are unknown/disabled devices, fix them with the latest drivers from the device manufacturer's website (not the PC Manufacturer)
3. Visit Windows Update and get all updates (may take repeated visits)
4. Visit Windows Update and get Service Pack 1 (usually under Important Updates). Read these notes for installing SP1: Steps to follow before you install Windows 7 SP1 and Windows Server 2008 R2 SP1 from the Microsoft Download Center
5. Visit Windows Update and get any other available updates. May take repeated visits, but keep it up until you get several "Windows is updated" results.
If you're having difficulties with installing a Service Pack, please use the SURTool from this link: What is the System Update Readiness Tool?

If Driver Verifier blamed your Habu drivers, then they are most likely to blame (we have seen a lot of hardware problems from Razer devices recently). Visit the Razer support website and download/install fresh drivers: Razer Support
To test, remove the drivers and the device from your system - and see if that stops the BSOD's (without using Driver Verifier)

Just FYI - a recent poster (early Nov 2011) states that they were advised by Asus to manually set their memory settings/timings/voltages because of issues with the M4 series of motherboards.
You can get the settings/timings/voltages from the website of your RAM manufacturer.

Your ASACPI.sys driver dates from 2005. This is a know cause of BSOD's in Win7 systems. Please visit the Asus website for your motherboard and download/install the latest version of the ATK0110 ACPI Utility driver from there: ASUS - Motherboards- ASUS M4N68T-M V2 You'll need to install either the AISuite or the PCProbe utility as there is no separate download for this driver.

Your nvm62x64.sys driver dates from 2008, but doesn't appear in any of the memory dumps except for the first one on 24 Mar 2012 (I ran 9 after that). If you haven't updated your nVidia chipset drivers, then you should do that now. From the results of the other memory dumps it appears that you have updated them.

Further info on BSOD error messages available at: http://www.carrona.org/bsodindx.html

The following info is just FYI, I've already addressed the issues that I saw in the above paragraphs
3RD PARTY DRIVERS PRESENT IN THE DUMP FILES

Code:


nvstor.sys      Wed May 20 02:45:37 2009 (4A13A711)
nvstor64.sys    Fri Apr 09 05:22:41 2010 (4BBEF1E1)
amdxata.sys     Tue May 19 13:56:59 2009 (4A12F2EB)
SASKUTIL64.SYS  Tue Jul 12 17:00:01 2011 (4E1CB5D1)
SASDIFSV64.SYS  Thu Jul 21 19:03:00 2011 (4E28B024)
ASACPI.sys      Sun Mar 27 22:30:36 2005 (42476C4C)
nvmf6264.sys    Thu Mar 04 20:04:39 2010 (4B9058A7)
nvhda64v.sys    Tue May 10 05:41:18 2011 (4DC9083E)
habu.sys        Fri Aug 07 00:22:07 2009 (4A7BABEF)
cpuz135_x64.sys Wed Sep 21 04:23:41 2011 (4E799F0D)
nvlddmkm.sys    Fri Jan 07 21:07:22 2011 (4D27C6DA)
nvBridge.kmd    Fri Jan 07 20:57:22 2011 (4D27C482)
nvhda64v.sys    Tue Jan 17 07:45:46 2012 (4F156D7A)
nvlddmkm.sys    Wed Feb 29 13:04:52 2012 (4F4E68C4)
nvlddmkm.sys    Sat May 21 00:07:04 2011 (4DD73A68)
nvBridge.kmd    Fri May 20 23:58:23 2011 (4DD7385F)
nvm62x64.sys    Fri Oct 17 17:01:06 2008 (48F8FD12)

Code:


Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\032512-28501-01.dmp]
Built by: 7600.16917.amd64fre.win7_gdr.111118-2330
Debug session time: Sun Mar 25 16:09:14.143 2012 (UTC - 4:00)
System Uptime: 0 days 0:01:39.595
Probably caused by : memory_corruption ( nt!MiFindNodeOrParent+0 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  dllhost.exe
FAILURE_BUCKET_ID:  X64_0xA_nt!MiFindNodeOrParent+0
Bugcheck code 0000000A
Arguments 00000000`00000028 00000000`00000002 00000000`00000000 fffff800`02d19ed8
BiosVersion = 0901   
BiosReleaseDate = 07/05/2011
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\032512-29905-01.dmp]
Built by: 7600.16917.amd64fre.win7_gdr.111118-2330
Debug session time: Sun Mar 25 16:06:17.803 2012 (UTC - 4:00)
System Uptime: 0 days 0:02:06.629
Probably caused by : win32k.sys ( win32k!xxxFreeWindow+cbf )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  sdksetup.exe
FAILURE_BUCKET_ID:  X64_0x50_win32k!xxxFreeWindow+cbf
Bugcheck code 00000050
Arguments fffff100`c1dac9e0 00000000`00000000 fffff960`0014030f 00000000`00000007
BiosVersion = 0901   
BiosReleaseDate = 07/05/2011
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\032512-29218-01.dmp]
Built by: 7600.16917.amd64fre.win7_gdr.111118-2330
Debug session time: Sun Mar 25 15:55:03.501 2012 (UTC - 4:00)
System Uptime: 0 days 2:40:28.342
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+22 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x50_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+22
Bugcheck code 00000050
Arguments fffff0a0`08779590 00000000`00000000 fffff880`10b7ccee 00000000`00000007
BiosVersion = 0901   
BiosReleaseDate = 07/05/2011
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\032512-42447-01.dmp]
Built by: 7600.16917.amd64fre.win7_gdr.111118-2330
Debug session time: Sun Mar 25 09:26:59.551 2012 (UTC - 4:00)
System Uptime: 0 days 0:02:00.034
Probably caused by : ntkrnlmp.exe ( nt!ExAllocatePoolWithTag+51d )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0x50
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_0x50_VRF_nt!ExAllocatePoolWithTag+51d
Bugcheck code 00000050
Arguments fffff280`03981388 00000000`00000000 fffff800`02db88ed 00000000`00000007
BiosVersion = 0901   
BiosReleaseDate = 07/05/2011
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\032412-38204-01.dmp]
*** WARNING: Unable to verify timestamp for Unknown_Module_0022003d`00650070
*** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_0022003d`00650070
Built by: 7600.16917.amd64fre.win7_gdr.111118-2330
Debug session time: Sat Mar 24 21:20:41.989 2012 (UTC - 4:00)
System Uptime: 0 days 0:01:38.847
*** WARNING: Unable to verify timestamp for Unknown_Module_0022003d`00650070
*** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_0022003d`00650070
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
BUGCHECK_STR:  0xc4_f6
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
Bugcheck code 000000C4
Arguments 00000000`000000f6 c1c1c1c1`0000017c fffffa80`07581b30 fffff880`04a4cb01
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\032412-42619-01.dmp]
Built by: 7600.16917.amd64fre.win7_gdr.111118-2330
Debug session time: Sat Mar 24 21:18:07.586 2012 (UTC - 4:00)
System Uptime: 0 days 0:01:35.068
*** ERROR: Module load completed but symbols could not be loaded for habu.sys
Probably caused by : habu.sys ( habu+b01 )
DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
BUGCHECK_STR:  0xc4_f6
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  razerhid.exe
FAILURE_BUCKET_ID:  X64_0xc4_f6_VRF_habu+b01
Bugcheck code 000000C4
Arguments 00000000`000000f6 cfcfcfcf`00000178 fffffa80`074e0b30 fffff880`04bf6b01
BiosVersion = 0901   
BiosReleaseDate = 07/05/2011
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\032412-40263-01.dmp]
Built by: 7600.16917.amd64fre.win7_gdr.111118-2330
Debug session time: Sat Mar 24 20:59:19.837 2012 (UTC - 4:00)
System Uptime: 0 days 0:03:01.320
*** ERROR: Module load completed but symbols could not be loaded for habu.sys
Probably caused by : habu.sys ( habu+b01 )
DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
BUGCHECK_STR:  0xc4_f6
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  razerhid.exe
FAILURE_BUCKET_ID:  X64_0xc4_f6_VRF_habu+b01
Bugcheck code 000000C4
Arguments 00000000`000000f6 67676767`00000178 fffffa80`04e25230 fffff880`05071b01
BiosVersion = 0901   
BiosReleaseDate = 07/05/2011
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\032412-18766-01.dmp]
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sat Mar 24 19:03:06.999 2012 (UTC - 4:00)
System Uptime: 0 days 0:02:39.451
Probably caused by : ntkrnlmp.exe ( nt!ExAllocatePoolWithTag+51d )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_0x50_nt!ExAllocatePoolWithTag+51d
Bugcheck code 00000050
Arguments fffff280`03963648 00000000`00000000 fffff800`02dbd8ed 00000000`00000007
BiosVersion = 0901   
BiosReleaseDate = 07/05/2011
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\032412-20888-01.dmp]
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sat Mar 24 18:56:51.359 2012 (UTC - 4:00)
System Uptime: 0 days 0:20:58.811
Probably caused by : ntkrnlmp.exe ( nt!KiProcessExpiredTimerList+103 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  League of Lege
FAILURE_BUCKET_ID:  X64_0xA_nt!KiProcessExpiredTimerList+103
Bugcheck code 0000000A
Arguments fffff280`03d7c823 00000000`00000002 00000000`00000000 fffff800`02cd4363
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\032412-19156-01.dmp]
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sat Mar 24 12:16:08.089 2012 (UTC - 4:00)
System Uptime: 0 days 0:03:20.931
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+10b )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x50_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+10b
Bugcheck code 00000050
Arguments fffff0a0`01019820 00000000`00000000 fffff880`042aa05b 00000000`00000007
BiosVersion = 0901   
BiosReleaseDate = 07/05/2011
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

jmil23 · 02 Apr 2012

So I figured I'd update this in case anybody comes along this thread. I tried everything posted and was still getting bsods (it did help me narrow it down to psu/ram though). It got to the point where my computer just cycled between restarts/bsods. Since I was getting a wide variety of bsods and a few restarts w/ no bsod I figured my old psu might not be powering my rig well so I ordered a new one and lo and behold I haven't had a bsod in 3 days.