Windows 10: Nt_wrong_symbols related BSODs.

I have been having issues with WIFI related BSODs for a while now and after receiving a slightly different model from the manufacturer, am getting a different cause of the issue.


Attached is a link to one of the crash dumps:

https://1drv.ms/u/s!Au_wXx6AhDbAdxl7YQfD_jxKjQ8?e=sGpfbR


I would be grateful for any help/solutions to the problem.

:)

 

BSOD- atikmpag.sys

This is most likely due to an installation/upgrade error with ATI driver's. I suggest doing DriveSweeper and the following:

• Drivesweeper all drivers & in Safe Mode
• Unistall all drivers that aren't used in DriveSweeper (CCC Profiler Updates, MSI AfterBurner, anything related to ATI that use's it's drivers.)
• After you do this, the first thing you need to do is go into Device Manager and Unistall your ATI Drivers

Once your done, restart the PC and then try installing the latest drivers.


I had several issues with this in the past, but I overcame it with logical reasoning and whenever I have a driver issue, I just use these steps and I always overcome the problem.

Best of luck! *Toast :toast:

 

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.

 

Blue Screen Problems

How long did you let memtest run for? I would let it run overnight. Did you try running something like Intel Burn Test? It sounds like you took the steps I would suggest. I had that same motherboard (and E8400) and when I had that BSOD it was always memory related.