My BSOD problem

I've been having a strange issue with my computer for a while now. A strange combination of random restarts, freezing but most commonly BSOD all with different error messages. I've tried a lot even removing some RAM and changing my keyboard. I've also had it checked 4 times with still no results.

I've attached the info below.

Please help!

View attachment


Noob Whisperer
Concerned about the presence of this driver
a6h87yax.SYS 11/16/2010
I will assume that since you also have
sptd.sys 3/3/2012
It is some how link with either Daemon Tools or Alcohol 120 uninstall either or both and then download and run and UNINSTALL using this tool DuplexSecure - Downloads get the correct version for your architecture.
Since most of your recent BSODs are x124 stop errors "HARDWARE"
You need to consider updating your BIOS
BiosVendor = American Megatrends Inc.
BiosVersion = 0802   
BiosReleaseDate = 12/21/2010
BaseBoardManufacturer = ASUSTeK Computer INC.
BaseBoardProduct = SABERTOOTH X58
BaseBoardVersion = Rev 1.xx
from here ASUS - Motherboards- ASUS SABERTOOTH X58
iaStor.sys 6/4/2009 using the update utility from here Intel® Driver Update Utility
mv91xx.sys 12/25/2009 Marvell disc controller from here Marvell drivers scroll down to Marvell MV-91xx (88SE91xx/92xx) Ahci/Raid Controller and grab this one Drivers Version /Vista/7 New

Last edited:
Thanks Trouble,

I did most of the fixes minus the marvell drivers and the second uninstall for Alcohol 120. The problem was the moment the computer booted up after the BIOS update it instantly BSODed. I've attached the dumps.

Thanks for the help!

View attachment


Noob Whisperer
Not sure where to go from here.
The good news is that your most recent dump file was not a x124 stop (HARDWARE) error.
The bad news is that it was
    # Any other values for parameter 1 must be individually examined.
Arg1: 0000000000041790, The subtype of the bugcheck.
Arg2: fffffa800c4c4e50
Arg3: 000000000000ffff
Arg4: 0000000000000000
This can often be a product of buggy drivers so I would still recommend catching up that Marvell host controller driver soon.
As well as this one wdcsam64.sys 4/16/2008 from here WD Support / Downloads / Select Product
If you have a WD USB 3.0 product attached to your NEC integrated USB host controller, disconnect it for the time being or at least make sure it is not connected at boot time for now.
You still have sptd.sys known to have occasional BSOD issues with Win7 that really should go for now.
You have Symantec / Norton installed, again known to have BSOD issues occasionally with Win7 that should also go for now. Uninstall it and run this
Replace at least for now with MSE from here
Your Realtek Audio driver needs to be updated from here Realtek
Your Realtek NIC driver needs to be updated from here Realtek
And in light of your previous x124 HARDWARE stop errors you should probably test your memory:
Download Memtest86+ from this location here. Burn the ISO to a CD and boot the computer from the CD from a cold boot after leaving it off for an hour or more.
Ideally let it run for at least 7 passes / 6-8 hours. If errors appear before that you can stop that particular test. Any time Memtest86+ reports errors, it can be either bad RAM or a bad Mobo slot. Perform the test RAM sticks individually as well as all possible combinations. When you find a good one then test it in all slots. Post back with the results.
See this Guide to using Memtest 86+
Regarding your Blue Screen immediately following your BIOS update
Anytime you update your systems BIOS there may be some resetting of pre-configured settings so you may want to go into the BIOS and examine anything that you may have manually configured yourself. Additionally you may want to attempt to use one of the system pre-sets usually marked as Defaults, or Optimized or both or either. Additionally you want to make sure that your disk controller settings are configured properly and were not changed by the Flash Utility. Whether they were formerly set to AHCI or AHCI / RAID or NATIVE IDE, they will need to be returned to that setting in order for your system to boot reliably.
Any new dump files, please attach.

Last edited:
Ok so now I've done everything except the memtest (although I remember doing that a few months ago and all was ok). So far things have improved drastically (Thanks Randy!). The problem is I still have one remaining problem which is that i get frequent graphics card crashes (attached). I'm not sure where the dumps for the card go, it's an ATI Radeo HD 5800 Series card. I'm not overclocking or anything but I am running it on two monitors but even on one it was doing the same thing.

