BSOD on sleep/hibernate

andyhostetler · 06 Jul 2019

I am getting a BSOD often when my PC goes into sleep mode. It is not every time, and the error codes I'm getting are different. This started about a month ago and has generated CRITICAL STRUCTURE CORRUPTION, KERNEL THREAD PRIORITY FLOOR VIOLATION, IRQL NOT LESS OR EQUAL, PAGE FAULT IN NONPAGED AREA, ATTEMPTED WRITE TO READ ONLY MEMORY (most recently), and others I don't recall or have pictures of. I made sure all Windows updates were installed and have run both Windows Memory Diagnostic (all good) and MemTest86+ (10+ passes with no errors). Every crash that I've looked into (that is, since I've been really trying to fix this) has had ntoskrnl.exe listed, though I've read that is a catch-all sometimes and doesn't really mean that file is problematic. The computer runs fine while I'm using it. Only when it sleeps does it crash. The most recent minidump is attached. Thank you,
Andy

MrPepka · 06 Jul 2019

1. Run Driver Verifier
2. Select "Create custom settings (for code developers)"
3. Select all standard settings and 2 additional options (Force pending I/O request, IRP Logging)
4. Select "Select driver names from a list"
5. Select all drivers except Microsoft drivers
6. Reboot computer

jdc1 · 06 Jul 2019

ntoskrnl.exe is the kernel (core) of the Windows operating system.
If there was a significant problem with this file, Windows wouldn't be working as well as it is now.

Only one minidump makes it harder to figure out the problem, please (in the future) don't delete any of the older minidumps until they've been uploaded here.

BIOS dates from 2008. I suggest visiting the HP support site for your model and obtaining the latest BIOS update.
I also am concerned that HP may no longer be supporting this model and it may not be compatible w/Win10.

Please update your AMD video drivers to the latest available version from the AMD website: https://www.amd.com/en/support
Please update your audio drivers to the latest available version available at the Realtek website: PC Audio Codecs > High Definition Audio Codecs Software - REALTEK

This may be a bit difficult as the system is so old. I attempted to locate the s3700f model on the HP US website and was unable to find it. As such I'm not able to advise on the exact models for the video and audio cards.
dxdiag shows the video card to be a Radeon HD 5000/6000/7350/8350 Series
MSINFO32 shows the audio card to be a Realtek High Definition Audio device

If this doesn't fix things, I'd suggest running Driver Verifier according to these instructions: Enable and Disable Driver Verifier in Windows 10
Once the system crashes, reboot to ensure a minidump was created.
Then zip up the minidump and upload it with your next post.

zbook · 06 Jul 2019

1) Open administrative command prompt and type or copy and paste:
2) sfc /scannow
3) dism /online /cleanup-image /restorehealth
4) wmic recoveros set autoreboot = false
5) Powercfg -h off
6) When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread

7) chkdsk /r /v
This may take hours to run so plan to run overnight.
Run on all drives using the syntax: chkdsk /r /v C: or chkdsk /r /v D: changing the drive letter to the applicable drive.

C:\Windows\system32>chkdsk /r /v
The type of the file system is NTFS.
Cannot lock current drive.

Chkdsk cannot run because the volume is in use by another
process. Would you like to schedule this volume to be
checked the next time the system restarts? (Y/N)

Type: Y
reboot

8) Use the information in this link to find the chkdsk report in the event viewer. Copy and paste into notepad > save to desktop > post into the thread using one drive or drop box share link:
Read Chkdsk Log in Event Viewer in Windows 10 Windows 10 Performance Maintenance Tutorials
Read Chkdsk Log in Event Viewer in Windows 10

9) In the left lower corner search type: system or system control > open system control panel > on the left pane click advanced system settings

a) > on the advanced tab under startup and recovery > click settings > post an image of the startup and recovery window into the thread

b) > on the advanced tab under performance > click on settings > on the performance options window > click on the advanced tab > under virtual memory > click on change > post an image of the virtual memory window into the thread

10) For any BSOD:

a) run the V2 log collector to collect new log files

b) open file explorer> this PC > C: > in the right upper corner search for: C:\Windows\memory.dmp
> if the file size is < 1.5 GB then zip > post a separate share link into the thread using one drive, drop box, or google drive

11) Download and install HP diagnostics windows: (right upper area of this link)
HP PC Hardware Diagnostics | HP(R) Official Site

12) Launch the application > click system tests > click system extensive test tab > click run once (run overnight) > the next day click component tests > run all (some are interactive) > click test logs > post an image of the results into the thread

