The computer has rebooted from a bugcheck. The bugcheck was: 0x000000c2

sittingpilgrim · Oct 6, 2022

Random BSOD, happened while I was away from the computer - happened earlier this morning as well.

Link to log collector file

A few notes:

I had been getting a BSOD caused by VirtualBox, which I've uninstalled temporarily
I've been unable to install optional build KB5017389 (tried a few times, gave up) - some of the log errors may be from these attempts
no overclocking
computer is a couple of years old, had been running well (no BSOD) under Win10 - updated to Win11 about a week ago; no longer under warranty

zbook · Oct 7, 2022

1) Run:

https://www.elevenforum.com/attachments/tuneup_plus_log-bat.36285/

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

2) The BIOS:

Upgrade the BIOS: Version/Date HP Q85 Ver. 01.20.00, 3/22/2022

1.20 > 1.21

Code:

- Fixes an issue where a system that enters Sleep Mode unexpectedly wakes a short time later. - 
Addresses security vulnerabilities CVE-2022-31635, CVE-2022-31636, CVE-2022-31637, CVE-2022-31638, CVE-2022-31639. - 
Addresses security vulnerabilities CVE-2022-31640, CVE-2022-31641, CVE-2022-31642. - 
Provides the following firmware: 
Embedded Controller (EC), version 02.3F.00 
Intel GOP, version 9.0.1067 B4 
Intel Management Engine Consumer, version 11.8.90.3987 (Production) 
Intel vBIOS, version 9.0.1052 B3 
Intel/Realtek PXE ROM RTL8111, version 2.65 
Intel/Realtek PXE ROM RTL8153, version 2.019 (2016/06/28) 
Intel/Realtek UEFI PXE ROM RTL8111, version 2.039 
NVIDIA vBIOS, version 82.08.70.00.59 
USB Type-C Power Delivery (PD) Firmware (CCG4), version 8.10

Driver - HP ProBook 450 G5 Notebook PC | HP® Customer Support

support.hp.com

3) Run Memtest86 (free version) for two tests of four passes each (total eight passes)

MemTest86 - Official Site of the x86 Memory Testing Tool

MemTest86 is the original self booting memory testing software for x86 and ARM computers. Supporting both BIOS and UEFI, with options to boot from USB.

www.memtest86.com

Take pictures and post images or share links into this thread using one drive, drop box, or google drive.

Memtest86 can run overnight.

Just one error is a test fail and testing can be aborted.

Memtest86 has a feature to create text reports.

If possible, please include the text reports with the images in the share links.

sittingpilgrim · Oct 7, 2022

Thanks for your response.

Here is the link to Tuneup log

The BSOD recurred during the night, apparently during an automated backup by Veeam (which failed); Veeam wakes my system, backs up; then puts it back to sleep. This also failed 24 hours before, but has worked previously (and backup succeeds when done manually).

I will try and update the BIOS later today.

Edit: Rebooted, ran the chkdsk /scan again, with no errors; the chkdsk /spotfix suggested by the tuneup log ran successfully

zbook · Oct 7, 2022

Overnight please run administrative command prompt:

chkdsk /b /v C:

C:\WINDOWS\system32>chkdsk /b /v C:
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

Post a new V2 share link into the newest post.

Upgrade the BIOS as planned.

When possible please run Memtest86 for two tests of four passes and post images or share links into this thread.

Code:

  Found an unneeded link ($FILE_NAME: "isNativeFunction.js") in index "$I30" of directory "\Users\tom\AppData\Local\Yarn\Cache\v4\npm-@babel-runtime-7.12.5-410e7e487441e1b360c29be715d870d9b985882e\node_modules\@babel\runtime\helpers <0x1d,0xd6488>"
        ... repaired online.
    Found an unneeded link ($FILE_NAME: "ISNATI~1.JS") in index "$I30" of directory "\Users\tom\AppData\Local\Yarn\Cache\v4\npm-@babel-runtime-7.12.5-410e7e487441e1b360c29be715d870d9b985882e\node_modules\@babel\runtime\helpers <0x1d,0xd6488>"
        ... repaired online.
                                                                                      
    Found an unneeded link ($FILE_NAME: "LockMDL2.ttf") in index "$I30" of directory "\Windows.old\Windows\SystemApps\Microsoft.LockApp_cw5n1h2txyewy\Assets <0xa,0x101393>"
        ... repaired online.
                                                                                      
    Found an unneeded link ($FILE_NAME: "LockMDL2.ttf") in index "$I30" of directory "\Windows.old\Windows\WinSxS\amd64_microsoft-windows-lockapp.appxmain_31bf3856ad364e35_10.0.19041.1741_none_5bfe47c6894d0a6d <0x8,0x1616ea>"
        ... repaired online.

