Question GPU fans spin up to 100%, screen goes black and pc reboots after a while - hilfe, hilfe!!! :)

Nov 8, 2022
5
0
10
Hello fellow gamers!

I require assistance from the experts here.

First of all my rig:
Asus X99 Mobo
i7-6850k
32gb DDR4-3200 RAM
Asus Strix 1080ti GPU
2tb M.2 SSD
EVGA Supernova 1000w PSU.
Monitor: Asus ROG PG27AQ - 4k

My issue:
2 weeks ago when i was playing f1 22, my screen froze with a click emanating from the monitor once, and had to restart the PC. Since then whenever I game, randomly (usually 10-20min after starting or even less after the issue happens) the GPU fans spin up to max, the screen goes black and the pc eventually restarts itself.

Ive read a lot on the internet but I am unsure the best way to trouble shoot
What ive done so far:
  • Reinstalled Windows
  • cleaned out the pc
  • reapplied thermal paste to CPU and GPU, their temps are very good under load (40 degrees on CPU and 50 degrees on GPU)
  • reseated GPU and tried it in the other PCIE x16 slot as well.
  • reattached all the power supply cables into all the components (mobo, ssd-s, gpu, cpu)

Ive read it could be GPU or PSU issue, but i thought Id ask the expert community here.

Looking forward to some advice, appreciate it in advance! If i need to supply any additional information, ill be checking this post frequently.
 
Nov 8, 2022
5
0
10
Which SuperNova exactly? G1, G2, G3, GQ, PS, P2, T2?

Also, what Event Viewer (Windows Logs -> System) says at the time of the black screens?

But as far as symptoms go, it points towards GPU issue. If it were PSU issue, PC would reboot/shut down on an instant.
Here, you'd need 2nd, known to work GPU, to test it out.

its EVGA Supernova 1000W G2 80+Gold

Event Viewer:
  • Faults: 455, 1001,1101,6008, 10001,
  • Warnings: 1, 4, 27, 63, 123,134, 200-202, 225, 360,1534,4155,10010,10016,
  • Critical:41 (63) - after looking this up, this occurs when PSU is faulty... - but then again, im unitiated and i dont know what this is :D

Also the system created a memory dump, i link:


Microsoft (R) Windows Debugger Version 10.0.25200.1003 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\MEMORY.DMP]
Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.

Symbol search path is: srv*
Executable search path is:
Missing image name, possible paged-out or corrupt data.
Unable to load image Unknown_Module_0000000000000000, Win32 error 0n2 *** WARNING: Unable to verify timestamp for Unknown_Module_0000000000000000
*** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_0000000000000000 Unable to add module at 0000000000000000
WARNING: .reload failed, module list may be incomplete
WARNING: Mismatch between nt!KdDebuggerDataBlock and nt!KdVersionBlock - KernBase (Kernel Base Address)
Windows 10 Kernel Version 19041 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff80750e00000 PsLoadedModuleList = 0xfffff80751a2a270
Debug session time: Tue Nov 8 05:16:09.942 2022 (UTC + 1:00)
System Uptime: 0 days 1:21:45.619
Missing image name, possible paged-out or corrupt data.
Unable to load image Unknown_Module_0000000000000000, Win32 error 0n2 *** WARNING: Unable to verify timestamp for Unknown_Module_0000000000000000
*** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_0000000000000000 Unable to add module at 0000000000000000
WARNING: .reload failed, module list may be incomplete
Loading Kernel Symbols
Missing image name, possible paged-out or corrupt data.
.Unable to load image Unknown_Module_0000000000000000, Win32 error 0n2 *** WARNING: Unable to verify timestamp for Unknown_Module_0000000000000000
*** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_0000000000000000 Unable to add module at 0000000000000000
Unable to read KLDR_DATA_TABLE_ENTRY at 00000000`00000000 - HRESULT 0x80004002

WARNING: .reload failed, module list may be incomplete
GetContextState failed, 0xD0000147
CS descriptor lookup failed
GetContextState failed, 0xD0000147
For analysis of this file, run !analyze -v
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
Unable to get program counter
No flat address for current instruction
?? ???
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147


And the issue only occurs while gaming, so essentially when GPU goes to 1950 MHz Core frequency
Thanks for those who are helping !
 
Nov 8, 2022
5
0
10
Also ran a GPU stress test with the OCCT program.

The issue happened again.

The following eventviewer logs were created:
Fault: 6008, 161,1001,1005
Critical: 41 (63)

At the moment of failure the x99 Motherboard was showing code:30
 
Last edited:

Aeacus

Titan
Ambassador
Supernova G2 is good quality PSU and i doubt it being an issue. Still, there are lemons, even among the best.
Here, you'd need 2nd, known to work and good quality PSU to test it out. Just hook 2nd PSU up, by also replacing all power cables and test it again.

Kernel error 41 is to do with power delivery. Could be PSU, or could be main electricity grid. If you'd have good quality UPS, then main electricity grid can be excluded. However, you also have other errors as well.

As far as memory dumps go, here i need to summon @Colif , who is expert in those and can define them. I'm specialized on hardware myself.

-----

Regarding hardware, there is no other way than having 2nd component, to test it.

I'd 1st get 2nd PSU and test with it, since some errors point towards PSU issue.
If 2nd PSU fixes your issues, we can safely assume it was PSU issue. If it doesn't fix it, i'd replace GPU next and test with 2nd GPU as well.

If 2nd GPU, running off from 2nd PSU, fixes your issue, all is good. If not, issue can rely somewhere in software (OS).
With software, analyzing dumps can pinpoint the exact issue. If they don't, clean Win install would get rid of all software issues.
 

Colif

Win 11 Master
Moderator
not much i can do with corrupted data in that report

Can you follow option one on the following link - here - and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD - that creates a file in c windows/minidump after the next BSOD

  1. Open Windows File Explore
  2. Navigate to C:\Windows\Minidump
  3. Copy the mini-dump files out onto your Desktop
  4. Do not use Winzip, use the built in facility in Windows
  5. Select those files on your Desktop, right click them and choose 'Send to' - Compressed (zipped) folder
  6. Upload the zip file to the Cloud (OneDrive, DropBox . . . etc.)
  7. Then post a link here to the zip file, so we can take a look for you . . .
41(63) just means an unexpected restart, it doesn't mean PSU in all cases.

what brand m.2 drive?