Thanks for the help



Fantastic Member
Microsoft Community Contributor
Excuse me for butting in here, but I'd like to explain the graphics error that you're getting. I haven't read the entire post, nor have I checked any of the uploaded reports - I'm only replying to the problem described in your last post.

The error is actually a Blue Screen"ish" error. By this I mean it's a STOP error, but the graphics drivers are able to recover from it - so it doesn't present you with a BSOD.

Just FYI - there are basically 3 types of errors considered in the WHEA:
- Corrected errors
- Uncorrected but recoverable errors
- Uncorrected Fatal Error (this is the BSOD)

The first step here is to replace your graphics drivers with a fresh copy to see if it's a driver problem that's causing the issues (we do this first because it's easiest and it's free). To do this, please follow the steps at this link: ATI video cards - DRIVER ONLY installation procedure

Should this not fix things, then have a look at this troubleshooting guide (STOP 0x117 and STOP 0x116 are very similar and we use the same troubleshooting steps for each): STOP 0x116: VIDEO_TDR_ERROR troubleshooting - Windows 7 Forums

Thanks Usasma,

Ok so at this point I've done all the listed above except for the memtest (though I have done that before and it was fine) and the second step recommended by Usasma. I've done a complete CCleaner run of the ATI drivers before reinstalling them to no avail. Graphics card still sporadically crashes and I just got another BSOD memory_management error. Dump below.

I'll try the last two recommendations tonight.

Is there any other info I could give that could help with a solution??? I'm at my wits end. View attachment

UPDATE: Another BSOD 5 minutes after reboot: View attachment

Last edited:


Fantastic Member
Microsoft Community Contributor
Again, let me stress that I haven't checked the rest of the posts and am only referring to video issues here.
Run the video card memory test from here: Hardware Diagnostics

Then, if the problem continues, try another video card. If you don't have one that you can test with, purchase one from a store that will let you return it if it's not needed.

Ok at this point the computer won't stay on for longer than 10-15 minutes before a BSOD with the MEMORY_MANAGEMENT error.

I ran the memtest for over 10 hours with no errors. The video card tests were the only things that failed so I guess we go back to square one and I think that what I have is a faulty graphics card. Unfortunately going out of town now so I guess I'll have to run this experiment once I'm back.

Thanks a lot for the help guys and I'll post back with results.

Hi guys,

So I switched out the graphics card to an older NVIDIA card which never gave me problems. All was well until last night another BSOD and for the next ten minutes I got three BSODs. I had to keep the computer off for about ten minutes then turn it back on, after that the comp remained on over night.

Its really frustrating, I don't understand what it could be :s

I really appreciate the help guys. View attachment


Well-Known Member

Now i am not a pro at debugging, but if you are crashing with another video card, Then i have a nagging feeling that this may be a bad PCI, PCI-E, etc port on your mobo.

********************************************************************************                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *

Attempt to reset the display driver and recover from timeout failed.
Arg1: fffffa8012e5b010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8800f7c04d4, The pointer into responsible device driver module (e.g. owner tag).
Arg3: 0000000000000000, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000002, Optional internal context dependent data.

Debugging Details:

