Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.

Windows 7: Multiple Different BSOD

21 Aug 2010   #1

Windows 7
Multiple Different BSOD

Windows x64
Core i5 2.67 @ 3.71
HD 5770
8GB Ram
Main drive is 160GB Intel SSD
Secondary is Seagate 2TB

I have had perhaps one BSOD a week for the past 3 weeks, nothing serious or so I thought, but today things aren't going so well. The reported cause was the video card, but as I require my computer on pretty much 24/7 and restarting is a hassle (since my graphics card doesn't detect my main monitor over a DisplayPort -> VGA adaptor reliably) I ignored it.

Generally quite shortly after logging on, anything from 10seconds to 20mins I am getting a BSOD. The listed causes seem to change, the three most recent came from:

Cache Manager

Earlier today there was also another one caused by the video card.

Booting into safe mode I managed to make an image of my main drive, the computer seems to be able to stay on without issue in safe mode.

I downloaded and ran the BSOD Dump & System File Collection App which seems to run successfully but is not creating any output files in C:\Users\Tom\Documents.

perfmon /report would not work either, just giving the message .h1{ font-family: 'Segoe UI'; font-weight: bolder; font-size: 12pt; } .text{ font-family: 'Segoe UI'; font-weight: normal; font-size: 12pt; } .info{ font-family: 'Segoe UI'; font-weight: normal; font-style: italic; font-size: 12pt; } [IMG]res://wdc.dll/error.gif[/IMG] Error:

An error occured while attempting to generate the report.

Tried running "WhoCrashed" but that require windbg to be installed which I can't do in safe mode it seems.

Any thoughts on what to try next? I'll have a go at getting the BSOD tool to run before it crashes if I boot normally...

Update: My Secondary HDD could not report its name properly in BIOS. I ran some basic tests on this and the main drive last time I logged on, BSOD came part way through Long D.S.T (Using SeaTools). Passed the earlier ones before that.

If this is the HDD failing then this is the 4th HDD to fail in as many months after being connected to this computer. Something strange happening.

Update2: Managed to run off the BSOD tool seconds before it crashed. Have attached to post.

My System SpecsSystem Spec
21 Aug 2010   #2

Microsoft Community Contributor Award Recipient

Windows 10, Home Clean Install

Follow instructions and you will be helped.
My System SpecsSystem Spec
21 Aug 2010   #3

Windows 7

Quote   Quote: Originally Posted by richc46 View Post
Follow instructions and you will be helped.
As I said in the post, I did try to do those things but had difficulty in doing so.

Having now disconnected the secondary drive it has stayed on long enough for me to run perfmon as well.

Further Info:

- x86 (32-bit) or x64 ? x64
- the original installed OS on the system? Own built system
- an OEM or full retail version? Full Retail
- OEM = came pre-installed on system
- Full Retail = you purchased it from retailer

- What is the age of system (hardware)? 6 months
- What is the age of OS installation (have you re-installed the OS?) 3 months

Thank you for any assistance.
My System SpecsSystem Spec

21 Aug 2010   #4

64-bit Windows 8.1 Pro

We need more than the performance report... run the tool again as administrator and upload the entire results..
My System SpecsSystem Spec
21 Aug 2010   #5

Windows 7

Quote   Quote: Originally Posted by Tews View Post
We need more than the performance report... run the tool again as administrator and upload the entire results..
It would not work whilst in safe mode, I did try several times. The report I managed to get before it crashed after booting normally is already attached to the first post. I have reattached it again to this post.
My System SpecsSystem Spec
21 Aug 2010   #6

Microsoft Window 7 Professional 32 bit

Hi and Welcome to SF!

First of all, please update this driver:
ASACPI   ASACPI.sys   Mon Mar 28 09:30:36 2005 (42476C4C)
The 2005 version of this driver is a known BSOD cause.
Please visit this link: ASUSTeK Computer Inc.-Support- download_item_mkt
Scroll down to the Utilities category, then scroll down to the "ATK0110 driver for WindowsXP/Vista/Windows 7 32&64-bit " (it's about the 10th item down).
Download and install it.
Go to C:\Windows\System32\drivers to check and make sure that the ASACPI.sys file is date stamped from 2009 or 2010 (NOT 2005).

In case you can't find it, I've attach that for you, but let's go find it in case what i have is the old one.

Other out of date drivers:
SaiH8000 SaiH8000.sys Fri Apr 04 18:26:34 2008 (47F6106A) 
 Saitek Hid driver Download drivers and software for Saitek products
wdcsam64 wdcsam64.sys Wed Apr 16 15:39:08 2008 (4805BB2C)
Western Digital External Drive RAID Manager
WD Support > Downloads > Select Product
Please remove any CD virtualization programs such as Daemon Tools and Alcohol 120%. They use a driver, found in your dmp, sptd.sys, that is notorious for causing BSODs. Use this SPTD uninstaller when you're done: DuplexSecure - Downloads

Stop code 7E is typically caused by graphic card. Since directX was blamed in one of the DMP, I would recommend you to re-install the graphic card driver first, if doesn't work then perhaps you can try to borrow another one from friends or store.
When upgrading your graphic driver you MUST remove all traces of the current driver. In order to do that we recommend using Guru3D - Driver Sweeper

When it is removed then download and install the fresh copy.

BugCheck 34, {50830, fffff8800339a7b8, fffff8800339a020, fffff800031938bb}

Probably caused by : ntkrnlmp.exe ( nt!IopDeleteFile+24b )

Followup: MachineOwner
BugCheck 19, {22, 1000000000000, 0, 0}

GetPointerFromAddress: unable to read from fffff800030c50e0
GetUlongFromAddress: unable to read from fffff800030331b0
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+72f8 )

