Windows 10: I keep getting BSOD with different messages

Every day if not multiple times a day, I get a blue screen of death with a different message. I have gotten "IRQL_NOT_LESS_OR_EQUAL" "KMODE_EXCEPTION_NOT_HANDLED" "CLOCK_WATCHDOG_TIMEOUT" "CRITICAL PROCESS DIED" and the list goes on and on. I have tried a bunch of things such as tweaking with Bios Settings, installing updates on everything, deleting various files, changing other settings, etc. This has been going on for a few months now.I am resisting resetting my whole computer because I have a ton of important files and applications and I am unsure if I would be able to get them back, and I

:)

 

7 different BSoD

Hey guys,

I have a serious problem. I make it as short as possible:

• system runs 100 % fine with the 10.12
• updatet to Catalyst 11.1 -> BSoD
• updatet to 11.1 Hotfix -> BSoD
• rollback to 10.12 -> BSoD
• removed ALL AMD files manually, installed 10.12 -> BSoD

• Temps are fine
• no sfc /scannow errors
• no chkdsk errors
• Prime, Furmark all fine
• regardless what driver I install -> BSoD
• I did no hw changes, no OC

Here are my BSoDs I receive:

• 0x0000010e
• 0x1000007e
• 0x0000007e
• 0x0000004e
• 0x0000003b
• dxgmms1.sys
• PFN_LIST_CORRUPT

They all refer to the GPU of course ...

From now on I receive a BSoD every time I try to play a game (especially BC2 and SC II) even if I completely remove the old driver and make a clean install.
Apparently the 11.1 damaged my system irreparable.

Any advice or info would be very much appreciated *Smile

 

7 different BSoD

First off this is what I went through once I installed them 11.1 drivers . BSOD till I had to reinstall the OS .
It seems that some maybe missing the point here this STARTED for you after you installed the 11.1 drivers and then as it would seem you are getting them after a clean install of the old drivers . Correct ? If so have you wiped the HDD and did a clean install of the OS ?
If not then I would do this before thinking your cards are going out .

 

Getting BSOD 0x124 error

Ignore what everone said here.

0x124 BSOD is usually related to VCCIO (VTT), run Prime95 version 26.6 with custom sizes of 512K to 640K with 50% of your memory for at least 8 hours.

If you get a 0x124 BSOD, increase VCCIO voltage by small steps, run Prime95 again until your stable.

If you pass Prime95 512K to 640K without a BSOD, then its Vcore too low. I'd suggest running IntelBurnTest with 80% of your memory to verify stability (8 to 12 hours).

Oh, and yeah, if this problem appeared all of the sudden, the reason is CPU degradation, you can prevent it by enabling C-States or adjust your overclock to use lower voltages.