fresh crash tonight and I can't figure out the issue

egp320i

Diamond Member
Gold Supporting Member
Joined
Dec 26, 2024
Messages
1,830
Reaction score
1,782
Points
1,893
Location
USA
010425-40328-01.dmp 1/4/2025 9:09:06 PM KMODE_EXCEPTION_NOT_HANDLED 0x0000001e ffffffff`c0000005 fffff801`3c02e334 00000000`00000001 ffff9c0c`ed5ad020 ntoskrnl.exe ntoskrnl.exe+3fe8f0 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 10.0.19041.5247 (WinBuild.160101.0800) x64 ntoskrnl.exe+3fe8f0 C:\Windows\Minidump\010425-40328-01.dmp 8 15 19041 2,778,508 1/4/2025 9:19:29 PM

few weeks ago I upgraded my memory to 16GB, passed all memory tests
bios upgraded to the last, all drivers updated to the latest

this is a driver or memory issue thus I am baffled
 
Maybe that box you scrambled together is nothing but crap.
 
my box was custom built by me and I picked only the best so nope, no issues for many years, rock solid
 
yeah OK, just been building computers for friends, family and others for 25 years but per you I know nothing

if you are some expert why don't you offer some insight instead of being a dick with zero info?
 
Sounds to me of a bad update which is not uncommon with Windows.

If you haven't already done so:
See if Fast Startup is turned on in settings, if it is turn it off.
Run Windows Memory Diagnostics.
Run System File Checker.
If all else fails do a Roll Back. If the problem still persists then it could be a hardware driver conflict.
 
I would turn updates off.
Also, often the latest BIOSes n stuff aren't the best thing.
Offhand, I say it's an errata or CPU power supply problem.
 
last bios was years ago, the only MS update of late was just .net framework but that was 12/26
 
010425-40328-01.dmp 1/4/2025 9:09:06 PM KMODE_EXCEPTION_NOT_HANDLED 0x0000001e ffffffff`c0000005 fffff801`3c02e334 00000000`00000001 ffff9c0c`ed5ad020 ntoskrnl.exe ntoskrnl.exe+3fe8f0 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 10.0.19041.5247 (WinBuild.160101.0800) x64 ntoskrnl.exe+3fe8f0 C:\Windows\Minidump\010425-40328-01.dmp 8 15 19041 2,778,508 1/4/2025 9:19:29 PM

few weeks ago I upgraded my memory to 16GB, passed all memory tests
bios upgraded to the last, all drivers updated to the latest

this is a driver or memory issue thus I am baffled
If you can... Download a program called driver easy and let it update all your drives...
 
010425-40328-01.dmp 1/4/2025 9:09:06 PM KMODE_EXCEPTION_NOT_HANDLED 0x0000001e ffffffff`c0000005 fffff801`3c02e334 00000000`00000001 ffff9c0c`ed5ad020 ntoskrnl.exe ntoskrnl.exe+3fe8f0 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 10.0.19041.5247 (WinBuild.160101.0800) x64 ntoskrnl.exe+3fe8f0 C:\Windows\Minidump\010425-40328-01.dmp 8 15 19041 2,778,508 1/4/2025 9:19:29 PM

few weeks ago I upgraded my memory to 16GB, passed all memory tests
bios upgraded to the last, all drivers updated to the latest

this is a driver or memory issue thus I am baffled
Bad RAM stick? Memtest.
 
Bad RAM stick? Memtest.
brand new 2x8 RAM, memtest 86+ pass, windows memtest pass also
Highly binned muskin redline using only top micron chips, this is not some cheap chinese memory
I always build the best
 
brand new 2x8 RAM, memtest 86+ pass, windows memtest pass also
Highly binned muskin redline using only top micron chips, this is not some cheap chinese memory
I always build the best
Try running a heavy Cinebench on it. That should expose any weaknesses quickly.
Memtest 86..what is this..XP?
 
