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

Computer Won't Sleep and BOSD


  • Please log in to reply
7 replies to this topic

#1 drewer

drewer

  • Members
  • 4 posts
  • OFFLINE
  •  
  • Local time:01:54 AM

Posted 21 January 2013 - 01:31 AM

I've been getting nowhere try to solve this on my own so here is the situation:
1. I have have issues with the computer not sleeping properly for the last couple months. Occasionally, instead of sleeping the screen will turn off but the computer will keep running and none of the keys will work, leaving the computer stuck in this state until I restart it manually or the battery dies.

2. In the last month or so, I started getting BOSDs. Here are the details from the BlueScreenViewer:

==================================================
Dump File : 012113-45443-01.dmp
Crash Time : 1/21/2013 12:56:24 AM
Bug Check String : BAD_POOL_HEADER
Bug Check Code : 0x00000019
Parameter 1 : 00000000`00000020
Parameter 2 : fffffa80`0885eba0
Parameter 3 : fffffa80`0885edb0
Parameter 4 : 00000000`042100b2
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+7efc0
File Description : NT Kernel & System
Product Name : Microsoftฎ Windowsฎ Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17944 (win7sp1_gdr.120830-0333)
Processor : x64
Crash Address : ntoskrnl.exe+7efc0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\windows\Minidump\012113-45443-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 266,376
==================================================

==================================================
Dump File : 011413-27580-01.dmp
Crash Time : 1/14/2013 9:05:01 PM
Bug Check String : BAD_POOL_HEADER
Bug Check Code : 0x00000019
Parameter 1 : 00000000`00000020
Parameter 2 : fffffa80`08aad840
Parameter 3 : fffffa80`08aada50
Parameter 4 : 00000000`04210047
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+7efc0
File Description : NT Kernel & System
Product Name : Microsoftฎ Windowsฎ Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17944 (win7sp1_gdr.120830-0333)
Processor : x64
Crash Address : ntoskrnl.exe+7efc0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\windows\Minidump\011413-27580-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 266,376
==================================================

==================================================
Dump File : 011013-31886-01.dmp
Crash Time : 1/10/2013 11:08:07 PM
Bug Check String :
Bug Check Code : 0x00000124
Parameter 1 : 00000000`00000000
Parameter 2 : fffffa80`08573028
Parameter 3 : 00000000`be000000
Parameter 4 : 00000000`00800400
Caused By Driver : hal.dll
Caused By Address : hal.dll+12a3b
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+7efc0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\windows\Minidump\011013-31886-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 275,264
==================================================

==================================================
Dump File : 010913-33477-01.dmp
Crash Time : 1/9/2013 7:02:44 PM
Bug Check String :
Bug Check Code : 0x00000124
Parameter 1 : 00000000`00000000
Parameter 2 : fffffa80`08563028
Parameter 3 : 00000000`be000000
Parameter 4 : 00000000`00800400
Caused By Driver : hal.dll
Caused By Address : hal.dll+12a3b
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+7efc0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\windows\Minidump\010913-33477-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 266,936
==================================================

==================================================
Dump File : 121112-16801-01.dmp
Crash Time : 12/11/2012 8:08:05 PM
Bug Check String : BAD_POOL_HEADER
Bug Check Code : 0x00000019
Parameter 1 : 00000000`00000020
Parameter 2 : fffffa80`073ae000
Parameter 3 : fffffa80`073ae210
Parameter 4 : 00000000`04210000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+7efc0
File Description : NT Kernel & System
Product Name : Microsoftฎ Windowsฎ Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17944 (win7sp1_gdr.120830-0333)
Processor : x64
Crash Address : ntoskrnl.exe+7efc0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\windows\Minidump\121112-16801-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 266,376
==================================================


I've updated all the driver I could find, but haven't tried a clean install yet (I do have everything backed up) and have run AVG antivirus which hasn't come up with anything. I appreciate any help.

BC AdBot (Login to Remove)

 


#2 Artrooks

Artrooks

  • Members
  • 1,463 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New York
  • Local time:02:54 AM

Posted 21 January 2013 - 08:32 AM

Welcome drewer, :)

If we could gather a little more information about the problem computer, it might prove helpful in pointing toward a solution.

