PC Restarts while gaming

PaulScott670

Bronze Level Poster
Hi all,

I got a blue screen error while playing Warzone 2. Apparently from what I've read it's a hardware issue. I have attached a copy of the reliability monitor report. My specs are below also. Thanks.

Case
CORSAIR iCUE 5000T RGB MID TOWER GAMING CASE
Promotional Item
Whilst stocks last, get a Corsair Peripheral Bundle with every iCUE system! [UK Layout]
Processor (CPU)
Intel® Core™ i9 24-Core Processor i9-13900K (Up to 5.8GHz) 36MB Cache
Motherboard
ASUS® ROG MAXIMUS Z790 HERO (DDR5, LGA1700, USB 3.2, PCIe 5.0) - ARGB Ready
Memory (RAM)
32GB Corsair DOMINATOR PLATINUM RGB DDR5 5600MHz (2 x 16GB)
Graphics Card
24GB ASUS TUF GEFORCE RTX 4090 OC EDITION - HDMI, DP
1st M.2 SSD Drive
4TB CORSAIR MP600 PRO NVMe PCIe M.2 SSD (up to 7000 MB/R, 6850 MB/W)
1st M.2 SSD Drive
2TB CORSAIR FORCE MP600 NVMe PCIe M.2 SSD (up to 4950 MB/R, 4000 MB/W)
Power Supply
CORSAIR 1000W RMx SERIES™ - MODULAR 80 PLUS GOLD, ULTRA QUIET
Power Cable
1 x 1.5 Metre UK Power Cable (Kettle Lead, 1.0mm Core)
Processor Cooling
CORSAIR iCUE H150i ELITE LCD XT RGB CPU Cooler
Thermal Paste
STANDARD THERMAL PASTE FOR SUFFICIENT COOLING
Extra Case Fans
3 x Corsair LL120 RGB LED Fan + Controller Kit
Sound Card
ONBOARD 6 CHANNEL (5.1) HIGH DEF AUDIO (AS STANDARD)
Network Card
10/100/1000 GIGABIT LAN PORT
USB/Thunderbolt Options
MIN. 2 x USB 3.0 & 2 x USB 2.0 PORTS @ BACK PANEL + MIN. 2 FRONT PORTS
Operating System
Windows 11 Home 64 Bit - inc. Single Licence [KUK-00003]
 

Attachments

  • Screenshot 2023-06-16 213050.png
    Screenshot 2023-06-16 213050.png
    24.6 KB · Views: 81

SpyderTracks

We love you Ukraine
Hi all,

I got a blue screen error while playing Warzone 2. Apparently from what I've read it's a hardware issue. I have attached a copy of the reliability monitor report. My specs are below also. Thanks.

Case
CORSAIR iCUE 5000T RGB MID TOWER GAMING CASE
Promotional Item
Whilst stocks last, get a Corsair Peripheral Bundle with every iCUE system! [UK Layout]
Processor (CPU)
Intel® Core™ i9 24-Core Processor i9-13900K (Up to 5.8GHz) 36MB Cache
Motherboard
ASUS® ROG MAXIMUS Z790 HERO (DDR5, LGA1700, USB 3.2, PCIe 5.0) - ARGB Ready
Memory (RAM)
32GB Corsair DOMINATOR PLATINUM RGB DDR5 5600MHz (2 x 16GB)
Graphics Card
24GB ASUS TUF GEFORCE RTX 4090 OC EDITION - HDMI, DP
1st M.2 SSD Drive
4TB CORSAIR MP600 PRO NVMe PCIe M.2 SSD (up to 7000 MB/R, 6850 MB/W)
1st M.2 SSD Drive
2TB CORSAIR FORCE MP600 NVMe PCIe M.2 SSD (up to 4950 MB/R, 4000 MB/W)
Power Supply
CORSAIR 1000W RMx SERIES™ - MODULAR 80 PLUS GOLD, ULTRA QUIET
Power Cable
1 x 1.5 Metre UK Power Cable (Kettle Lead, 1.0mm Core)
Processor Cooling
CORSAIR iCUE H150i ELITE LCD XT RGB CPU Cooler
Thermal Paste
STANDARD THERMAL PASTE FOR SUFFICIENT COOLING
Extra Case Fans
3 x Corsair LL120 RGB LED Fan + Controller Kit
Sound Card
ONBOARD 6 CHANNEL (5.1) HIGH DEF AUDIO (AS STANDARD)
Network Card
10/100/1000 GIGABIT LAN PORT
USB/Thunderbolt Options
MIN. 2 x USB 3.0 & 2 x USB 2.0 PORTS @ BACK PANEL + MIN. 2 FRONT PORTS
Operating System
Windows 11 Home 64 Bit - inc. Single Licence [KUK-00003]
That’s not the cause, that’s the symptom of the pc shutting down unexpectedly.

