Question PC crashing ntoskrnl.exe

Feb 14, 2023
7
0
10
Hello!

I have been getting some weird pc crashes! The screen goes black with like weird contrast of whatever i was playing at the time for like 10 seconds and then the pc restarts. I have only noticed this crash happen while streaming with OBS or having OBS open at all. I know that doesnt mean it could happen without it being open, only that it hasnt yet. Minidump and pc specs below!

this is copied from bluescreenviewer

020123-6515-01.dmp 2/1/2023 9:38:26 PM IRQL_NOT_LESS_OR_EQUAL 0x0000000a ffffffffffffffd0 0000000000000002 0000000000000001 fffff805088d14d6 ntoskrnl.exe ntoskrnl.exe+428f20 x64 ntoskrnl.exe+428f20 C:\Windows\Minidump\020123-6515-01.dmp 16 15 22621 3,478,324 2/1/2023 9:39:15 PM



minidump file - https://www.mediafire.com/file/sivfciu6szgbd9w/021323-6765-01.dmp/file

PC specs
9QyacGc.png


the psu provided by ibuypower did pop in decemeber and i have replaced it with a corsair CX-M Series CX750M psu.
i also have a samsung 860 evo 1 TB
 

c1c1op

Prominent
Feb 7, 2023
29
3
535
An ntoskrnl.exe error can occur for a variety of reasons:

1. Incorrect overclocking and undervolting, which led to overheating.
2. Physical deletion of the file (in general, this is quite difficult to do, but it is possible if you use software that affects system elements).
3. File damage/replacement by a virus.
4. Damage to registry entries.
5. The presence of problematic or old drivers.
6. Internal system failure.
7. Failure of the hard drive.
8. OS has not been updated to the latest version.
9. Damage or malfunction of the RAM.
 
Feb 14, 2023
7
0
10
An ntoskrnl.exe error can occur for a variety of reasons:

1. Incorrect overclocking and undervolting, which led to overheating.
2. Physical deletion of the file (in general, this is quite difficult to do, but it is possible if you use software that affects system elements).
3. File damage/replacement by a virus.
4. Damage to registry entries.
5. The presence of problematic or old drivers.
6. Internal system failure.
7. Failure of the hard drive.
8. OS has not been updated to the latest version.
9. Damage or malfunction of the RAM.
yea for sure! im hoping someone can look at the minidump and help me narrow that list down!
 
Feb 14, 2023
7
0
10
I would put the blame on that PSU. Not a high quality unit, and the wattage is a bit low, for a 3080.
are you talking about the corsair psu? ive seen where it says 750 is the suggested wattage for the 3080, but like you said have also seen where some people have problems with the 750, just sucks because i bought the corsair one to replace the one that popped in december. hoping someone can read the dmp file and try to narrow it a little more
 

logainofhades

Titan
Moderator
The CX750m is not a high quality unit either. RM and RMx are the better units, and even then, 750w is a bit low, for a 3080. RTX 3000 cards have big transient power spikes, that can spike the wattage further than the over current protection can handle, on a low quality unit.
 
Feb 14, 2023
7
0
10
The CX750m is not a high quality unit either. RM and RMx are the better units, and even then, 750w is a bit low, for a 3080. RTX 3000 cards have big transient power spikes, that can spike the wattage further than the over current protection can handle, on a low quality unit.
damn man, someone on reddit checked out the dmp file and said i should run the tests in this article https://www.tomshardware.com/how-to...ddress for which it lacks valid access rights

im hoping someone else can find and post what problem shows up in the minidump so i can cross check it with the article. I followed the advice and
i ran SFC scannow and got some files couldnt be repaired. checked the cbs log for it and found this

Hashes for file member [l:8]'img0.jpg' do not match.
Expected: {l:32 ml:33 b:a37491a5e479e191cfe547b484426037455ce8aacff7ab15f91925330c24864f}.
Actual: {l:32 b:821e370679f3d1129c433d01517566d8f443057f36999f65128b48f43f86f161}.
2023-02-19 13:57:01, Info CSI 000001c4 [SR] Cannot repair member file [l:8]'img0.jpg' of Microsoft-Windows-Shell-Wallpaper-Windows, version 10.0.22621.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2023-02-19 13:57:01, Info CSI 000001c5 Hashes for file member [l:8]'img0.jpg' do not match.
Expected: {l:32 ml:33 b:a37491a5e479e191cfe547b484426037455ce8aacff7ab15f91925330c24864f}.
Actual: {l:32 b:821e370679f3d1129c433d01517566d8f443057f36999f65128b48f43f86f161}.
2023-02-19 13:57:01, Info CSI 000001c6 [SR] Cannot repair member file [l:8]'img0.jpg' of Microsoft-Windows-Shell-Wallpaper-Windows, version 10.0.22621.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2023-02-19 13:57:01, Info CSI 000001c7 [SR] This component was referenced by [l:120]'Microsoft-Windows-Shell-Wallpaper-Common-Package~31bf3856ad364e35~amd64~~10.0.22621.900.bbfda86ee1af8cfeb4dd44713d59ea24'
2023-02-19 13:57:01, Info CSI 000001c8 Hashes for file member [l:8]'img0.jpg' do not match.
Expected: {l:32 ml:33 b:a37491a5e479e191cfe547b484426037455ce8aacff7ab15f91925330c24864f}.
Actual: {l:32 b:821e370679f3d1129c433d01517566d8f443057f36999f65128b48f43f86f161}.
2023-02-19 13:57:01, Info CSI 000001c9 [SR] Could not reproject corrupted file \??\C:\Windows\Web\Wallpaper\Windows\\img0.jpg; source file in store is also corrupted


i deleted the file and reran SFC scannow and got 'files were repaired' and i was like nice! then i reran it one more time and got the same error in the CBS log 🥲😂

but if no one can find anything else, or deleting that file didnt do anything, i guess i will go higher with the psu and get the model you recommend. how high of a wattage should i go?
 

logainofhades

Titan
Moderator
Your windows install may be corrupted by this point. A fresh install, of Windows, is probably going to be necessary assuming your ssd isn't faulty. You can use crystaldiskinfo to determine drive health.

Even some high dollar Seasonics have had issues with RTX 3000's spikes. I wouldn't get anything less than a corsair RMx, or Evga G6 850w.
 
Feb 14, 2023
7
0
10
Your windows install may be corrupted by this point. A fresh install, of Windows, is probably going to be necessary assuming your ssd isn't faulty. You can use crystaldiskinfo to determine drive health.

Even some high dollar Seasonics have had issues with RTX 3000's spikes. I wouldn't get anything less than a corsair RMx, or Evga G6 850w.
greaaaat lol, well i'll run the crystaldiskinfo and see what it says and if the problem persists, i'll follow the trail of replacing psu, and then reinstalling windows 🫠
 
Feb 14, 2023
7
0
10
Your windows install may be corrupted by this point. A fresh install, of Windows, is probably going to be necessary assuming your ssd isn't faulty. You can use crystaldiskinfo to determine drive health.

Even some high dollar Seasonics have had issues with RTX 3000's spikes. I wouldn't get anything less than a corsair RMx, or Evga G6 850w.
i ran samsung magician and everything seems fine with the evo! crystaldiskinfo doesnt show anything wrong with the WD nvme