Windows 10: BSOD IRQL_NOT_LESS_OR_EQUAL when waking from Hibernate

If you tell me the things that the zip file creation runs, maybe I can run them myself and collect the data that way.

This is the latest minidump .dmp file which should have been in that zip file. 081217-10203-01.zip

This is the latest TFdebugFiles zip

 

The challenge is the event logs and a few others.
The easy ones are msinfo32 and dxdiag which each take a minute or two to load.
The troubleshooting would be incomplete without all of the logs.
It's a puzzle as it was working.
See if there is a result with the latest trial and error method in the earlier post.

 

There was no definitive misbehaving driver displayed in the debugging.

Were you able to run scannow, restorehealth and chkdsk?

 

See my post above, I just edited it, TFdebugFiles uploaded. It mysteriously disappeared, very odd (not in recycle bin either). So I had to run the Hibernate etc again to create it again.

Not sure which instruction is the "trial and error" method in which earlier post?

 

If the scannow or restorehealth cannot be completed or if mysterious things happen one option to fix possible registry issues is an in place upgrade repair. This should save files and applications.
Please create a bootable windows 10 iso:
Download Windows 10
This link has text and images:
Repair Install Windows 10 with an In-place Upgrade Windows 10 Installation Upgrade Tutorials

 

Yes, all done last week, no errors.

Mysteriously, I can now see all available networks when clicking on the wirerless icon in the taskbar system tray. I don't know how this has repaired itself!

I don't want to start messing with the registry by a windows repair just now, but will do soon and report back.

 

I've been off air for a bit while HP have tried a few things. At one point there was some corrupt memory. I think this was a red herring as I checked the memory when I first started getting the stop code and it was fine, so I didn't think replacing the memory would solve the problem. And it didn't. HP fixed a new motherboard last week and I still get stop code. They are coming back next week to fit yet another motherboard, saying this will fix it, but I don't think it will.

I've run the latest data collection/dmp file etc and wonder if you could look at to see if anything has changed (I've downloaded several drivers which needed updating which weren't actually showing up, or getting listed in the HP utility check, to no effect). I attach the file.

HP-HENRY-03_09_2017_233855_70.zip

 

The zip was empty.

Please attempt again allowing 5 minutes for it to complete and see if it works.

Also post a memory.dmp:

%SystemRoot%\MEMORY.DMP

C:\Windows\MEMORY.DMP

 

Were you able to give the dm log collector another try?
Have you tried clean boot or safe mode:

https://support.microsoft.com/en-us/...oot-in-windows
How to perform a Clean Boot in Windows 10 - TechNet Articles - United States (English) - TechNet Wiki

Perform a Clean Boot in Windows 10 to Troubleshoot Software Conflicts Windows 10 Performance Maintenance Tutorials

See if you can post:

msinfo32
dxdiag
%SystemRoot%\MEMORY.DMP
%SystemRoot%\Minidump

 

Every time I run the TENSFORUMdm_log_collector.exe application it produces an empty zip file although it appears to run through all the analysis with no problem. It was working perfectly well before so no idea why the data, which is being generated, is now not written to the file.

I've done all the other things you've selected, more than once!. They produce nothing of any interest - all OK.

I've been working with a clean boot for a couple of weeks now.

Safe mode has no hibernate option, so cannot check whether hibernating in safe mode would throw up the stop code or not.

 

The DM log collector collect may txt files. These are some of them:

msinfo32
dxdiag
%SystemRoot%\MEMORY.DMP
%SystemRoot%\Minidump

Since it is malfunctioning in the computer environment please manually generate the above txt.s and one drive links so that they can be troubleshooted.

1) mini dump: file explorer > this PC local c: drive > search:
%SystemRoot%\Minidump
or
c:\windows\minidump


2) memory dump: file explorer > this PC local c: drive > search:
%SystemRoot%\MEMORY.DMP
or
C:\Windows\MEMORY.DMP


3) msinfo32: In left lower corner search type msinfo32 wait 5 minutes for it to load > save to desktop > share link

4) dxdiag: In left lower corner search type dxdiag > wait 5 minutes for it to load > save to desktop > share link

 

Here are the files attached.

There is no MEMORY.DMP

Attachment 151831

 

Do you use ccleaner?

There were approximately 50 mini dump files so there must be a memory dump file

download and install everything search: voidtools

Search for:

%SystemRoot%\MEMORY.DMP
or
C:\Windows\MEMORY.DMP
or
MEMORY.DMP


The MSINFO32 was not able to be opened.

Please attempt to:
1) send another zip file
2) send msinfo32
3) send memory.dmp file

 

Here is another MSINFO32 saved file.

I do not use ccleaner.

I have a search everything program,including system & hidden, and I can assure you there is no MEMORY.dmp file

HP_HENRY-040917_systeminfo.zip

 

At this juncture it is unclear how the dm log collector was able to collect logs and is no longer able to do so.
It is unclear how the windows error reporting indicates windows memory dump and there is no memory dump file to be found.
The troubleshooting process is handicapped when there are missing test results and logs.

1) find a flash drive that you can format
2) create a bootable windows 10 iso
3) perform an in place upgrade repair (save files and applications)
4) follow the text and images in this link:
Repair Install Windows 10 with an In-place Upgrade Windows 10 Installation Upgrade Tutorials