While I was using my PC (simply going through my files) the screen went dark and the fans went very loud, switched it off using the power button on the case and turned it back on, everything seems to be working fine, what was the reason for this?
The marked "Critical" event is when I forced the shutdown as it says this: So the events timed at 11:27 PM.
Log Name: Application Source: Application Error Date: 14/04/2024 11:27:27 pm Event ID: 1000 Task Category: Application Crashing Events Level: Error Keywords: User: S-1-5-90-0-7 Computer: DESKTOP-9V3QBF9 Description: Faulting application name: dwm.exe, version: 10.0.22621.2506, time stamp: 0xdef1fe51 Faulting module name: dwmcore.dll, version: 10.0.22621.3447, time stamp: 0x1501f850 Exception code: 0x8898008d Fault offset: 0x000000000011d6cd Faulting process id: 0x0x2AF0 Faulting application start time: 0x0x1DA8EAA29BA7480 Faulting application path: C:\Windows\System32\dwm.exe Faulting module path: C:\Windows\System32\dwmcore.dll Report Id: c05ac5f0-eee5-4169-9ad9-1eea978e626e Faulting package full name: Faulting package-relative application ID: Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Application Error" Guid="{a0e9b465-b939-57d7-b27d-95d8e925ff57}" /> <EventID>1000</EventID> <Version>0</Version> <Level>2</Level> <Task>100</Task> <Opcode>0</Opcode> <Keywords>0x8000000000000000</Keywords> <TimeCreated SystemTime="2024-04-14T20:27:27.0301041Z" /> <EventRecordID>1299</EventRecordID> <Correlation /> <Execution ProcessID="3920" ThreadID="11316" /> <Channel>Application</Channel> <Computer>DESKTOP-9V3QBF9</Computer> <Security UserID="S-1-5-90-0-7" /> </System> <EventData> <Data Name="AppName">dwm.exe</Data> <Data Name="AppVersion">10.0.22621.2506</Data> <Data Name="AppTimeStamp">def1fe51</Data> <Data Name="ModuleName">dwmcore.dll</Data> <Data Name="ModuleVersion">10.0.22621.3447</Data> <Data Name="ModuleTimeStamp">1501f850</Data> <Data Name="ExceptionCode">8898008d</Data> <Data Name="FaultingOffset">000000000011d6cd</Data> <Data Name="ProcessId">0x2af0</Data> <Data Name="ProcessCreationTime">0x1da8eaa29ba7480</Data> <Data Name="AppPath">C:\Windows\System32\dwm.exe</Data> <Data Name="ModulePath">C:\Windows\System32\dwmcore.dll</Data> <Data Name="IntegratorReportId">c05ac5f0-eee5-4169-9ad9-1eea978e626e</Data> <Data Name="PackageFullName"> </Data> <Data Name="PackageRelativeAppId"> </Data> </EventData> </Event> Log Name: Application Source: Dwminit Date: 14/04/2024 11:27:29 pm Event ID: 0 Task Category: None Level: Warning Keywords: Classic User: N/A Computer: DESKTOP-9V3QBF9 Description: The Desktop Window Manager process has exited. (Process exit code: 0x8898008d, Restart count: 2, Primary display device ID: NVIDIA GeForce GTX 1660 SUPER) Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Dwminit" /> <EventID Qualifiers="32770">0</EventID> <Version>0</Version> <Level>3</Level> <Task>0</Task> <Opcode>0</Opcode> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2024-04-14T20:27:29.0148640Z" /> <EventRecordID>1300</EventRecordID> <Correlation /> <Execution ProcessID="1300" ThreadID="0" /> <Channel>Application</Channel> <Computer>DESKTOP-9V3QBF9</Computer> <Security /> </System> <EventData> <Data>0x8898008d</Data> <Data>2</Data> <Data>NVIDIA GeForce GTX 1660 SUPER</Data> </EventData> </Event>
It could be the video card driver, disconnect pc from net > uninstall the video card driver > run DDU in safe mode > restart > install same or previous "preferably previous" driver version > restart. See if it does it again. If it does the issue lies elsewhere, possibility of the power supply starting to go bad at this age exists.
There's no airflow going trough the front. Its like case is all sealed to not get airflow. Looks like PSU is shoved somewhere in backside against wall and is surrounded by wires.
Have you checked the temps? Freeman is right as there is no airflow and that alone can cause the sudden stops and fans going max Maybe its the chipset or even ram overheating
I have a PC from a friend here which had the same issues. Today a new Nvidia Driver 552.22 just came out and it looked that is it fixed. I ran Prime 95 (Small FFT) together with Furmark and with 552.12 it crashed within 5 Minutes , now it runs nearly 30 Minutes and did not crash again. But before you install the new drivers use DDU and uninstall everything before. EDIT: CPU Intel 12900k, with Inno3D RTX 4070 (non TI/Super) Max Temp 69.6°C / HotSpot 88.3°C
@MK77P Is the PCI-E cable clipped in or is there a slight gap? I had the same thing happen with an RTX 2070 Super only to find out that the fan shroud was blocking the 6+2 PCI-E cable from being clipped into place. Using a native 8-pin PCI-E cable resolved the issue.
The PCI-E cable is seated well but it might actually be related to a cable, the GPU HDMI cable, because I touched it (from the back of the case where it's plugged to the GPU) while the PC was on and the exact same thing happened but I'm not sure if the first time this happened as shown in the recorded video is actually the HDMI cable because when that happened I didn't touch anything nor did anything move but touching the HDMI cable did do the same exact thing.
@MK77P Your video is so funny. Interesting outage anyway. A new bios battery wont hurt. Put on in, they don't last forever. btw it is considered better practise to use the display port with an appropriate cable..
I've heard bad or cheap HDMI cables can have some pins shorted that shouldn't be actually, not a bad idea to try with a better quality cable first. The crashes point to dwm too which would fit. Quick search of the exception code came up with 2 topics from answers.microsoft that match yours exactly dwm.exe and dwmcore.dll crash while gaming on win 10 - Microsoft Community dwm.exe crash and causes black screen while gaming/intensive sessions - Microsoft Community
My monitor only has a HDMI and VGA ports and the GPU has 3x DisplayPorts and one HDMI. So what would be best? DisplayPort to HDMI? or DisplayPort to VGA?
@MK77P Uh hu, When the time comes for you to treat your self to a new monitor. Make sure it comes with a display port. Most will be display port 1.4 but we are at 2.0 now. 2.0 is no big deal yet as even NVidia struggle to fit a display port 2.0 to their GFX cards.
Got a new cable (DisplayPort - HDMI) a week ago and today the same issue happened twice, the first time happened without even touching the PC, just had it on with an open browser and the second time while playing a game. Guess we can rule out this being a HDMI cable issue.