New AMD system crashing on resuming from hibernation. Plz help.

Ahmed79

New Member
Local time
6:42 PM
Posts
18
Thread starter
Hello, my computer shuts down while booting up from a hibernated state.

Once running, it doesn't crash and when i shut it down (instead of hibernating) and restart, its still fine.
Problem happens only when I hibernate my PC and then start it back up , it shuts down just after loading windows appears and then I have to manually start the PC again.

I updated the BIOS to the latest version, drivers that I checked using MSI dragon center are all updated. Very few apps installed. No anti virus apps.

Processor AMD Ryzen 5 5600X 6-Core Processor 3.70 GHz
Installed RAM 16.0 GB
GFX card MSI 3070
PSU is Cooler master 650W v2

Windows is updated with the latest updates already (upto 21H1).
Using a NVMe Samsung 960.
PC is only 5 months old.


4 different Crash dumps uploaded on the links (the last link one being the latest):



The steps that I've taken so far in trying to fix this:

- Increased hibernation file size to 100%.. also disabled and re-enabled hibernation to delete and create a fresh hibernation file.

- Ran Windows Memory Diagnostic Tool

- Ran Memtest86 with 4 passes and no errors found.

- Ran chkdsk and sfc scannow too.

- Samsung Magician shows the NVMe health as normal.

- Ran Driver verifier with all non-MS drivers selected.

- Updated all drivers to their latest version.

- BIOS updated to the latest version already.

- Clean installed Windows a couple of days ago .

- Windows updated with the latest patches upto 21H1.

- Very few apps installed ATM, like Steam, MSI dragon center, some media viewer/apps..

- PC is newly assembled 5-6 months ago.. and I didn't have this problem until a month back when I installed an android game emulator and my pc crashed with a BSOD after that and failed to recover which made me clean reinstall Windows again.


CPU is not overclocked.. nor is the GFX card.. RAM is running on XMP profile 1 on stated speeds on the box.


If you could analyze the crash dumps, it'd help point to the exact cause.

Thanks in advance for your valuable time, any help will be greatly appreciated.
 
Windows Version
10 21H1 (Build 19043.1023)

Attachments

  • DESKTOP-2V23DDE-(2021-06-05_22-36-34).zip
    1.7 MB · Views: 20
  • whocrashed SS.jpg
    whocrashed SS.jpg
    267.5 KB · Views: 25

My Computer

System One

  • Operating System
    Windows 10

zbook

Active Member
Member
VIP
Local time
8:42 PM
Posts
328
Hi Ahmed79 ,

Please perform the following steps in sequence:

1) Open administrative command prompt (ACP) and type or copy and paste:
2) sfc /scannow
3) dism /online /cleanup-image /scanhealth
4) dism /online /cleanup-image /restorehealth
5) sfc /scannow
6) chkdsk /scan
7) wmic recoveros set autoreboot = false
8) wmic recoveros set DebugInfoType = 7
9) wmic recoveros get autoreboot
10) wmic recoveros get DebugInfoType
11) wmic Computersystem where name="%computername%" set AutomaticManagedPagefile=True
12) wmic Computersystem where name="%computername%" get AutomaticManagedPagefile
13) powercfg -h off
14) bcdedit /enum {badmemory}

15) 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


16) Run HD Tune (free version) (all drives)

HD Tune website

HD Tune
www.hdtune.com
Post images into the thread for results on these tabs:
a) Health
b) Benchmark
c) Full error scan


17) Run Sea Tools for Windows
long generic test
Post an image of the test result into the thread
SeaTools (Windows) | Seagate

How to use SeaTools for Windows | Seagate Support US

Tutorial for the use of SeaTools for Windows, explaining the most common features:
knowledge.seagate.com


18) Open administrative command prompt and type or copy and paste:
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


19) 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 a one drive, drop box, or google drive share link:
Read Chkdsk Log in Event Viewer in Windows 10 Windows 10 Performance Maintenance Tutorials
www.tenforums.com

Read Chkdsk Log in Event Viewer in Windows 10

