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: BSOD 0x0000007a after waked up from sleep.

09 Oct 2013   #1

Microsoft Windows 7 (6.1) 64-bit Service Pack 1 (Build 7601)
 
 
BSOD 0x0000007a after waked up from sleep.

Hi,

Sorry to bother you.
My Window7 occasionally got BSOD after wake-up from sleep mode.
Please refer to the attached files for dump and system information.
Please kindly help me, thank you very much.




Attached Files
File Type: zip SF_09-10-2013.zip (761.7 KB, 11 views)
File Type: zip 100913-9157-01.zip (36.0 KB, 1 views)
My System SpecsSystem Spec
.

09 Oct 2013   #2

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium 64Bit
 
 

Welcome to the forum.
Code:
Microsoft (R) Windows Debugger Version 6.2.9200.20512 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\USER\Downloads\SF_09-10-2013\SF_09-10-2013\100813-16068-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18229.amd64fre.win7sp1_gdr.130801-1533
Machine Name:
Kernel base = 0xfffff800`02c4e000 PsLoadedModuleList = 0xfffff800`02e916d0
Debug session time: Tue Oct  8 06:14:16.795 2013 (UTC + 6:00)
System Uptime: 0 days 13:12:57.365
Loading Kernel Symbols
...............................................................
................................................................
.................................................
Loading User Symbols
Loading unloaded module list
..........................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck F4, {3, fffffa800f061a60, fffffa800f061d40, fffff80002fca0d0}

----- ETW minidump data unavailable-----
Probably caused by : csrss.exe

Followup: MachineOwner
---------
Code:
Microsoft (R) Windows Debugger Version 6.2.9200.20512 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\USER\Downloads\SF_09-10-2013\SF_09-10-2013\100913-9157-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18229.amd64fre.win7sp1_gdr.130801-1533
Machine Name:
Kernel base = 0xfffff800`02c5e000 PsLoadedModuleList = 0xfffff800`02ea16d0
Debug session time: Wed Oct  9 18:10:34.469 2013 (UTC + 6:00)
System Uptime: 1 days 4:17:12.327
Loading Kernel Symbols
...............................................................
................................................................
..........................................................
Loading User Symbols
Loading unloaded module list
..............................................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 7A, {fffff6fc40032558, ffffffffc000000e, 8765abe0, fffff880064ab000}

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

Followup: MachineOwner
---------
7A and F4 are storage (hard drive) related bugchecks. Please complete the following steps:
Code:
Model	INTEL SSDSC2CW060A ATA Device
Quote   Quote: Originally Posted by writhziden View Post
If you have an SSD, make sure the following are up to date:
  • SSD firmware
  • BIOS Version
  • Chipset Drivers
  • Hard disk controller drivers/SATA drivers
  • If you have a Marvell IDE ATA/ATAPI device, make sure the drivers are up to date from the Intel site or Marvell site and not from your motherboard/vendor support site.
------------------------
Reduce the start-up items.------------
System File Checker
------------
Disk Check (Hard Drive)
My System SpecsSystem Spec
10 Oct 2013   #3

Microsoft Windows 7 (6.1) 64-bit Service Pack 1 (Build 7601)
 
 

Hi, koolkat77:

Thank you for reply.
I just finished Memtest. It took almost 23 hours to get Pass 7.
I will try your suggestion and let you know if any.
Thank you very much!
My System SpecsSystem Spec
.


10 Oct 2013   #4

Microsoft Windows 7 (6.1) 64-bit Service Pack 1 (Build 7601)
 
 

Hi,

FYI.
SSD firmware is 400i.
BIOS is v6.8.
Intel(R) 7 Series/C216 Chipset Family SATA AHCI Controller - 1E03 with driver v9.3.0.1011.


Attached Images
 
My System SpecsSystem Spec
10 Oct 2013   #5

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium 64Bit
 
 

Upload a screenshot using:Test your Hard Drive(s) by running:
My System SpecsSystem Spec
10 Oct 2013   #6

Microsoft Windows 7 (6.1) 64-bit Service Pack 1 (Build 7601)
 
 

koolkat77,

FYI.
By the way, is this INTEL SSD running in SATA/600 mode? I got very poor performance, didn't I?
IBSOD 0x0000007a after waked up from sleep.-2013-10-11_082929.jpg
BSOD 0x0000007a after waked up from sleep.-2013-10-11_083716.jpg
BSOD 0x0000007a after waked up from sleep.-2013-10-11_084829.jpg
Name:  mobile01-5247c1fd8b4c24f64217bb05313e64f9.jpg
Views: 13
Size:  129.4 KB


My System SpecsSystem Spec
10 Oct 2013   #7

Microsoft Windows 7 (6.1) 64-bit Service Pack 1 (Build 7601)
 
 

koolkat77,

