F5F Stay Refreshed Hardware Desktop Frequent system crashes, trouble identifying problems

Frequent system crashes, trouble identifying problems

Frequent system crashes, trouble identifying problems

Pages (3): Previous 1 2 3 Next
D
DeadOctober
Junior Member
5
11-18-2024, 06:01 PM
#11
You're seeing the same issue on both RAM sticks, which suggests they might be defective together.
D
DeadOctober
11-18-2024, 06:01 PM #11

You're seeing the same issue on both RAM sticks, which suggests they might be defective together.

M
mcbudder2004
Senior Member
687
11-18-2024, 06:01 PM
#12
All drivers are current, CPU temps are normal and within acceptable ranges, I only use the built-in antivirus from Windows, the pagefile is enabled on all drives. I’m not sure what’s going on anymore, but thank you for your assistance.
M
mcbudder2004
11-18-2024, 06:01 PM #12

All drivers are current, CPU temps are normal and within acceptable ranges, I only use the built-in antivirus from Windows, the pagefile is enabled on all drives. I’m not sure what’s going on anymore, but thank you for your assistance.

B
Beatress
Member
161
11-18-2024, 06:01 PM
#13
It seems the current approach to handling their setup isn't ideal, likely because both components are faulty. Have you checked if the board's BIOS is up to date? Update it and retry. If that fails, switch to a different RAM module—different brands often work together. Most boards should fit most RAM types, but modern systems sometimes face issues with mismatched configurations. With today’s high memory capacities and speeds, these problems are increasingly frequent.
B
Beatress
11-18-2024, 06:01 PM #13

It seems the current approach to handling their setup isn't ideal, likely because both components are faulty. Have you checked if the board's BIOS is up to date? Update it and retry. If that fails, switch to a different RAM module—different brands often work together. Most boards should fit most RAM types, but modern systems sometimes face issues with mismatched configurations. With today’s high memory capacities and speeds, these problems are increasingly frequent.

C
CocaCola15
Senior Member
603
11-18-2024, 06:02 PM
#14
The BIOS has been updated recently, but I’m not able to replace the RAM at the moment since I need a new one to try it out.
C
CocaCola15
11-18-2024, 06:02 PM #14

The BIOS has been updated recently, but I’m not able to replace the RAM at the moment since I need a new one to try it out.

C
Ccows
Junior Member
4
11-18-2024, 06:02 PM
#15
When you change the RAM, please inform us of the outcomes. Until then, if you're seeking a software solution for the hardware issue, expect a lengthy process.
C
Ccows
11-18-2024, 06:02 PM #15

When you change the RAM, please inform us of the outcomes. Until then, if you're seeking a software solution for the hardware issue, expect a lengthy process.

P
pacmanmoon1
Junior Member
15
11-18-2024, 06:02 PM
#16
Lowering RAM speed to 4800 remains an issue, even without XMP support. If it doesn’t stop crashing, attempt using XMP at a higher speed such as 5600MHz. Keep in mind that hardware limitations may prevent full performance at the recommended rates.
P
pacmanmoon1
11-18-2024, 06:02 PM #16

Lowering RAM speed to 4800 remains an issue, even without XMP support. If it doesn’t stop crashing, attempt using XMP at a higher speed such as 5600MHz. Keep in mind that hardware limitations may prevent full performance at the recommended rates.

X
XpSlayer21
Junior Member
32
11-18-2024, 06:02 PM
#17
It's currently at 4800 as shown in the screenshots and logs. @kiron The crashes seem to stem from memory issues. Windows moves low-priority RAM data into the page file and retrieves it when needed, making storage appear like memory (and vice versa). The memory controller is part of the CPU, so a failure there would cause this behavior. In your situation, one crash appears random—finding a page fault in random data—while another was during memory compression. At this point, it could be any of these scenarios. If you have additional dump files, they could help clarify whether it's related to storage or RAM/CPU.
X
XpSlayer21
11-18-2024, 06:02 PM #17

It's currently at 4800 as shown in the screenshots and logs. @kiron The crashes seem to stem from memory issues. Windows moves low-priority RAM data into the page file and retrieves it when needed, making storage appear like memory (and vice versa). The memory controller is part of the CPU, so a failure there would cause this behavior. In your situation, one crash appears random—finding a page fault in random data—while another was during memory compression. At this point, it could be any of these scenarios. If you have additional dump files, they could help clarify whether it's related to storage or RAM/CPU.

C
c_x_y
Member
227
11-18-2024, 06:02 PM
#18
You changed the GPU to a different setup, probably assuming it was DDR4. It seems like the mainboard RAM or CPU might be faulty. I recommend starting with a new RAM package that meets the quality standards.
C
c_x_y
11-18-2024, 06:02 PM #18

You changed the GPU to a different setup, probably assuming it was DDR4. It seems like the mainboard RAM or CPU might be faulty. I recommend starting with a new RAM package that meets the quality standards.

X
xdHammodixd
Junior Member
39
11-18-2024, 06:02 PM
#19
Thanks to everyone’s support, I’ve finally identified the issue. It turned out the DANG CPU was the culprit—my RAM worked fine when swapped into another system, so it had to be the CPU or motherboard. I tried a compatible CPU and it fixed everything. Now I can stop worrying about those frustrations and look forward to Intel’s warranty.
X
xdHammodixd
11-18-2024, 06:02 PM #19

Thanks to everyone’s support, I’ve finally identified the issue. It turned out the DANG CPU was the culprit—my RAM worked fine when swapped into another system, so it had to be the CPU or motherboard. I tried a compatible CPU and it fixed everything. Now I can stop worrying about those frustrations and look forward to Intel’s warranty.

_
_Rammel_
Junior Member
27
11-18-2024, 06:02 PM
#20
That implies it’s either the CPU or the board. You didn’t verify the CPU was faulty—just that the board works with another CPU. Until you test the issue on another board using your original CPU, you can’t rule out a defective board.
_
_Rammel_
11-18-2024, 06:02 PM #20

That implies it’s either the CPU or the board. You didn’t verify the CPU was faulty—just that the board works with another CPU. Until you test the issue on another board using your original CPU, you can’t rule out a defective board.

Pages (3): Previous 1 2 3 Next