Windows 10: Problem With BSOD on homebuilt PC

HI, I'll try to be as detailed with my problem whilst being as limited with my computer knowledge.


Essentially I've been having problems with my computer since I built it, I can't pin down what's wrong with it, but at this point I'm guessing either a memory stick or motherboard hardware error.


I've had my computer for about 6 months, specs are as follows


Mobo:Asrock Ab350M-Pro4

RAM: Team Elite DDR4 2400MHz, 8Gb


GPU: Asus Phoenix GeForce 1050ti 4GB DDR5

CPU: AMD Ryzen 2200g AM4

HDD: Western digital blue 1TB SATA3 HDD 64M WD10EZEX

Wireless Adapter: TP-Link TL-WN725N Wireless N USB nano Adapter



BSOD Error code usually states :

K-Mode Exception not handles

Attempted to write to read-only memory

and others


I've tested my memory using the memory diagnostic tool and memtest many times (probably close to 50 runs now over both) but never had a fail


I've also checked event viewer and the only consistent memory is a runtime broker error which is supposedly due to innapropriate permissions.


I can upload a .DMP file if anybody thinks it is necessary, I've never checked as I don't know how to interpret the data


Thanks in Advance everybody!



:)

 

PC reboots (no BSOD) on CPU stress

Hi fellow TPU members,

not too long ago, the box my gf's PC was transported in gave way on the stairs. Yes, you got it right, that sent a PC tumbling down a flight of steps alright.

Stuff broke. Also, stuff remained intact somehow.

I bought her a new case, new CPU cooler and we removed the floppy drive, so far so good. But the PC started crashing for no apparent reason, without a BSOD.

I tested:

• Memtest86+, left overnight, 0 errors
• Scanned the HDD for errors, nothing there
• Left FurMark burning up the GFX card and drawing some power, no problems there
• Ran Ubuntu from a Live CD doing nothing special, didn't crash
• Ran OCCT, Linpack, Prime95, all 3 caused reboots within minutes
• Oh, and I disabled "Restart on error" so I'm sure it's not a BSOD.

Now, I can still try and test something CPU intensive on Ubuntu, but my guess is the CPU didn't survive.
Before I do anything drastic like whippin' out the magic wallet and get her a new AMD quad, is there anything I didn't see?
I'm guessing the motherboard could be borkered as well, but can I check that other than replacing the CPU with a working one?
Any suggestions on which proggies I can use from an Ubuntu Live CD to stress the CPU?

 

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:

 

Weird BSOD problem


Hi Everyone,

I have a weird BSOD problem which I cannot solve for a while(it persists still after upgrade to Windows 10 from Windows 7)

The main strange thing about this is that I get BSOD only after cold boot.
So it acts like this:

1. start PC.
2. Get to Windows Logo Screen
3. BSOD
4. Restart
5. Get to menu where I can try to repair or Start NormallyIf I Choose Repair, it will fail to repair and will try to restoreIf I Choose Start Normally, it will start OK, no BSOD, can work normally, games, browse internet, everything is normal.6. Shutdown PC
7. Next time when I start is all over again i.e. Go to Step 1

I have this problem for a while, so what I tried:

1. Another Windows 7
2. Another HDD
3. Only HDD connected
4. Changed RAM
5. Tried with built in GPU
6. Upgraded to Windows 10

Result is the same as above every time.

Please suggest what could be the cause.
Logs collected with DM_Log_Collector, attached.


Thank you

PS. This thread is a continuation of this one: Frequent multiple errors BSOD. Solved - Windows 7 Help Forums the only thing changed is Windows 10 now. instead of Windows 7. If that helps somehow.