F5F Stay Refreshed Hardware Desktop The system is experiencing a crash and requires assistance.

The system is experiencing a crash and requires assistance.

The system is experiencing a crash and requires assistance.

W
wdawg39
Member
52
03-08-2025, 03:02 PM
#1
Occurring for some time now. Feeling overwhelmed by the frequent crashes and seeking clarity. The DRIVER_IRQL_NOT_LESS_OR_EQUAL error keeps appearing. Appreciate your help. DMP files aren't available since Perfmon stops scanning after 60 seconds; I can share a screenshot if needed, or point you to the right place in Perfmon settings. Operating System - Windows 11 x64 What version of the operating system was originally installed? It's hard to recall, but it seems like a retail purchase rather than an OEM setup. Media purchased about 3-4 years ago. OS installation history: several reinstalls have taken place. CPU model: Ryzen 3600. Graphics card: GTX 1660 Super. Motherboard: B450-A PRO MAX Power Supply (brand & wattage not required if it's a laptop). Seasonic power supply: 650W. Manufacturer: N/A. Exact model number: not available (OEM or laptop). Device type: Desktop?
W
wdawg39
03-08-2025, 03:02 PM #1

Occurring for some time now. Feeling overwhelmed by the frequent crashes and seeking clarity. The DRIVER_IRQL_NOT_LESS_OR_EQUAL error keeps appearing. Appreciate your help. DMP files aren't available since Perfmon stops scanning after 60 seconds; I can share a screenshot if needed, or point you to the right place in Perfmon settings. Operating System - Windows 11 x64 What version of the operating system was originally installed? It's hard to recall, but it seems like a retail purchase rather than an OEM setup. Media purchased about 3-4 years ago. OS installation history: several reinstalls have taken place. CPU model: Ryzen 3600. Graphics card: GTX 1660 Super. Motherboard: B450-A PRO MAX Power Supply (brand & wattage not required if it's a laptop). Seasonic power supply: 650W. Manufacturer: N/A. Exact model number: not available (OEM or laptop). Device type: Desktop?

L
lonewolf014
Junior Member
13
03-08-2025, 03:02 PM
#2
This seems to be a data retrieval problem from the dump files. Memory isn't necessarily about RAM, though that's often the main concern. Windows moves low-priority RAM information into the page file and retrieves it when needed, making storage appear like memory. The memory controller is built into the CPU, and if it fails, it can make storage look like memory. If storage accounts for roughly half of the dumps, storage or its drivers are likely the culprit—this isn't present here, so storage probably isn't the issue. Be sure to remove any overclocking or undervoltage settings. For testing RAM, run the system normally with a single stick at a time. If only one stick causes crashes, the problem is likely in the CPU. Memory testers tend to miss faulty DDR4 and newer RAM quite often, so I'm not confident in their results. Also, some Zen 2 CPUs (3000, 4000 series, and certain laptop 5000 series) have a quirk where a defective CPU will almost always appear as memory in the dumps—no explanation known.
L
lonewolf014
03-08-2025, 03:02 PM #2

This seems to be a data retrieval problem from the dump files. Memory isn't necessarily about RAM, though that's often the main concern. Windows moves low-priority RAM information into the page file and retrieves it when needed, making storage appear like memory. The memory controller is built into the CPU, and if it fails, it can make storage look like memory. If storage accounts for roughly half of the dumps, storage or its drivers are likely the culprit—this isn't present here, so storage probably isn't the issue. Be sure to remove any overclocking or undervoltage settings. For testing RAM, run the system normally with a single stick at a time. If only one stick causes crashes, the problem is likely in the CPU. Memory testers tend to miss faulty DDR4 and newer RAM quite often, so I'm not confident in their results. Also, some Zen 2 CPUs (3000, 4000 series, and certain laptop 5000 series) have a quirk where a defective CPU will almost always appear as memory in the dumps—no explanation known.

P
PaigeOfTheBook
Senior Member
733
03-08-2025, 03:02 PM
#3
This has been a nearly yearly task with this device. I've tried everything—testing RAM with diagnostics, running memtest86, even purchasing additional RAM to rule out slot issues. I inspected each slot and every stick individually. So far, the RAM appears to be functioning correctly. XMP is only set to 3200, which is the maximum allowed on this board for two 16GB sticks. It still crashes at base speed when XMP is off. I’m not sure if any other components are overclocked; it seems unlikely, as there’s no visible overclocking in the BIOS. I know the CPU has a base clock of 3.60, but it often runs above that—sometimes over 4. It might just automatically boost. I’ve adjusted settings in regedit to see if changing the lock value at 3.60 helps, but it still fails. It could be a random issue, so maybe a completely new build would be better.
P
PaigeOfTheBook
03-08-2025, 03:02 PM #3

This has been a nearly yearly task with this device. I've tried everything—testing RAM with diagnostics, running memtest86, even purchasing additional RAM to rule out slot issues. I inspected each slot and every stick individually. So far, the RAM appears to be functioning correctly. XMP is only set to 3200, which is the maximum allowed on this board for two 16GB sticks. It still crashes at base speed when XMP is off. I’m not sure if any other components are overclocked; it seems unlikely, as there’s no visible overclocking in the BIOS. I know the CPU has a base clock of 3.60, but it often runs above that—sometimes over 4. It might just automatically boost. I’ve adjusted settings in regedit to see if changing the lock value at 3.60 helps, but it still fails. It could be a random issue, so maybe a completely new build would be better.

J
Jorski
Member
219
03-08-2025, 03:02 PM
#4
I didn't realize the PC's Seasonic PSU had been humming or moving for a while. It features a fan switch to prevent constant operation—probably not due to loose bearings. I only brought it up recently, and it seems like a power problem. This could mean the CPU isn't getting enough power, which explains why these components are failing. We should replace the PSU next week and see if that fixes things.
J
Jorski
03-08-2025, 03:02 PM #4

I didn't realize the PC's Seasonic PSU had been humming or moving for a while. It features a fan switch to prevent constant operation—probably not due to loose bearings. I only brought it up recently, and it seems like a power problem. This could mean the CPU isn't getting enough power, which explains why these components are failing. We should replace the PSU next week and see if that fixes things.

D
DutchManiak
Member
161
03-08-2025, 03:02 PM
#5
D
DutchManiak
03-08-2025, 03:02 PM #5

Y
yayassad
Member
66
03-08-2025, 03:02 PM
#6
I'm not claiming they always fail, but I'm puzzled this only lasted so long. Swapping the PSU this week will help us understand what's happening.
Y
yayassad
03-08-2025, 03:02 PM #6

I'm not claiming they always fail, but I'm puzzled this only lasted so long. Swapping the PSU this week will help us understand what's happening.

W
wolfcore10
Junior Member
29
03-08-2025, 03:02 PM
#7
Following the latest PSU and GPU issues, confirmed they aren't related to dirty power. Occasionally it freezes and restarts without any display changes, and sometimes it triggers numerous BSOD errors. I observed unusual events in the event viewer, adjusted registry memory management, and added a maximum page pool to test. After two days, no crashes have occurred so far. I believe creating an unlimited page pool resolved the CPU memory problem. I'll keep monitoring from here. Four days on, it seems this fix worked!
W
wolfcore10
03-08-2025, 03:02 PM #7

Following the latest PSU and GPU issues, confirmed they aren't related to dirty power. Occasionally it freezes and restarts without any display changes, and sometimes it triggers numerous BSOD errors. I observed unusual events in the event viewer, adjusted registry memory management, and added a maximum page pool to test. After two days, no crashes have occurred so far. I believe creating an unlimited page pool resolved the CPU memory problem. I'll keep monitoring from here. Four days on, it seems this fix worked!