You're experiencing BSODs on your Asus PC without any diagnostic logs being generated.
You're experiencing BSODs on your Asus PC without any diagnostic logs being generated.
Hello. My computer experienced another BSOD, and here is the link:
https://www.dropbox.com/scl/fi/h6s4...ey...ftqkr3yyhr&st=gfsh7hjg&dl=0
I appreciate your help with this.
That's interesting because in your System log, which runs from Dec 2023 to today, there isn't a single BSOD recorded, neither are there any dump files. I can see a lot of system restarts in your System log that are not BSOD related and that suggests a hardware cause. RAM is always the first point of call with hardware related failures, and in your Application log there are large numbers of application error messages with memory related exceptions - this is also a big pointer towards bad RAM. Here's an example...
Code:
Log Name: Application
Source: Application Error
Date: 06/03/2024 20:47:47
Event ID: 1000
Task Category: Application Crashing Events
Level: Error
Keywords:
User: S-1-5-21-656615451-3364641526-1564194660-1001
Computer: Liam
Description:
Faulting application name: Explorer.EXE, version: 10.0.22621.3155, time stamp: 0x3fb2d7a4
Faulting module name: Taskbar.dll, version: 10.0.22621.3155, time stamp: 0xc16a5390
Exception code: 0xc0000005
Fault offset: 0x0000000000164abb
Faulting process ID: 0x0x1334
Faulting application start time: 0x0x1DA6D293E2D0A98
Faulting application path: C:\Windows\Explorer.EXE
Faulting module path: C:\Windows\System32\Taskbar.dll
Report ID: 6a90e5bd-f235-41fb-b4de-471ab6e3440a
Faulting package full name:
Faulting package-relative application ID:
The 0xC0000005 exception code is an invalid memory access and whilst that can be caused by many things bad RAM is certainly one.
Did you ever test your RAM with Memtest86 as I suggested in
post #2
? If not then please do that now.
In addition to this (and possibly related) your System log shows a huge number of errors for nvlddmkm.sys, the Nvidia graphics driver....
Code:
Log Name: System
Source: nvlddmkm
Date: 22/06/2024 02:57:53
Event ID: 153
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: Liam
Description:
The description for Event ID 153 from source nvlddmkm cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
\Device\00000095
Reset TDR occurred on GPUID:100
The message resource is present but the message was not found in the message table
The TDR reset referenced there relates to the Windows Timeout Detection and Recovery feature, this resets the graphics driver and card if a graphics hang occurs. This error (and the huge number of similar errors) is telling you that a graphics hang happened and was recovered by TDR. That will cause a crash to desktop for the app that was using the graphics card at the time. It is entirely possible that the graphics hang was caused by bad RAM.
You need to properly test your RAM with Memtest86 as advised before moving on to other potential causes.
I observed that prior to my computer executing this task, the Service Host: AVCTP Service reaches 100% CPU before the BSOD UNEXPECTED_STORE_EXCEPTION appears. I might need to run Memtest86 if my machine keeps doing this. I could possibly have to stay up all night to resolve it.
The AVCTP Service operates as a Bluetooth service, managing the Audio/Visual Control Transport Protocol that oversees commands for audio-visual devices linked through Bluetooth. When no audio-visual devices are connected via Bluetooth, you may safely turn off this service using services.msc.