1. ) Please follow this link: BSOD Posting Instructions Windows 8 - Windows 7 - Vista.
  • Follow all instructions with the exception of:
    • Create a new thread HERE and attach the file(s) after step 4
  • Note: Both files of Step 1 need to be in the Documents folder.
Next, Upload the zipped folder to a File Sharing website of your choosing because Bleeping Computer has a 512 K only upload limit and this file will be much larger.
2. ) To help us get a better look at your computer's hardware, please download and install Speccy by Piriform. (mirror site)
  • Run Speccy and from the top menu, select File --> Publish Snapshot. Click "Yes" to proceed.
  • Click, Copy to Clipboard and paste this address into your next post.
3. ) Please download MiniToolBox by farbar, save it to your Desktop, then run it.
  • Check the following checkbox:
    • List Installed Programs
  • Please click Go.
    • Post the contents of (Result.txt).
    • A copy of Result.txt will be saved in the same directory the tool is run.

Regards,
Brooks



 


#3 drewer

drewer
  • Topic Starter

  • Members
  • 4 posts
  • OFFLINE
  •  
  • Local time:01:54 AM

Posted 21 January 2013 - 12:36 PM

http://www.mediafire.com/?8cm4t3n8119tt3c (Windows7_Vista_jcgriff2.zip)

http://speccy.piriform.com/results/j7eO6OYVXR8DnuIrqZRco6N (Speccy)

http://www.mediafire.com/view/?ehbyeygs6l4uu5o (MiniToolBox)

#4 Artrooks

Artrooks

  • Members
  • 1,463 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New York
  • Local time:02:54 AM

Posted 21 January 2013 - 05:15 PM

Hello drewer,

Thank you for supplying that information. :) I'll deal with the BSOD issue first.

(1.) Your computer is running more than one anti-virus program.
  • Having two or more anti-virus programs running at the same time can cause your computer to run slowly, become unstable and in rare cases, crash.
  • AVG 2013
  • Microsoft Security Essentials
My suggestion is to uninstall AVG 2013. Because you are experiencing blue screen issues, Microsoft Security Essentials is more stable and "plays better" with the MS operating system. Feel free to install any anti-virus software of your choosing when the blue screen issues abate.


(2.) STOP 0x00000124: WHEA_UNCORRECTABLE_ERROR
Usual causes: Hardware, Incompatibility, May be driver corruption

Also see Stop 0x124 - what it means and what to try

Your 0x124 bug checks blame the processor, but it is highly likely that other hardware or poorly performing drivers are responsible. The goal is to rule out other hardware and software influences. Processors can go bad but it's not common.

x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor @ fffffa8008573138
Section @ fffffa80085732c0
Offset : 664
Length : 264
Flags : 0x00000000
Severity : Fatal

Error : Internal timer (Proc 3 Bank 3)
Status : 0xbe00000000800400
Address : 0x0000388002e478c0
Misc. : 0x000000000003ffff


Your 0x124 bug checks also flag the following driver.

*** WARNING: Unable to verify timestamp for k57nd60a.sys
*** ERROR: Module load completed but symbols could not be loaded for k57nd60a.sys
k57nd60a.sys	Fri Apr 01 00:05:37 2011
k57nd60a.sys - Broadcom NetLink ™ Gigabit Ethernet Driver

Try to update this driver via the Lenovo website for your particular notebook model. It looks as if you are using the Intel WiFi to connect to the internet.
  • If you can't update the Broadcom driver, then see if the adapter can be disabled in BIOS.
  • If it can be, then as a test, uninstall the Broadcom NetLink ™ Gigabit Ethernet adapter in device manager, reboot, enter BIOS, then disable it.

(3.) RE: SlimDrivers

I don't recommend third party driver download software nor do I recommend Microsoft Updates for third party drivers. They may deliver drivers that are similar but aren't tested for compatibility with your particular hardware. That can lead to system instability and BSODs. This is particularly important with notebook computers where drivers need to work very closely with the installed hardware for energy saving modes.

The only place to obtain reliable, stable drivers for your hardware is from the computer manufacturer's or hardware manufacturer's website.

  • If your computer is an OEM product (Sony, Dell, HP, etc.), the best drivers for your specific model would be found on their website.
  • If your system is home built, then the best drivers will be found on the motherboard site (Gigabyte, Asus, etc) and the manufacturer's website of any add-on components (graphics - nVidia, ATI, etc).



