BSOD when gaming

matt11 · Jul 9, 2022

DESKTOPZ490X-(2022-07-09_14-27-52).zip

Compressed (zipped) Folder

1drv.ms

LiveKernel Reports 2022-07-09 (14-31-25).zip

Compressed (zipped) Folder

1drv.ms

glasskuter · Jul 9, 2022

I noticed in your post dated June 18 you said "MSI said they repaired a component on the GPU itself as it was a hardware fault." I would not be wanting a repaired gpu but a replacement one.

If your i7-10700k is as picky as my i9-10900 when it comes to ram, I will say zbook may have a point. Mine required that all 4 ram slots be populated with exactly the same make/model ram. It did not like mixing brands, even when the pairs were in different banks and even when Crucial said their ram was compatible with the original Micron ram. I found that hard to believe since Crucial uses Micron chips, but it proved to be correct. My PC did not like it.

zbook · Jul 9, 2022

Please 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.

The above script will modify the startup and recovery system failure and virtual memory / page file settings so that they are optimal for dump file creation and dump file debugging.

Please maintain these settings throughout the troubleshooting.

If you manually power off the computer please record the date and time and post the data into this thread.

There were recent abnormal shutdowns.

One was related to problems with hibernation.

There were no recent BSOD or live kernel events recorded since June 28, 2022.

Open administrative command prompt and type or copy and paste: (plan to reboot the computer)

powercfg -hibernate off

shutdown -r

What is the status of the PSU?
See if you can swap test it.

Code:

Intel(R) Ethernet Controller (2) I225-V    PCI\VEN_8086&DEV_15F3&SUBSYS_E0001458&REV_02\4&1BA68F3E&0&00E3    This device is disabled.

Code:

Event[11800]
  Log Name: System
  Source: Microsoft-Windows-Kernel-Power
  Date: 2022-07-08T18:26:20.3440000Z
  Event ID: 41
  Task: N/A
  Level: Critical
  Opcode: Info 
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: DesktopZ490X
  Description:
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Code:

Event[11789]
  Log Name: System
  Source: EventLog
  Date: 2022-07-08T18:26:24.6010000Z
  Event ID: 6008
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DesktopZ490X
  Description:
The previous system shutdown at 6:03:36 PM on ?7/?8/?2022 was unexpected.

Code:

Event[11662]
  Log Name: System
  Source: Microsoft-Windows-Kernel-Power
  Date: 2022-07-08T17:23:30.6750000Z
  Event ID: 41
  Task: N/A
  Level: Critical
  Opcode: Info 
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: DesktopZ490X
  Description:
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Code:

Event[11652]
  Log Name: System
  Source: EventLog
  Date: 2022-07-08T17:23:36.3340000Z
  Event ID: 6008
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DesktopZ490X
  Description:
The previous system shutdown at 4:54:01 PM on ?7/?8/?2022 was unexpected.

Code:

Event[11110]
  Log Name: System
  Source: Microsoft-Windows-Kernel-Power
  Date: 2022-07-02T08:10:57.6540000Z
  Event ID: 41
  Task: N/A
  Level: Critical
  Opcode: Info 
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: DesktopZ490X
  Description:
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Code:

Event[11099]
  Log Name: System
  Source: EventLog
  Date: 2022-07-02T08:11:01.4480000Z
  Event ID: 6008
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DesktopZ490X
  Description:
The previous system shutdown at 9:31:13 AM on ?7/?1/?2022 was unexpected.

Code:

Event[11087]
  Log Name: System
  Source: Microsoft-Windows-Kernel-Boot
  Date: 2022-07-02T08:10:55.0920000Z
  Event ID: 16
  Task: N/A
  Level: Error
  Opcode: Info 
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: DesktopZ490X
  Description:
Windows failed to resume from hibernate with error status 0xC0000411.

glasskuter · Jul 10, 2022

It may not be applicable to you but I wanted to mention the following points anyway. If either turns out to affect you zbook will probably find it in your logs..

