Question "Unexpected_Kernel_Mode_Trap" BSOD ?

[Altom_]

long story short
fresh install of Windows other than downloading steam, battlenet,brave I've been getting this issue for a while. I tried contacting Microsoft and I had a specialist that was going to "help" but 2 weeks or so later and he's radio silent I have tried all sorts of things but if I can get some suggestions that be fantastic

Latest minidump:
minidump-.zip

This is all while trying to launch Fortnite and its only Fortnite that has the issue and its most likely because of the Easy Anti-Cheat. However, other games work ok that also have EAC so i don't know.
help would be greatly appreciated!

PC Specs
Mobo: Gigabyte X870 AORUS ELITE WiFi7 ICE
CPU: Ryzen 9 7950X3D
GPU: RTX 4080 Super
RAM: Corsair 64GB DDR5
SSD_01: WD SN850
SSD_02: Samsung 990 Pro
OS: Windows 11

 

[johnbl]

looking at the bugcheck.
system was up 1.33 seconds then got a double fault on a cpu core.
the time is important. If you think the system was up longer. For example you were playing a game and the screen went blank it means something different than you just tried to boot up and got the bugcheck. I will see if there is a clear cause of the bugcheck. will take a minute

notes:
usbfilter.sys Thu Nov 26 17:26:01 2015
unexpected old driver.
unable to read machine info or cpu info from dump. this can mean the bios is out of date. (or the dump happened too early)

basically, a double fault happens when the system detects something is wrong (a fault) then goes to a error handler to recover but the error handler also generates a fault. in this case the bugcheck just shuts down the system.

Here is what I generally look for in this case:
if the system timer is up for like over 5 minutes it tends to be over heating like a blocked vent on a laptop or a broken cpu fan.
but your system was up for 1.3 seconds. This can mean a bad voltage to the cpu. you would boot into bios and see if it can display your voltages and see how close they are to the standard voltages 3.3v 5 v and 12v

if you think that the system was up longer, IE you were playing a game or something, it is common for a GPU to pull to much power from the pci/e slot and trigger the motherboard protection circuits that reset the CPU. The power supply is suppose to prevent the cpu from restarting until the power is back to normal after the reset but often the power supply fakes the signal and the cpu restart without havng the power correct and then the cpu calls a bugcheck because of a error caused by the power being undervoltage for a second.
so it boils down to this: if you let your PC get cool, will it boot up? Were you using the PC when it failed?

your system looked pretty clean except for the old usbfilter driver.
bios update might fix the fact that the machine info could not be read.

 

[Altom_]

looking at the bugcheck.
system was up 1.33 seconds then got a double fault on a cpu core.
the time is important. If you think the system was up longer. For example you were playing a game and the screen went blank it means something different than you just tried to boot up and got the bugcheck. I will see if there is a clear cause of the bugcheck. will take a minute

notes:
usbfilter.sys Thu Nov 26 17:26:01 2015
unexpected old driver.
unable to read machine info or cpu info from dump. this can mean the bios is out of date. (or the dump happened too early)

basically, a double fault happens when the system detects something is wrong (a fault) then goes to a error handler to recover but the error handler also generates a fault. in this case the bugcheck just shuts down the system.

Here is what I generally look for in this case:
if the system timer is up for like over 5 minutes it tends to be over heating like a blocked vent on a laptop or a broken cpu fan.
but your system was up for 1.3 seconds. This can mean a bad voltage to the cpu. you would boot into bios and see if it can display your voltages and see how close they are to the standard voltages 3.3v 5 v and 12v

if you think that the system was up longer, IE you were playing a game or something, it is common for a GPU to pull to much power from the pci/e slot and trigger the motherboard protection circuits that reset the CPU. The power supply is suppose to prevent the cpu from restarting until the power is back to normal after the reset but often the power supply fakes the signal and the cpu restart without havng the power correct and then the cpu calls a bugcheck because of a error caused by the power being undervoltage for a second.
so it boils down to this: if you let your PC get cool, will it boot up? Were you using the PC when it failed?

your system looked pretty clean except for the old usbfilter driver.
bios update might fix the fact that the machine info could not be read.

