BSOD guaranteed on Wake from Sleep Mode - refurbished HP desktop

[Lestertrey]

Hello and thanks for all of the great information I found here. In a nutshell, I get a BSOD, every time the CPU wakes up from sleep mode.

After reading many of the posts here, I thought maybe I could trouble shoot this myself. Ran a memory check and a DSKCHK, updated the BIOS, updated lots of model specific drivers from the HP website (but obviously not the right ones.) Downloaded Whocrashed, downloaded the MS SDK debugging tools. And gave up when I didn't have the right SYMBOLS pack. I tried, I really tried, for hours and hours. So today's event log is probably bloated from my failed efforts, and I apologize if that makes it harder. I included an older less cluttered version of the SF Diagnostic tools output from yesterday, before I undertook all of those efforts.


There seem to be two recurring issues:

This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x7A (0x20, 0xFFFFFFFFC000009D, 0xFFFFFA8004E84078, 0x0)
Error: KERNEL_DATA_INPAGE_ERROR

This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA8005C22240, 0xFFFFFA8005C22520, 0xFFFFF80002DDD7B0)
Error: CRITICAL_OBJECT_TERMINATION


Thanks for your assistance.
Lester

I got this as an off-lease refurb from Tiger Direct. Aside form the sleep=death problem, I really like the machine (upgrading from XP and Vista.)

Hewlett-Packard HP Compaq dc7900 Small Form Factor
Board: Hewlett-Packard 3031h
3992 Megabytes Usable Installed Memory
Intel(R) Q45/Q43 Express Chipset [Display adapter] (2x)

2.53 gigahertz Intel Core2 Duo
64 kilobyte primary memory cache
3072 kilobyte secondary memory cache
64-bit ready
Multi-core (2 total)
Not hyper-threaded

ATAPI DVD D DH16D3S ATA Device [Optical drive]

Hitachi HDS721010KLA330 [Hard drive] (1000.20 GB) -- drive 0, s/n GTE000PAJZ0EGE, rev GKAOA9DA, SMART Status: Healthy

 

[HonorGamer]

Hello,

Well it seems this one could be a multiple of problems.

First off I suggest for the time being uninstall norton, and install Microsoft Security Essentials - Microsoft Windows Do a full scan.

Also I suggest installing https://www.malwarebytes.org/ Install the free version. Make sure on the installer, uncheck that you want to use the trial version.

We are gonna try and knock it all out in a single post. So do 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 Windows 7) (winlogon for XP).
Copy/paste the results into your next post.

http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

BugCheck 0x124

You have a 0x124 hardware bugcheck. If the system is still under warranty, I would recommend sending it in to have diagnostic tests done and any bad hardware replaced.

   Warning

Before you proceed with the following, answer these two questions: Are you still under warranty? Does your warranty allow you to open up the machine to check hardware? If you are unsure of the answers to these questions, contact your system manufacturer. :warn:WARNING: The steps that follow can void your warranty!!!

For your hardware stop 0x124 crash, read through http://www.sevenforums.com/crash-lockup-debug-how/35349-stop-0x124-what-means-what-try.html and use the following hardware checks to supplement that link.

• If you are overclocking any hardware, please stop.
  
  
• 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.
  
  
• Run all but the advanced tests with SeaTools for HDDs.
  SeaTools for Windows
  
  SeaTools for DOS​
  
  
• Monitor temperatures during the following tests.
  
  Use the following programs to monitor the temperatures.​
  • Real Temp is a good CPU temperature monitor.
  • Speccy - System Information - Free Download will monitor all hardware temperatures.
  • HWiNFO, HWiNFO32 & HWiNFO64 - Hardware Information and Analysis Tools can be inaccurate for CPU temperatures, but is a good program for GPU temperature monitoring.
  • Use FurMark: VGA Stress Test, Graphics Card and GPU Stability Test, Burn-in Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net to test the graphics card GPU. Let it run until the GPU temperatures even out or until the GPU temperatures reach a dangerous level (you can find the max temperature for your card on either the nVidia or AMD sites; if you are not sure, ask us). The goal is to get a steady temperature, find out if the GPU is overheating, or to see if there are any artifacts present in the test itself: look for strange pixelated patterns on the screen or colors that do not look like they belong. Then use the |MG| Video Memory Stress Test 1.7.116 Download to test your graphics card memory. Let the memory test run for at least seven passes; the more the better.
    
    
  • Run http://www.sevenforums.com/tutorials/100352-hardware-stress-test-prime95.html to determine any hardware problems. Run all three tests for a few hours each. If you get errors, stop the test and post back here.
    
    
  • Follow the steps for doing CPU stress test using IntelBurnTest
  
  
• Run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).
  
  For Part 3: If You Have Errors: If you swap any memory components, follow these steps for ESD safety:
  1. Shut down and turn off your computer.
  2. Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
  3. Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
  4. Make sure you are grounded by using proper grounding techniques, i.e. work on an anti-static workbench, anti-static desk, or an anti-static pad. Hold something metallic while touching it to the anti-static surface, or use an anti-static wristband to attach to the anti-static material while working. If you do not have an anti-static workbench, desk, or pad, you can use your computer tower/case by finding a metal hold in it, such as a drive bay.
  Once these steps have been followed, it is safe to remove and replace components within your computer.

Remember to read closely through http://www.sevenforums.com/crash-lockup-debug-how/35349-stop-0x124-what-means-what-try.html for the crash.
​

Coutesy of: writhziden

After all of this, please post back. And remember when you are doing the stress tests, make sure you are monitoring your temps.

-Gamer

 

[Lestertrey]

I know I ran CHKDSK, but don't see it in the log, so I would guess that PC went to sleep and crashed. Since then I have disabled sleep mode as a stop gap, and that's working, I will run CHKDSK again. Thanks again, this really is a great site I've learned a lot trouble shooting this. The last machine I built from the ground up ran WIN95, when I was young and had time to play. I was never an expert, and now I'm quite rusty and obsolete.

More to come,
Les

 

[HonorGamer]

Thanks for the update, and please post back!

-Gamer

 

[Brutusfly]

Same PC, same issue

Having the same issue with a nearly identical hp dc7900 sff pc. I've replaced nearly all drivers and flashed the bios. Changes to BIOS settings have so far not helped. I'll be more cautious about buying hp next time, as I don't foresee a solution other than wasting power by not sleeping the pc.:sarc: