Blue Screen Of Death (STOP error)

jamsworld · 31 Jul 2011

Hey,Thought I'd come here to get help with my crash.
I have Home Premium x64 (came with my MESH PC) with dual booted XP (I dont use it though) And recently i have been getting Blue screens. Lots Of blue screns. Especially a minute or two after games. Can anyone help me out?

Its an OEM Windows, The PC itself is around a year and a half old (but it has been upgraded (well, my graphics card)) and i havent changed the windows 7 installation. I do have a copy ofwindows 7 professional if it would help?

Thanks in advance :)

usasma · 31 Jul 2011

Your IDE Controller and CPUZ both have problems in the perfmon report
Please uninstall CPUZ and download/install chipset drivers for your motherboard (to fix the IDE controller issue)

For the Chipset driver:
- go to this link: http://support.asus.com/download/dow...odel=M4A785T-M
- select your OS
- download/install the driver listed under the Chipset section.

MSINFO32 lists a lot of Video errors (STOP 0x117 predominantly).
Please follow the steps in this link to troubleshoot it (STOP 0x116 and 0x117 are very similar, so troubleshooting is the same): STOP 0x116: VIDEO_TDR_ERROR troubleshooting

Alcohol 120% contains a driver (sptd.sys) that causes many BSOD's in Windows 7 (FYI - Daemon Tools uses the same driver). Please uninstall the program, then use this free tool to ensure that the offending sptd.sys driver has been removed: DuplexSecure - FAQ - Remove 64 bit sptd.sys

Your chipset drivers (in particular AsIO.sys) and your networking drivers are very old (from 2007) and should be updated. One of the BSOD's refers to networking also.

Finally, here's a list of drivers present in the memory dump that should be updated:
OLDER DRIVERS PRESENT IN THE DUMP FILES
- Create a System Restore Point prior to doing any of this. DO NOT mess with the drivers themselves - leave the Windows\System32\drivers directory alone unless we specifically direct you to it!
- Please update these drivers from the device manufacturer's website - or uninstall them from your system. Reference links are included below.
- DO NOT use Windows Update or the Update Drivers function of Device Manager.
- Please feel free to post back about any drivers that you are having difficulty locating.
- Windows Update exceptions may be noted below for Windows drivers:

Code:


amdxata.sys            Fri Mar 19 12:18:18 2010 (4BA3A3CA)
sptd.sys               Sun Oct 11 16:55:14 2009 (4AD24632)
AtiPcie.sys            Tue May 05 11:00:22 2009 (4A005486)
AsIO.sys               Mon Dec 17 04:11:49 2007 (47663D55)
Rt64win7.sys           Mon Mar 21 09:20:32 2011 (4D8750A0)
GEARAspiWDM.sys        Mon May 18 08:17:04 2009 (4A1151C0)
ASACPI.sys             Wed May 13 21:25:17 2009 (4A0B72FD)
mcdbus.sys             Tue Feb 24 05:34:07 2009 (49A3CD1F)
amdiox64.sys           Thu Feb 18 10:17:53 2010 (4B7D5A21)
viahduaa.sys           Thu Jul 09 23:07:01 2009 (4A56B055)
netr7364.sys           Sun Sep 23 23:08:50 2007 (46F72A42)
LUsbFilt.Sys           Wed Jun 17 12:49:46 2009 (4A391EAA)
LHidFilt.Sys           Wed Jun 17 12:49:39 2009 (4A391EA3)
LMouFilt.Sys           Wed Jun 17 12:49:43 2009 (4A391EA7)
S3DInjectionDriver.sys Fri Apr 24 15:37:38 2009 (49F21502) - likely from here: http://www.iz3d.com/
RimSerial_AMD64.sys    Mon Nov 24 12:01:01 2008 (492ADDCD)
AtihdW76.sys           Wed Nov 17 07:02:04 2010 (4CE3C43C)
cpuz132_x64.sys        Thu Mar 26 19:17:23 2009 (49CC0D03)
cpuz135_x64.sys        Tue Nov 09 08:33:36 2010 (4CD94DB0)
aswSnx.SYS             Mon Jul 04 07:36:55 2011 (4E11A5D7)
atikmdag.sys           Tue Apr 19 21:53:29 2011 (4DAE3C99)
vcsvad.sys             Sun Nov 16 04:51:18 2008 (491FED16)
aswRdr.SYS             Tue May 10 07:59:58 2011 (4DC928BE)
atikmdag.sys           Wed Jan 26 17:48:28 2011 (4D40A4BC)
Rt64win7.sys           Wed Jun 23 05:10:45 2010 (4C21CF95)
aswSnx.SYS             Tue May 10 08:04:06 2011 (4DC929B6)

