BSOD ERROR

Pages (3): Previous 1 2 3 Next

kickingzombie
Junior Member

11-21-2025, 08:53 PM

#11

Temperatures are similar for the CPU 40C (98F) and the GPU 30C (86F)

kickingzombie

11-21-2025, 08:53 PM #11

Temperatures are similar for the CPU 40C (98F) and the GPU 30C (86F)

WhatsThePack
Member

215

11-21-2025, 10:33 PM

#12

I also tried RAM on a friend's PC and it functioned perfectly, no error messages appeared.

WhatsThePack

11-21-2025, 10:33 PM #12

I also tried RAM on a friend's PC and it functioned perfectly, no error messages appeared.

GigiCakes
Senior Member

261

11-23-2025, 12:40 PM

#13

Operating actively even when under stress. And still, the drivers responded well.

GigiCakes

11-23-2025, 12:40 PM #13

Operating actively even when under stress. And still, the drivers responded well.

iiNyanRainbows
Junior Member

11-24-2025, 08:04 AM

#14

As TofuHaroto mentioned, start by checking the drivers and assess your drive's health. Look for bad sectors—power surges might have harmed the drive or corrupted data.

iiNyanRainbows

11-24-2025, 08:04 AM #14

As TofuHaroto mentioned, start by checking the drivers and assess your drive's health. Look for bad sectors—power surges might have harmed the drive or corrupted data.

lTalonzl
Member

147

11-24-2025, 09:38 AM

#15

I checked the drivers, everything seems fine with 100 health. I’m now updating the drivers and will let you know once it’s complete.

lTalonzl

11-24-2025, 09:38 AM #15

I checked the drivers, everything seems fine with 100 health. I’m now updating the drivers and will let you know once it’s complete.

captainben05
Junior Member

11-24-2025, 10:35 PM

#16

During the installation of new GPU drives, an issue occurred on Tuesday, July 28, 2020 at 17:13:20. Your computer stopped working or a problem was logged with a crash dump file located at C:\Windows\Minidump\072820-7906-01.dmp. This likely resulted from the ntoskrnl.exe process (nt+0x1C23A0) encountering a bugcheck code 0x1CE. The error message indicated a CUSTOM_ERROR file at C:\Windows\system32. Further investigation suggested another driver might be responsible, though its exact identity remains unclear. On the same date and time, a crash occurred in the Windows kernel, possibly linked to ndis.sys (ndis!NdisAcquireReadWriteLock+0x261) with the same error code. System configuration may also play a role in this situation.

captainben05

11-24-2025, 10:35 PM #16

ItsSpanky
Member

176

12-09-2025, 03:39 PM

#17

I mentioned saving crucial information and restoring Windows.

ItsSpanky

12-09-2025, 03:39 PM #17

I mentioned saving crucial information and restoring Windows.

MarkizCraft
Member

12-10-2025, 01:20 PM

#18

The issue isn't with the CPU. I'm sure I'll reinstall Windows.

MarkizCraft

12-10-2025, 01:20 PM #18

The issue isn't with the CPU. I'm sure I'll reinstall Windows.

Raze_FR
Member

200

12-11-2025, 06:16 AM

#19

A simple option is to reinstall Windows if feasible. Changing the board shouldn't lead to window issues, though it might occasionally happen. You could test it on another operating system, especially with the GPU considered.

Raze_FR

12-11-2025, 06:16 AM #19

Eva52044
Junior Member

12-13-2025, 08:06 PM

#20

I used it a few days back on a friend's PC, it displayed errors and froze during the Windows logo load. It functions normally now, but I'm unsure what to do next—will I reinstall Windows or investigate further?

Eva52044

12-13-2025, 08:06 PM #20

Pages (3): Previous 1 2 3 Next