Hmmm ok I'll have to check my voltages but my pc will boot up at cold temps well as cold was 15c I think I launched the game straight after a restart as it was a fresh install and wanted to make sure everything was working ok i can play other games perfectly fine and it wont crash or anything. my Bios is currently at the latest version available my temps don't seem to be an issue at all usually 50-70 depending on what game / work load for CPU
my power supply is a Seasonic VERTEX PX-1000 ATX3.0 1000W 80 Plus Platinum Modular Power Supply so i would of thought it be good enough? if not overkill to be honest

 

[johnbl]

check the connections from the power supply to the GPU. make sure they are connected fully. if the GPU over heats or is overclocked it can pull too much power from the PCI/e bus and trigger the motherboard protection circuits. for GPU that is factory overclocked you might underclock the GPU and see if you have the same problem as before. With a good motherboard and PSU if too much power goes thru the PCI/e bus then you will just get a blank black screen. More power is used by higher resolution monitors. (or higher refresh rates)

for the gpu supplemental power connector, inspect it, sometimes a pin gets pushed out to the plastic holder. make sure the connector did not melt or has a bad connection. If it has a bad connection then the card will try to take power from the card bus and the motherboard protection circuit will reset your CPU

 

[johnbl]

check the connections from the power supply to the GPU. make sure they are connected fully. if the GPU over heats or is overclocked it can pull too much power from the PCI/e bus and trigger the motherboard protection circuits. for GPU that is factory overclocked you might underclock the GPU and see if you have the same problem as before. With a good motherboard and PSU if too much power goes thru the PCI/e bus then you will just get a blank black screen. More power is used by higher resolution monitors. (or higher refresh rates)

for the gpu supplemental power connector, inspect it, sometimes a pin gets pushed out to the plastic holder. make sure the connector did not melt or has a bad connection. If it has a bad connection then the card will try to take power from the card bus and the motherboard protection circuit will reset your CPU

looks like your psu has rated 600w gpu power connector.
I think the new connectors are rated at 675 watts to prevent melt down of the connector. (for the 4090 cards)
psu spec indicates the PSU can provide up to 996 watts on the 12v. I would check the 600 watt cable for damage/poor connection.
12VHPWR and 12V-2x6 the 12v 2 X6 can handle 675 watts

 

[mikemid]

if you put a new hardware, try to remove it then try again, also see event viewer

 

[Altom_]

if you put a new hardware, try to remove it then try again, also see event viewer

looks like your psu has rated 600w gpu power connector.
I think the new connectors are rated at 675 watts to prevent melt down of the connector. (for the 4090 cards)
psu spec indicates the PSU can provide up to 996 watts on the 12v. I would check the 600 watt cable for damage/poor connection.
12VHPWR and 12V-2x6 the 12v 2 X6 can handle 675 watts

event viewer
File System Filter 'EasyAntiCheat_EOSSys' (Version 6.1, ‎2025‎-‎01‎-‎20T14:17:57.000000000Z) does not support bypass IO.
Supported features: 0x4.

sends that 9 times

The previous system shutdown at 21:24:23 on ‎26/‎01/‎2025 was unexpected.
Dump file creation failed due to error during dump creation. BugCheckProgress was: 0x00080A25

The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Audit events have been 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 could be wrong but i believe i have already got one installed
but also looking online i cant seem to find any in the UK
unless im looking at something like this

https://www.amazon.co.uk/Corsair-Premium-600W-12VHPWR-Cable/dp/B0BLXWHW2N/ref=sr_1_22?sr=8-22

socket seems good though!

 

[johnbl]

the driver that failed to load was a touch screen driver. the failure reason was
17: kd> !error 0xC0000365
Error code: (NTSTATUS) 0xc0000365 (3221226341) - The driver was not loaded because it failed its initialization call. might mean that your touch screen is not working. (do not remove touch screen drivers using device manager. I have seen systems that have done this and had to be sent back to the OEM to have it fixed)
note: in another database the vendor id came up as

Creative Technology, Ltd​

but the device id was not listed. (so I am not sure as to the failed device )

the entry for the bugcheck is ok. it is expected if the system failed to complete shutdown. It just tells the system to run extra tests on your file system on the next bootup.

