Question Constant blue screens and hard crashes ?

Toggle sidebar Toggle sidebar
A

AlmightyKing

May 10, 2024
31
0
30
Hello
Im computer constantly freezes or locks up and immediately shuts off.
No overclocking, no undervolting.

I tried everything, here's a list so far.

  • resetting the entire PC through recovery T
  • throwing a couple of extra fans inside the computer
  • Memory test both sticks of RAM with Memtest86
  • command prompt (sfc scannow, checkdsk, etc)
  • Reseat the GPU
  • Reseat the CPU
  • Reset the RAM
  • Update Bios
  • Remove GPU drivers with DDU and reinstall

This is getting extremely frustrating, Im about sell the whole computer and find something else to do.

Here are the details from the Event Viewer and the Reliability History viewer:
Problem signature
Problem Event Name: BlueScreen
Code: 1e
Parameter 1: ffffffffc0000005
Parameter 2: fffff806d1896735
Parameter 3: 0
Parameter 4: ffffffffffffffff
OS version: 10_0_26100
Service Pack: 0_0
Product: 256_1
OS Version: 10.0.26100.2.0.0.256.48
Locale ID: 1033
Extra information about the problem
Bucket ID: IP_MISALIGNED_GenuineIntel.sys

I've also been getting these code as well from previous blue screens
blue screeen code 7e 0x0000007e blue screen code 133 Blue Screen;
BCCode:50

Source
Windows
Summary
Shut down unexpectedly
Date
‎4/‎15/‎2025 11:12 PM
Status
Report sent
Problem signature
Problem Event Name: BlueScreen
Code: 133
Parameter 1: 1
Parameter 2: 1e00
Parameter 3: fffff80394fc33b0
Parameter 4: 0
OS version: 10_0_26100
Service Pack: 0_0
Product: 256_1
OS Version: 10.0.26100.2.0.0.256.48
Locale ID: 1033
Extra information about the problem
Bucket ID: 0x133_ISR_nt!KeYieldExecution
Server information: c355c059-f3b5-4b38-8852-fa2907bf87c2

*Literally as I was writing this, I got another blue screen*
Source
Windows
Summary
Shut down unexpectedly
Date
‎4/‎18/‎2025 5:41 AM
Status
Report sent
Problem signature
Problem Event Name: BlueScreen
Code: 13a
Parameter 1: 17
Parameter 2: ffffa28791100340
Parameter 3: ffffa287d407ac20
Parameter 4: 0
OS version: 10_0_26100
Service Pack: 0_0
Product: 256_1
OS Version: 10.0.26100.2.0.0.256.48
Locale ID: 1033
Extra information about the problem
Bucket ID: 0x13a_17_nt!RtlpHeapHandleError

PC Specs
MBD: Asus PRIME Z790-V AX
CPU: Intel Core i9-12900K
GPU: Nvidia RTX 4070-TS (Ti-Super)
RAM: G.Skill Ripjaws S5 32GB (2 x 16GB) DDR5-6000
SSD: Samsung 990 Pro M.2 2TB
PSU: Thermaltake Smart BM3 750 W 80+ Bronze Certified
 
Last edited:
Misgar said:
If you've been running your RAM with XMP enabled at 6400MT/s, I strongly recommend switching off XMP and restore the memory speed back to the JEDEC default (probably 4800MT/s).


Did you get any errors in MemTest? Even one error means you need to take action.
Click to expand...
Thats strange, ive always ran XMP on these particular sticks of ram. Could that be causing all of this? Could simply turning off XMP solve for all these annoying blue screens?

Zero errors in Memtest86. Did all 13 test for each stick, took about 4 hours total. Heres some pictures, let me know if the link works
https://postimg.cc/gallery/xqDkfXx
 
AlmightyKing said:
Thats strange, ive always ran XMP on these particular sticks of ram. Could that be causing all of this? Could simply turning off XMP solve for all these annoying blue screens?

Zero errors in Memtest86. Did all 13 test for each stick, took about 4 hours total. Heres some pictures, let me know if the link works
https://postimg.cc/gallery/xqDkfXx
Click to expand...
Did you run memtest with both sticks installed in the proper slots?

Do you get these crashes when using just one stick of ram in the proper slot?

Perhaps remove the gpu and run off the igp.....test.
 
AlmightyKing said:
Thats strange, ive always ran XMP on these particular sticks of ram. Could that be causing all of this? Could simply turning off XMP solve for all these annoying blue screens?
Click to expand...
Running memory too fast can cause problems. As I suggested, try switching off XMP and see if stability improves.

