Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

BSOD when waking laptop from Sleep


  • Please log in to reply
11 replies to this topic

#1 chrisupi007

chrisupi007

  • Members
  • 35 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Puerto Rico
  • Local time:11:31 AM

Posted 01 December 2014 - 09:43 PM

I'm having BSOD most of the times I wake the laptop form sleep mode, it didn't happen back in Vista. Here is the dump:

 

==================================================
Dump File         : 120114-56906-01.dmp
Crash Time        : 12/1/2014 7:45:36 PM
Bug Check String  : KERNEL_DATA_INPAGE_ERROR
Bug Check Code    : 0x0000007a
Parameter 1       : fffff6e0`00b2f620
Parameter 2       : ffffffff`c000003f
Parameter 3       : 00000000`1f022880
Parameter 4       : ffffc001`65ec4000
Caused By Driver  : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+153ca0
File Description  : NT Kernel & System
Product Name      : Microsoft® Windows® Operating System
Company           : Microsoft Corporation
File Version      : 6.3.9600.17238 (winblue_gdr.140723-2018)
Processor         : x64
Crash Address     : ntoskrnl.exe+153ca0
Stack Address 1   :
Stack Address 2   :
Stack Address 3   :
Computer Name     :
Full Path         : C:\Windows\Minidump\120114-56906-01.dmp
Processors Count  : 2
Major Version     : 15
Minor Version     : 9600
Dump File Size    : 301,544
Dump File Time    : 12/1/2014 7:49:24 PM
==================================================

 

 



BC AdBot (Login to Remove)

 


#2 splico

splico

  • Members
  • 157 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Croatia
  • Local time:04:31 PM

Posted 05 December 2014 - 03:51 PM

The error code KERNEL_DATA_INPAGE_ERROR STOP: 0x0000007A states that the requested page of kernel data from the paging file could not be read into memory. It appears that there are some issues with the hard disk.

Use check disk command for any errors on hard disk -

Warning: Microsoft does not recommend interrupting the CHKDSK process. Microsoft does not guarantee the integrity of the disk if the CHKDSK program is interrupted. For safety you can back up your data before using the check disk command.

Use the check disk commands as follows:
 1. Click Start. 
 2. In search window type 'cmd' and ENTER. Right click and select 'Run as administrator'.
 3. Type at the command prompt CHKDSK /P and press ENTER to scan the disk.
 4. Then type CHKDSK C: /F /R and press ENTER to repair corrupt sectors, if there are any.

NOTE: The root drive has to be C: and the command may schedule a task at the system startup, if it does, then press Y to schedule a task and restart the computer to perform chkdsk.
Once chkdsk completes, boot to the desktop and then check.


BTW what size is your HDD drive? There is a hotfix for similar symptoms in Windows 7 when you have large SATA drive:

http://support.microsoft.com/kb/977178

But please first try CheckDisk.

 

Hope this helps. Let us know the results.


Edited by splico1985, 05 December 2014 - 03:55 PM.

 "Helpdesk: There is an icon on your computer labeled "My Computer". Double click on it.
User: What's your computer doing on mine?"


#3 dc3

dc3

    Bleeping Treehugger


  • Members
  • 30,683 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:Sierra Foothills of Northern Ca.
  • Local time:08:31 AM

Posted 06 December 2014 - 12:16 PM

In Windows 8/8.1 there is a much simpler way to open the Elevated Command Prompt.

 

Press the Windows key windowskey_zps092d5c75.png and the X key.   A menu will open with the option Command Prompt (Admin), click on this.
 
If the chkdsl /r doesn't resolve this issue please run SeaTool for Windows.
 

Please download and run SeatTool for Windows.
 
When the website opens scroll down till you find the I Accept button and click on it.
 
If you scroll down below this button you will find instruction for installing this.
 
Once you install this program you will see an image similar to the one below.
 
seagate3_zps1fa1f71c.jpg
 
1.  SeaTools for Windows will search for hdds on your computer.  Please remove any external storage devices connected via USB port.
 
2.  Detected Drives will list the hdd/s found.  Place a check mark in the drive you want to run the scan on.
 
3.  You will see Basic Tests above Detected Drives, move the mouse pointer over this.
 
4.  A menu will open with options for different scans, please click on Long Generic Test
 
5.  This will start the scan.  When the scan is complete you will see the result under Test Status , please post the results in your topic.  

Family and loved ones will always be a priority in my daily life.  You never know when one will leave you.

 

 

 

 


#4 chrisupi007

chrisupi007
  • Topic Starter

  • Members
  • 35 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Puerto Rico
  • Local time:11:31 AM