010425-40328-01.dmp 1/4/2025 9:09:06 PM KMODE_EXCEPTION_NOT_HANDLED 0x0000001e ffffffff`c0000005 fffff801`3c02e334 00000000`00000001 ffff9c0c`ed5ad020 ntoskrnl.exe ntoskrnl.exe+3fe8f0 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 10.0.19041.5247 (WinBuild.160101.0800) x64 ntoskrnl.exe+3fe8f0 C:\Windows\Minidump\010425-40328-01.dmp 8 15 19041 2,778,508 1/4/2025 9:19:29 PM

few weeks ago I upgraded my memory to 16GB, passed all memory tests
bios upgraded to the last, all drivers updated to the latest

this is a driver or memory issue thus I am baffled
I gather you've had multiple crashes? Is each one different, is the error report (like shown above) always the same or different?

Be careful with memory, unless you do a truly exhaustive test you can easily miss certain kinds of faults.

The message indicates that an unexpected exception arose within code that was running in kernel mode, if no mention is made of a driver then I would suspect memory.

I have a box here with 128GB and from time to time it will crash and I suspect memory, but I was unable to the memory stick based memory checker to run at boot time, so I've noy bothered to really pursue, it crashes usually every few weeks and I can live with it.

You'll see the dump file: 010425-40328-01.dmp

That can be debugged with the windows kernel debugger, sometimes that can let you gather more detailed info about the crash.

I have an earlier machine I built that had 64GB and that had occasional random crashes (in the video driver), I found a single stick was to blame so removed it and just continued, it had 48GB at that point but I wasn't too concerned.

The crash was always in the video driver not because of a driver bug but because drivers are loaded very early during the boot and often get placed at the same physical address every boot, that driver somehow got impacted by the memory issue.

 
Last edited:
I use blue screen viewer, the craches are alway kmode and I would get one every other day, bought new high end memory, ran many passes and no errors
about 30 days went by and then a fresh kmode which baffled me as I figured the problem was solved
no crash in 10 though and there was another windows .net update so maybe that was the issue
so far so good, all drivers are the latest so it should be that issue
 
010425-40328-01.dmp 1/4/2025 9:09:06 PM KMODE_EXCEPTION_NOT_HANDLED 0x0000001e ffffffff`c0000005 fffff801`3c02e334 00000000`00000001 ffff9c0c`ed5ad020 ntoskrnl.exe ntoskrnl.exe+3fe8f0 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 10.0.19041.5247 (WinBuild.160101.0800) x64 ntoskrnl.exe+3fe8f0 C:\Windows\Minidump\010425-40328-01.dmp 8 15 19041 2,778,508 1/4/2025 9:19:29 PM

few weeks ago I upgraded my memory to 16GB, passed all memory tests
bios upgraded to the last, all drivers updated to the latest

this is a driver or memory issue thus I am baffled
These are baffling. I have PC I built in 2022 and after like six months I began to experience crashes of the OS (Windows 11). These have been random, sometimes I'd see two in a day and others I'd see one every two weeks. The failure message varies too and even sometime it blames CPU temperature getting to high.

Like you I've been building PC for many years, I recall building my first 16MB machine in 1991 and installing the first version of Windows NT 3.1 back then.

I recently installed newer ASUS chipset drivers hoping that might be it, but nope.

I recently tested all 128GB of RAM and that took over 18 hours and passed without issues.

All of the installed device drivers are signed drivers too.

When I do teak something I can never tell if the next crash is somehow connected to the change or just as random as it was before I made the change.

I've debugged a couple of dump files but really don't see much, I know quite a lot about the OS internals but frankly I don't have enough expertise to really analyze this sensibly now.

The MOBO is an Asus Prime X570-P and the CPU is a Ryzen 5950X.

I'm now starting to wonder if it might be a component insertion fault, the CPU or perhaps a memory module not seated correctly...
 
1) check your memory cards recommended speed and compare it to your bias registered speed-did you forget to change the bios for your new specs? Are you over clocking? Did you reinsert your card like SH suggested might be the issue (partially inserted not locked all the way but thought it was?
2)use a ram cleaner, maybe the newer programs and files being larger are making your anount of ram still not enough. AI, VR, gaming, movie and music editors all use all your ram.
3)might be your board is starting to go
4) use cc cleaner see if it's a residual file that caused it
5) use iobit or your system to check for errors and clean and defrag your registry.
 
Back
Top Bottom