Another user who was using an RTX 3080 gpu reported kernel power event 41 just yesterday. Another on 5/3 using an RTX 3080. @zbook you helped both of them. While trying to help the guy yesterday I found quite a few reports across the web on both the 2070 and 3080 gpu causing event 41. Are you overclocking this gpu? It was advised on several of the forums I was reading on (including Nvidia's) that the power limit on these graphics cards should be lowered for testing. Have you monitored the temps of this gpu through Geforce Experience.? Maximum power may be causing it to overheat.

Another user using a gaming rig with RTX 2070 traced his Event 41 BSOD problem back to Corsair ICUE software.

Nobody · Jul 10, 2022

matt11 said:
DESKTOPZ490X-(2022-06-27_09-23-41).zip

Compressed (zipped) Folder

1drv.ms

Microsoft OneDrive - Access files anywhere. Create docs with free Office Online.

Store photos and docs online. Access them from any PC, Mac or phone. Create and work together on Word, Excel or PowerPoint documents.

1drv.ms

A V2 and Live Kernel Reports
MSI would only tell me that a component on the board was bad and was repaired/replaced. No other info there. Everything is still in warranty for another year at least.

Were these before MSI replaced that component?

Because there was one 0x124 WHEA_UNCORRECTABLE_ERROR. In addition to that, several VIDEO_ENGINE_TIMEOUT_DETECTED errors. These are probably the ones that cause black screens. But the first one needs to be checked, because some part is possibly broken. Plus some USB related bug check too. Re-installing chipset driver might help with those usb related.

The downside of those TDR-related problems is that they happen randomly, so if the graphics card is tested elsewhere, it might work flawlessly that time. Besides that, it might work on another pc without any problems. I have first-hand experience with TDR problems. The problem was fixed when Gigabyte released bios updates for that gpu that fixed the problem. These days, those bios updates for gpu's don't seem to be published too much.

If it goes well, the problem can be solved, but usually people end up reinstalling Windows. And that doesn't always help either. Good luck solving the problem. :)

I forgot about this at first

Code:

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
nt!_WHEA_ERROR_RECORD structure that describes the error condition. Try !errrec Address of the nt!_WHEA_ERROR_RECORD structure to get more details.
Arguments:
Arg1: 0000000000000007, BOOT Error
Arg2: ffffd202d326e020, Address of the nt!_WHEA_ERROR_RECORD structure.
Arg3: 0000000000000000
Arg4: 0000000000000000

Debugging Details:
------------------


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 1812

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 1815

    Key  : Analysis.Init.CPU.mSec
    Value: 296

    Key  : Analysis.Init.Elapsed.mSec
    Value: 6141

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 89

    Key  : Bugcheck.Code.DumpHeader
    Value: 0x124

    Key  : Bugcheck.Code.Register
    Value: 0x29789e90

    Key  : Dump.Attributes.AsUlong
    Value: 18

    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1


FILE_IN_CAB:  WHEA-20220528-1314.dmp

DUMP_FILE_ATTRIBUTES: 0x18
  Kernel Generated Triage Dump
  Live Generated Dump

BUGCHECK_CODE:  124

BUGCHECK_P1: 7

BUGCHECK_P2: ffffd202d326e020

BUGCHECK_P3: 0

BUGCHECK_P4: 0

PROCESS_NAME:  smss.exe

STACK_TEXT: 
fffff58f`29789e40 fffff801`4ae074bf     : ffffd202`d326e000 00000000`00000000 ffffd202`d326e020 00000059`b83af740 : nt!LkmdTelCreateReport+0x1de
fffff58f`2978a380 fffff801`4ae073b6     : ffffd202`d326e000 00000000`00000000 00000000`00000000 ffffd202`df6f7900 : nt!WheapReportLiveDump+0x7b
fffff58f`2978a3c0 fffff801`4ac4d4d9     : 00000000`00000001 fffff58f`2978aa60 00000000`00000000 00000000`000002ac : nt!WheapReportDeferredLiveDumps+0x7a
fffff58f`2978a3f0 fffff801`4aa80902     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000001 : nt!WheaCrashDumpInitializationComplete+0x59
fffff58f`2978a420 fffff801`4a829075     : ffffd202`db79d080 00000000`00000000 00000000`0000022c 00000000`00000001 : nt!NtSetSystemInformation+0xa72
fffff58f`2978a9e0 00007ffb`55367524     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25
00000059`b83af6e8 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffb`55367524


MODULE_NAME: GenuineIntel

IMAGE_NAME:  GenuineIntel.sys

STACK_COMMAND:  .cxr; .ecxr ; kb

FAILURE_BUCKET_ID:  LKD_0x124_7_GenuineIntel__UNKNOWN_IMAGE_GenuineIntel.sys

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {5ea80f6a-69bf-5d6f-8fd2-cd87deb91a03}

Followup:     MachineOwner
---------

6: kd> lmvm GenuineIntel
Browse full module list
start             end                 module name
Mini Kernel Dump does not contain unloaded driver list

Cromax · Jul 10, 2022

Did you replace PSU? Cause if its still old psu it probably variable voltage

ShamrockRig · Jul 10, 2022

glasskuter said:
It may not be applicable to you but I wanted to mention the following points anyway. If either turns out to affect you zbook will probably find it in your logs..

Another user who was using an RTX 3080 gpu reported kernel power event 41 just yesterday. Another on 5/3 using an RTX 3080. @zbook you helped both of them. While trying to help the guy yesterday I found quite a few reports across the web on both the 2070 and 3080 gpu causing event 41. Are you overclocking this gpu? It was advised on several of the forums I was reading on (including Nvidia's) that the power limit on these graphics cards should be lowered for testing. Have you monitored the temps of this gpu through Geforce Experience.? Maximum power may be causing it to overheat.

Another user using a gaming rig with RTX 2070 traced his Event 41 BSOD problem back to Corsair ICUE software.

Not sure if its helpful, I have a 2070super and ive got two reported LiveKernalEvents code 141 in maybe the last 10 days or so. I've been running +180mhz on the core and +500mhz on the MemClock for around 2 years now.
Again, I dont really have any help to add, Just thought id mention in case its a thing :)

ShamrockRig · Jul 10, 2022

Oh and secondly, My temp limit is at 116%, My core voltage is +100%, Temp limit is set at 88. Max ive ever seen is something like high 60's, Custom fan curve too ofcourse.

matt11 · Jul 10, 2022

glasskuter said:
I noticed in your post dated June 18 you said "MSI said they repaired a component on the GPU itself as it was a hardware fault." I would not be wanting a repaired gpu but a replacement one.

If your i7-10700k is as picky as my i9-10900 when it comes to ram, I will say zbook may have a point. Mine required that all 4 ram slots be populated with exactly the same make/model ram. It did not like mixing brands, even when the pairs were in different banks and even when Crucial said their ram was compatible with the original Micron ram. I found that hard to believe since Crucial uses Micron chips, but it proved to be correct. My PC did not like it.

its just very frustrating that everything was working perfectly for over a year until just a few months ago. i will definitely be looking at replacing my RAM but I'm not able to at the moment.

matt11 · Jul 10, 2022

zbook said:

Please 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.

The above script will modify the startup and recovery system failure and virtual memory / page file settings so that they are optimal for dump file creation and dump file debugging.

Please maintain these settings throughout the troubleshooting.

If you manually power off the computer please record the date and time and post the data into this thread.

There were recent abnormal shutdowns.

One was related to problems with hibernation.

There were no recent BSOD or live kernel events recorded since June 28, 2022.

Open administrative command prompt and type or copy and paste: (plan to reboot the computer)

powercfg -hibernate off

shutdown -r

What is the status of the PSU?
See if you can swap test it.

Code:

Intel(R) Ethernet Controller (2) I225-V    PCI\VEN_8086&DEV_15F3&SUBSYS_E0001458&REV_02\4&1BA68F3E&0&00E3    This device is disabled.

Code:

Event[11800]
  Log Name: System
  Source: Microsoft-Windows-Kernel-Power
  Date: 2022-07-08T18:26:20.3440000Z
  Event ID: 41
  Task: N/A
  Level: Critical
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: DesktopZ490X
  Description:
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Code:

Event[11789]
  Log Name: System
  Source: EventLog
  Date: 2022-07-08T18:26:24.6010000Z
  Event ID: 6008
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DesktopZ490X
  Description:
The previous system shutdown at 6:03:36 PM on ?7/?8/?2022 was unexpected.

Code:

Event[11662]
  Log Name: System
  Source: Microsoft-Windows-Kernel-Power
  Date: 2022-07-08T17:23:30.6750000Z
  Event ID: 41
  Task: N/A
  Level: Critical
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: DesktopZ490X
  Description:
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Code:

Event[11652]
  Log Name: System
  Source: EventLog
  Date: 2022-07-08T17:23:36.3340000Z
  Event ID: 6008
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DesktopZ490X
  Description:
The previous system shutdown at 4:54:01 PM on ?7/?8/?2022 was unexpected.

Code:

Event[11110]
  Log Name: System
  Source: Microsoft-Windows-Kernel-Power
  Date: 2022-07-02T08:10:57.6540000Z
  Event ID: 41
  Task: N/A
  Level: Critical
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: DesktopZ490X
  Description:
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Code:

Event[11099]
  Log Name: System
  Source: EventLog
  Date: 2022-07-02T08:11:01.4480000Z
  Event ID: 6008
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DesktopZ490X
  Description:
The previous system shutdown at 9:31:13 AM on ?7/?1/?2022 was unexpected.

Code:

Event[11087]
  Log Name: System
  Source: Microsoft-Windows-Kernel-Boot
  Date: 2022-07-02T08:10:55.0920000Z
  Event ID: 16
  Task: N/A
  Level: Error
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: DesktopZ490X
  Description:
Windows failed to resume from hibernate with error status 0xC0000411.

I ran the script and command prompt. I RMA both the GPU and PSU. MSI said they fixed the GPU and sent it back and Corsair completely replaced the PSU with a brand new model. It's a 1000W Corsair PSU btw. I may be sending the GPU back again for complete replacement this week.

matt11 · Jul 10, 2022

glasskuter said:
It may not be applicable to you but I wanted to mention the following points anyway. If either turns out to affect you zbook will probably find it in your logs..

Another user who was using an RTX 3080 gpu reported kernel power event 41 just yesterday. Another on 5/3 using an RTX 3080. @zbook you helped both of them. While trying to help the guy yesterday I found quite a few reports across the web on both the 2070 and 3080 gpu causing event 41. Are you overclocking this gpu? It was advised on several of the forums I was reading on (including Nvidia's) that the power limit on these graphics cards should be lowered for testing. Have you monitored the temps of this gpu through Geforce Experience.? Maximum power may be causing it to overheat.

Another user using a gaming rig with RTX 2070 traced his Event 41 BSOD problem back to Corsair ICUE software.

I have no overclocking software installed nor any custom fan curves or anything else for the GPU or CPU. I have monitored the temps when I have been able to game and idle I'm at 25-30 C and under load up to 70-75 C

zbook · Jul 10, 2022

Please view the startup and recovery system failure settings and virtual memory / page file settings.

Post images or share links into this thread.

In a few days post a new V2 share link.

In the next post please indicate each major hardware component and the approximate swap or replacement date.
And indicate any component that had been replaced more than once in the past 45 days
CPU, GPU, Drive, RAM, Motherboard

matt11 · Jul 11, 2022

RMA's in BOLD. Everything else is original brand new from October 2020 sold by Newegg directly to me.

CPU
Intel Core i7-10700K 3.8 GHz 8-Core Processor

CPU Cooler
Corsair iCUE H150i ELITE CAPELLIX 75 CFM Liquid CPU Cooler

Motherboard
Gigabyte Z490 AORUS ULTRA ATX LGA1200 Motherboard

Memory
G.Skill Trident Z RGB 32 GB (2 x 16 GB) DDR4-3600 CL16 Memory

Storage
Western Digital Black SN750 1 TB M.2-2280 NVME Solid State Drive

Video Card
MSI GeForce RTX 2070 SUPER 8 GB GAMING X Video Card
RMA - Received back Monday, June 13, 2022 - MSI stated "the type of repair that was done was swapping of an electrical component which implies the issue was due to hardware malfunction."

Case
Corsair iCUE 4000X RGB ATX Mid Tower Case

Power Supply
Corsair RM1000x 1000 W 80+ Gold Certified Fully Modular ATX Power Supply
RMA - "Unfortunately your RM1000x (SKU: CP-9020094-NA) is no longer available. As per Corsair's warranty we are able to offer you a comparable alternative as a replacement. In this case, we can provide the RM1000x (SKU: CP-9020201-NA) as a replacement instead."
https://www.corsair.com/us/en/Categories/Products/Power-Supply-Units/RMx-Series/p/CP-9020201-NA
I accepted and installed the same day I received my GPU back from MSI

Monitor
Gigabyte G32QC 31.5" 2560x1440 165 Hz Monitor

Keyboard
Corsair K57 RGB Bluetooth Wireless Gaming Keyboard

Mouse
Corsair HARPOON RGB Wireless Optical Mouse

Headphones
SteelSeries Arctis 7 Headset

I will update in a couple days of use with new V2 logs.

Cromax · Jul 11, 2022

Did you do CHKDSK C: /F /R /X it takes longer but just in case..

matt11 · Jul 19, 2022

DESKTOPZ490X-(2022-07-19_18-13-26).zip

Compressed (zipped) Folder

1drv.ms

matt11 · Jul 19, 2022

Cromax said:
Did you do CHKDSK C: /F /R /X it takes longer but just in case..

Yes but its still crashing. it actually crashed when I ran v2 the first time today.

Cromax · Jul 19, 2022

matt11 said:
Yes but its still crashing. it actually crashed when I ran v2 the first time today.

Do you have fast startup enabled? and did you try running with 1 stick of ram testing each stick?

edit:nvm i read at begin fast startup is off

glasskuter · Jul 19, 2022

It's been very hard for me to follow what's happened in 61 posts, so forgive if my suggestion is redundant. Why not put the system in its most basic state that will boot into windows. Disconnect all peripherals except mobo, power supply, cpu, one stick of ram into bank 0 slot nearest the cpu and your boot drive. Use the integrated graphics(remember it won't handle heavy gaming). If it still crashes under normal use, swap the ram stick with the one you removed and try again. If it still crashes that eliminates it being the ram or your gpu. That leaves the mobo, cpu, m.2, or psu. I would rule out the power supply as it is new. That leaves the cpu, m.2, and mobo. You can eliminate the m.2 if you have a ssd or hdd you can clone to (better still throw a clean install on it) leaving only the cpu and mobo as the possible culprits.

If it does not crash in this basic state, you know it points to the gpu.

zbook · Jul 20, 2022

Please perform an in place upgrade repair.

Repair Install Windows 11 with an In-place Upgrade Tutorial

This tutorial will show you how to do a repair install of Windows 11 by performing an in-place upgrade without losing anything. If you need to repair or create a new recovery partition or having problems with the Windows 11 operating system on your PC, and the usual solutions will not fix it...

www.elevenforum.com

Then run the script in posts 63 and 70:

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

The script makes sure that the setting is on automatic.
The setting is no longer on automatic.
How come the setting was changed again?

matt11 · Aug 7, 2022

Sorry it's been awhile. MSI has the worst customer service ever. I've had to send my graphics card back 4 times now because they kept telling me they would replace it, so I'd send it back and 2 weeks later the same card would show up at my door. I've talked to 4 different people and they all keep telling they will replace it but then they don't. Hopefully this time. I will run a in-Place Upgrade in the mean time and when my new card shows up we will go from there.

Here is the log file from Tuneup.bat