Windows 8 BSOD in Black Osp 2

Micha

New Member
Welcome. In the beginning sorry for my spelling. bsod shows me while playing coda. on win 7 also I thought I had a similar problem with wine 8 rozwiarze But none of that .. graphics card drivers also ive loaded later errors. 19.11 2 times today I had bsod but not written into the folder I do not know why. I greet
 

Attachments

  • W7F_19-11-2012.rar
    573.2 KB · Views: 343
Sorry for not replying sooner - have been very busy getting ready for the holidays!

There are problems with this device:
GT-I9100 USB\VID_04E8&PID_6860&MS_COMP_MTP&SAMSUNG_ANDROID\6&11B631E3&0&0000 This device cannot start.
It looks like a Samsung Android Phone to me - please un-install it from your system. Also, if there is software associated with it (such as Samsung KIES) please uninstall that also.

Daemon Tools (and Alcohol % software) are known to cause BSOD's on some Win7 systems (mostly due to the sptd.sys driver, although I have seen dtsoftbus01.sys blamed on several occasions). I suspect this is also the case with Win8 systems.
Please un-install the program, then use the following free tool to ensure that the troublesome sptd.sys driver is removed from your system (pick the 32 or 64 bit system depending on your system's configuration): [DEL] DuplexSecure - FAQ [/DEL] Link broken as of 21 Jul 2012
New link (15 Aug 2012): DuplexSecure - Downloads (pick the appropriate version for your system and select "Un-install" when you run it).
Alternate link: Disc-Tools.com
Manual procedure here: Registry and SPTD problems | DAEMON Pro Help

The ASACPI.sys driver dates from 2005 and is known to cause BSOD's in Win7 systems. Again, we suspect the same in Windows 8. Please update this to the latest version available from Asus (it's the 2009 version).

ASACPI.sys Sun Mar 27 22:30:36 2005 (42476C4C)
Asus ATK0110 ACPI Utility (a known BSOD maker in Win7). Also a part of the Asus PCProbe and AISuite Utilities
http://www.carrona.org/drivers/driver.php?id=ASACPI.sys

Please also update your Audio drivers - they date from 2009.

Troubleshoot video issues with this post: Video TDR Timeout - 0x116 + 0x117

Analysis:
The following is for informational purposes only.
Code:
[font=lucida console]**************************Sat Nov 17 06:17:26.211 2012 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\111712-41293-01.dmp]
Windows 8 Kernel Version 9200 MP (4 procs) Free x64
Built by: [B]9200[/B].16424.amd64fre.win8_gdr.120926-1855
System Uptime:[B]1 days 12:19:10.330[/B]
BugCheck Code: [B]BugCheck 9F, {3, fffffa8008800060, fffff802c9d188e0, fffffa8006ecde10}[/B]
*** ERROR: Module load completed but symbols could not be loaded for partmgr.sys
*** WARNING: Unable to verify timestamp for atapi.sys
*** ERROR: Module load completed but symbols could not be loaded for atapi.sys
Probably caused by :[B]atapi.sys[/B]
BugCheck Info: [B]DRIVER_POWER_STATE_FAILURE (9f)[/B]
Arguments: 
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: fffffa8008800060, Physical Device Object of the stack
Arg3: fffff802c9d188e0, nt!TRIAGE_9F_POWER on Win7, otherwise the Functional Device Object of the stack
Arg4: fffffa8006ecde10, The blocked IRP
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
BUGCHECK_STR:  0x9F
PROCESS_NAME: [B]System[/B]
FAILURE_BUCKET_ID: [B]0x9F_3_IMAGE_atapi.sys[/B]
CPUID:        "Intel(R) Core(TM)2 Quad CPU    Q8300  @ 2.50GHz"
MaxSpeed:     2500
CurrentSpeed: [B]2500[/B]
  BIOS Version                  2001   
  BIOS Release Date             02/25/2009
  Manufacturer                  System manufacturer
  Product Name                  System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Tue Nov 13 07:41:39.166 2012 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\111512-29749-01.dmp]
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\111412-68000-01.dmp]
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\111312-26878-01.dmp]
Windows 8 Kernel Version 9200 MP (4 procs) Free x64
Built by: [B]9200[/B].16424.amd64fre.win8_gdr.120926-1855
System Uptime:[B]0 days 14:11:57.602[/B]
BugCheck Code: [B]BugCheck 3B, {c0000005, fffff8027f018241, fffff8800ce44480, 0}[/B]
Probably caused by :[B]memory_corruption[/B]
BugCheck Info: [B]SYSTEM_SERVICE_EXCEPTION (3b)[/B]
Arguments: 
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff8027f018241, Address of the instruction which caused the bugcheck
Arg3: fffff8800ce44480, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
BUGCHECK_STR:  0x3B
PROCESS_NAME: [B]Steam.exe[/B]
FAILURE_BUCKET_ID: [B]MEMORY_CORRUPTION_STRIDE[/B]
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Nov 12 17:28:59.566 2012 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\111212-31403-01.dmp]
Windows 8 Kernel Version 9200 MP (4 procs) Free x64
Built by: [B]9200[/B].16424.amd64fre.win8_gdr.120926-1855
System Uptime:[B]0 days 23:45:22.874[/B]
BugCheck Code: [B]BugCheck 116, {fffffa8008f56010, fffff8800758da88, ffffffffc00000b5, a}[/B]
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by :[B]nvlddmkm.sys ( nvlddmkm+14ba88 )[/B]
BugCheck Info: [B]VIDEO_TDR_FAILURE (116)[/B]
Arguments: 
Arg1: fffffa8008f56010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8800758da88, The pointer into responsible device driver module (e.g. owner tag).
Arg3: ffffffffc00000b5, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 000000000000000a, Optional internal context dependent data.
DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT
BUGCHECK_STR:  0x116
PROCESS_NAME: [B]System[/B]
FAILURE_BUCKET_ID: [B]0x116_IMAGE_nvlddmkm.sys[/B]
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
[/font]

