F5F Stay Refreshed Hardware Desktop PC crashes only during idle time or while running non-intensive games. Looking for someone to review my logs and assist

PC crashes only during idle time or while running non-intensive games. Looking for someone to review my logs and assist

PC crashes only during idle time or while running non-intensive games. Looking for someone to review my logs and assist

Pages (2): 1 2 Next
J
juri1990
Senior Member
441
11-25-2016, 10:36 AM
#1
I have searched extensively online for solutions to my blue screen problem, consistently encountering errors like "KERNEL_SECURITY_CHECK_FAILURE" and "IRQL_NOT_LESS_OR_EQUAL." Over the past month, I've been experiencing these issues without any clear resolution. It seems I might need to replace some components, but I haven't identified a specific cause. I'm hoping someone could review my system logs or provide further guidance that would help fix this without requiring additional costs. These crashes typically occur when I'm not running resource-intensive games, though I've had multiple failures even during normal usage—two on Trombone Champ and none on Destiny 2 after playing for several hours. My system details are listed below in case they assist.
J
juri1990
11-25-2016, 10:36 AM #1

I have searched extensively online for solutions to my blue screen problem, consistently encountering errors like "KERNEL_SECURITY_CHECK_FAILURE" and "IRQL_NOT_LESS_OR_EQUAL." Over the past month, I've been experiencing these issues without any clear resolution. It seems I might need to replace some components, but I haven't identified a specific cause. I'm hoping someone could review my system logs or provide further guidance that would help fix this without requiring additional costs. These crashes typically occur when I'm not running resource-intensive games, though I've had multiple failures even during normal usage—two on Trombone Champ and none on Destiny 2 after playing for several hours. My system details are listed below in case they assist.

E
Ender_Craft47
Posting Freak
866
11-25-2016, 10:48 AM
#2
Hello there! I've searched extensively online to find a solution for my blue screen problem. Could you share what steps you've already taken so we don't repeat them? Also, what BIOS version are you using on your motherboard? I noticed the installer for your operating system is flagged with ntkrnlmp.exe in WinDbg—where did you get it from?
E
Ender_Craft47
11-25-2016, 10:48 AM #2

Hello there! I've searched extensively online to find a solution for my blue screen problem. Could you share what steps you've already taken so we don't repeat them? Also, what BIOS version are you using on your motherboard? I noticed the installer for your operating system is flagged with ntkrnlmp.exe in WinDbg—where did you get it from?

M
Meteor6666
Junior Member
7
12-07-2016, 09:36 PM
#3
Place MemTest on a flash drive and execute the checks. There is significant memory damage occurring.
M
Meteor6666
12-07-2016, 09:36 PM #3

Place MemTest on a flash drive and execute the checks. There is significant memory damage occurring.

N
Nani100
Member
213
12-11-2016, 12:46 AM
#4
I completed memory tests on both RAM sticks and they all passed. I reinstalled Windows from the official Microsoft site. The same Windows version I originally downloaded in October 2022 when building the PC still worked after the installation, which means the problems continued. I'm currently using BIOS version 7D54v12, the latest driver for my X3D CPU.

I've also run "sfc scannow" and "CHKDSK" in CMD, and performed Windows memory tests and MemTest86, all of which showed no errors. I updated every outdated driver, including reinstalling the Nvidia graphics driver. I disabled XMP settings on my RAM and ran the PC with a single stick for six days without a crash, though I experienced random BSODs one day despite no changes. I've also tried AMD chipset drivers via their software.
N
Nani100
12-11-2016, 12:46 AM #4

I completed memory tests on both RAM sticks and they all passed. I reinstalled Windows from the official Microsoft site. The same Windows version I originally downloaded in October 2022 when building the PC still worked after the installation, which means the problems continued. I'm currently using BIOS version 7D54v12, the latest driver for my X3D CPU.

