What does this BSOD indicate about the kernel mode trap?
What does this BSOD indicate about the kernel mode trap?
short summary
recent update on Windows without Steam, Battlenet, Brave has caused problems for a while. I reached out to Microsoft but no one responded; a specialist was available but didn’t get through. I’ve tried many fixes but need some good advice.
latest minidump: minidump-.zip
issues appear when launching Fortnite, possibly due to Easy Anti-Cheat. Other games with EAC seem unaffected.
help is really needed!
reviewing the bugcheck results shows the system was operational for about 1.33 seconds before encountering a double fault on a CPU core. The timing is crucial. If you believe the system ran longer—such as during gameplay and the screen went blank—it indicates a different issue than simply a failed boot. I’ll investigate whether there’s a clear reason behind the bugcheck. It should take around a minute.
notes:
usbfilter.sys Thu Nov 26 17:26:01 2015
unexpected old driver.
unable to read machine information or CPU details from the dump. This might suggest the BIOS is outdated (or the dump occurred too early).
generally, I look for these signs in this scenario:
if the system timer has been running for more than 5 minutes, it could indicate overheating—like a blocked vent on a laptop or a faulty CPU fan.
however, your system was up for just 1.3 seconds. This might point to an incorrect voltage being supplied to the CPU. You would normally boot into BIOS to check if it can display your voltages and compare them to standard values (3.3v, 5v, 12v).
if you suspect the system was active longer—such as while playing a game—it’s common for the GPU to draw excessive power through the PCI/exp slot, activating motherboard protection circuits that reset the CPU. The power supply is meant to prevent the CPU from restarting until power returns to normal after the reset, but sometimes it sends a false signal, causing the CPU to restart without proper voltage and then trigger a bugcheck due to an undervoltage error.
in short: let your PC cool down before checking if it boots. Were you using the computer when it failed?
your system appeared clean except for the old USBFILTER driver.
a BIOS update could resolve the issue where machine information couldn’t be read.
I'll need to verify my voltages, but I'm expecting the PC to start up properly even in cold conditions—last time it was around 15°C. I think I started the game right after a restart since it was a fresh install, just to confirm everything is functioning correctly. I can play other games without any issues and they don't crash. My BIOS is up to date, and my temperatures are normal, usually between 50-70 depending on the game or CPU load.
My power supply is a Seasonic VERTEX PX-1000 ATX3.0 1000W 80 Plus Platinum Modular Power Supply, so I wouldn't expect anything too much. If not, it's not overkill at all.
verify the links from the power source to the GPU. confirm they are fully attached. if the GPU overheats or runs at an overclocked state, it may draw excessive power from the PCI/e bus, activating the motherboard safeguards. for a factory-optimized GPU, consider lowering its speed and compare with previous issues. with a solid motherboard and PSU, excessive power through the PCI/e bus usually results in a blank black display. increased power consumption is also seen with higher resolution monitors or faster refresh rates.
it seems your psu has a 600w gpu power connector. i believe the updated connectors are rated at 675 watts to avoid damage to the connector, especially for 4090 cards. the psu spec says it can supply up to 996 watts on 12v. i recommend checking the 600 watt cable for any issues or poor connection. 12v hpwr and 12v-2x6 can handle 675 watts.
when you install a new hardware, attempt to remove it and retry, additionally check the event viewer.
event viewer
File System Filter 'EasyAntiCheat_EOSSys' (Version 6.1, 2025-01-20T14:17:57.000000000Z) lacks support for bypass IO.
Supported features: 0x4.
It sends that 9 times.
The prior system shutdown at 21:24:23 on 26/01/2025 was unexpected.
Dump file creation failed because of an error during dump creation. BugCheckProgress was: 0x00080A25.
The system restarted without a clean shutdown. This issue might stem from the system failing to respond, crashing, or losing power suddenly.
Audit events were dropped by the transport. 0
The driver Driver\WUDFRd failed to load.
Device: HID\VID_041E&PID_3287&MI_00&Col03\a&2aaec0de&0&0002
Status: 0xC0000365
12v-2x6
I might be mistaken, but I think I already have one installed.
Looking online doesn’t help much—I can’t find anything in the UK.
Unless it’s something like this: https://www.amazon.co.uk/Corsair-Premium...22?sr=8-22
The socket looks okay though!
the driver that did not load was a touch screen driver. the reason for failure was
17: kd> !error 0xC0000365
error code: (NTSTATUS) 0xc0000365 (3221226341) - the driver could not be loaded due to initialization issues. this might indicate a problem with your touch screen. avoid removing touch screen drivers through the device manager. i have observed systems where this happened and had to return them to the OEM for repair.
note: in another database, the vendor id appeared as
Creative Technology, Ltd
but the device id was missing. so i am uncertain about the exact device involved.
the bugcheck entry is fine. it is typical if the system failed to shut down completely. it simply instructs the system to perform additional tests on your file system during the next startup.
ok for the socket as long as it isn’t melted or a pin has been pushed out of the plastic.