3rd Party Drivers:
The following is for information purposes only.
Any drivers in red should be updated or removed from your system. And should have been discussed in the body of my post.
Code:
[font=lucida console]**************************Sat Nov 17 06:17:26.211 2012 (UTC - 5:00)**************************
[COLOR=RED][B]ASACPI.sys             Sun Mar 27 22:30:36 2005 (42476C4C)[/B][/COLOR]
[COLOR=RED][B]ADIHdAud.sys           Thu May 21 04:21:06 2009 (4A150EF2)[/B][/COLOR]
[COLOR=RED][B]a4bwcvqo.SYS           Tue Dec 27 17:30:45 2011 (4EFA4715)[/B][/COLOR]
[COLOR=RED][B]dtsoftbus01.sys        Fri Jan 13 08:45:46 2012 (4F10358A)[/B][/COLOR]
nvhda64v.sys           Tue Jul  3 11:25:04 2012 (4FF30ED0)
intelppm.sys           Wed Jul 25 22:26:48 2012 (5010AAE8)
[COLOR=RED][B]sptd.sys               Sat Aug 18 17:05:38 2012 (503003A2)[/B][/COLOR]
yk63x64.sys            Tue Sep 25 13:20:12 2012 (5061E7CC)
nvlddmkm.sys           Fri Nov  9 05:17:51 2012 (509CD84F)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Tue Nov 13 07:41:39.166 2012 (UTC - 5:00)**************************
[COLOR=RED][B]ak6u1uev.SYS           Tue Dec 27 17:30:45 2011 (4EFA4715)[/B][/COLOR]
ssudbus.sys            Thu Aug 30 21:34:04 2012 (5040148C)
ssudmdm.sys            Thu Aug 30 21:34:34 2012 (504014AA)
nvlddmkm.sys           Tue Oct  2 14:21:13 2012 (506B3099)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Nov 12 17:28:59.566 2012 (UTC - 5:00)**************************
[COLOR=RED][B]a5368rdo.SYS           Tue Dec 27 17:30:45 2011 (4EFA4715)[/B][/COLOR]
[/font]
http://www.carrona.org/drivers/driver.php?id=ASACPI.sys
http://www.carrona.org/drivers/driver.php?id=ADIHdAud.sys
a4bwcvqo.SYS - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
http://www.carrona.org/drivers/driver.php?id=dtsoftbus01.sys
http://www.carrona.org/drivers/driver.php?id=nvhda64v.sys
http://www.carrona.org/drivers/driver.php?id=intelppm.sys
http://www.carrona.org/drivers/driver.php?id=sptd.sys
yk63x64.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
ak6u1uev.SYS - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
http://www.carrona.org/drivers/driver.php?id=ssudbus.sys
http://www.carrona.org/drivers/driver.php?id=ssudmdm.sys
http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
a5368rdo.SYS - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
 