fffff880`0f7c04d4 4883ec28        sub     rsp,28h






fffff880`03b8d9c8 fffff880`05e84000 : 00000000`00000116 fffffa80`12e5b010 fffff880`0f7c04d4 00000000`00000000 : nt!KeBugCheckEx
fffff880`03b8d9d0 fffff880`05e83d0a : fffff880`0f7c04d4 fffffa80`12e5b010 fffffa80`12f84d50 fffffa80`12f62010 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`03b8da10 fffff880`05f2af07 : fffffa80`12e5b010 00000000`00000000 fffffa80`12f84d50 fffffa80`12f62010 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`03b8da40 fffff880`05f54b75 : 00000000`ffffffff 00000000`02ce9938 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`03b8db20 fffff880`05f532bb : 00000000`00000102 00000000`00000000 00000000`02ce9938 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`03b8db50 fffff880`05f262c6 : ffffffff`ff676980 fffffa80`12f62010 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`03b8dbf0 fffff880`05f52e7a : 00000000`00000000 fffffa80`16e51910 00000000`00000080 fffffa80`12f62010 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`03b8dd00 fffff800`03371e6a : 00000000`fffffc32 fffffa80`12f8a060 fffffa80`0e59a040 fffffa80`12f8a060 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`03b8dd40 fffff800`030cbec6 : fffff880`03786180 fffffa80`12f8a060 fffff880`037910c0 fffff880`01f6d975 : nt!PspSystemThreadStartup+0x5a
fffff880`03b8dd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16

STACK_COMMAND:  .bugcheck ; kb

fffff880`0f7c04d4 4883ec28        sub     rsp,28h

SYMBOL_NAME:  nvlddmkm+19e4d4

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys


FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

Followup: MachineOwner
Transmit Data Register (TDR) ould point to either a problem with the driver ( i think ) or the driver failing when it can't find the chip.

********************************************************************************                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *

Use !analyze -v to get detailed debugging information.

BugCheck F4, {3, fffffa801309c600, fffffa801309c8e0, fffff8000337e510}

Probably caused by : wininit.exe

Followup: MachineOwner

6: kd> !analyze -v
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *

A process or thread crucial to system operation has unexpectedly exited or been
Several processes and threads are necessary for the operation of the
system; when they are terminated (for any reason), the system can no
longer function.
Arg1: 0000000000000003, Process
Arg2: fffffa801309c600, Terminating object
Arg3: fffffa801309c8e0, Process image file name
Arg4: fffff8000337e510, Explanatory message (ascii)

Debugging Details:

PROCESS_OBJECT: fffffa801309c600


MODULE_NAME: wininit

FAULTING_MODULE: 0000000000000000 

PROCESS_NAME:  WerFault.exe

BUGCHECK_STR:  0xF4_WerFault.exe




LAST_CONTROL_TRANSFER:  from fffff80003406892 to fffff8000307f1c0

fffff880`0889db08 fffff800`03406892 : 00000000`000000f4 00000000`00000003 fffffa80`1309c600 fffffa80`1309c8e0 : nt!KeBugCheckEx
fffff880`0889db10 fffff800`033b2e8b : ffffffff`ffffffff fffffa80`1281b360 fffffa80`1309c600 fffffa80`127ab340 : nt!PspCatchCriticalBreak+0x92
fffff880`0889db50 fffff800`03331f74 : ffffffff`ffffffff 00000000`00000001 fffffa80`1309c600 00000000`00000008 : nt! ?? ::NNGAKEGL::`string'+0x176d6
fffff880`0889dba0 fffff800`0307e453 : fffffa80`1309c600 fffff880`000000ff fffffa80`1281b360 00000000`00000000 : nt!NtTerminateProcess+0xf4
fffff880`0889dc20 00000000`775815da : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0020cea8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x775815da


FOLLOWUP_NAME:  MachineOwner

IMAGE_NAME:  wininit.exe

FAILURE_BUCKET_ID:  X64_0xF4_WerFault.exe_IMAGE_wininit.exe

BUCKET_ID:  X64_0xF4_WerFault.exe_IMAGE_wininit.exe

Followup: MachineOwner
Wininit.exe is a windows 7 core process in XP, Vista, and 7. This allows programs to run while the computer is still booting up. Check for startup program viruses.

WerFault.exe is supposedly Win Vista error reporting (also in 7)

Being as it says the word TERMINATION i would check the seating of your video card, improper seating can cause it to turn off.. If BSOD's persist try MemTest86+ (bootable) to look for RAM problems (those seems to be an epidemic anymore :(

If you are overclocking STOP!!!!!!!!!!!!!!

Also as one of the pro's on here said earlier i think, check out SpeedFan to monitor your temperatures.

(professionals here, please tell me where i am wrong so i can get better at this, thank you!)

This website is not affiliated, owned, or endorsed by Microsoft Corporation. It is a member of the Microsoft Partner Program.