The spec for the i9-12900K on CPU-World shows it's "guaranteed" to work up to 4800MT/s. You should be able to push faster XMP speeds, but 6000MT/s might be verging on instability on your mobo.
https://www.cpu-world.com/CPUs/Core_i9/Intel-Core i9 i9-12900K.html

Memory controller
The number of controllers: 2
Memory channels (per controller): 2
Memory channels (total): 4
Supported memory: DDR4-3200, DDR5-4800
ECC supported: Yes

On many 4-slot mobos, DIMM slots A2/B2 provide the most stable operation. Check your mobo manual for recommended RAM placement.
 
kernel mode heap corruption, could be bad ram settings, could be a stupid kernel driver. you should provide the actual minidump files but you might need to provide a kernel dump to figure out the problem. sometimes if memtest86 is ok and you still have this problem you have to run verifer to find cases where a driver is accessing kernel memory incorrectly. (stupid mouse drivers or mouse firmware most often)

for the watchdog timeout
I don't recognize the 1e00 timeout value
but you would run the debugger command
!dpcwatchdog

slower device have longer timeout values. Maybe a drive.
I think the time out is 30 seconds (not sure what that is in clock ticks)
I guess it could be a slower device like a gpu sound driver

one of the bugchecks is common for overheated cpu or
for overclocked cpu or bad power to the cpu. checking the system up timer can give a clue as to the cause.

first/best guess would be a bad/stupid driver corrupting kernel memory. system up time can help figure this out. stupid driver generally do not do kernel corruption until after some system sleep cycles.

note: for most hardware related issues you should provide a kernel dump. the minidump does not contain the proper data.
(some data for watchdog timeouts was added to the minidump since it happens so often)

the watchdog timeout was in a slow device, not the cpu, gpu or even the slower USB. Most likely something like a drive or tablet pad. if it is the drive, you would update firmware, update bios and chipset drivers depending on the type of drive and its interface. also check the drive SMART data.
(assuming it is not some stupid driver problem corrupting kernel memory, stupid drivers generally work until windows memory management moves something in memory, This happens a lot with memory compression)
 
Last edited:
SkyNetRising said:
Run memtest with both modules installed.
It may pass with single module, but fail with multiple modules installed.

BTW - what BIOS version is your board currently at?
Click to expand...

I'll try to run both sticks and give you an update.
I'm currently using the most up-to-date BIOS version (1813).
 
Misgar said:
Running memory too fast can cause problems. As I suggested, try switching off XMP and see if stability improves.

The spec for the i9-12900K on CPU-World shows it's "guaranteed" to work up to 4800MT/s. You should be able to push faster XMP speeds, but 6000MT/s might be verging on instability on your mobo.
https://www.cpu-world.com/CPUs/Core_i9/Intel-Core i9 i9-12900K.html

Memory controller
The number of controllers: 2
Memory channels (per controller): 2
Memory channels (total): 4
Supported memory: DDR4-3200, DDR5-4800
ECC supported: Yes

On many 4-slot mobos, DIMM slots A2/B2 provide the most stable operation. Check your mobo manual for recommended RAM placement.
Click to expand...
Currrently I have my ram slotted at A2/B2 so I don't think the slotting is the problem. I just turned off XMP, will give it a run for couple hours and figure out the problem.

On a side note, could the temps be a problem? Anytime I blue screen, my CPU sits at 40c in BIOs. During full load, I've seen this CPU shoot up to 85-90c.
 
johnbl said:
kernel mode heap corruption, could be bad ram settings, could be a stupid kernel driver. you should provide the actual minidump files but you might need to provide a kernel dump to figure out the problem. sometimes if memtest86 is ok and you still have this problem you have to run verifer to find cases where a driver is accessing kernel memory incorrectly. (stupid mouse drivers or mouse firmware most often)

for the watchdog timeout
I don't recognize the 1e00 timeout value
but you would run the debugger command
!dpcwatchdog

slower device have longer timeout values. Maybe a drive.
I think the time out is 30 seconds (not sure what that is in clock ticks)
I guess it could be a slower device like a gpu sound driver

one of the bugchecks is common for overheated cpu or
for overclocked cpu or bad power to the cpu. checking the system up timer can give a clue as to the cause.

first/best guess would be a bad/stupid driver corrupting kernel memory. system up time can help figure this out. stupid driver generally do not do kernel corruption until after some system sleep cycles.

note: for most hardware related issues you should provide a kernel dump. the minidump does not contain the proper data.
(some data for watchdog timeouts was added to the minidump since it happens so often)

the watchdog timeout was in a slow device, not the cpu, gpu or even the slower USB. Most likely something like a drive or tablet pad. if it is the drive, you would update firmware, update bios and chipset drivers depending on the type of drive and its interface. also check the drive SMART data.
(assuming it is not some stupid driver problem corrupting kernel memory, stupid drivers generally work until windows memory management moves something in memory, This happens a lot with memory compression)
Click to expand...
Wow thats alot information. what steps should I take first to prevent this blue screen from happening? I was able to pull most of the data from event viewer and view reliability history
 