sittingpilgrim · Oct 7, 2022

I've updated the BIOS

Also ran the full Memtest86 - see HTML report, or full log of tests. There appears to be one bad bit.

I'll run the chkdsk later, and post the results

sittingpilgrim · Oct 7, 2022

chkdsk /b /v results

zbook · Oct 7, 2022

Nice progress.

See if the HP UEFI hardware diagnostics can detect the RAM problem detected by Memtest86.

Download and install HP UEFI hardware diagnostics version 8.7.1.0:

https://ftp.hp.com/pub/softpaq/sp141501-142000/sp141572.exe

Plan to run the HP UEFI hardware diagnostics overnight while sleeping.

Power on the computer > repetitively click F2 or F10 > system > extensive > loop until error > the next day if it has found any problems it will have stopped with and error message or code > take pictures and post images or share links into this thread

If it does not find any errors after two or more loops then click esc > post images or share links displaying the tests performed with results into this thread

The prior chkdsk switches displayed Total duration: 19.11 minutes (1147189 ms).
Check the duration and findings when run from command prompt at boot.

Plan to run again the chkdsk switches overnight while sleeping.
Open command prompt at boot:

Open Command Prompt at Boot in Windows 11 Tutorial

This tutorial will show you how to open an elevated command prompt at boot in Windows 11. The Command shell is an entry point for typing commands in the Command Prompt console window. By typing commands at the command prompt, you can perform tasks on your computer without using the Windows GUI...

www.elevenforum.com

After opening command prompt at boot run again chkdsk /b /v C:

Run the Crucial scanner and post a URL / link into this thread:

Crucial System Scanner | Memory Upgrade Scanner | Crucial

Upgrade your system storage with our range of solid state drives. Find prices, specs and customer reviews to help choose the best device for you.

www.crucial.com

After completing all of the above steps please post a new V2 share link into the newest post.

sittingpilgrim · Oct 10, 2022

Ran the HP UEFI Hardware Diagnostic - no errors found after 5+ iterations
Saving the test logs to USB failed, but got copy of the QR Code - all it contained was:

Model: HP ProBook 450 G5

Serial Number: 5CD815888S
Product ID: 3CX21UT#ABA
CSO Number:
Agent ID:
================================================
Start Time Type Result Failure ID
------------------- ------------------ -------- ---------------------------
2022-10-08 19:22:35 System [E] Passed NA

<END>

Ran the chkdsk command using the command prompt at boot. It completed without any hiccups, but I am unable to find the results in the event viewer.

The reliability of the system has increased since the update of the BIOS and the fix of the disk error. Saw one BSOD when attempting to reboot into the UEFI (hitting F2 repeatedly brought it up, requiring a hard reboot).

sittingpilgrim · Oct 10, 2022

Link to Crucial scan information

sittingpilgrim · Oct 10, 2022

Same BSOD error recurred.

philc43 · Oct 11, 2022

When you ran Memtest you reported that you had errors and the log shows that this was the case. Unfortunately, this means that your memory module is faulty and will need to be replaced. If possible see if this can be done under warranty but as it is over 2 years old you may not be covered. The memory failure will explain your BSODs as shown by the diagnosis of memory corruption

Code:

2022-10-07 14:42:10 - Finished pass #4 (of 4) (Cumulative error count: 6)
2022-10-07 14:42:10 - Cleanup - Unlocking all memory ranges...
2022-10-07 14:42:10 - All memory ranges successfully unlocked
2022-10-07 14:42:12 - Test result: FAIL (Errors: 6)

Code:

