View Single Post
21 Aug 2010  

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