Windows 7: bsod after resuming sleep

Zer0K3wL · 03 Jun 2011

anyone can check my dump file and find the cause maybe ?

suspecting my sb x-fi my self.

060211-6988-01.dmp

used to be 100% stable my rig but now it bsod sometimes after resuming sleep.

**yowanvista** · 03 Jun 2011

ASACPI.sys the 2005 version is a huge cause of BSODs

Information

The 2005 version of this driver is a known BSOD cause.
Please visit this link: ASUSTeK Computer Inc. -Support- Drivers and Download P7P55D LE
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 12th 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)

Update your Marvel Yukon Gigabit/network driver
http://www.marvell.com/support.html

Code:

ASACPI.sys        fffff880`04c11000    fffff880`04c19000    0x00008000    0x42476c4c    28/03/2005 06:30:36

Download Malwarebytes
Install, update and run a system scan

Zer0K3wL · 03 Jun 2011

hmmmm i had 1 dated from 2004 installed 2009 vision now.
reporting back soon.
i shall do a full scan asswell with malware bytes ^_^.

thnx a lot btw.

edit: put computer into sleep then resumed it locked up black screen without giving me a bsod.

gonna check further now.

edit: again put in sleep and its acting weird and diferent each time this time it gotten further sudenly its preparing security options.

it did give black screen again no bsod but i did get a dump file this time again.

http://www.**************/?am6u4wqtlv3kevd

quick scan finisched in 1 min since i'm on a ssd did't find anything
full scan has been going on now for 17 mins did't find anything yet.

edit: downloading new network drivers meanwhile installing them will test after malware bytes is done.

edit: 1 hour scan did't find anything i got like 3 tb on data save to asume dont got any malware virus or trojan.

I'm using nod32 asswell anyway.

Zer0K3wL · 03 Jun 2011

got bsod again could't make dump file.

http://i51.tinypic.com/14nibde.jpg

i got hunch now whats causing it tough not 100% sure yet have to test further think its 1 off my ssd tweaks not being aplied correctly.

**cluberti** · 03 Jun 2011

The error code the BSOD calls out in param 2 is the reason the filesystem driver (ntfs.sys) told the system to crash, although withtout a dump we don't know what the I/O request was to or to what file:

Code:

 
# for hex 0xc0000056 / decimal -1073741738 :
  STATUS_DELETE_PENDING                                         ntstatus.h
# A non close operation has been requested of a file object
# with a delete pending.

I'd say you have a filesystem filter driver (antivirus, antimalware) causing it, or the filesystems on each hard disk in the machine may need to have chkdsk /r /f run against it to make sure they are clean of errors (or, perhaps, both). Otherwise, some driver on the system is closing a file object and marking it for deletion, and then making a request for it immediately after while the deletion is still pending. That doesn't seem as likely as the former, though.

Zer0K3wL · 03 Jun 2011

hmmmm I'll check out my new hitachi 2 tb hdd it had 1 pending sector count before but then vanished.
got new bsod screenshot.

http://i54.tinypic.com/ivj1j6.jpg

this one did't get dump file tough cant see to locate it latest is from 3-6-2011 and not 4-6-2011
really odd.

i also run nod32 smart security 5.0

anyway i did a full format write 0 to the hd back then which fixed it.
think the pending sector gotten re written as a ultra dma crc error which usualy caused by bad sata cable.

edit:

here's a full list off dump files i got atm.

http://www.**************/?2j51vodns9gk854 ziped into 1 archive

Quote: Originally Posted by cluberti

The error code the BSOD calls out in param 2 is the reason the filesystem driver (ntfs.sys) told the system to crash, although withtout a dump we don't know what the I/O request was to or to what file:

Code:

 
# for hex 0xc0000056 / decimal -1073741738 :
  STATUS_DELETE_PENDING                                         ntstatus.h
# A non close operation has been requested of a file object
# with a delete pending.

I'd say you have a filesystem filter driver (antivirus, antimalware) causing it, or the filesystems on each hard disk in the machine may need to have chkdsk /r /f run against it to make sure they are clean of errors (or, perhaps, both). Otherwise, some driver on the system is closing a file object and marking it for deletion, and then making a request for it immediately after while the deletion is still pending. That doesn't seem as likely as the former, though.

i let chdsk run for now on my hitachi drive will probaly downgrade my nod32 to 4.0 to see if that fixes problems asswell if so i guess i have to mail them and report it

hmmmmm chdsk runs quite fast so far 4-5 did't find any problems so far i think

edit: now i think about it my laptop i put in sleep and resume from sleep all the time it also has the nod32 5.0 beta.

no errors on my hitachi hdd checking my samsung drive after if checked my ssd for errors.

Quote:

Chkdsk cannot run because the volume is in use by another
process. Chkdsk may run if this volume is dismounted first.
ALL OPENED HANDLES TO THIS VOLUME WOULD THEN BE INVALID.
Would you like to force a dismount on this volume? (Y/N) y
Volume dismounted. All opened handles to this volume are now invalid.
Volume label is shit.

CHKDSK is verifying files (stage 1 of 5)...
26880 file records processed.
File verification completed.
6 large file records processed.
0 bad file records processed.
0 EA records processed.
0 reparse records processed.
CHKDSK is verifying indexes (stage 2 of 5)...
27474 index entries processed.
Index verification completed.
0 unindexed files scanned.
0 unindexed files recovered.
CHKDSK is verifying security descriptors (stage 3 of 5)...
26880 file SDs/SIDs processed.
Security descriptor verification completed.
298 data files processed.
CHKDSK is verifying Usn Journal...
37413304 USN bytes processed.
Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
26864 files processed.
File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
171511891 free clusters processed.
Free space verification is complete.
Windows has checked the file system and found no problems.

1953512447 KB total disk space.
1267263704 KB in 8791 files.
11776 KB in 299 indexes.
0 KB in bad sectors.
189399 KB in use by the system.
65536 KB occupied by the log file.
686047568 KB available on disk.

4096 bytes in each allocation unit.
488378111 total allocation units on disk.
171511892 allocation units available on disk.

Zer0K3wL · 03 Jun 2011

think i found the problem now or least i disabled both my mechanical hard drives in device manager did't bsod yet.

gonna leave one on to see which one causes it.

i suspect my samsung drive.

Yep probaly samsung drive gonna disable it now and keep only my hitachi drive enabled to see if it crash again.

edit: if i leave both disabled i get bsod.

if i leave 1 enabled does't matter which mechanical drive it bsod.

uninstalling nod32 beta 5.0 then rebooting and checking if sleep mode still crashes the system

edit: nod32 not causing it.

Think i found the fix by re enabling apm on both drives.
dont known why it was causing problems.

edit: either I'm wrong or advanced power management wont stay on for both my drives

edit: aint apm either i dont known whats wrong at all anyore lol everything used be 100% stable now its bsod on each time i resume sleep.

the only fix is disabling both drives which i'm defiantly not gonna do.

Windows aint even giving my 2 mechanical drives any time to resume they still clicking on and boom bsod.

Zer0K3wL · 04 Jun 2011

bump.

still no fix did bios update did't help either.

all i known is it only resume properly each time if i disable both mechanical hard drives.

edit: what tool do i need to check these dmp files my self would like to check them out my self.

Windows 7: bsod after resuming sleep

bsod after resuming sleep problems?