F5F Stay Refreshed Hardware Desktop Fehler in WoW: Speicher nicht gefunden, 132.

Fehler in WoW: Speicher nicht gefunden, 132.

Fehler in WoW: Speicher nicht gefunden, 132.

8
8959za94
Junior Member
1
03-01-2018, 12:41 AM
#1
I noticed this is clearly a hardware problem. It's quite unusual. After several weeks of testing, memory tests came back normal—everything passed before and even after replacing a new set of RAM. The graphics card handled 16 hours of intensive use without issues. Both SSD drives showed no errors. The cooling system was functioning properly; there were no overheating signs or indications of overclocking.

Issue: My husband and I have the same setup, except for the cooling system. He’s had his system set up for about six months, until a severe storm knocked out power twice before we could return home in time to protect our custom hardware. His games like World of Warcraft and Destiny frequently crash with error 132 (possibly called Centipede in Destiny).

Once the computer was plugged back in after the storm, it took a while to start up, but afterward it seemed normal. After roughly two weeks since the power outage, the crashes began. His games would freeze for 2 to 4 seconds before crashing with error 132, occurring anywhere from 20 minutes to an hour later. Sometimes he could play for several hours, sometimes just an hour. There were no blue screens during those sessions.

A friend suggested replacing the power supply unit (PSU) before making major changes like ordering a new motherboard or rebuilding the whole build. This did help—we managed to play for nearly eight hours before it crashed again. After that, I thought about getting a better surge protector and then swapping all the PSU-connected cables.

This problem is strange because only memory issues were reported, even though everything related to RAM looked fine. But after replacing the PSU, performance improved. I’m really unsure what to do next; I don’t want to swap the motherboard, just want to enjoy gaming with him again. Any suggestions would be greatly appreciated.
8
8959za94
03-01-2018, 12:41 AM #1

I noticed this is clearly a hardware problem. It's quite unusual. After several weeks of testing, memory tests came back normal—everything passed before and even after replacing a new set of RAM. The graphics card handled 16 hours of intensive use without issues. Both SSD drives showed no errors. The cooling system was functioning properly; there were no overheating signs or indications of overclocking.

Issue: My husband and I have the same setup, except for the cooling system. He’s had his system set up for about six months, until a severe storm knocked out power twice before we could return home in time to protect our custom hardware. His games like World of Warcraft and Destiny frequently crash with error 132 (possibly called Centipede in Destiny).

Once the computer was plugged back in after the storm, it took a while to start up, but afterward it seemed normal. After roughly two weeks since the power outage, the crashes began. His games would freeze for 2 to 4 seconds before crashing with error 132, occurring anywhere from 20 minutes to an hour later. Sometimes he could play for several hours, sometimes just an hour. There were no blue screens during those sessions.

A friend suggested replacing the power supply unit (PSU) before making major changes like ordering a new motherboard or rebuilding the whole build. This did help—we managed to play for nearly eight hours before it crashed again. After that, I thought about getting a better surge protector and then swapping all the PSU-connected cables.

This problem is strange because only memory issues were reported, even though everything related to RAM looked fine. But after replacing the PSU, performance improved. I’m really unsure what to do next; I don’t want to swap the motherboard, just want to enjoy gaming with him again. Any suggestions would be greatly appreciated.

M
MilleA
Junior Member
33
03-01-2018, 12:41 AM
#2
The testing used memtest86 as the primary tool; other options like aida64, prime95, and cinebench are available but may not isolate hardware faults between CPU, IMC, and RAM. If those don’t reveal issues, focus on storage problems since both WoW and Destiny frequently engage storage during operation. The extended recovery phase after a crash is noteworthy—does it eventually POST and then boot normally, or does it stall before recovery?
M
MilleA
03-01-2018, 12:41 AM #2

The testing used memtest86 as the primary tool; other options like aida64, prime95, and cinebench are available but may not isolate hardware faults between CPU, IMC, and RAM. If those don’t reveal issues, focus on storage problems since both WoW and Destiny frequently engage storage during operation. The extended recovery phase after a crash is noteworthy—does it eventually POST and then boot normally, or does it stall before recovery?

W
Wisam2040
Junior Member
25
03-01-2018, 12:41 AM
#3
We relied on memtest86 during the initial power-up after the storm. We disconnected the surge protector, allowed it to sit for five minutes, then restarted the computer. The indicator light was initially red, so we waited before turning it back on. After a short delay, the light turned green and the system booted without issues. It has been running normally since then.
W
Wisam2040
03-01-2018, 12:41 AM #3

We relied on memtest86 during the initial power-up after the storm. We disconnected the surge protector, allowed it to sit for five minutes, then restarted the computer. The indicator light was initially red, so we waited before turning it back on. After a short delay, the light turned green and the system booted without issues. It has been running normally since then.

L
LucasandClaus
Senior Member
438
03-01-2018, 12:41 AM
#4
I regret to say it seems like a mismatch; we identified the power supply issue and resolved it, but now it keeps crashing again. I’ll probably bring it to a specialist since I’m not comfortable fixing computers on my own.
L
LucasandClaus
03-01-2018, 12:41 AM #4

I regret to say it seems like a mismatch; we identified the power supply issue and resolved it, but now it keeps crashing again. I’ll probably bring it to a specialist since I’m not comfortable fixing computers on my own.