BSOD Bug Check Code: For informational purposes only.
Spoiler

Regards,
Brooks



 


#5 drewer

drewer
  • Topic Starter

  • Members
  • 4 posts
  • OFFLINE
  •  
  • Local time:01:54 AM

Posted 21 January 2013 - 06:24 PM

Hi Artrooks,
I followed your advise so far and this is the status:

1. Uninstalled AVG Antivirus

2. Uninstalled Broadcom driver and re-installed via the download from the Lenovo website. Do you recommend uninstalling this as well and disabling it in BIOS or just wait to see what happens?

3. Uninstalled SlimDriver

Under the "Stop 0x124 - what it means and what to try", number 6 suggests running MDSCHED to check the memory. When I tried to do so I got this message: "Windows cannot check for memory problems. An error is preventing Windows from checking for memory problems during startup. To run the Windows Memory Diagnostic manually, boot the computer from the Windows installation disc, and then select Windows Memory Diagnostic from the Windows Boot Manager menu."

I should note that I had replaced my memory about a month ago as an upgrade to 6GB of memory. Could my computer be rejecting it or some other incompatibility?

#6 Artrooks

Artrooks

  • Members
  • 1,463 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New York
  • Local time:02:54 AM

Posted 21 January 2013 - 07:21 PM

Hello,

Uninstalled Broadcom driver and re-installed via the download from the Lenovo website. Do you recommend uninstalling this as well and disabling it in BIOS or just wait to see what happens?

Let's see how the re-installation goes. If it shows up in another bug check, you can then disable the adapter.


Regarding testing memory, please follow this post: Windows 7 - RAM - Test with Memtest86+ to either create a bootable CD (Method 2) or bootable USB flash drive (Method 1) to run the test.
  • Once the computer is booted from the CD or USB flash drive, MemTest86+ will start automatically and continue until you stop it by pressing the ESC key.
  • My recommendation would be to run MemTest86+ overnight; at least 12 hours rather than just 7 passes.
    • There should be NO errors reported.
    • The test can be stopped by pressing the ESC key as soon as an error is reported or after a suitable testing period without errors .
  • See Part 3: If you have errors.
    • Warning: If your computer is still under warranty, opening the case to remove memory for testing purposes, may VOID that warranty.

Let us know if there are any new BSODs.

Regards,
Brooks



 


#7 drewer

drewer
  • Topic Starter

  • Members
  • 4 posts
  • OFFLINE
  •  
  • Local time:01:54 AM

Posted 24 January 2013 - 11:23 PM

So far so good. I was wondering about the original issue though, the problem with the computer not going to sleep properly. I've noticed that when it does seem to stall the fan starts kicking into overdrive (even if it was running normally before I tried to put the computer to sleep) and starts blowing a lot of hot air.

#8 Artrooks

Artrooks

  • Members
  • 1,463 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New York
  • Local time:02:54 AM

Posted 25 January 2013 - 11:51 AM

Hello,

Regarding the intermittent sleep issue:

When looking at your System event log, I see this entry occurring with relative frequency:

Log Name: System
  Source: Microsoft-Windows-Kernel-Power
  Date: 2013-01-21T11:16:06.857
  Event ID: 89
  Task: N/A
  Level: Information
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: Jacob-Y470
  Description: 
ACPI thermal zone ACPI\ThermalZone\TZ00 has been enumerated. 			
_PSV = 400K 			
_TC1 = 2 			
_TC2 = 5 			
_TSP = 1000ms 			
_AC0 = 343K 			
_AC1 = 328K 			
_AC2 = 0K 			
_AC3 = 0K 			
_AC4 = 0K 			
_AC5 = 0K 			
_AC6 = 0K 			
_AC7 = 0K 			
_AC8 = 0K 			
_AC9 = 0K 			
_CRT = 400K 			
_HOT = 400K 			
_PSL - see event data.

This could be caused by a hot CPU as further indicated by the sudden fan speed increase and hot air exiting that you describe during the failed sleep episodes.

I found one Lenovo Forum post re:"ACPI thermal zone ACPI\ThermalZone\TZ00 has been enumerated" that recommended to update Power Management and BIOS.
  • See post here
  • Warning: Do NOT use the download links in that post as they pertain to a different Lenovo system.
I would try the above first.

Regards,
Brooks



 





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users