ok for the socket as long as it does not look melted or some pin pushed out of the plastic.

 

[Altom_]

the driver that failed to load was a touch screen driver. the failure reason was
17: kd> !error 0xC0000365
Error code: (NTSTATUS) 0xc0000365 (3221226341) - The driver was not loaded because it failed its initialization call. might mean that your touch screen is not working. (do not remove touch screen drivers using device manager. I have seen systems that have done this and had to be sent back to the OEM to have it fixed)

the entry for the bugcheck is ok. it is expected if the system failed to complete shutdown. It just tells the system to run extra tests on your file system on the next bootup.

ok for the socket as long as it does not look melted or some pin pushed out of the plastic.

I don't have a touchscreen...

 

[johnbl]

I don't have a touchscreen...

do you have a creative technology device?

 

[Altom_]

the driver that failed to load was a touch screen driver. the failure reason was
17: kd> !error 0xC0000365
Error code: (NTSTATUS) 0xc0000365 (3221226341) - The driver was not loaded because it failed its initialization call. might mean that your touch screen is not working. (do not remove touch screen drivers using device manager. I have seen systems that have done this and had to be sent back to the OEM to have it fixed)
note: in another database the vendor id came up as

Creative Technology, Ltd​

but the device id was not listed. (so I am not sure as to the failed device )

the entry for the bugcheck is ok. it is expected if the system failed to complete shutdown. It just tells the system to run extra tests on your file system on the next bootup.

ok for the socket as long as it does not look melted or some pin pushed out of the plastic.

Ooo I just had a thought actually I was able to attach windows to my Microsoft account this was a while back so maybe windows 8.1 I think or maybe 10 I can't remember off the top of my head but I believe it was an OEM windows and I've just been using it ever since so maybe I need a new windows? I have no idea creative technology maybe my speakers? They're called creative pebbles

Edit: just unplugged speakers still no change didn't remove drivers or anything I just unplugged from the pc

 

[johnbl]

Ooo I just had a thought actually I was able to attach windows to my Microsoft account this was a while back so maybe windows 8.1 I think or maybe 10 I can't remember off the top of my head but I believe it was an OEM windows and I've just been using it ever since so maybe I need a new windows? I have no idea creative technology maybe my speakers? They're called creative pebbles

Edit: just unplugged speakers still no change didn't remove drivers or anything I just unplugged from the pc

if it is the creative pebble, it is a usb 2 device. you could unplug it, then go into control panel, device manager, find the menu option to show hidden devices and enable it. if it shows a greyed out entry you can delete it. windows leaves the driver installed for usb devices that are removed. it just hides the device but the driver still loads and in some cases can cause problems.

 

[Altom_]

if it is the creative pebble, it is a usb 2 device. you could unplug it, then go into control panel, device manager, find the menu option to show hidden devices and enable it. if it shows a greyed out entry you can delete it. windows leaves the driver installed for usb devices that are removed. it just hides the device but the driver still loads and in some cases can cause problems.

yea I'm still having the issue unfortunately i can play for hours on other games perfectly fine and yet i cant even boot a Fortnite so i think its something to do with them and not me at this point however been talking to them for dayss its 1 email a day thing and its not going anywhere

 

[Altom_]

if it is the creative pebble, it is a usb 2 device. you could unplug it, then go into control panel, device manager, find the menu option to show hidden devices and enable it. if it shows a greyed out entry you can delete it. windows leaves the driver installed for usb devices that are removed. it just hides the device but the driver still loads and in some cases can cause problems.

Epic games response:

"however, this seems to be a direct issue with your operating system, so at this point, the Epic Games team is not able to assist you with this"

Is there a way to revert back to windows 10? Or maybe I could try upgrading to windows 11 pro or is there away to fix a corrupted windows? I mean all the SFC scan and dism seem all ok so I'm not sure?

 

[Altom_]

Solved it! turns out switching the ram around fixed it so I was using all four and it's dual channel so I switched the ram around into different channels and it's working now as to why it worked I'm not sure as I did resit the ram before hand and didn't do anything and swapping it around does sooo I guess sometimes the most complicated faults are the simplest to fix