testing an intermittent restart issue

john errington · Jun 8, 2022

I have a clients laptop that she reports crashes infrequently - about once a month.
NO BSOD info because logging was not set up.

I've run stress tests (furmark, heavyload, occt) over 24 h periods with no issues. I'm confident it is not a hardware issue.

Does anyone know of a "realistic" stress /benchmark I can run to simulate extended periods of "office" use?

I have set the PC to record dump files now (why isnt that the default?) so may get more diagnostics if the fault happens again.

zbook · Jun 8, 2022

Many computers with malfunctioning hardware may have false negatives using software stress testing.

To find the malfunctioning hardware swap testing components or testing in a local computer store may be required.

Laptops though have very limited components for swap testing.

So testing may be required at the computer manufacturer or in a local computer store.

By default computers are set up to record BSOD if they occur.

Many times the logs may have entries about failure to generate files.

There is a Ten Forums script that is used to detect any modifications and reset some of the settings.

https://www.tenforums.com/attachments/bsod-crashes-debugging/360137d1645183388-batch-files-use-bsod-debugging-tuneup_plus_log.bat

Have the client monitor their computer using reliability monitor:

Reliability Monitor is the Best Windows Troubleshooting Tool You Aren't Using

When it comes to hidden gems in Windows, nothing beats the Reliability monitor tool, hidden behind a link inside of another tool that you don't use either.

www.howtogeek.com

john errington · Jun 8, 2022

thanks for the link zbook. I'd not run a batch script without knowing more about it, so I'm looking through this.

Batch files for use in BSOD debugging - Windows 10 Help Forums

Information This thread is for use by the BSOD team to store batch files that can be used to collect additional data, fix settings or anything else that is useful in debugging BSOD problems in Windows 10. The way I see it working is the first

www.tenforums.com

Typically the laptop has no exchangeable parts, but all the tests I have done show the hardware is OK and I have no reason to suspect otherwise.

The links will give me a great help in diagnosing these problems in future

V2 Log Collector

V2 Log collector for collecting files to diagnose Windows 10+ BSOD problems. https://www.elevenforum.com/resources/v2-log-collector.1/download

www.elevenforum.com

john errington · Jun 9, 2022

I now have the output from the V2 log collector - but its 2.06MB and the forum wont let me upload it - "the uploaded file is too large"

zbook · Jun 9, 2022

If uploads do not work then use share links.

For share links please use one drive, drop box, or google drive.

Make sure that share links are available without logon.

john errington · Jun 9, 2022

Thanks zbook, didnt know if that was allowed Here is the V2 log file

LAPTOP-43BNMQL5-(2022-06-09_05-52-11).zip

drive.google.com

zbook · Jun 9, 2022

The logs indicated manually initiated BSODs.

There were no spontaneous BSOD.

1) The BIOS: Version/Date Insyde Corp. V1.13, 08/11/2017

Upgrade the BIOS: 1.13 > 2.02

Product Support | Acer United Kingdom

2) Run:

https://www.tenforums.com/attachments/bsod-crashes-debugging/360137d1645183388-batch-files-use-bsod-debugging-tuneup_plus_log.bat

Post a share link into this thread using one drive, drop box, or google drive.

john errington · Jun 12, 2022

I have returned the PC to the client for now, having already done the SFC & DISM, cleared logs etc. I'll come back if the issue happens again. Thanks for help I now have more resources at my disposal should I meet this issue again.

zbook · Jun 12, 2022

You're welcome.

What was happening with the manually initiated BSOD?

Which method were you using?

john errington · Jun 12, 2022

I'd enable page file on C drive (SSD) and set up to provide a kernel memory dump file in the event of another crash.

Tested by forcing a keyboard-initiated system crash as below:

How to force a Windows 'Blue Screen of Death' — and why you might want to

Did you know that you can intentionally force a Blue Screen of Death on Windows 10? Now you do.

www.windowscentral.com

In the registry key HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\kbdhid\Parameters, create a value named CrashOnCtrlScroll, and set it equal to a REG_DWORD value of 0x01.

In the registry key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\i8042prt\Parameters

Right-click on the right side, select New, and then click on DWORD (32-bit) Value.

Name as CrashOnCtrlScroll, and set it equal to a REG_DWORD value of 0x01.

Restart the system for these settings to take effect.

Hold down the rightmost CTRL key, and press the SCROLL LOCK key twice.

The system then calls KeBugCheck and issues bug check 0xE2 (MANUALLY_INITIATED_CRASH). Unless crash dumps have been disabled, a crash dump file is written at this point.

zbook · Jun 12, 2022

So it was to confirm that crash dump could be created?

john errington · Jun 12, 2022

yes, thats correct

testing an intermittent restart issue

Member

My Computer

Well-known member

My Computer

Member

My Computer

Member

My Computer

Well-known member

My Computer

Member

My Computer

Well-known member

My Computer

Member

My Computer

Well-known member

My Computer

Member

My Computer

Well-known member

My Computer

Member

My Computer