Windows 7: Bsod after waking from sleep.

maurice c · 15 Oct 2010

Running amd phenom 955x4, ga-880gm usb3 motherboard, kingston hyperx blu 4g 1600 ddr3, Caviar green 1.5tb drive and GV-R545SC-1GI graphics card.

Built this system about 4 weeks ago, has been pretty unstable, bsods when waking from sleep but not all the time. Thought it was the printer driver but I uninstalled it and made no difference. I have run memtest86 for 5 passes and no errors, hard drive tests good as well. Have changed the hard drive cable and still no difference.

Windows7 64, oem version installed myself. all parts new a month ago.

Any help with this one would be greatly appreciated.

maurice c · 17 Oct 2010

Seems to happen when I wake it up from sleep and opera is open on the desktop, I have uninstalled the stpd driver form Daemon tools and still got a 0000f4 bsod. Any Ideas?

wish · 17 Oct 2010

Hi,
Your dumps have ERROR_CODE: (NTSTATUS) 0xc000009d - STATUS_DEVICE_NOT_CONNECTED.

Looks like something wrong with your hardrive.
Perform check disk -> cmd(as admin) -> chkdsk /r /f -> enter

Go to Power option-> Change plan settings-> Change advance power settings
- Set turn off hardisk after = never
- Allow Hybrid sleep = off

While troubleshooting it's better to :
- Remove Kaspersky and replace it with MSE
- Uninstall Alcohol/Daemon and remove its driver with SPTDinst
(you may install both latter after the problem solved)

This driver need to do update:
adfs.SYS --> adobe software

Logs

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 7A, {20, ffffffffc000009d, fffffa8005d517c8, 0}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4c5e0 )

Followup: MachineOwner
---------

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

KERNEL_DATA_INPAGE_ERROR (7a)
The requested page of kernel data could not be read in.  Typically caused by
a bad block in the paging file or disk controller error. Also see
KERNEL_STACK_INPAGE_ERROR.
If the error status is 0xC000000E, 0xC000009C, 0xC000009D or 0xC0000185,
it means the disk subsystem has experienced a failure.
If the error status is 0xC000009A, then it means the request failed because
a filesystem failed to make forward progress.
Arguments:
Arg1: 0000000000000020, lock type that was held (value 1,2,3, or PTE address)
Arg2: ffffffffc000009d, error status (normally i/o status code)
Arg3: fffffa8005d517c8, current process (virtual address for lock type 3, or PTE)
Arg4: 0000000000000000, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)

Debugging Details:
------------------


ERROR_CODE: (NTSTATUS) 0xc000009d - STATUS_DEVICE_NOT_CONNECTED

DISK_HARDWARE_ERROR: There was error with disk hardware

BUGCHECK_STR:  0x7a_c000009d

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  1

LAST_CONTROL_TRANSFER:  from fffff800032b53fc to fffff8000327d740