You need the error before that that triggered the crash.

It’s best to follow the guide for uploading logs:

 

PaulScott670

Bronze Level Poster
That’s not the cause, that’s the symptom of the pc shutting down unexpectedly.

You need the error before that that triggered the crash.

It’s best to follow the guide for uploading logs:

I looked through the event viewer filtering for error and critical etc. nothing was there that matched up with the timing of my issue.
 

ubuysa

The BSOD Doctor
It's kinda risky making a diagnosis based on only one dump, is that the only one you've had?

That said, this one dump is pretty conclusive. The bugcheck is the classic IRQL_NOT_LESS_OR_EQUAL and what that means is that a kernel-mode driver was running at an elevated IRQL (when page faults are not permitted) and it attempted to access a memory location that is invalid (either unallocated or paged out). The dump triage is able to identify the failing driver...
Rich (BB code):
FAILURE_BUCKET_ID:  AV_cpuz157_x64!unknown_function
The cpuz157_x64.sys driver is of course a component of CPUZ. In the stack trace we see more clearly where it was involved...
Rich (BB code):
23: kd> knL
 # Child-SP          RetAddr               Call Site
00 fffff88d`36141c68 fffff802`3c0418a9     nt!KeBugCheckEx
01 fffff88d`36141c70 fffff802`3c03cf34     nt!KiBugCheckDispatch+0x69
02 fffff88d`36141db0 fffff802`3c028208     nt!KiPageFault+0x474
03 fffff88d`36141f48 fffff802`3bf3ec92     nt!HalpPciReadMmConfigUshort+0x8
04 fffff88d`36141f50 fffff802`3bf3eae6     nt!HalpPCIPerformConfigAccess+0x5a
05 fffff88d`36141f80 fffff802`3bf3e995     nt!HalpPciAccessMmConfigSpace+0x82
06 fffff88d`36141fc0 fffff802`3bf95f0a     nt!HalpPCIConfig+0xc5
07 fffff88d`36142040 fffff802`3bf95e67     nt!HalpReadPCIConfig+0x56
08 fffff88d`36142090 fffff802`3bf95d81     nt!HalpGetPCIData+0xd3
09 fffff88d`36142160 fffff802`9e085502     nt!HalGetBusDataByOffset+0x41
0a fffff88d`361421a0 00000000`00000000     cpuz157_x64+0x5502
The cpuz157_x64.sys driver is called first (these are push-down stacks) and if we look in more detail at that frame (frame 10) we can see the problem...
Rich (BB code):
23: kd> .frame /r 10
Cannot find frame 0x10, previous scope unchanged
0a fffff88d`361421a0 00000000`00000000     cpuz157_x64+0x5502
rax=fffff8023c020000 rbx=0000000000000004 rcx=fffff7e100022000
rdx=000000ae5e5fdf40 rsi=0000000000000002 rdi=fffff8029e080000
rip=fffff8029e085502 rsp=fffff88d361421a0 rbp=fffff88d361426f1
 r8=0000000000000052  r9=0000000000000052 r10=fffff8023c028200
