For the last couple of weeks i've been having a persisting problem with windows seemingly crashing to a black screen whenever i play 'graphically demanding' games.
After about 4-5 minutes of gameplay (not counting being sat in a menu or paused), the monitor(s) will cease receiving input and turn themselves into the standby state, my graphics card's lighting will turn to default white and the fans will ramp up to 100%. Most of the time i can still hear audio and i can still retain control of any applications through the mouse and keyboard, although the screen(s) will be black and will not receive any input until i power the system off manually via the power button.
After trawling through event viewer i located the suspect events, an event with the code 1000 (or sometimes 1001) relating to an appcrash with dwm.exe, something i understand is a core windows process dealing with desktop windows and their effects, this in turn causes the NVIDIA drivers to crash, leading to a blacked out screen from which it will not recover.
My first fix naturally was to re-install the graphics drivers and did so via the GeForce experience application, to no effect.
Next i rolled back the drivers to a build before the issue arose. Again, no change. The system still crashed to a black screen after gameplay.
From there i decided to disable windows aero effects, the desktop slideshows and whatnot. I also re-installed the offending programs to see if that made any difference. Nothing.
I changed the windows power plan to high-power mode, removed any unused USB devices save the mouse and keyboard, used just the one monitor, reseated every component and cleared the ports for dust and debris, turned down the in-game graphics settings (which should have been my first move but it escaped me until then), ensured windows was up to date, and tried once more .... black screen.
Went through and deleted everything related to Nvidia and it's drivers, uninstalled via DDU and re-installed the older drivers manually via their website. Deleted any program that allowed altering of the GPU RGB settings/fan control and such, including monitoring software and tried again. Interestingly this allowed me to play for a good hour without a crash, and i suspected i could have gone longer but after rebooting the system, it happened again. I ran a Furmark test to see if the GPU would crap out but after twenty minutes on a rather demanding stress test, nothing happened, i only stopped as my temperatures were getting high.
Strange to think it can handle a stress test but not in an actual game.
Nevertheless i pressed on. I tested it with only one stick of RAM in the PC, and went through each systematically, the crash occurred with all of them.
I went and wiped my current windows user profile, re-installed windows afresh and installed nothing but the graphics drivers for my card and the game as a testbed, as i could reliably replicate the crash within a short time frame. It happened once more.
I started to suspect my hardware was an issue so i tested it out with a friends GPU in the system and it didn't crash, though after about 40-50 minutes, the system gave me a BSOD with an IRQL_NOT_LESS_OR_EQUAL error code.
That leads me up to now, i figured it could be the PSU, it's getting on four years old though has not shown any signs of wear or tear recently, though components, like people age and i can understand that. Though i don't have a spare at hand at the moment to test with.
As for the errors, they are almost always followed by a LiveKernelEvent with a code of 141, or sometimes 117, rarely. Looking in windows reliability monitor, there can be as little as one 'Desktop Windows Manager - stopped working' entries, from what i understand windows is trying to reboot the drivers to no avail.
Unfortunately, since resetting windows, most of the logs i have are gone and the only ones are recently. Though i have a couple of entries from one of the first few times it has happened.
https://drive.google.com/file/d/1BKPjCoTNtWst8urincWTinNDJ-Nr3sD_/view - Google Drive to a reliability report XML.
Attached is a DxDiag from before i swapped out the GPU for another one. Though i can post that too if you want. Any other information i'd be happy to provide.
After about 4-5 minutes of gameplay (not counting being sat in a menu or paused), the monitor(s) will cease receiving input and turn themselves into the standby state, my graphics card's lighting will turn to default white and the fans will ramp up to 100%. Most of the time i can still hear audio and i can still retain control of any applications through the mouse and keyboard, although the screen(s) will be black and will not receive any input until i power the system off manually via the power button.
After trawling through event viewer i located the suspect events, an event with the code 1000 (or sometimes 1001) relating to an appcrash with dwm.exe, something i understand is a core windows process dealing with desktop windows and their effects, this in turn causes the NVIDIA drivers to crash, leading to a blacked out screen from which it will not recover.
My first fix naturally was to re-install the graphics drivers and did so via the GeForce experience application, to no effect.
Next i rolled back the drivers to a build before the issue arose. Again, no change. The system still crashed to a black screen after gameplay.
From there i decided to disable windows aero effects, the desktop slideshows and whatnot. I also re-installed the offending programs to see if that made any difference. Nothing.
I changed the windows power plan to high-power mode, removed any unused USB devices save the mouse and keyboard, used just the one monitor, reseated every component and cleared the ports for dust and debris, turned down the in-game graphics settings (which should have been my first move but it escaped me until then), ensured windows was up to date, and tried once more .... black screen.
Went through and deleted everything related to Nvidia and it's drivers, uninstalled via DDU and re-installed the older drivers manually via their website. Deleted any program that allowed altering of the GPU RGB settings/fan control and such, including monitoring software and tried again. Interestingly this allowed me to play for a good hour without a crash, and i suspected i could have gone longer but after rebooting the system, it happened again. I ran a Furmark test to see if the GPU would crap out but after twenty minutes on a rather demanding stress test, nothing happened, i only stopped as my temperatures were getting high.
Strange to think it can handle a stress test but not in an actual game.
Nevertheless i pressed on. I tested it with only one stick of RAM in the PC, and went through each systematically, the crash occurred with all of them.
I went and wiped my current windows user profile, re-installed windows afresh and installed nothing but the graphics drivers for my card and the game as a testbed, as i could reliably replicate the crash within a short time frame. It happened once more.
I started to suspect my hardware was an issue so i tested it out with a friends GPU in the system and it didn't crash, though after about 40-50 minutes, the system gave me a BSOD with an IRQL_NOT_LESS_OR_EQUAL error code.
That leads me up to now, i figured it could be the PSU, it's getting on four years old though has not shown any signs of wear or tear recently, though components, like people age and i can understand that. Though i don't have a spare at hand at the moment to test with.
As for the errors, they are almost always followed by a LiveKernelEvent with a code of 141, or sometimes 117, rarely. Looking in windows reliability monitor, there can be as little as one 'Desktop Windows Manager - stopped working' entries, from what i understand windows is trying to reboot the drivers to no avail.
Unfortunately, since resetting windows, most of the logs i have are gone and the only ones are recently. Though i have a couple of entries from one of the first few times it has happened.
Log Name: Application
Source: Windows Error Reporting
Date: 22/02/2022 22:53:58
Event ID: 1001
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: Elliots-PC
Description:
Fault bucket 1486643659604955993, type 4
Event Name: APPCRASH
Response: Not available
Cab Id: 0
Problem signature:
P1: dwm.exe
P2: 10.0.19041.746
P3: 6be51595
P4: KERNELBASE.dll
P5: 10.0.19041.1503
P6: b2acaea9
P7: e0464645
P8: 000000000010b382
P9:
P10:
Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERBF94.tmp.dmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERC032.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERC042.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERC05E.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERC06F.tmp.txt
These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_dwm.exe_f44735eac4cf1775ef43a9cc34beb965765144b0_c2f10bab_e9ea1991-a1a2-480f-9915-297252eae2cf
Analysis symbol:
Rechecking for solution: 0
Report Id: eb3a0bf1-21f4-4a90-b9b1-55c83f021618
Report Status: 268435456
Hashed bucket: d6508a4cd1925dc5d4a19e8826571359
Cab Guid: 0
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Windows Error Reporting" />
<EventID Qualifiers="0">1001</EventID>
<Version>0</Version>
<Level>4</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2022-02-22T22:53:58.2783051Z" />
<EventRecordID>156463</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>Application</Channel>
<Computer>Elliots-PC</Computer>
<Security />
</System>
<EventData>
<Data>1486643659604955993</Data>
<Data>4</Data>
<Data>APPCRASH</Data>
<Data>Not available</Data>
<Data>0</Data>
<Data>dwm.exe</Data>
<Data>10.0.19041.746</Data>
<Data>6be51595</Data>
<Data>KERNELBASE.dll</Data>
<Data>10.0.19041.1503</Data>
<Data>b2acaea9</Data>
<Data>e0464645</Data>
<Data>000000000010b382</Data>
<Data>
</Data>
<Data>
</Data>
<Data>
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERBF94.tmp.dmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERC032.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERC042.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERC05E.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERC06F.tmp.txt</Data>
<Data>\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_dwm.exe_f44735eac4cf1775ef43a9cc34beb965765144b0_c2f10bab_e9ea1991-a1a2-480f-9915-297252eae2cf</Data>
<Data>
</Data>
<Data>0</Data>
<Data>eb3a0bf1-21f4-4a90-b9b1-55c83f021618</Data>
<Data>268435456</Data>
<Data>d6508a4cd1925dc5d4a19e8826571359</Data>
<Data>0</Data>
</EventData>
</Event>
Source: Windows Error Reporting
Date: 22/02/2022 22:53:58
Event ID: 1001
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: Elliots-PC
Description:
Fault bucket 1486643659604955993, type 4
Event Name: APPCRASH
Response: Not available
Cab Id: 0
Problem signature:
P1: dwm.exe
P2: 10.0.19041.746
P3: 6be51595
P4: KERNELBASE.dll
P5: 10.0.19041.1503
P6: b2acaea9
P7: e0464645
P8: 000000000010b382
P9:
P10:
Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERBF94.tmp.dmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERC032.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERC042.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERC05E.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERC06F.tmp.txt
These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_dwm.exe_f44735eac4cf1775ef43a9cc34beb965765144b0_c2f10bab_e9ea1991-a1a2-480f-9915-297252eae2cf
Analysis symbol:
Rechecking for solution: 0
Report Id: eb3a0bf1-21f4-4a90-b9b1-55c83f021618
Report Status: 268435456
Hashed bucket: d6508a4cd1925dc5d4a19e8826571359
Cab Guid: 0
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Windows Error Reporting" />
<EventID Qualifiers="0">1001</EventID>
<Version>0</Version>
<Level>4</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2022-02-22T22:53:58.2783051Z" />
<EventRecordID>156463</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>Application</Channel>
<Computer>Elliots-PC</Computer>
<Security />
</System>
<EventData>
<Data>1486643659604955993</Data>
<Data>4</Data>
<Data>APPCRASH</Data>
<Data>Not available</Data>
<Data>0</Data>
<Data>dwm.exe</Data>
<Data>10.0.19041.746</Data>
<Data>6be51595</Data>
<Data>KERNELBASE.dll</Data>
<Data>10.0.19041.1503</Data>
<Data>b2acaea9</Data>
<Data>e0464645</Data>
<Data>000000000010b382</Data>
<Data>
</Data>
<Data>
</Data>
<Data>
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERBF94.tmp.dmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERC032.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERC042.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERC05E.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERC06F.tmp.txt</Data>
<Data>\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_dwm.exe_f44735eac4cf1775ef43a9cc34beb965765144b0_c2f10bab_e9ea1991-a1a2-480f-9915-297252eae2cf</Data>
<Data>
</Data>
<Data>0</Data>
<Data>eb3a0bf1-21f4-4a90-b9b1-55c83f021618</Data>
<Data>268435456</Data>
<Data>d6508a4cd1925dc5d4a19e8826571359</Data>
<Data>0</Data>
</EventData>
</Event>
Source
Windows
Summary
Hardware error
Date
23/02/2022 00:37
Status
Not reported
Description
A problem with your hardware caused Windows to stop working correctly.
Problem signature
Problem Event Name: LiveKernelEvent
Code: 141
Parameter 1: ffff8309ea2d9050
Parameter 2: fffff80639968ca4
Parameter 3: 0
Parameter 4: d64
OS version: 10_0_19043
Service Pack: 0_0
Product: 768_1
OS Version: 10.0.19043.2.0.0.768.101
Locale ID: 1033
Windows
Summary
Hardware error
Date
23/02/2022 00:37
Status
Not reported
Description
A problem with your hardware caused Windows to stop working correctly.
Problem signature
Problem Event Name: LiveKernelEvent
Code: 141
Parameter 1: ffff8309ea2d9050
Parameter 2: fffff80639968ca4
Parameter 3: 0
Parameter 4: d64
OS version: 10_0_19043
Service Pack: 0_0
Product: 768_1
OS Version: 10.0.19043.2.0.0.768.101
Locale ID: 1033
https://drive.google.com/file/d/1BKPjCoTNtWst8urincWTinNDJ-Nr3sD_/view - Google Drive to a reliability report XML.
Attached is a DxDiag from before i swapped out the GPU for another one. Though i can post that too if you want. Any other information i'd be happy to provide.