Please refer to the system information file.
SystemInformation.zip


My System SpecsSystem Spec
11 Oct 2013   #8

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium 64Bit
 
 

Code:
*******************************************************************************
*                                                                             *
*                        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: fffff6fc40032558, lock type that was held (value 1,2,3, or PTE address)
Arg2: ffffffffc000000e, error status (normally i/o status code)
Arg3: 000000008765abe0, current process (virtual address for lock type 3, or PTE)
Arg4: fffff880064ab000, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)

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


ERROR_CODE: (NTSTATUS) 0xc000000e - A device which does not exist was specified.

DISK_HARDWARE_ERROR: There was error with disk hardware

BUGCHECK_STR:  0x7a_c000000e

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002d46742 to fffff80002cd3b80

STACK_TEXT:  
fffff880`03563708 fffff800`02d46742 : 00000000`0000007a fffff6fc`40032558 ffffffff`c000000e 00000000`8765abe0 : nt!KeBugCheckEx
fffff880`03563710 fffff800`02cfa91f : fffffa80`0ce1b870 fffff880`03563880 fffff800`02f0e540 fffffa80`0ce1b870 : nt! ?? ::FNODOBFM::`string'+0x36c1a
fffff880`035637f0 fffff800`02ce11b9 : 00000000`00000000 00000000`00000001 ffffffff`ffffffff 00000000`00000008 : nt!MiIssueHardFault+0x28b
fffff880`035638c0 fffff800`02d07700 : 00000000`00000001 fffff880`064ab000 fffffa80`0fc1ba00 fffff6fc`40032530 : nt!MmAccessFault+0x1399
fffff880`03563a20 fffff800`02d078f0 : fffffa80`0cdd67c0 fffffa80`00000001 fffffa80`00000000 fffff800`02c7cd62 : nt!MiInPageSingleKernelStack+0x134
fffff880`03563b30 fffff800`02d0787f : 00000000`00000000 00000000`00000001 fffffa80`0ca6bae0 00000000`00000080 : nt!MmInPageKernelStack+0x40
fffff880`03563b90 fffff800`02d075c4 : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`0ca6ba00 : nt!KiInSwapKernelStacks+0x1f
fffff880`03563bc0 fffff800`02f71bae : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeSwapProcessOrStack+0x84
fffff880`03563c00 fffff800`02cc48c6 : fffff880`009eb180 fffffa80`0ca96040 fffff880`009f5fc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`03563c40 00000000`00000000 : fffff880`03564000 fffff880`0355e000 fffff880`03563910 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+36c1a
fffff800`02d46742 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+36c1a

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  51fb06cd

FAILURE_BUCKET_ID:  X64_0x7a_c000000e_nt!_??_::FNODOBFM::_string_+36c1a

BUCKET_ID:  X64_0x7a_c000000e_nt!_??_::FNODOBFM::_string_+36c1a

Followup: MachineOwner
---------
It is good to know that there is no issue with the SSD. But, the crash dump says ....
Code:
ERROR_CODE: (NTSTATUS) 0xc000000e - A device which does not exist was specified.

DISK_HARDWARE_ERROR: There was error with disk hardware
So it appears that it is the RAMDisc that is causing the issue there.
Description RAMDiskVE
Size 2.00 GB (2,147,483,648 bytes)

Disable it in BIOS. then perform a clean reinstall.
Clean Reinstall - Factory OEM Windows 7
My System SpecsSystem Spec
11 Oct 2013   #9

Microsoft Windows 7 (6.1) 64-bit Service Pack 1 (Build 7601)
 
 

Hi,

I reinstalled OS without RAMDisk but still got BSOD. Very strange.
A dump file is attached.
101113-9438-01.zip


My System SpecsSystem Spec
17 Oct 2013   #10

Microsoft Windows 7 (6.1) 64-bit Service Pack 1 (Build 7601)
 
 

Hi,

I think my BSOD after wake-up from sleep is solved.
SATA ACHI Controller driver was changed from Microsoft to INTEL for 3 days, and no BSOD happened.
BSOD 0x0000007a after waked up from sleep.-2013-10-18_085917.png

I'll continue checking if any.
Thank you, sir!


My System SpecsSystem Spec
Reply

 BSOD 0x0000007a after waked up from sleep.




Thread Tools



Similar help and support threads for2: BSOD 0x0000007a after waked up from sleep.
Thread Forum
Solved BSOD everytime computer wakes from sleep, error 0x0000007a BSOD Help and Support
BSOD after waking computer from sleep error: 0x0000007A BSOD Help and Support
BSOD doing nothing, error 0x0000007A BSOD Help and Support
BSOD with STOP 0X0000007A BSOD Help and Support
Laptop waked up from hibernate on it's own Performance & Maintenance

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 05:45 PM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33