r11=0000000000000000 r12=0000000000000000 r13=ffffd709c390fc40
r14=ffffd709ca67f8e0 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00040282
cpuz157_x64+0x5502:
fffff802`9e085502 ??              ???
The instruction pointer (the RIP register) is pointing into the cpuz157_x64.sys driver (at 0x5502 bytes into cpuz157_x64) and this location is invalid (the ?? ??? characters indicate an invalid location). As you can see from the details of cpuz157_x64.sys below, the module exists between address 0xfffff802`9e080000 up to 0xfffff802`9e08d000, so the address cpuz157_x64+0x5502 (0xfffff802`9e085502) is within the cpuz157_x64.sys driver. This is thus a cpux157_x64.sys glitch....
Rich (BB code):
23: kd> lmDvmcpuz157_x64
Browse full module list
start             end                 module name
fffff802`9e080000 fffff802`9e08d000   cpuz157_x64 T (no symbols)          
    Loaded symbol image file: cpuz157_x64.sys
    Image path: cpuz157_x64.sys
    Image name: cpuz157_x64.sys
    Browse all global symbols  functions  data
    Timestamp:        Tue Jan 31 11:36:56 2023 (63D8E138)
    CheckSum:         0000D770
    ImageSize:        0000D000
    Translations:     0000.04b0 0000.0
Now things become strange because the install date of this driver is January 2023, yet the current version of CPUZ is 2.06. Version 1.57 is over 10 years old now, so I don't really know what's going on there. I would completely uninstall CPUZ (in fact I'd uninstall all CPUID products), reboot, and then download and install the latest version.
 

PaulScott670

Bronze Level Poster
It's kinda risky making a diagnosis based on only one dump, is that the only one you've had?

That said, this one dump is pretty conclusive. The bugcheck is the classic IRQL_NOT_LESS_OR_EQUAL and what that means is that a kernel-mode driver was running at an elevated IRQL (when page faults are not permitted) and it attempted to access a memory location that is invalid (either unallocated or paged out). The dump triage is able to identify the failing driver...
Rich (BB code):
FAILURE_BUCKET_ID:  AV_cpuz157_x64!unknown_function
The cpuz157_x64.sys driver is of course a component of CPUZ. In the stack trace we see more clearly where it was involved...
Rich (BB code):
23: kd> knL
 # Child-SP          RetAddr               Call Site
00 fffff88d`36141c68 fffff802`3c0418a9     nt!KeBugCheckEx
01 fffff88d`36141c70 fffff802`3c03cf34     nt!KiBugCheckDispatch+0x69
02 fffff88d`36141db0 fffff802`3c028208     nt!KiPageFault+0x474
03 fffff88d`36141f48 fffff802`3bf3ec92     nt!HalpPciReadMmConfigUshort+0x8
04 fffff88d`36141f50 fffff802`3bf3eae6     nt!HalpPCIPerformConfigAccess+0x5a
05 fffff88d`36141f80 fffff802`3bf3e995     nt!HalpPciAccessMmConfigSpace+0x82
06 fffff88d`36141fc0 fffff802`3bf95f0a     nt!HalpPCIConfig+0xc5
07 fffff88d`36142040 fffff802`3bf95e67     nt!HalpReadPCIConfig+0x56
08 fffff88d`36142090 fffff802`3bf95d81     nt!HalpGetPCIData+0xd3
09 fffff88d`36142160 fffff802`9e085502     nt!HalGetBusDataByOffset+0x41
0a fffff88d`361421a0 00000000`00000000     cpuz157_x64+0x5502
The cpuz157_x64.sys driver is called first (these are push-down stacks) and if we look in more detail at that frame (frame 10) we can see the problem...
Rich (BB code):
23: kd> .frame /r 10
Cannot find frame 0x10, previous scope unchanged
0a fffff88d`361421a0 00000000`00000000     cpuz157_x64+0x5502
rax=fffff8023c020000 rbx=0000000000000004 rcx=fffff7e100022000
rdx=000000ae5e5fdf40 rsi=0000000000000002 rdi=fffff8029e080000
rip=fffff8029e085502 rsp=fffff88d361421a0 rbp=fffff88d361426f1
 r8=0000000000000052  r9=0000000000000052 r10=fffff8023c028200
r11=0000000000000000 r12=0000000000000000 r13=ffffd709c390fc40
r14=ffffd709ca67f8e0 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00040282
cpuz157_x64+0x5502:
fffff802`9e085502 ??              ???
The instruction pointer (the RIP register) is pointing into the cpuz157_x64.sys driver (at 0x5502 bytes into cpuz157_x64) and this location is invalid (the ?? ??? characters indicate an invalid location). As you can see from the details of cpuz157_x64.sys below, the module exists between address 0xfffff802`9e080000 up to 0xfffff802`9e08d000, so the address cpuz157_x64+0x5502 (0xfffff802`9e085502) is within the cpuz157_x64.sys driver. This is thus a cpux157_x64.sys glitch....
Rich (BB code):
23: kd> lmDvmcpuz157_x64
Browse full module list
start             end                 module name
fffff802`9e080000 fffff802`9e08d000   cpuz157_x64 T (no symbols)          
    Loaded symbol image file: cpuz157_x64.sys
    Image path: cpuz157_x64.sys
    Image name: cpuz157_x64.sys
    Browse all global symbols  functions  data
    Timestamp:        Tue Jan 31 11:36:56 2023 (63D8E138)
    CheckSum:         0000D770
    ImageSize:        0000D000
    Translations:     0000.04b0 0000.0
