Windows 10: My System is getting a nasty BSOD prepare for trouble and make it double

Hello Microsoft community, My lovely computer has been getting the random bluescreen on and off for years. I've always found it manageable and even used some preventive measures to stop a couple. BUT my nemesis "SYSTEM_SERVICE_EXECEPTION" I'll further refer to this as "SSE" is back and more prominent then ever this time he's even brought a friend "ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY" the one other time I mention this its called "AEM". I've been fighting "SSE" for quite a long time, I thought by now we could settle our differences over some tea but now he's starting a syndicate again

:)

 

HD4850 atikmdag.sys stopped responding - BSOD

well thats the very first step in trouble shooting BSODs, its obvious your system cant handle the overclock.

 

BAD_POOL_HEADER BSOD, Dump File attached


Hi Groggubus,

Welcome to the 10forums

Please remove / disable items from the startup in taskmanager
These programs could interfere with the boot process giving you trouble and increase the boot time.

Daemon tools, Alcohol 120% and Power Archiver Pro uses SCSI Pass Through Direct (SPTD), which is a well known cause for BSOD's.
Please remove Daemon Tools and run the SPTD pass through remover.

1. Uninstall Daemon Tools
2. Download the SPTD standalone installer and follow these steps:
   • Double click the executable to open it
   • Click on the button shown below

If the button is grayed out, like in the image, there is no more SPTD installation on your system, and you can close the window

Please follow this suggestion for the BSOD

1. Please open BitDefender and go to the modules,
2. Go to the firewall settings,
3. Uncheck 'Block port scans in the network',
4. Reboot your system <-- IMPORTANT

 

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.