Followup: MachineOwner
BugCheck 1000007E, {ffffffffc0000005, fffff80002e796a9, fffff880033a8908, fffff880033a8170}

Probably caused by : ntkrnlmp.exe ( nt!IopInsertRemoveDevice+59 )

Followup: MachineOwner
BugCheck 3B, {c0000005, fffff800031958bb, fffff8800c459080, 0}

Probably caused by : ntkrnlmp.exe ( nt!IopDeleteFile+24b )

Followup: MachineOwner
BugCheck 24, {1904fb, fffff880056cf228, fffff880056cea90, fffff80002e5b80d}

Unable to load image \SystemRoot\system32\DRIVERS\mozy.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for mozy.sys
*** ERROR: Module load completed but symbols could not be loaded for mozy.sys
Probably caused by : Ntfs.sys ( Ntfs!NtfsFlushVolume+601 )

Followup: MachineOwner
BugCheck 7F, {8, 80050031, 6f8, fffff88004558060}

Probably caused by : dxgmms1.sys ( dxgmms1!VidSchiUpdateContextRunningTimeAtISR+10 )

Followup: MachineOwner
Let us know if you need help

My System SpecsSystem Spec
22 Aug 2010   #7

Windows 7 - Vista

Hi -

No doubt that the 2005 Asus ATK0110 driver is big issue here and needs to be updated.

One of the dumps listed mosy.sys as a probable cause. Update your Mozy installation -

Online Backup, Data Backup & Remote Backup Solutions | Mozy

One of the BSOD bugchecks = 0x24 (1904fb,,,) = NTFS file system with 0xc0000005 exception = memory access violation; another named ntfs.sys as probable cause.

Run chkdsk /r on HDD after driver updates.

Regards. . .


My System SpecsSystem Spec
22 Aug 2010   #8

Windows 7

Ok I updated the ASACPI.sys file. Confusingly I distinctly recall updating this file last time I had troubles, don't know why it has reverted to the old version.

Uninstalled, cleaned, reinstalled video card drivers.

Updated Mozy.

Uninstalled Daemon Tools, have a problem in that there was still a drive mounted, but Daemon was not aware of it, so I couldn't figure out how to unmount it before uninstalling. I then used the tool I was linked to, did all the restarts but the mounted drive still remains somehow. I don't have any other emulation software installed as far as I know.

There were no newer drivers for Western Digital or Saitek.

I still have my other HDD disconnected and my computer seems to be fine. As I mentioned before this computer seems to have a history of destroying HDDs, I have no idea why though. Last time I was told it might be my PSU so I replaced that but same thing has happened again it seems.
My System SpecsSystem Spec

 Multiple Different BSOD

Thread Tools

Similar help and support threads
Thread Forum
BSOD Multiple types multiple times a day, can't pin down the problem
Hello everyone, I came here once before for assistance, but the issue was unable to be resolved. Here is the link to the previous thread. There is no singular trigger to set this off. Sometimes I can...
BSOD Help and Support
Multiple BSOD Multiple Drivers - Fresh Install (atikmdag.sys = main)
Hi, i had been having issues with bluescreens once every week or so. I took action by updating my drivers etc but this did not fix the issue. I re-installed windows and got all my drivers on and such yet the problem persists with more bluescreens, more often and with more driver causes. Before the...
BSOD Help and Support
BSOD Multiple times multiple errors 0x0000001A
Last week I started receiving BSODs, and after the first one it got to the point where my computer was not booting up and my hard drive was beeping very angrily at me. I was not sure what all the problems were, however I also knew that there was something seriously wrong with my hard drive, so I...
BSOD Help and Support
BSOD errors. multiple times during multiple programs
windows 7 x64 - original install on system but i don't have my disks. they are somewhere... - full retail version installed - age of the system is approximately 3 years - age of the install is approximately 2 years it seems to happen at random but i get BSODs. approximately 2-3 times a day...
BSOD Help and Support
Multiple BSOD at Random Times with Multiple Drivers Identified
I am trying to get my wife's new computer up and running without any BSOD or program failures. Note that the system was not initially set up to capture the dmp files so all the earliest ones are missing. I presented the initial problems to the original seller who recommended sticking with MSE and...
BSOD Help and Support

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 20:01.
Twitter Facebook Google+