STACK_TEXT:  
fffff880`03b08828 fffff800`032b53fc : 00000000`0000007a 00000000`00000020 ffffffff`c000009d fffffa80`05d517c8 : nt!KeBugCheckEx
fffff880`03b08830 fffff800`03267637 : fffffa80`05d51760 00000000`c000009d 00000000`00000000 fffffa80`05d517f8 : nt! ?? ::FNODOBFM::`string'+0x4c5e0
fffff880`03b088f0 fffff800`0325a0c7 : fffffa80`039f5a10 fffffa80`039f5a60 00000000`00000000 00000000`00000000 : nt!IopCompletePageWrite+0x57
fffff880`03b08920 fffff800`03284b9d : fffffa80`039f5a10 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDeliverApc+0x1d7
fffff880`03b089a0 fffff800`03280d4b : 00000103`03b08b01 00000000`00000000 fffffa80`00000000 fffff880`03b08a50 : nt!KiCommitThreadWait+0x3dd
fffff880`03b08a30 fffff800`03217abf : fffffa80`00000002 fffff880`03b08d20 00000000`00000001 fffffa80`00000013 : nt!KeWaitForMultipleObjects+0x271
fffff880`03b08ce0 fffff800`03521c06 : fffffa80`039f5a10 00000000`00000000 00000000`00000080 00000000`00000001 : nt!MiModifiedPageWriter+0xcf
fffff880`03b08d40 fffff800`0325bc26 : fffff880`03763180 fffffa80`039f5a10 fffff880`0376dfc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`03b08d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+4c5e0
fffff800`032b53fc cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+4c5e0

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9

FAILURE_BUCKET_ID:  X64_0x7a_c000009d_nt!_??_::FNODOBFM::_string_+4c5e0

BUCKET_ID:  X64_0x7a_c000009d_nt!_??_::FNODOBFM::_string_+4c5e0

Followup: MachineOwner
---------

maurice c · 18 Oct 2010

Heres are the last two results of chkdsk, seems good.
Checking file system on C:
The type of the file system is NTFS.

A disk check has been scheduled.
Windows will now check the disk.

CHKDSK is verifying files (stage 1 of 5)...
189952 file records processed.
File verification completed.
116 large file records processed.
0 bad file records processed.
0 EA records processed.
60 reparse records processed.
CHKDSK is verifying indexes (stage 2 of 5)...
239092 index entries processed.
Index verification completed.
0 unindexed files scanned.
0 unindexed files recovered.
CHKDSK is verifying security descriptors (stage 3 of 5)...
189952 file SDs/SIDs processed.
Cleaning up 172 unused index entries from index $SII of file 0x
Cleaning up 172 unused index entries from index $SDH of file 0x
Cleaning up 172 unused security descriptors.
Security descriptor verification completed.
24571 data files processed.
CHKDSK is verifying Usn Journal...
35810728 USN bytes processed.
Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
189936 files processed.
File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
322241309 free clusters processed.
Free space verification is complete.
CHKDSK discovered free space marked as allocated in the
master file table (MFT) bitmap.
CHKDSK discovered free space marked as allocated in the volume
Windows has made corrections to the file system.

1465033727 KB total disk space.
175644156 KB in 153412 files.
87960 KB in 24572 indexes.
0 KB in bad sectors.
336371 KB in use by the system.
65536 KB occupied by the log file.
1288965240 KB available on disk.

4096 bytes in each allocation unit.
366258431 total allocation units on disk.
322241310 allocation units available on disk.

Internal Info:
00 e6 02 00 48 b7 02 00 4b e2 04 00 00 00 00 00 ....H...K.....
ce 10 00 00 3c 00 00 00 00 00 00 00 00 00 00 00 ....<.........
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ..............

Windows has finished checking your disk.
Please wait while your computer restarts.

08-Oct-10 3:05:10 AM

Checking file system on C:
The type of the file system is NTFS.

A disk check has been scheduled.
Windows will now check the disk.

CHKDSK is verifying files (stage 1 of 5)...
143360 file records processed.
File verification completed.
85 large file records processed.
0 bad file records processed.
0 EA records processed.
60 reparse records processed.
CHKDSK is verifying indexes (stage 2 of 5)...
184274 index entries processed.
Index verification completed.
0 unindexed files scanned.
0 unindexed files recovered.
CHKDSK is verifying security descriptors (stage 3 of 5)...
143360 file SDs/SIDs processed.
Security descriptor verification completed.
20458 data files processed.
CHKDSK is verifying Usn Journal...
36272416 USN bytes processed.
Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
143344 files processed.
File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
324547866 free clusters processed.
Free space verification is complete.
Windows has checked the file system and found no problems.

1465033727 KB total disk space.
166482980 KB in 118628 files.
69352 KB in 20459 indexes.
0 KB in bad sectors.
289927 KB in use by the system.
65536 KB occupied by the log file.
1298191468 KB available on disk.

4096 bytes in each allocation unit.
366258431 total allocation units on disk.
324547867 allocation units available on disk.

Internal Info:
00 30 02 00 57 1f 02 00 e3 e4 03 00 00 00 00 00 .0..W.........
41 10 00 00 3c 00 00 00 00 00 00 00 00 00 00 00 A...<.........
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ..............

Windows has finished checking your disk.
Please wait while your computer restarts.

maurice c · 05 Nov 2010

[Solved] Windows 7: Hard Drives Disappear after Sleep Resume - general-discussion - windows-7

Easy fix.................

wish · 05 Nov 2010

Glad to hear that

Btw what exactly you did to solve the problem?

maurice c · 07 Nov 2010

Seems that large sata drives don't respond quick enough when waking from sleep for windows so it bsod's and shuts down if its the primary drive, the drive disappears if its a secondary drive, the hot-fix fixes this problem.

Windows 7: Bsod after waking from sleep.

Bsod after waking from sleep. problems?