Posted 13 December 2014 - 08:15 PM

1. Here's the SeaTools logs:

 

 

--------------- SeaTools for Windows v1.2.0.10 ---------------
12/6/2014 9:23:27 PM
Model: Hitachi HTS543216L9A300
Serial Number: 090404FB2200VCEH9Y2A
Firmware Revision: FB2OC40C
Identify - Started 12/6/2014 9:23:27 PM
Identify - Started 12/6/2014 9:24:25 PM
Long Generic - Started 12/6/2014 9:27:23 PM
Long Generic - Started 12/12/2014 1:18:49 PM
Long Generic - Pass 12/12/2014 2:33:06 PM
 

 

--------------- SeaTools for Windows v1.2.0.10 ---------------
12/6/2014 9:23:27 PM
Model: WDC WD5000BPVT-00HXZT1
Serial Number: WD-WX41A2181990
Firmware Revision: 01.01A01
Identify - Started 12/6/2014 9:23:27 PM
Identify - Started 12/6/2014 9:24:25 PM
Identify - Started 12/6/2014 9:24:50 PM
Long Generic - Started 12/6/2014 9:27:24 PM
Long Generic - Started 12/12/2014 1:18:50 PM
Long Generic - Pass 12/12/2014 3:57:22 PM

 

 

2. Here's more bsod dumps:

 

 

==================================================
Dump File         : 120614-127218-01.dmp
Crash Time        : 12/6/2014 11:20:23 AM
Bug Check String  : KERNEL_DATA_INPAGE_ERROR
Bug Check Code    : 0x0000007a
Parameter 1       : fffff6e0`00eb5870
Parameter 2       : ffffffff`c000003f
Parameter 3       : 00000000`37452820
Parameter 4       : ffffc001`d6b0e434
Caused By Driver  : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+153ca0
File Description  : NT Kernel & System
Product Name      : Microsoft® Windows® Operating System
Company           : Microsoft Corporation
File Version      : 6.3.9600.17238 (winblue_gdr.140723-2018)
Processor         : x64
Crash Address     : ntoskrnl.exe+153ca0
Stack Address 1   :
Stack Address 2   :
Stack Address 3   :
Computer Name     :
Full Path         : C:\Windows\Minidump\120614-127218-01.dmp
Processors Count  : 2
Major Version     : 15
Minor Version     : 9600
Dump File Size    : 301,488
Dump File Time    : 12/6/2014 11:34:47 AM
==================================================

==================================================
Dump File         : 120814-58609-01.dmp
Crash Time        : 12/8/2014 2:38:18 PM
Bug Check String  : KERNEL_DATA_INPAGE_ERROR
Bug Check Code    : 0x0000007a
Parameter 1       : fffff6fc`00481a08
Parameter 2       : ffffffff`c000003f
Parameter 3       : 00000000`18fb4860
Parameter 4       : fffff800`90341c3c
Caused By Driver  : dxgkrnl.sys
Caused By Address : dxgkrnl.sys+b9c3c
File Description  : DirectX Graphics Kernel
Product Name      : Microsoft® Windows® Operating System
Company           : Microsoft Corporation
File Version      : 6.3.9600.17210 (winblue_gdr.140612-1509)
Processor         : x64
Crash Address     : ntoskrnl.exe+153ca0
Stack Address 1   :
Stack Address 2   :
Stack Address 3   :
Computer Name     :
Full Path         : C:\Windows\Minidump\120814-58609-01.dmp
Processors Count  : 2
Major Version     : 15
Minor Version     : 9600
Dump File Size    : 301,408
Dump File Time    : 12/8/2014 2:41:26 PM
==================================================

==================================================
Dump File         : 121214-73015-01.dmp
Crash Time        : 12/12/2014 1:10:24 PM
Bug Check String  :
Bug Check Code    : 0xc000021a
Parameter 1       : ffffc001`f16460d0
Parameter 2       : 00000000`00000000
Parameter 3       : 00000000`00000000
Parameter 4       : 00000000`00000000
Caused By Driver  : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+153ca0
File Description  : NT Kernel & System
Product Name      : Microsoft® Windows® Operating System
Company           : Microsoft Corporation
File Version      : 6.3.9600.17238 (winblue_gdr.140723-2018)
Processor         : x64
Crash Address     : ntoskrnl.exe+153ca0
Stack Address 1   :
Stack Address 2   :
Stack Address 3   :
Computer Name     :
Full Path         : C:\Windows\Minidump\121214-73015-01.dmp
Processors Count  : 2
Major Version     : 15
Minor Version     : 9600
Dump File Size    : 300,088
Dump File Time    : 12/12/2014 1:13:43 PM
==================================================