BSOD BUGCHECK SUMMARY

Code:


Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\073111-33477-01.dmp]
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Sun Jul 31 12:32:50.483 2011 (UTC - 4:00)
System Uptime: 0 days 6:12:29.997
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4987d )
BUGCHECK_STR:  0x1E_c0000005
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  iexplore.exe
FAILURE_BUCKET_ID:  X64_0x1E_c0000005_nt!_??_::FNODOBFM::_string_+4987d
Bugcheck code 0000001E
Arguments ffffffff`c0000005 fffff800`03098bac 00000000`00000000 ffffffff`ffffffff
BiosVersion = 0402   
BiosReleaseDate = 08/24/2009
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\073111-30014-01.dmp]
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Sat Jul 30 17:06:17.757 2011 (UTC - 4:00)
System Uptime: 0 days 7:36:15.271
*** WARNING: Unable to verify timestamp for atikmpag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
Probably caused by : atikmpag.sys ( atikmpag+79c8 )
DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT
BUGCHECK_STR:  0x116
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys
Bugcheck code 00000116
Arguments fffffa80`0d93c180 fffff880`040ee9c8 00000000`00000000 00000000`00000002
BiosVersion = 0402   
BiosReleaseDate = 08/24/2009
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\072911-31387-01.dmp]
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Fri Jul 29 07:13:18.889 2011 (UTC - 4:00)
System Uptime: 0 days 0:19:57.403
*** WARNING: Unable to verify timestamp for netr7364.sys
*** ERROR: Module load completed but symbols could not be loaded for netr7364.sys
Probably caused by : netr7364.sys ( netr7364+2e212 )
BUGCHECK_STR:  0xC5_2
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xC5_2_netr7364+2e212
Bugcheck code 000000C5
Arguments fffffa00`0326c3c0 00000000`00000002 00000000`00000001 fffff800`03210677
BiosVersion = 0402   
BiosReleaseDate = 08/24/2009
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\072811-37705-01.dmp]
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Thu Jul 28 07:01:59.262 2011 (UTC - 4:00)
System Uptime: 0 days 0:13:15.776
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_4_PROC
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  explorer.exe
FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE
Bugcheck code 00000101
Arguments 00000000`00000031 00000000`00000000 fffff880`02fd5180 00000000`00000003
BiosVersion = 0402   
BiosReleaseDate = 08/24/2009
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\061511-29187-01.dmp]
Built by: 7600.16792.amd64fre.win7_gdr.110408-1633
Debug session time: Wed Jun 15 11:21:15.727 2011 (UTC - 4:00)
System Uptime: 0 days 0:28:01.038
Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceExit+2f )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  csrss.exe
FAILURE_BUCKET_ID:  X64_0x50_nt!KiSystemServiceExit+2f
Bugcheck code 00000050
Arguments ffffba00`099a2250 00000000`00000000 fffff800`02ed698a 00000000`00000007
BiosVersion = 0402   
BiosReleaseDate = 08/24/2009
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\060311-20654-01.dmp]
Built by: 7600.16792.amd64fre.win7_gdr.110408-1633
Debug session time: Fri Jun  3 07:29:17.909 2011 (UTC - 4:00)
System Uptime: 0 days 0:21:55.595
Probably caused by : ntkrnlmp.exe ( nt!KiCommitThreadWait+185 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  AvastSvc.exe
FAILURE_BUCKET_ID:  X64_0xA_nt!KiCommitThreadWait+185
Bugcheck code 0000000A
Arguments fffffa80`02fd5190 00000000`00000002 00000000`00000001 fffff800`02e7c945
BiosVersion = 0402   
BiosReleaseDate = 08/24/2009
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

jamsworld · 02 Aug 2011

First of all: Thank you. I downloaded pretty much all of the drivers, rebooted my system, and had a good long session of mass effect. No crashes.Great performance.

But it didn't last long. I then decided "why not update the bios?". It worked fine. But now when i turn my PC on it loads the bios splash screen, and then an AMI (american Megatrends) screen comes up saying :
Chassis intruded!
or
Power supply surges detected during the previous power on
ASUS Anti-surge was triggered to protect system from unstable power supply unit
Fatal Error... System halted.

I cannot get to windows ( except for one odd occasion) and chassis doesn't look intruded. I do have a cheap power supply, but there weren't any previous power problems. I can enter the bios, but i'm not sure what to change. Any help?

Other helpful info:
I followed parts of the tutorial you sent (The STOP ox116) and changed some RAM options ( i think)
I have backups from before i downloaded any drivers and after
I used a program called device doctor to check any drivers i hadn't got to, and accidentally installed a slightly out of date video driver for my 5770, but i ran mass effect fine.

Again, thank you for the previous post, and thank you for the next post (if there is one?)

usasma · 02 Aug 2011

I'm not familiar with your BIOS, but it's evident that there's an intrusion detection thing built into it.
I'd check the mobo owner's manual for any mention of intrusion detection - then disable it if necessary.

As for the PSU instability - you can probably turn that off in the BIOS also. But I'd have to wonder if that's such a good idea? PSU's don't always just stop working - they often give out surges before they die. You may be able to disable it temporarily, but a new, quality PSU is your best solution here. I'd suggest you check the mobo owner's manual for assistance with this function.

As for the changed settings, there's a setting in your BIOS to load Default/Optimized/FailSafe values. If you load them, and then save them when exiting - you've set the system back to it's intended values.

I'm not familiar with Device Doctor and prefer not to use any programs to update drivers (they're only as good as the people who update the dates in their databases - and that's a real difficult job!) What we'll do is to wait for the next BSOD and see what it tells us.

Good luck!

jamsworld · 02 Aug 2011

I am 100% sure that the PSU wont die - its only a month old and it has been acting fine.
Sadly i cannot seem to find anything in the manual to do with this. The bios had an option to turn off Asus power surge protection, but alas, nothing. I have set the BIOS to a certain value ( there was only one option about this) but all it changes is the power surge thing back on, which doesn't make any difference.
In future i am planning to get a 650w 80+ psu, but right now i cant afford it.
should i attempt to get onto windows (i may have found a temporary way) and change the load a system restore point?
This experience has taught me to only fix what is broken

Thanks yet again.

usasma · 02 Aug 2011

What's the make and model (and country of purchase) of your system.
If you have a link to the user's manual I'll have a look at it.

jamsworld · 03 Aug 2011

M4A785T-M Asus Motherboard
8gb RAM
ATI 5770 1gb
phenom II x4 955 3.20 ghz

the PC was built by MESH (but the ATI 5770 was an upgrade from me)
I have read everything.
Why did i flash my BIOS

IF it helps i can get into windows 7, but i cant downgrade the BIOS because of an EEPROM error in ASUS upgrade utility.
I also tried EZflash from within the bios and there was an error to that effect.
And i looked for jumpers, but only one called CRAM? was found.

Yet again, thanks.:)