13) Open the HP website > support > software and drivers Access Denied > enter the product or serial number or model > select the operating system > view drivers > post a URL or hyperlink into the thread

andyhostetler · 06 Jul 2019

zbook said:

1) Open administrative command prompt and type or copy and paste:

Microsoft Windows [Version 10.0.18362.207]
(c) 2019 Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>sfc /scannow

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.

C:\WINDOWS\system32>dism /online /cleanup-image /restorehealth

Deployment Image Servicing and Management tool
Version: 10.0.18362.1

Image Version: 10.0.18362.207

[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.

C:\WINDOWS\system32>wmic recoveros set autoreboot = false
Updating property(s) of '\\DESKTOP-PQFP9T0\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Home|C:\\WINDOWS|\\Device\\Harddisk0\\Partition1"'
Property(s) update successful.

C:\WINDOWS\system32>Powercfg -h off

C:\WINDOWS\system32>

zbook said:

7) chkdsk /r /v

I'll get back to you as soon as I have this.

zbook said:

9) In the left lower corner search type: system or system control > open system control panel > on the left pane click advanced system settings

Attachment 239525 Attachment 239524

zbook said:

10) For any BSOD:

I was using another program to view dump files. I had one full memory dump, but I think it got erased when I changed those advanced settings above to small. If they are elsewhere, I'll gladly provide them.

I will finish up tomorrow after the chkdsk runs. Thank you all for speedy replies.
Andy

zbook · 06 Jul 2019

1) For startup and recovery system failure:
a) change small memory dump to automatic memory dump
b) make sure the directory changes from minidump to memory.dmp
c) reboot to maintain settings

2) For any BSOD:

a) run the V2 log collector to collect new log files

b) open file explorer> this PC > C: > in the right upper corner search for: C:\Windows\memory.dmp
> if the file size is < 1.5 GB then zip > post a separate share link into the thread using one drive, drop box, or google drive

andyhostetler · 07 Jul 2019

zbook said:

8) Use the information in this link to find the chkdsk report in the event viewer.

File is attached.
Attachment 239581

zbook said:

10) For any BSOD:

a) run the V2 log collector to collect new log files

I changed the settings back to automatic from small. Something I had read mentioned only needing the minidumps. Running V2 log collector today only pulled the same file that was shared yesterday, so I'll try to recreate the BSOD and attach that log file when it happens.

zbook said:

13) Open the HP website > support > software and drivers Access Denied > enter the product or serial number or model > select the operating system > view drivers > post a URL or hyperlink into the thread

Access Denied
As mentioned by jdc1, this is an older system, supported only through Vista. I also upgraded some components, so HP couldn't even identify the unit using their program. No specific drivers are listed, and HP says all drivers for older machines are supplied through Device Manager.
Attachment 239582

Thanks again, and I'll post results as soon as I can get the other diagnostics run.
Andy

zbook · 07 Jul 2019

The chkdsk report displayed:

Code:

Windows has made corrections to the file system.

When available please post the results for post #4 step #12.

andyhostetler · 08 Jul 2019

zbook said:

The chkdsk report displayed:

Code:

Windows has made corrections to the file system.

I saw that, too. Is it common to have some errors like this?

zbook said:

When available please post the results for post #4 step #12.

They are below. Everything passed except an audio test where I clicked 'other' instead of 'headphones.' The ones marked canceled are because I had trouble running all tests at once and figured I should wait until I had time to do individual tests.
Attachment 239616 Attachment 239617 Attachment 239618

Also, after running all updates the last couple days, it will no longer BSOD on sleep, but it will not wake. If I hit a key or move the mouse, the fans speed up, and the lights on the tower go blue, but the displays remain dark, as though they are not receiving any signal. The keyboard is unresponsive as well, without the caps/num lock lights working. I ran another V2 log connector and have attached it just in case it is helpful. My initial thought is to roll back the Radeon software and try again, but I will wait for further instructions before doing that.
Attachment 239620

krzemien · 08 Jul 2019

Question that needs to be asked: do you need to have/use sleep mode on a desktop PC?

As I posted last week or so in another thread:

And unless it's enabled already you could turn hibernation on (as I did) (...). Drawback is slightly longer wake-up time (and hopefully nothing else, Windows OS does not really handle any of these sleep / hibernation modes well like Apple hardware does - IMHO, naturally).

Still, it would be good to narrow down what's the exact culprit.