Now things become strange because the install date of this driver is January 2023, yet the current version of CPUZ is 2.06. Version 1.57 is over 10 years old now, so I don't really know what's going on there. I would completely uninstall CPUZ (in fact I'd uninstall all CPUID products), reboot, and then download and install the latest version.

Thank you. I’ve had multiple issues with this system, I’ve been advised to do so many things. One of them being a clean install. I haven’t come across CPUID at all to be honest. How do I go about uninstalling then reinstalling?
 

TonyCarter

VALUED CONTRIBUTOR
Thank you. I’ve had multiple issues with this system, I’ve been advised to do so many things. One of them being a clean install. I haven’t come across CPUID at all to be honest. How do I go about uninstalling then reinstalling?
Did you do a full 'format & reinstall' or just a 'Windows reset'?

Maybe the old version of CPUZ was installed as part of the optional installs with the motherboard...as I remember my Armoury Crate offering all sorts of rubbish, which is why I didn't reinstall it after wiping mine.
 

PaulScott670

Bronze Level Poster
Did you do a full 'format & reinstall' or just a 'Windows reset'?

Maybe the old version of CPUZ was installed as part of the optional installs with the motherboard...as I remember my Armoury Crate offering all sorts of rubbish, which is why I didn't reinstall it after wiping mine.
Full format/clean install.
 

PaulScott670

Bronze Level Poster
Formatted all drivers etc. Clean install of windows. All recommended windows updates. But while it was doing this Armory crate auto installed.
 

Martinr36

MOST VALUED CONTRIBUTOR
Clean install instructions

Download a new copy of Windows using the Media Creation Tool (Second option on linked page) to an 8GB (min) USB.
Boot that USB and choose a Custom Install.
Delete all UEFI partitions on the system drive (EFI System, Recovery, MSR Reserved, Primary).
Select the unallocated space that results and click the Next button. The installer will create the correct partitions and install Windows.
Run Windows Update repeatedly, even across reboots, until no more updates are found.
You may need/want to download and install the latest graphics driver from the Nvidia/AMD website (they change so regularly the latest version isn't always in the Windows libraries).

This is also worth a watch
 

PaulScott670

Bronze Level Poster
But you’ve got cpuz installed and you don’t know how, and armoury crate and you’re facing instability. It’s not a clean install.

I deleted all partitions and formatted all drives. I don’t know what else I could have done? While I was installing all windows/optional updates as I was advised to do. Armoury crate was installed.
 

SpyderTracks

We love you Ukraine
I deleted all partitions and formatted all drives. I don’t know what else I could have done? While I was installing all windows/optional updates as I was advised to do. Armoury crate was installed.
I’m not saying you didn’t, what I’m saying is that you have programs that’s shouldn’t be installed causing instability. So you need a clean install, especially as you don’t know how one of them was installed. It’s not a stable installation.

You shouldn’t be formatting anything on a clean install, not sure where you’re getting that from

The guide above shows you how to stop armoury crate installing.
 
Top