usasma · 03 Aug 2011

Everything that I can find out about this mobo say select "disable" for the anti-surge in the BIOS and it should work.
If yours isn't working that way, and you have issues with trying to reflash the BIOS - then I'd have to suspect a problem with your mobo.

If you can get into Win7, how do you do it? Are you able to function normally in Windows? If so, keep using the system and see what happens.

jamsworld · 03 Aug 2011

To get into windows 7 i have to go into the bios and then press exit and save changes. Usually it works...
I can run everything fine, but i daren't play on my precious save games

but otherwise it all works (one USB stick wasn't recognised, but i seem to have fixed that)
I read up on the EEPROM error, and it is a problem purely for Asus motherboards, and it gives me the ability to upgrade my BIOS even further, but i am not sure if that is a good idea. HOWEVER the Asus update utility gives me the option to save my current BIOS, so all would not be lost.(Unless it doesn't let me downgrade to THAT)
But yeah.
Any ideas how to downgrade? Or should I update it further? Are the features in the new BIOS worth keeping?
Also i have disabled Anti-surge, but that doesn't give me the option to skip the warning any more

But yeah.
Again, thanks (I say that ALOT)

usasma · 03 Aug 2011

Have you tried downloading the older version of the BIOS and installing that?
Always save before updating - you never know if you're gonna need it (and the files aren't very large).