BugCheck C2, {d, ffff908d570c5500, 64536d4d, 206550334391b0fc}
Probably caused by: memory_corruption ( nt!MiDeleteControlArea+b3 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck C2, {d, ffffce08996f9ee0, 3168704e, 1bcefcccbef5a0c4}
Probably caused by: NETIO.SYS ( NETIO!PplpGenericFreeFunction+1a )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck C2, {d, ffffc10f6efcbec0, 64536d4d, 374f377372748b42}
Probably caused by: memory_corruption ( nt!MiDeleteControlArea+b3 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck C2, {99, ffffe281419ec010, 0, 0}
Probably caused by: ntkrnlmp.exe ( nt!AlpcpDeferredFreeCompletionPacketLookaside+33 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck C2, {99, ffffe5820916e940, 0, 0}
Probably caused by: memory_corruption ( nt!MiDeleteControlArea+b3 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

sittingpilgrim · Oct 11, 2022

Thanks for your feedback.

Any ideas why this began after upgrading to Windows 11? I see that all of the inputs to this thread are from users who have chosen to remain with Windows 10 (or perhaps have not updated their status). Why would the new OS be more 'sensitive' to what appear to be minor hardware faults (one bad bit out of 16GB)? I would expect the evolution of an OS to create an environment that is more robust in error handling.

philc43 · Oct 11, 2022

I also have Windows 11 but on my desktop for working on these threads I use W10. In general W11 is behaving quite well but it can't correct for bad memory areas and if that region gets used it will cause the sort of problems you have experienced. Data Servers often use error correcting code (ECC) memory to help this situation but there is a slight performance impact from using it.

I'm not sure if W11 is inherently more susceptible to errors than W10 - what could be happening is that W11 is using more of the memory areas than W10 was.

sittingpilgrim · Oct 11, 2022

Thanks again for all your assistance.

I've ordered a replacement 16GB memory module. Upon receipt and installation, I'll run the Memtest again. Hopefully it will be free of problems and, with it, the cause of this issue.

philc43 · Oct 11, 2022

sittingpilgrim said:
Thanks again for all your assistance.

I've ordered a replacement 16GB memory module. Upon receipt and installation, I'll run the Memtest again. Hopefully it will be free of problems and, with it, the cause of this issue.

You are welcome

zbook · Oct 11, 2022

The HP UEFI hardware diagnostics were reported not to be able to detect the errors found using Memtest86.

Code:

Test    # Tests Passed    Errors
Test 0 [Address test, walking ones, 1 CPU]    4/4 (100%)    0
Test 1 [Address test, own address, 1 CPU]    4/4 (100%)    0
Test 2 [Address test, own address]    4/4 (100%)    0
Test 3 [Moving inversions, ones & zeroes]    3/4 (75%)    1
Test 4 [Moving inversions, 8-bit pattern]    4/4 (100%)    0
Test 5 [Moving inversions, random pattern]    4/4 (100%)    0
Test 6 [Block move, 64-byte blocks]    4/4 (100%)    0
Test 7 [Moving inversions, 32-bit pattern]    1/4 (25%)    4
Test 8 [Random number sequence]    4/4 (100%)    0
Test 9 [Modulo 20, ones & zeros]    3/4 (75%)    1
Test 10 [Bit fade test, 2 patterns, 1 CPU]    4/4 (100%)    0
Test 13 [Hammer test]    4/4 (100%)    0
Last 10 Errors
2022-10-07 13:45:00 - [Data Error] Test: 7, CPU: 2, Address: 59A55424, Expected: 00010000, Actual: 00010080
2022-10-07 12:53:43 - [Data Error] Test: 9, CPU: 6, Address: 59A55424, Expected: 81DC8E06, Actual: 81DC8E86
2022-10-07 12:32:44 - [Data Error] Test: 7, CPU: 6, Address: 59A55424, Expected: 10000000, Actual: 10000080
2022-10-07 12:17:50 - [Data Error] Test: 3, CPU: 6, Address: 59A55424, Expected: 00000000, Actual: 00000080
2022-10-07 11:20:24 - [Data Error] Test: 7, CPU: 2, Address: 59A55424, Expected: 20000000, Actual: 20000080

To view chkdsk results:

https://www.tenforums.com/attachments/bsod-crashes-debugging/317041d1612147952-batch-files-use-bsod-debugging-chkdskfromevent.bat

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

sittingpilgrim · Oct 12, 2022

The event viewer log didn't have chkdsk results from the 10/10 run from the command prompt at boot; I'll try again.

sittingpilgrim · Oct 20, 2022

The new memory is installed and tested with MemTest - no errors; see results

philc43 · Oct 20, 2022

That's good news. See if the system is stable over the next few days and let us know.

zbook · Oct 21, 2022

In case you have the ability to communicate with HP it may be useful to document the problem and submit evidence to HP.
For example the images for results of their HP UEFI hardware diagnostics.
This thread had the Memtest86 results displaying failure but did not have the HP UEFI hardware diagnostics displaying failure with the installed RAM part number and computer serial number.
Again they will require evidence (images of the run with the computer serial number) of the diagnostic failure for it to be useful.

Glad to read that the computer is now without unexpected shutdowns and restarts.
The longer the testing period the more useful the results.