F5F Stay Refreshed Software Operating Systems You're experiencing frequent random IRQL_NOT_LESS_OR_EQUAL crashes?

You're experiencing frequent random IRQL_NOT_LESS_OR_EQUAL crashes?

You're experiencing frequent random IRQL_NOT_LESS_OR_EQUAL crashes?

Pages (3): Previous 1 2 3 Next
A
AlmightyEag
Posting Freak
785
10-21-2021, 04:16 AM
#11
All those dumps continue to display failures when the processor moves from idle to running state. I would now like you to attempt starting Windows in Safe Mode. In Safe Mode, a minimalized version of Windows runs with only essential services and drivers, usually without third-party applications. This means you won’t be able to perform meaningful tasks or play games, and many devices might not function correctly due to missing drivers. For instance, your display may appear at low resolution because only the basic Windows driver is used. The value of Safe Mode lies in its stability—being a stripped-down system makes it reliable. If you encounter BSODs or crashes there, it likely points to a hardware issue. However, if it runs smoothly in Safe Mode, the problem probably resides with a third-party driver or service not loaded in that environment. We can then explore another method to identify the faulty service or driver.
A
AlmightyEag
10-21-2021, 04:16 AM #11

All those dumps continue to display failures when the processor moves from idle to running state. I would now like you to attempt starting Windows in Safe Mode. In Safe Mode, a minimalized version of Windows runs with only essential services and drivers, usually without third-party applications. This means you won’t be able to perform meaningful tasks or play games, and many devices might not function correctly due to missing drivers. For instance, your display may appear at low resolution because only the basic Windows driver is used. The value of Safe Mode lies in its stability—being a stripped-down system makes it reliable. If you encounter BSODs or crashes there, it likely points to a hardware issue. However, if it runs smoothly in Safe Mode, the problem probably resides with a third-party driver or service not loaded in that environment. We can then explore another method to identify the faulty service or driver.

I
iShake74
Junior Member
17
10-21-2021, 08:11 AM
#12
This seems beneficial for me to do. In the future, if several hours have gone by and there are no BSODs, I’ll verify that a third-party driver or service is responsible. Right now, I plan to adjust my power settings and observe any changes. Another approach I can take is employing Driver Verifier. I’m familiar with its usage. When I launch Driver Verifier, I’ll keep the computer idle until a BSOD appears. I’ll also create a restore point prior to running it, just in case my system becomes stuck in a boot loop.
I
iShake74
10-21-2021, 08:11 AM #12

This seems beneficial for me to do. In the future, if several hours have gone by and there are no BSODs, I’ll verify that a third-party driver or service is responsible. Right now, I plan to adjust my power settings and observe any changes. Another approach I can take is employing Driver Verifier. I’m familiar with its usage. When I launch Driver Verifier, I’ll keep the computer idle until a BSOD appears. I’ll also create a restore point prior to running it, just in case my system becomes stuck in a boot loop.

S
sydneyyyyyy
Senior Member
396
10-21-2021, 09:05 PM
#13
I've encountered this problem before, have you considered trying to reinstall, rearrange, or swap the RAM? It helped for me.
S
sydneyyyyyy
10-21-2021, 09:05 PM #13

I've encountered this problem before, have you considered trying to reinstall, rearrange, or swap the RAM? It helped for me.

T
TheYoanZ
Member
156
10-27-2021, 06:53 PM
#14
I recommend giving it another shot by reseating the RAM to check if it resolves the issue.
T
TheYoanZ
10-27-2021, 06:53 PM #14

I recommend giving it another shot by reseating the RAM to check if it resolves the issue.

P
Pokechu
Junior Member
21
10-27-2021, 07:55 PM
#15
Re-seating the RAM didn't resolve the issue. The BSOD persisted. Swapping the RAM wouldn't help because I already purchased the same type of RAM for my computer last year. I believe everything is functioning correctly.
P
Pokechu
10-27-2021, 07:55 PM #15