How to Read Event Viewer Log for Chkdsk (Check Disk) in Windows 10
www.tenforums.com
www.tenforums.com


20) These steps / tests can be performed overnight:
a) HD Tune full error scan
b) Sea Tools for Windows long generic test
c) Chkdsk /r /v


21) For any BSOD after completing steps #1 > #15:

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 > save to the downloads folder > zip > post a separate share link into the thread using one drive, drop box, or google drive
 

My Computer

System One

  • Operating System
    Windows 10

Ahmed79

New Member
Local time
6:42 PM
Posts
18
Thread starter
Firstly, thank you so much for your detailed reply.
I feel that with you I've finally found the right place to figure out and fix this annoying issue, god willing.

Microsoft Windows [Version 10.0.19043.1023]
(c) 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 /scanhealth

Deployment Image Servicing and Management tool
Version: 10.0.19041.844

Image Version: 10.0.19043.1023

[==========================100.0%==========================] No component store corruption detected.
The operation completed successfully.

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

Deployment Image Servicing and Management tool
Version: 10.0.19041.844

Image Version: 10.0.19043.1023

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

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>chkdsk /scan
The type of the file system is NTFS.

Stage 1: Examining basic file system structure ...
398336 file records processed.
File verification completed.
Phase duration (File record verification): 1.84 seconds.
5144 large file records processed.
Phase duration (Orphan file record recovery): 0.00 milliseconds.
0 bad file records processed.
Phase duration (Bad file record checking): 0.93 milliseconds.

Stage 2: Examining file name linkage ...
2867 reparse records processed.
579286 index entries processed.
Index verification completed.
Phase duration (Index verification): 6.00 seconds.
0 unindexed files scanned.
Phase duration (Orphan reconnection): 338.09 milliseconds.
0 unindexed files recovered to lost and found.
Phase duration (Orphan recovery to lost and found): 0.41 milliseconds.
2867 reparse records processed.
Phase duration (Reparse point and Object ID verification): 6.33 milliseconds.

Stage 3: Examining security descriptors ...
Security descriptor verification completed.
Phase duration (Security descriptor verification): 46.09 milliseconds.
90476 data files processed.
Phase duration (Data attribute verification): 0.22 milliseconds.
CHKDSK is verifying Usn Journal...
40966224 USN bytes processed.
Usn Journal verification completed.
Phase duration (USN journal verification): 103.63 milliseconds.

Windows has scanned the file system and found no problems.
No further action is required.

975607862 KB total disk space.
129752932 KB in 294996 files.
188016 KB in 90477 indexes.
0 KB in bad sectors.
537622 KB in use by the system.
65536 KB occupied by the log file.
845129292 KB available on disk.

4096 bytes in each allocation unit.
243901965 total allocation units on disk.
211282323 allocation units available on disk.
Total duration: 8.34 seconds (8346 ms).

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

C:\Windows\system32>wmic recoveros set DebugInfoType = 7
Updating property(s) of '\\DESKTOP-2V23DDE\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Home|C:\\Windows|\\Device\\Harddisk1\\Partition3"'
Property(s) update successful.

C:\Windows\system32>wmic recoveros get autoreboot
AutoReboot
FALSE


C:\Windows\system32>wmic recoveros get DebugInfoType
DebugInfoType
7


C:\Windows\system32>wmic Computersystem where name="%computername%" set AutomaticManagedPagefile=True
Updating property(s) of '\\DESKTOP-2V23DDE\ROOT\CIMV2:Win32_ComputerSystem.Name="DESKTOP-2V23DDE"'
Property(s) update successful.

C:\Windows\system32>wmic Computersystem where name="%computername%" get AutomaticManagedPagefile
AutomaticManagedPagefile
TRUE


C:\Windows\system32>powercfg -h off

C:\Windows\system32>bcdedit /enum {badmemory}

RAM Defects
-----------
identifier {badmemory}