Last edited by a moderator:
thank you for describing the problem but I have acpi next bsod and can not be installed even alsuite and probe. join the next BSOD even though I do not know what to do. during the day I got 3 bsod including 1 dump with the rest of August is not enrolled.View attachment 111212-31403-01.dmp
 
You must do ALL of the following things to ensure that we've taken the proper steps for fixing this problem.

1) Daemon Tools must be uninstalled and then the offending sptd.sys driver must be removed using the special tool that I linked to:
Daemon Tools (and Alcohol % software) are known to cause BSOD's on some Win7 systems (mostly due to the sptd.sys driver, although I have seen dtsoftbus01.sys blamed on several occasions).
Please un-install the program, then use the following free tool to ensure that the troublesome sptd.sys driver is removed from your system (pick the 32 or 64 bit system depending on your system's configuration): [DEL] DuplexSecure - FAQ [/DEL] Link broken as of 21 Jul 2012
New link (15 Aug 2012): DuplexSecure - Downloads (pick the appropriate version for your system and select "Un-install" when you run it).
Alternate link: Disc-Tools.com
Manual procedure here: Registry and SPTD problems | DAEMON Pro Help

2) It appears that you have an Asus P5Q Premium motherboard. As such you must adjust the memory timings/settings/voltages in the BIOS. You must get this information from the RAM manufacturer (I think it is Kingston) and then manually input it into the BIOS. In other words - DO NOT use the Auto setting in the BIOS for memory, it often has problems. FYI - I have not seen problems with this recently, so you can feel free to leave this step until last.

3) Go to this page on the Asus website: ASUSTeK Computer Inc. -Support- Drivers and Download P5Q Premium
Select the + sign next to the Utilities section
Select the first item in the Utilities section - it is named "ATK0110 driver for WindowsXP/Vista/Win7 32&64-bit"
Download and extract the file (it will be named "MB_WIN7_ATK.ZIP")
Before running it, right click on the AsAcpiIns.exe file in the directory named "64", select "Properties", then select the "Compatibility" tab. Then set the program to run in Compatibility Mode for Windows 7 or Windows 7 SP1.
Finally, install it by double clicking on the AsAcpiIns.exe file in the directory named "64"

4) Conduct the troubleshooting steps at this link to help rule out problems with the video: Video TDR Timeout - 0x116 + 0x117
The steps are (basically):
- uninstall all nVidia software/drivers from the system
- download and install the latest drivers from nVidia

- ensure that the video card (and the system) are not overclocked while testing.
- ensure that the video card is getting adequate air flow
- ensure that the video card's fan is working (if so equipped)
- ensure that the video card's cooler is free of dirt/dust/hairballs
- ensure that the video card is getting power (reseat the power connector if so equipped)

Run the free diagnostics from here (particularly the video tests): Hardware Diagnostics
And, try another video card to see if that fixes the problem.

5) Update your audio drivers, they date from 2009. I don't think that this is related to the BSOD issues, but updating the drivers is a good idea.
*************************************************
Again, this memory dump blames the video driver. While it's possible that it's only the driver that's causing the problem - we have seen many other BSOD issues with the other things that I have mentioned. So, IMO it's possible that one or more of these things is causing problems with the video driver - that's why I suggest fixing them all.

Good luck!

Analysis:
The following is for informational purposes only.
Code:
[font=lucida console]**************************Mon Nov 12 17:28:59.566 2012 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\111212-31403-01.dmp]
Windows 8 Kernel Version 9200 MP (4 procs) Free x64
Built by: [B]9200[/B].16424.amd64fre.win8_gdr.120926-1855
System Uptime:[B]0 days 23:45:22.874[/B]
BugCheck Code: [B]BugCheck 116, {fffffa8008f56010, fffff8800758da88, ffffffffc00000b5, a}[/B]
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by :[B]nvlddmkm.sys ( nvlddmkm+14ba88 )[/B]
BugCheck Info: [B]VIDEO_TDR_FAILURE (116)[/B]
Arguments: 
Arg1: fffffa8008f56010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8800758da88, The pointer into responsible device driver module (e.g. owner tag).
Arg3: ffffffffc00000b5, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 000000000000000a, Optional internal context dependent data.
DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT
BUGCHECK_STR:  0x116
PROCESS_NAME: [B]System[/B]
FAILURE_BUCKET_ID: [B]0x116_IMAGE_nvlddmkm.sys[/B]
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
[/font]