Re-seating the RAM didn't resolve the issue. The BSOD persisted. Swapping the RAM wouldn't help because I already purchased the same type of RAM for my computer last year. I believe everything is functioning correctly.

B
banshee45
Senior Member
726
10-28-2021, 12:23 AM
#16
There was another crash on my computer, but this time there were no BSOD messages and it wasn't stuck. I used the computer normally until it suddenly restarted without warning. No BSOD appeared and Windows didn’t provide any memory dumps. I’m running out of options and want help fixing this before it becomes a permanent problem. These frequent crashes are really frustrating.
B
banshee45
10-28-2021, 12:23 AM #16

There was another crash on my computer, but this time there were no BSOD messages and it wasn't stuck. I used the computer normally until it suddenly restarted without warning. No BSOD appeared and Windows didn’t provide any memory dumps. I’m running out of options and want help fixing this before it becomes a permanent problem. These frequent crashes are really frustrating.

X
xXJay_BugXx
Senior Member
559
10-28-2021, 01:54 AM
#17
There are roughly five threads running on this PC, so I don't think the issue is related to software. Have you made any changes recently? I'm not trying to place blame, just curious. I'm wondering if the problem might be with the CPU or the motherboard—two components that are hard to test directly. There haven't been any real tests on the motherboard yet, but running Primte95 on the CPU could give some insight. The current errors seem to start when a core fails to wake up; is it always the same core each time? Earlier it was hypervisor-related issues, then page faults and IRQ problems, followed by crashes without dumps, and now the hypervisor again.
X
xXJay_BugXx
10-28-2021, 01:54 AM #17

There are roughly five threads running on this PC, so I don't think the issue is related to software. Have you made any changes recently? I'm not trying to place blame, just curious. I'm wondering if the problem might be with the CPU or the motherboard—two components that are hard to test directly. There haven't been any real tests on the motherboard yet, but running Primte95 on the CPU could give some insight. The current errors seem to start when a core fails to wake up; is it always the same core each time? Earlier it was hypervisor-related issues, then page faults and IRQ problems, followed by crashes without dumps, and now the hypervisor again.

R
Romain57730
Junior Member
1
11-10-2021, 09:17 PM
#18
The only change I made was the RAM, which I replaced last year.
I’m unsure whether the core that doesn’t wake up is always the same one.
It’s possible it could be a hardware issue, but I haven’t experienced frequent BSODs recently.
My motherboard, CPU, and GPU are five years old, so I’m not sure if they’ve developed problems quickly.
R
Romain57730
11-10-2021, 09:17 PM #18

The only change I made was the RAM, which I replaced last year.
I’m unsure whether the core that doesn’t wake up is always the same one.
It’s possible it could be a hardware issue, but I haven’t experienced frequent BSODs recently.
My motherboard, CPU, and GPU are five years old, so I’m not sure if they’ve developed problems quickly.

T
Tyazoyd
Member
71
11-11-2021, 09:47 PM
#19
I quoted ubuysa, wondering if he could explain from the dumps.
You've been facing issues since 2022. It could be one faulty component causing everything. It might just be a minor glitch that occasionally disrupts things. Two different versions of Windows...
just trying to assist
T
Tyazoyd
11-11-2021, 09:47 PM #19

I quoted ubuysa, wondering if he could explain from the dumps.
You've been facing issues since 2022. It could be one faulty component causing everything. It might just be a minor glitch that occasionally disrupts things. Two different versions of Windows...
just trying to assist

R
rosie2435
Senior Member
475
11-19-2021, 09:42 PM
#20
Sorry. My bad. If the issue persists, it's unclear which problem is responsible. You mentioned you only have one Windows version installed and that an automatic backup was created during the update to version 24H2.
R
rosie2435
11-19-2021, 09:42 PM #20

Sorry. My bad. If the issue persists, it's unclear which problem is responsible. You mentioned you only have one Windows version installed and that an automatic backup was created during the update to version 24H2.

Pages (3): Previous 1 2 3 Next