I had earlier seen the Crystal Disk Info showing yellow/caution on 2 functionality aspects of my old WD HDD D: drive, but I disregarded it thinking that my main drive is the new Samsung NVMe C: drive on which the OS is installed and also has all my apps and the hibernate file also is on it.
So I didn't think that the BSOD/Crash on resume from hibernation had anything to do with the D: drive.
Already ordered a new 2TB HDD which should arrive in 3 days time.

2 more files just uploaded worth having a look by you.

Crash dump of 116KB is uploaded here.. its from just before I performed the steps advised by you. Its the latest one.

Memory Dump file of 1gb is uploaded here.. its from just before I performed the steps advised by you. Its the latest one.


I am going to perform the chkdsk on D drive too now (already done on C and attached the report in a txt file) and will post back here with its results ASAP, in the meantime I've posted the rest of the info here for your analysis.

Thanks again for your valuable time.
 

Attachments

  • Benchmark C.jpg
    Benchmark C.jpg
    62.3 KB · Views: 22
  • Benchmark D.jpg
    Benchmark D.jpg
    71.5 KB · Views: 26
  • C Drive.jpg
    C Drive.jpg
    37.8 KB · Views: 22
  • C Drive2.jpg
    C Drive2.jpg
    85.4 KB · Views: 23
  • C Drive4.jpg
    C Drive4.jpg
    73 KB · Views: 19
  • C Drive5.jpg
    C Drive5.jpg
    82.9 KB · Views: 23
  • crystal disk info C.jpg
    crystal disk info C.jpg
    92.1 KB · Views: 28
  • crystal disk info D.jpg
    crystal disk info D.jpg
    101.2 KB · Views: 19
  • D Drive.jpg
    D Drive.jpg
    68.5 KB · Views: 25
  • Error scan C.jpg
    Error scan C.jpg
    105.5 KB · Views: 20
  • MSFT.jpg
    MSFT.jpg
    34.7 KB · Views: 21
  • SeaTest Temp1.jpg
    SeaTest Temp1.jpg
    55.6 KB · Views: 18
  • Error scan D.jpg
    Error scan D.jpg
    106.2 KB · Views: 21
  • chkdsk C drive.txt
    3.2 KB · Views: 23
Last edited:

My Computer

System One

  • Operating System
    Windows 10

zbook

Active Member
Member
VIP
Local time
8:42 PM
Posts
328
Nice progress.


The bugcheck before the commands was again A0 with Arg1 = 10e: The disk subsystem returned corrupt data while reading from the
hibernation file.



For any BSOD please run V2 to collect new files including dump files.




Run HD Sentinel: (free or trial edition)
Hard Disk Sentinel - HDD health and temperature monitoring
For each drive post images of these tabs into the thread:
Overview tab
Temperature
SMART
Disk performance





Code:
------------------------
Disk & DVD/CD-ROM Drives
------------------------
      Drive: C:
 Free Space: 830.4 GB
Total Space: 952.7 GB
File System: NTFS
      Model: Samsung SSD 970 EVO 1TB

      Drive: D:
 Free Space: 111.6 GB
Total Space: 953.9 GB
File System: NTFS
      Model: WDC WD10EADS-65L5B1
 

My Computer

System One

  • Operating System
    Windows 10

Ahmed79

New Member
Local time
6:42 PM
Posts
18
Thread starter
The chkdsk on D drive is still running with an ETA of 3+hrs.
I'll post the results here once its done.

One question, (after the chkdsk is finished on D drive) how will I be able to check/get the BSOD as the hibernation option is now disabled?

Thanks again.
 

Attachments

  • C drive overview.jpg
    C drive overview.jpg
    98.4 KB · Views: 21
  • C drive performance.jpg
    C drive performance.jpg
    107.3 KB · Views: 21
  • C drive smart.jpg
    C drive smart.jpg
    112.6 KB · Views: 22
  • C drive temps.jpg
    C drive temps.jpg
    100.4 KB · Views: 19
  • D drive overview.jpg
    D drive overview.jpg
    108.3 KB · Views: 19
  • D drive performance.jpg
    D drive performance.jpg
    111.2 KB · Views: 26
  • D drive smart.jpg
    D drive smart.jpg
    155.8 KB · Views: 20
  • D drive temps.jpg
    D drive temps.jpg
    124.7 KB · Views: 22