3rd Party Drivers:
The following is for information purposes only.
Any drivers in red should be updated or removed from your system. And should have been discussed in the body of my post.
Code:
[font=lucida console]**************************Mon Nov 12 17:28:59.566 2012 (UTC - 5:00)**************************
[COLOR=RED][B]ASACPI.sys         Sun Mar 27 22:30:36 2005 (42476C4C)[/B][/COLOR]
[COLOR=RED][B]ADIHdAud.sys       Thu May 21 04:21:06 2009 (4A150EF2)[/B][/COLOR]
[COLOR=RED][B]a5368rdo.SYS       Tue Dec 27 17:30:45 2011 (4EFA4715)[/B][/COLOR]
[COLOR=RED][B]dtsoftbus01.sys    Fri Jan 13 08:45:46 2012 (4F10358A)[/B][/COLOR]
intelppm.sys       Wed Jul 25 22:26:48 2012 (5010AAE8)
[COLOR=RED][B]sptd.sys           Sat Aug 18 17:05:38 2012 (503003A2)[/B][/COLOR]
nvlddmkm.sys       Tue Oct  2 14:21:13 2012 (506B3099)
[/font]
http://www.carrona.org/drivers/driver.php?id=ASACPI.sys
http://www.carrona.org/drivers/driver.php?id=ADIHdAud.sys
a5368rdo.SYS - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
http://www.carrona.org/drivers/driver.php?id=dtsoftbus01.sys
http://www.carrona.org/drivers/driver.php?id=intelppm.sys
http://www.carrona.org/drivers/driver.php?id=sptd.sys
http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
 
Last edited by a moderator:
hello. no longer nervously no withstand. still bsod still bsod. I removed the d-tools and sptd.sys, atk0110 update here as I stated above. nvidia drivers have changed, i loaded the new drivers for the sound card , everything from asus. I made also a test in Furmark. tested to 85 degrees Celsius. memstest080 zrobilm 50 tests a mistake. I already do not know what to do maybe I'll musial back to win 7 but there also I had a BSOD.I updated the drivers for intel processor. adds this new BSOD that, I was already 3 bsodView attachment 112612-15428-01.dmp
 
memstest080 zrobilm 50 tests a mistake.
Does this mean that there were errors when running MemTest?
If so, that is a big problem. Please use this procedure to test each stick/slot (start at step 6b): Memory Diagnostics

The memory dump shows that Daemon Tools is still installed.
Are you using Alcohol software? If so, it uses the same drivers as Daemon Tools (and will have to be un-installed also)
If not, please post back and I'll give detailed instructions on how to safely remove dtsoftbus01.sys and sptd.sys

Please be patient. Fixing simple BSOD's often takes several pages of postings - more complicated one's (like this one) can take even longer.
If you wish to get a head start, you can run these free diagnostics as time permits: Hardware Diagnostics

Just FYI - since the motherboard is older, it's possible that the video error is due to incompatibilities with the hardware. But we can't verify that until we've fixed the DaemonTools/Alcohol software issues. Once that's fixed, then we'll concentrate on testing the video to see what happens (and the Furmark test is a good start!).

Analysis:
The following is for informational purposes only.
Code:
[font=lucida console]**************************Mon Nov 26 14:39:21.476 2012 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\112612-15428-01.dmp]
Windows 8 Kernel Version 9200 MP (4 procs) Free x64
Built by: [B]9200[/B].16442.amd64fre.win8_gdr.121023-1503
System Uptime:[B]0 days 6:00:41.185[/B]
BugCheck Code: [B]BugCheck 139, {3, fffff80007e7e690, fffff80007e7e5e8, 0}[/B]
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by :[B]dxgmms1.sys ( dxgmms1!VidSchiUpdateContextStatus+513 )[/B]
BugCheck Info: [B]KERNEL_SECURITY_CHECK_FAILURE (139)[/B]
Arguments: 
Arg1: 0000000000000003, A LIST_ENTRY has been corrupted (i.e. double remove).
Arg2: fffff80007e7e690, Address of the trap frame for the exception that caused the bugcheck
Arg3: fffff80007e7e5e8, Address of the exception record for the exception that caused the bugcheck
Arg4: 0000000000000000, Reserved
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
BUGCHECK_STR:  0x139
PROCESS_NAME: [B]t6mp.exe[/B]
FAILURE_BUCKET_ID: [B]0x139_3_dxgmms1!VidSchiUpdateContextStatus[/B]
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
[/font]