I've also run "sfc scannow" and "CHKDSK" in CMD, and performed Windows memory tests and MemTest86, all of which showed no errors. I updated every outdated driver, including reinstalling the Nvidia graphics driver. I disabled XMP settings on my RAM and ran the PC with a single stick for six days without a crash, though I experienced random BSODs one day despite no changes. I've also tried AMD chipset drivers via their software.

B
Bratzoid
Junior Member
15
12-11-2016, 05:36 AM
#5
Are you overclocking at all?
B
Bratzoid
12-11-2016, 05:36 AM #5

Are you overclocking at all?

G
grisu112
Member
170
12-11-2016, 06:16 AM
#6
If you're not pushing the overclock limit and it's not the RAM issue, we can examine the CPU a bit more closely.
This individual achieved results by adjusting their voltage settings, though you should start with stress testing the CPU first. If that doesn't resolve the problem, we'll look into driver-related concerns.
G
grisu112
12-11-2016, 06:16 AM #6

If you're not pushing the overclock limit and it's not the RAM issue, we can examine the CPU a bit more closely.
This individual achieved results by adjusting their voltage settings, though you should start with stress testing the CPU first. If that doesn't resolve the problem, we'll look into driver-related concerns.

M
miknes123
Senior Member
646
12-13-2016, 08:27 PM
#7
Hey everyone, I've upgraded my BIOS to the newest release. I'll make sure to keep this thread current.
M
miknes123
12-13-2016, 08:27 PM #7

Hey everyone, I've upgraded my BIOS to the newest release. I'll make sure to keep this thread current.

R
rockstar4893
Junior Member
2
12-13-2016, 11:54 PM
#8
Yeah that didn't work unfortunately. I'm attaching the new dumps in case anything is different now. This was also a "IRQL_NOT LESS_OR EQUAL" BSOD
https://gofile.io/d/J9VEv0
R
rockstar4893
12-13-2016, 11:54 PM #8

Yeah that didn't work unfortunately. I'm attaching the new dumps in case anything is different now. This was also a "IRQL_NOT LESS_OR EQUAL" BSOD
https://gofile.io/d/J9VEv0

K
ketman34
Posting Freak
834
01-04-2017, 03:00 AM
#9
You're encountering minor errors in essential system operations with no clear overlap among them. It seems another external factor might be destabilizing the OS, or there could be a hardware problem such as CPU instability or motherboard failure. Consider running a stress test on your CPU.

It's also interesting that these issues appear more frequently when the system is idle or under low load, which could indicate driver-related problems. I observed that all other processors during those crashes were idle and locked in amdppm! ReadIoMemRaw. This suggests amdppm.sys manages CPU power states, which is likely normal.
K
ketman34
01-04-2017, 03:00 AM #9

You're encountering minor errors in essential system operations with no clear overlap among them. It seems another external factor might be destabilizing the OS, or there could be a hardware problem such as CPU instability or motherboard failure. Consider running a stress test on your CPU.

It's also interesting that these issues appear more frequently when the system is idle or under low load, which could indicate driver-related problems. I observed that all other processors during those crashes were idle and locked in amdppm! ReadIoMemRaw. This suggests amdppm.sys manages CPU power states, which is likely normal.

Z
zorro8003PL
Member
131
01-04-2017, 03:44 AM
#10
I'm planning to run some stress tests tomorrow, but regarding drivers, I recently got a new keyboard (ROG Azoth) about a week and a half before I started noticing these errors. Could there be any chance it might be the cause? The only other driver I've installed recently would have been when you first plugged in a keyboard.
Z
zorro8003PL
01-04-2017, 03:44 AM #10

I'm planning to run some stress tests tomorrow, but regarding drivers, I recently got a new keyboard (ROG Azoth) about a week and a half before I started noticing these errors. Could there be any chance it might be the cause? The only other driver I've installed recently would have been when you first plugged in a keyboard.

Pages (2): 1 2 Next