My Computer

System One

  • Operating System
    Windows 10

zbook

Active Member
Member
VIP
Local time
8:42 PM
Posts
328
The computer settings were optimized to create and save dump files.

Hibernation was turned off.

The computer should be monitored with all drives attached for BSOD and unexpected shutdowns and restarts without BSOD.

Use reliability monitor:
 

My Computer

System One

  • Operating System
    Windows 10

Ahmed79

New Member
Local time
6:42 PM
Posts
18
Thread starter
My PC doesn't crash or gets BSODs once logged into Windows or from normal restarts after proper manual shutdowns.

Without enabling hibernation and not resuming from hibernate, I worry that we may not get a crash/BSOD for analysis anytime soon or at all for that matter.
 

Attachments

  • reliability monitor.jpg
    reliability monitor.jpg
    184.8 KB · Views: 21
  • chkdsk on D so far.jpg
    chkdsk on D so far.jpg
    154.6 KB · Views: 25

My Computer

System One

  • Operating System
    Windows 10

zbook

Active Member
Member
VIP
Local time
8:42 PM
Posts
328
If there are no unexpected shutdowns and restarts with or without BSOD then we can move to the next step.

For now please don't detach the WDC drive.
 

My Computer

System One

  • Operating System
    Windows 10

Ahmed79

New Member
Local time
6:42 PM
Posts
18
Thread starter
Okay.

The chkdsk on D drive is done. Let me know what you want me to do next.

C:\Windows\system32>chkdsk /r /v D:
The type of the file system is NTFS.

Chkdsk cannot run because the volume is in use by another
process. Chkdsk may run if this volume is dismounted first.
ALL OPENED HANDLES TO THIS VOLUME WOULD THEN BE INVALID.
Would you like to force a dismount on this volume? (Y/N) y
Volume dismounted. All opened handles to this volume are now invalid.
Volume label is NEW.

Stage 1: Examining basic file system structure ...
284672 file records processed.
File verification completed.
Phase duration (File record verification): 3.52 seconds.
2334 large file records processed.
Phase duration (Orphan file record recovery): 0.00 milliseconds.
0 bad file records processed.
Phase duration (Bad file record checking): 0.27 milliseconds.

Stage 2: Examining file name linkage ...
329 reparse records processed.
296098 index entries processed.
Index verification completed.
Phase duration (Index verification): 21.11 seconds.
0 unindexed files scanned.
Phase duration (Orphan reconnection): 17.07 milliseconds.
0 unindexed files recovered to lost and found.
Phase duration (Orphan recovery to lost and found): 17.10 milliseconds.
329 reparse records processed.
Phase duration (Reparse point and Object ID verification): 2.24 milliseconds.

Stage 3: Examining security descriptors ...
Cleaning up 1824 unused index entries from index $SII of file 9.
Cleaning up 1824 unused index entries from index $SDH of file 9.
Cleaning up 1824 unused security descriptors.
Security descriptor verification completed.
Phase duration (Security descriptor verification): 46.07 milliseconds.
5714 data files processed.
Phase duration (Data attribute verification): 0.20 milliseconds.
CHKDSK is verifying Usn Journal...
41530520 USN bytes processed.
Usn Journal verification completed.
Phase duration (USN journal verification): 1.38 seconds.

Stage 4: Looking for bad clusters in user file data ...
284656 files processed.
File data verification completed.
Phase duration (User file recovery): 3.49 hours.

Stage 5: Looking for bad, free clusters ...
28565343 free clusters processed.
Free space verification is complete.
Phase duration (Free space recovery): 0.00 milliseconds.

Windows has scanned the file system and found no problems.
No further action is required.

976760000 KB total disk space.
862041524 KB in 64552 files.
34844 KB in 5715 indexes.
0 KB in bad sectors.
422256 KB in use by the system.
65536 KB occupied by the log file.
114261376 KB available on disk.

4096 bytes in each allocation unit.
244190000 total allocation units on disk.
28565344 allocation units available on disk.
Total duration: 3.50 hours (12606864 ms).
 

My Computer

System One

  • Operating System
    Windows 10

zbook

Active Member
Member
VIP
Local time
8:42 PM
Posts
328
It displayed cleaning and was unremarkable.

You can monitor for 3 - 5 days or you can turn on Windows driver verifier (WDV).

For WDV make a new restore point and post a new V2 before turning on the tool.

Post result for: verifier /querysettings


Read these links on Windows driver verifier:

Learn how to use the Windows Recovery Environment (RE) commands: reset and bootmode to turn off the tool



Windows driver verifier is designed to stress test drivers.

If there are misbehaving drivers the computer will crash.

If dump files are created they can be debugged.

Misbehaving drivers are then uninstalled or uninstalled and reinstalled.

The tool is run for approximately 48 hours and then an additional 36 hours after the last BSOD.

If there are no further BSOD this concludes the use of the tool.

After each BSOD you must turn off the tool in order to return to the desktop.

Learn the Windows RE commands reset and bootmode.

These are run in safe mode or safe mode with command prompt.

In case these fail the next option is system restore.

If system restore fails you can restore a backup image or use registry commands.

Start the tool with the 3 customized test settings in the Ten Forums link.

Increase the simultaneous customized test settings by 3 - 5 / hour up to the 19 customized test settings in the Microsoft link.

There can be performance problems and / or slow boot while using the tool.

If necessary the customized test settings can be modified.

Summary:
a) make a new restore point
b) test all non-Microsoft drivers
c) test no Microsoft drivers
d) after each BSOD use the reset command to turn off the tool
e) if the reset command does not work then use the bootmode command
f) only if both reset and bootmode command fail to turn off the tool then use restore
g) start with the 3 customized test settings in the Ten Forums link
h) increase the customized test settings up to the 19 customized test settings in the Microsoft link
i) report any performance problems or very slow boot so that the customized settings can be modified
 

My Computer

System One

  • Operating System
    Windows 10

Ahmed79

New Member
Local time
6:42 PM
Posts
18
Thread starter
Ok, I've created a restore point and made a new V2 (attached) and then started WDV with 3 customized settings as mentioned in the Ten Forums article.

I'll increase the customized settings by 3~5 more settings every few hours of PC usage until I reach 19 customized settings.

I'll report back here in case of any crash or BSODs.

Thanks again.
 

Attachments

  • DESKTOP-2V23DDE-(2021-06-07_01-41-00).zip
    1.4 MB · Views: 18

My Computer

System One

  • Operating System
    Windows 10

zbook

Active Member
Member
VIP
Local time
8:42 PM
Posts
328
If there are no performance problems or very slow boot you can also add DDI (all customized tests except 0x00000004 Randomized low resources simulation).


Code:
Event[1489]:
  Log Name: System
  Source: Microsoft-Windows-Kernel-Boot
  Date: 2021-05-26T12:02:37.7890000Z
  Event ID: 16
  Task: N/A
  Level: Error
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: DESKTOP-2V23DDE
  Description:
Windows failed to resume from hibernate with error status 0xC0000001.


Event[3335]:
  Log Name: System
  Source: Microsoft-Windows-Kernel-Boot
  Date: 2021-05-29T22:44:56.7110000Z
  Event ID: 16
  Task: N/A
  Level: Error
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: DESKTOP-2V23DDE
  Description:
Windows failed to resume from hibernate with error status 0xC0000001.


Event[5629]:
  Log Name: System
  Source: Microsoft-Windows-Kernel-Boot
  Date: 2021-06-06T10:39:29.8150000Z
  Event ID: 16
  Task: N/A
  Level: Error
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: DESKTOP-2V23DDE
  Description:
Windows failed to resume from hibernate with error status 0xC0000001.
 

My Computer

System One

  • Operating System
    Windows 10

Ahmed79

New Member
Local time
6:42 PM
Posts
18
Thread starter
Ok, I have selected all the tests on WDV except 'Randomized low resources simulation' and restarted the PC.
Will report as soon as I get anything.

Thanks.
 

My Computer

System One

  • Operating System
    Windows 10

Ahmed79

New Member
Local time
6:42 PM
Posts
18
Thread starter
Got a BSOD on the very next restart after enabling all settings (except the one mentioned by you) in WDV.
Tried to restart after that and again the same BSOD.. after that on next restart I got a screen asking me to do a system restore.
So, I did a system restore and I got a screen which said that Windows was attempting repairs and then it restarted again and booted normally into Windows.

Posting the memory dump link, crash dump and V2 attachments.

Mini crash dump

Memory Dump
 

Attachments

  • DESKTOP-2V23DDE-(2021-06-07_12-05-03).zip
    1.2 MB · Views: 23

My Computer

System One

  • Operating System
    Windows 10

Ahmed79

New Member
Local time
6:42 PM
Posts
18
Thread starter
I checked the smaller dump with windbg and among other things it also pointed towards ene.sys .

So I searched online about it and came across someone else discussing about it on this link:

And from there I reached this link:

Incidentally, I also have the Gskill Trident RAM , but mine is a non RGB version (no lights at all, just plain and I don't have any app/driver installed specifically for the RAM but still have this ene.sys file on my system).. and also I have the MSI dragon center (which has RGB control for MoBo and the GFX card) installed which according to them seems to conflict with eachother .

So please have a look at these links, they might be helpful in this case.
 

My Computer

System One

  • Operating System
    Windows 10

zbook

Active Member
Member
VIP
Local time
8:42 PM
Posts
328
See if you can uninstall or uninstall and reinstall ene.sys.

Late last year there were problems with cfosspeed6.sys.
This can be uninstalled or uninstalled and reinstalled or left as is unless it misbehaves with WDV.


This was a prior thread with both ene.sys and cfosspeed6.sys:
 

My Computer

System One

  • Operating System
    Windows 10

Ahmed79

New Member
Local time
6:42 PM
Posts
18
Thread starter
Ok, I'll delete ene.sys from safe mode for now and keep cfosspeed6.sys , unless BSODs/crashes don't stop.

After deleting ene.sys, should I re-enable WDV again to see if the problem is fixed?
Or should I enable hibernation again to check if the issue has been completely fixed?
Please advice accordingly.

Thanks.
 

My Computer

System One

  • Operating System
    Windows 10

zbook

Active Member
Member
VIP
Local time
8:42 PM
Posts
328
Please see the WDV instructions in the earlier post.

To turn off WDV > reboot into safe mode > use the reset or bootmode commands

Using system restore sometimes results in no new dump file.


Run WDV for 36 hrs after the last BSOD.

Post results from verifier /querysettings while using the tool.





Computers with event viewer: Windows failed to resume from hibernate with error status 0xC0000001 often cannot use hibernation without problems.

After completing WDV testing run the Windows power troubleshooter > post images of detailed results.
 
Last edited:

My Computer

System One

  • Operating System
    Windows 10

Ahmed79

New Member
Local time
6:42 PM
Posts
18
Thread starter
The WDV is currently disabled, it got disabled after the system restore as the PC didn't boot up after I enabled all the settings in WDV except one.

I've deleted ene.sys.

Now shall I enable WDV with all custom settings enabled (except 0x00000004 Randomized low resources simulation) or you want me to run it with some specific custom settings only? or just start with 3 as mentioned in your first post and then gradually increase by 5 every hour until BSOD/crash?

Thanks.
 

My Computer

System One

  • Operating System
    Windows 10

zbook

Active Member
Member
VIP
Local time
8:42 PM
Posts
328
During the prior WDV crash the computer was tested with all customized settings except
(0x00000004) Randomized low resources simulation.

Please restart WDV with the same (21) customized settings and run for 36 hours.
If there is another BSOD then plan to fix it followed by a 36 hour run.
 

My Computer

System One

  • Operating System
    Windows 10
Top