3rd Party Drivers:
The following is for information purposes only.
Any drivers in red should be updated or removed from your system. And should have been discussed in the body of my post.
Code:
[font=lucida console]**************************Mon Nov 26 14:39:21.476 2012 (UTC - 5:00)**************************
[COLOR=RED][B]ASACPI.sys         Wed May 13 21:25:17 2009 (4A0B72FD)[/B][/COLOR]
[COLOR=RED][B]ADIHdAud.sys       Thu May 21 04:21:06 2009 (4A150EF2)[/B][/COLOR]
[COLOR=RED][B]ahkie9gm.SYS       Tue Dec 27 17:30:45 2011 (4EFA4715)[/B][/COLOR]
[COLOR=RED][B]dtsoftbus01.sys    Fri Jan 13 08:45:46 2012 (4F10358A)[/B][/COLOR]
nvhda64v.sys       Tue Jul  3 11:25:04 2012 (4FF30ED0)
intelppm.sys       Wed Jul 25 22:26:48 2012 (5010AAE8)
[COLOR=RED][B]sptd.sys           Sat Aug 18 17:05:38 2012 (503003A2)[/B][/COLOR]
nvlddmkm.sys       Sun Nov 18 06:10:12 2012 (50A8C214)
[/font]
http://www.carrona.org/drivers/driver.php?id=ASACPI.sys
http://www.carrona.org/drivers/driver.php?id=ADIHdAud.sys
ahkie9gm.SYS - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
http://www.carrona.org/drivers/driver.php?id=dtsoftbus01.sys
http://www.carrona.org/drivers/driver.php?id=nvhda64v.sys
http://www.carrona.org/drivers/driver.php?id=intelppm.sys
http://www.carrona.org/drivers/driver.php?id=sptd.sys
http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
 
deleted the d-tools and what it SPTD You had me. update all the drivers from Asus. Framework for cleaning up today I'll take the evening. She took off the housing of the computer also some two days ago, because I thought that something heats. can blame the hard drive is really oldView attachment 112712-16005-01.dmp
 
memtest went out well without errors bootable version, in that I do not clean up or did not translate because I had no frame of compressed air tomorrow to change my pile. I do not know what I already deal ...
 
Upload the next memory dumps that occur and we'll work from there.
 
Unfortunately this dump file is corrupted and unreadable.
But based on the history of your problems, there are many different BSOD error codes - and there are some crashes that don't save memory dumps.
I'd suggest checking your hardware using these free diagnostics: Hardware Diagnostics (Start with the hard drive and memory tests).
 
check the hard drive from Seagate, unfortunately, the program did not detect anything. the same with memory framework for bsod I read all program errors bluescreneview sent last dump.

A problem has been detected and Windows has been shut down to prevent damage
to your computer.

The problem seems to be caused by the following file: rspndr.sys



If this is the first time you've seen this stop error screen,
restart your computer. If this screen appears again, follow
these steps:

Check to make sure any new hardware or software is properly installed.
If this is a new installation, ask your hardware or software manufacturer
for any Windows updates you might need.

If problems continue, disable or remove any newly installed hardware
or software. Disable BIOS memory options such as caching or shadowing.
If you need to use safe mode to remove or disable components, restart
your computer, press F8 to select Advanced Startup Options, and then
select Safe Mode.

Technical Information:

*** STOP: 0x00000139 (0x0000000000000003, 0xfffff880001d48b0, 0xfffff880001d4808,
0x0000000045000000)

*** rspndr.sys - Address 0xfffff8800b1d48b0 base at 0xfffff88003e28000 DateStamp
0x0010aa46
 
Try the other hardware tests at that link.

This error points to rspndr.sys - a network driver in Windows.
In most cases, when a Windows driver is blamed - it's not the Windows driver that's at fault.
Rather it's a 3rd party (non-Microsoft) driver that causes the Microsoft driver to crash

The next most common fault is a hardware problem.
And the least common fault is a Windows problem (because of the file protection mechanism's built into Windows).

Windows storage driver (atapi.sys)
memory corruption - either virtual or physical memory can be the cause, but the corruption can be caused by drivers or hardware
Video drivers x2 - can also be caused by hardware
Windows video driver (dxgmms1.sys)
Windows network driver (rspndr.sys)

Because of the different errors and Windows' not being able to settle on what to blame - it's most likely that this is a hardware problem. Please continue with the hardware tests that I suggested.

If they don't find anything, then try the clean install of Windows described here: Canned Speeches

Good luck!
 
Back
Top