windows 7 pro 64 bit BSOD After Standby Wakeup

[xfymars]

hi everyone, I have a desktop with i7 920 and ati hd 4870 video card, 1TB hard drive, running windows 7 pro 64bit. I get BSOD after standby wakeup these days.

Below is my information:

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.48
Locale ID: 1033

Additional information about the problem:
BCCode: 7a
BCP1: 0000000000000020
BCP2: FFFFFFFFC000009D
BCP3: FFFFFA8007290078
BCP4: 0000000000000000
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\042810-25568-01.dmp
C:\Users\Feiyu\AppData\Local\Temp\WER-33103-0.sysdata.xml

Read our privacy statement online:
Windows 7 Privacy Statement - Microsoft Windows

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

I also attached my dmp file. Please help me.
thank you very much.

 

[zigzag3143]

hi everyone, I have a desktop with i7 920 and ati hd 4870 video card, 1TB hard drive, running windows 7 pro 64bit. I get BSOD after standby wakeup these days.

Below is my information:

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.48
Locale ID: 1033

Additional information about the problem:
BCCode: 7a
BCP1: 0000000000000020
BCP2: FFFFFFFFC000009D
BCP3: FFFFFA8007290078
BCP4: 0000000000000000
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\042810-25568-01.dmp
C:\Users\Feiyu\AppData\Local\Temp\WER-33103-0.sysdata.xml

Read our privacy statement online:
Windows 7 Privacy Statement - Microsoft Windows

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

I also attached my dmp file. Please help me.
thank you very much.

Finally Disk Hardware. I would run the following:

CHKDSK /R /F:
Run CHKDSK /R /F from an elevated (Run as adminstrator) Command Prompt. Please do this for each hard drive on your system.
When it tells you it can't do it right now - and asks you if you'd like to do it at the next reboot - answer Y (for Yes) and press Enter. Then reboot and let the test run. It may take a while for it to run, but keep an occasional eye on it to see if it generates any errors. See "CHKDSK LogFile" below in order to check the results of the test.

Elevated Command Prompt:
Go to Start and type in "cmd.exe" (without the quotes)
At the top of the Search Box, right click on Cmd.exe and select "Run as administrator"

CHKDSK LogFile:
Go to Start and type in "eventvwr.msc" (without the quotes) and press Enter
Expand the Windows logs heading, then select the Application log file entry.
Double click on the Source column header.
Scroll down the list until you find the Chkdsk entry (wininit for Win7) (winlogon for XP).
Copy/paste the results into your next post.


Let us know if you need help

Ken

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\042810-25568-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*F:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02c60000 PsLoadedModuleList = 0xfffff800`02e9de50
Debug session time: Wed Apr 28 21:44:59.856 2010 (GMT-4)
System Uptime: 0 days 8:24:06.149
Loading Kernel Symbols
...............................................................
................................................................
..................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

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

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

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

2: 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: fffffa8007290078, 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 fffff80002d082dc to fffff80002cd0600

STACK_TEXT:  
fffff880`033d9828 fffff800`02d082dc : 00000000`0000007a 00000000`00000020 ffffffff`c000009d fffffa80`07290078 : nt!KeBugCheckEx
fffff880`033d9830 fffff800`02cba507 : fffffa80`07290010 00000000`c000009d 00000000`00000000 fffffa80`072900a8 : nt! ?? ::FNODOBFM::`string'+0x4c620
fffff880`033d98f0 fffff800`02cacfcf : fffffa80`0552d040 fffffa80`0552d090 00000000`00000000 00000000`00000000 : nt!IopCompletePageWrite+0x57
fffff880`033d9920 fffff800`02cd795d : fffffa80`0552d040 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDeliverApc+0x1d7
fffff880`033d99a0 fffff800`02cd3c4b : 00000103`064e0a01 00000000`00000000 00000000`00000000 fffff880`033d9a50 : nt!KiCommitThreadWait+0x3dd
fffff880`033d9a30 fffff800`02c6aa8f : fffffa80`00000002 fffff880`033d9d20 00000000`00000001 fffffa80`00000013 : nt!KeWaitForMultipleObjects+0x271
fffff880`033d9ce0 fffff800`02f75a86 : fffffa80`0552d040 00000000`00000000 00000000`00000080 00000000`00000001 : nt!MiModifiedPageWriter+0xcf
fffff880`033d9d40 fffff800`02caeb06 : fffff880`009b2180 fffffa80`0552d040 fffff880`009bd0c0 01cae06f`1f22b0c0 : nt!PspSystemThreadStartup+0x5a
fffff880`033d9d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+4c620
fffff800`02d082dc cc              int     3

SYMBOL_STACK_INDEX:  1

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

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4b88cfeb

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

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

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

 

[xfymars]

Below is the result. I'm not sure if this is the one needed, thank you so much, Ken!!

- System

- Provider


[ Name] Microsoft-Windows-Wininit


[ Guid] {206f6dea-d3c5-4d10-bc72-989f03c8b84b}


[ EventSourceName] Wininit


- EventID 1001


[ Qualifiers] 16384



Version 0


Level 4


Task 0


Opcode 0


Keywords 0x80000000000000

- TimeCreated


[ SystemTime] 2010-04-29T03:26:22.000000000Z



EventRecordID 1934


Correlation

- Execution


[ ProcessID] 0


[ ThreadID] 0



Channel Application


Computer Feiyu-PC435


Security
- EventData


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)... 87296 file records processed. File verification completed. 62 large file records processed. 0 bad file records processed. 2 EA records processed. 60 reparse records processed. CHKDSK is verifying indexes (stage 2 of 5)... 123904 index entries processed. Index verification completed. 0 unindexed files scanned. 0 unindexed files recovered. CHKDSK is verifying security descriptors (stage 3 of 5)... 87296 file SDs/SIDs processed. Cleaning up 288 unused index entries from index $SII of file 0x9. Cleaning up 288 unused index entries from index $SDH of file 0x9. Cleaning up 288 unused security descriptors. Security descriptor verification completed. 18305 data files processed. CHKDSK is verifying Usn Journal... 34601808 USN bytes processed. Usn Journal verification completed. CHKDSK is verifying file data (stage 4 of 5)... 87280 files processed. File data verification completed. CHKDSK is verifying free space (stage 5 of 5)... 18213893 free clusters processed. Free space verification is complete. Windows has checked the file system and found no problems. 102297599 KB total disk space. 29205112 KB in 68404 files. 46320 KB in 18306 indexes. 0 KB in bad sectors. 190591 KB in use by the system. 65536 KB occupied by the log file. 72855576 KB available on disk. 4096 bytes in each allocation unit. 25574399 total allocation units on disk. 18213894 allocation units available on disk. Internal Info: 00 55 01 00 c0 52 01 00 91 8c 02 00 00 00 00 00 .U...R.......... 11 01 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.