Windows 10: BSOD Errors Driver/RAM Related?

Hello folks,I've been getting near-constant BSOD errors since I upgraded my system about one month ago. I upgraded my mobo and RAM to a B550 Tomahawk and 4x8GB kit of Corsair LPX and whenever my system comes under load I can expect a BSOD error. Most of my stopcodes indicate driver or RAM-related errors; I don't believe it's a hardware issue at the present moment, but Windows doesn't indicate that any of my drivers are problematic in device manager. I'm hoping that someone here might be able to help me resolve this so I can get back to using my system normally. I

:)

 

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:

 

BSOD errors that are driver related

Hi, I'm getting tons of BSOD errors that I believe are driver related, but cannot find out which driver(s) are causing it. I have done a full system clean, and started from scratch, but still getting BSOD about once a day.

Attaching dump files here:

DMP

 

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.