==================================================
Dump File         : 121314-82375-01.dmp
Crash Time        : 12/13/2014 4:32:25 AM
Bug Check String  : KERNEL_DATA_INPAGE_ERROR
Bug Check Code    : 0x0000007a
Parameter 1       : fffff6e8`0081a1d0
Parameter 2       : ffffffff`c000003f
Parameter 3       : 00000000`a8687be0
Parameter 4       : ffffd001`0343a000
Caused By Driver  : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+153ca0
File Description  : NT Kernel & System
Product Name      : Microsoft® Windows® Operating System
Company           : Microsoft Corporation
File Version      : 6.3.9600.17238 (winblue_gdr.140723-2018)
Processor         : x64
Crash Address     : ntoskrnl.exe+153ca0
Stack Address 1   :
Stack Address 2   :
Stack Address 3   :
Computer Name     :
Full Path         : C:\Windows\Minidump\121314-82375-01.dmp
Processors Count  : 2
Major Version     : 15
Minor Version     : 9600
Dump File Size    : 301,536
Dump File Time    : 12/13/2014 2:41:16 PM
==================================================



#5 dc3

dc3

    Bleeping Treehugger


  • Members
  • 30,683 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:Sierra Foothills of Northern Ca.
  • Local time:08:31 AM

Posted 14 December 2014 - 09:42 AM

Please download and install Speccy to provide us with information about your computer.  When  FileHippo opens, click on Download latest version in the upper right pane.
 
When Speccy opens you will see a screen similar to the one below.
 
speccy9_zps2d9cdedc.png
 
Click on File which is outlined in red in the screen above, and then click on Publish Snapshot.
 
The following screen will appear, click on Yes.
 
speccy7_zpsfa02105f.png
 
The following screen will appear, click on Copy to Clipboard.
 
speccy3_zps1791b093.png
 
In your next post right click inside the Reply to Topic box, then click on Paste.  This will load a link to the Speccy log.

Family and loved ones will always be a priority in my daily life.  You never know when one will leave you.

 

 

 

 


#6 chrisupi007

chrisupi007
  • Topic Starter

  • Members
  • 35 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Puerto Rico
  • Local time:11:31 AM

Posted 15 December 2014 - 06:11 PM

Here's the Speccy Snapshot: http://speccy.piriform.com/results/6kg2Llzo5ge14W4AxCgv2vm



#7 chrisupi007

chrisupi007
  • Topic Starter

  • Members
  • 35 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Puerto Rico
  • Local time:11:31 AM

Posted 15 December 2014 - 10:11 PM

Update, I tried to open Control Panel por Programs & Features and got the error:The application has failed to start due to a side-by-side configuration error.

I restarted and now I get BSOD on boot:

Attached Files



#8 dc3

dc3

    Bleeping Treehugger


  • Members
  • 30,683 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:Sierra Foothills of Northern Ca.
  • Local time:08:31 AM

Posted 16 December 2014 - 01:52 PM

Did you try restarting after the data was collected?


Family and loved ones will always be a priority in my daily life.  You never know when one will leave you.

 

 

 

 


#9 chrisupi007

chrisupi007
  • Topic Starter

  • Members
  • 35 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Puerto Rico
  • Local time:11:31 AM

Posted 16 December 2014 - 01:55 PM

Yes, I tried restarting various times, still BSOD at boot

#10 chrisupi007

chrisupi007
  • Topic Starter

  • Members
  • 35 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Puerto Rico
  • Local time:11:31 AM

Posted 16 December 2014 - 10:31 PM

UPDATE: I formated the drive and did a clean install of Windows Vista (factory OS) and had no problems since then! I'll install updates, test and see how it goes.



#11 chrisupi007

chrisupi007
  • Topic Starter

  • Members
  • 35 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Puerto Rico
  • Local time:11:31 AM

Posted 08 February 2015 - 01:37 AM

SOLVED

 

No issues since Vista clean install, here's the new speccy: http://speccy.piriform.com/results/4AYVZrpk8WFcsBfyquY7add.



#12 dc3

dc3

    Bleeping Treehugger


  • Members
  • 30,683 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:Sierra Foothills of Northern Ca.
  • Local time:08:31 AM

Posted 08 February 2015 - 12:04 PM

Glad to hear that you have resolved your problem.

 

Speccy only reports information regarding hardware, it does not repair anything.  


Family and loved ones will always be a priority in my daily life.  You never know when one will leave you.

 

 

 

 





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users