AlmightyKing said:
Wow thats alot information. what steps should I take first to prevent this blue screen from happening? I was able to pull most of the data from event viewer and view reliability history
Click to expand...
well, provide the minidump, about 20 percent of the time it will name the driver.
you can run verifier.exe tests and it will force a bugcheck when a driver does something wrong. just be sure you know how to get in to safe mode and how to turn verifier off with verifier.exe /reset command. (for the cases where your machine immediately bugchecks on boot with verifier running)

or you can guess and just do the normal fix procedures. IE update bios, update motherboard provided drivers. (not the motherboard utilities)
often you can delay a bugcheck by making the system delete the pagefile.sys on system reboot. then just reboot more often. better to fix the problem.

you could google how to turn off windows memory compression.
I would not recommend it but it could delay problems with poor drivers that were not updated. ie without the memory compression, the windows memory manager will have less free space and less reason to move memory elements around and dumb user mode drivers will not overwrite the wrong area of kernel memory as often. (still best to figure out the cause)

note: the kernel mode heap corruption reported had a type of 0x17 that is not documented (types that are documented go up to 0x16)
https://learn.microsoft.com/en-us/w.../bug-check-0x13a--kernel-mode-heap-corruption
 
Last edited:
johnbl said:
well, provide the minidump, about 20 percent of the time it will name the driver.
you can run verifier.exe tests and it will force a bugcheck when a driver does something wrong. just be sure you know how to get in to safe mode and how to turn verifier off with verifier.exe /reset command. (for the cases where your machine immediately bugchecks on boot with verifier running)

or you can guess and just do the normal fix procedures. IE update bios, update motherboard provided drivers. (not the motherboard utilities)
often you can delay a bugcheck by making the system delete the pagefile.sys on system reboot. then just reboot more often. better to fix the problem.

you could google how to turn off windows memory compression.
I would not recommend it but it could delay problems with poor drivers that were not updated. ie without the memory compression, the windows memory manager will have less free space and less reason to move memory elements around and dump user mode drivers will not overwrite the wrong area of kernel memory as often. (still best to figure out the cause)
Click to expand...

Just ran verifier for all drivers except Microsoft. Let it run twice, computer blue-screened both times.

Heres the dump file for it, let me know if you can open it
One drive dump file
 
driver is part of ASUS Utility sound driver. you should update from the motherboard vendor.
strange I do not see the device when I look at your motherboard data ( the typical real tek driver is not installed)

https://www.asus.com/motherboards-c.../helpdesk_download?model2Name=PRIME-Z790-V-AX

see if you can update or remove or the driver

system ran 11 seconds, shows a stack corruption running
igovsd.sys
file date:Thu Sep 23 01:07:38 2021
Intelligo Virtual Audio Cable
 
Last edited:
AlmightyKing said:
Just did another windows verifier.
Heres a new dump file
Another dump
Click to expand...
same driver, you need to remove the driver or exclude it from verifier.exe testing

to exclude the driver you would add
/driver.exclude DriverList
so run verifier.exe with all of your options but add
/driver.exclude igovsd.sys

you should probably turn off any armory crate functions in bios.
if you exclude the driver you might not know if it was the cause, since it will still run but will not be checked.

you have the most current driver that I see. Microsoft update catalog does not have any driver by that name.

oh, i guess as a sound driver it could include the microphone.
 
Last edited:
johnbl said:
same driver, you need to remove the driver or exclude it from verifier.exe testing

to exclude the driver you would add
/driver.exclude DriverList
so run verifier.exe with all of your options but add
/driver.exclude igovsd.sys

you should probably turn off any armory crate functions in bios.
if you exclude the driver you might not know if it was the cause, since it will still run but will not be checked.
Click to expand...
Gonna run verifier again and unselect the igovsd.sys driver. Strange its labeled under Asustek computer inc. I'll update you in a couple of minutes
 
johnbl said:
same driver, you need to remove the driver or exclude it from verifier.exe testing

to exclude the driver you would add
/driver.exclude DriverList
so run verifier.exe with all of your options but add
/driver.exclude igovsd.sys

you should probably turn off any armory crate functions in bios.
if you exclude the driver you might not know if it was the cause, since it will still run but will not be checked.

you have the most current driver that I see. Microsoft update catalog does not have any driver by that name.

oh, i guess as a sound driver it could include the microphone.
Click to expand...
Just finished, got another blue screen even.
This one happened even with that driver unchecked.
Heres another dump More dumping
 
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom