UPGRADE From INTEL to AMD and BSODs

[Lexford]

Update: Getting BSOD's again even with new RAM...I'm at a loss. Best shot is to RMA the mobo and/or CPU if they'll let me.

 

[pcwizard7]

do a clean install before u call in the hardware warranty

 

[giovany86]

I would uninstall any intel drivers and install the latest AMD chipset, driver. else a clean install might be the only way

It's my 15th fresh install of Windows x)
So there are no Intel drivers and all my drivers are updated and also my bios is updated.

 

[Lexford]

Yeah a fresh install of windows won't do it, I had the same problem. Some things I will be trying and advise you to do the same:

• Obviously if you haven't already, make sure all drivers are up to date.
• Your chipset and mobo drivers are all on the motherboard website under the support tab. I'd put the link here but I can't since I'm a new user :/
• Next, check dumb stuff. Make sure RAM is seated properly. Power supply cables are plugged in properly in the PSU and on the MOBO. It's trivial, but worth a shot.
• Familiarize yourself with event viewer. See if the Kernel reported anything pointing to a specific program causing the issues. I found some in mine that mentioned Malwarebytes, so I uninstalled it last night. Time will tell if that helps.
• If this doesn't work, try using an older bios version perhaps, the oldest one that will support your processor. Perhaps a BIOS update broke something and that's why you're encountering the issue.
• If all else fails, I was looking through reddit threads of people with similar issues (same BSOD stop codes caused by ntoskrnl.exe), and they were able to fix it by replacing the CPU. They RMA'd the cpu's and AMD found them to be faulty. I even found one where someone with an intel cpu was having this issue.

Good luck buddy. If it's any consolation, I am also crying and ripping my hair out with this. On the plus side, I am now really good at troubleshooting BSODs.

 

[Lexford]

Update: I think I fixed it?

I was messing around with my RAM's timings and found that the CAS Latency was off by 1 clock from whats recommended on the RAM stick. I changed it in the BIOS to the proper setting, and its been stable ever since. I had a meeting to go and left it running for an hour and a half with no crash. I'll let it run overnight tonight and see what happens and post back here.

 

[Lexford]

Yep, just left it running overnight, no crashes. The problem was that, even though the XMP profile had the proper timings, the first one, CAS Latency, was supposed to be at 15. For whatever reason, a setting in the DRAM timings called Geardown was enabled, which prevented the CAS latency from going below 16. I disabled Geardown, the CAS latency was set correctly, and it fixed the problem. Good luck, let me know how it goes. If you're unfamiliar with ram timings, this tech quickie video will help:

 

[Lexford]

Uhm. So. Crashes started happening again. I'm at a loss.

 

[Koinov]

Dunno if anyone will read it, but it seems that problem is in AGESA, the most stable version is 1.0.0.3ab, 1.0.0.3abba and 1.0.0.4b are shitty and causing BSOD. Downgraded my mobo to 1.0.0.3ab and haven`t seen bsod for 10 hours straight. Just donwgrade your bios. I have asus strix x-370 gaming and I downgraded from 5220 to 5204. Hope that will help you guys

 

[giovany86]

My CPU is currently going to AMD Support Center in Netherland. Before that i tried every single bios update for my mobo, on every ones i had bsods :/ Currently i'm just waiting for it to arrive at their support center :/

 

[Captain_N]

Nevermind.

 

[urherenow]

This, folks, is why switching from Intel to AMD is never an "upgrade". I used to be a die-hard AMD fan. ALWAYS get more bang for your buck. But at the end of the day, you get what you pay for. Since making enough money to afford Intel instead of AMD, I've never looked back. It may cost more, but the performance is just better...

 

[YOUCANTSTOPME]

I know you said you did a PSU test but I would do some further testing. Just because it powers on your PC does not mean it is OK.

From my experience, power supplies are often one of the main culprits.

--------------------- MERGED ---------------------------

This, folks, is why switching from Intel to AMD is never an "upgrade".

lol. Except we don't know if that's the reason.

 

[giovany86]

Well, after receiving the new CPU from AMD Support Center, everything works fine and no more issue at all without having to reinstall windows (i already did some fresh install with the defective CPU) so, the problem was from the CPU which was defective (one core malfunctionning).

 

[SirGouki]

EDIT: This post was made before I realized there was a second page. I have not removed the original content because the definitions are not untrue.

- PAGE_FAULT_IN_NON_PAGED_AREA

This literally means your page file wasn't big enough to dump your RAM to at the time it tried to, which triggered the blue screen. It should be between 1.5x and 4x your RAM. I usually set mine to 2x and have never had any problems. Its the page file equivalent to the "Memory access violation at (some hex address) memory not readable/writable". In other words, Windows tried to put something from your ram on to the Hard drive in a place that was not reserved for it.

- SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
- SYSTEM_SERVICE_EXCEPTION

These are similar to each other: An important system operation failed, and Microsoft has not written a custom message to handle that failure. They could literally caused by anything.
KMODE_EXCEPTION_NOT_HANDLED is way more major, but is a similar thing. Can be caused by anything that would cause the Kernel to fail (such as suddenly switching from Intel to AMD, the instruction set changes are subtle but large enough to cause issues: Windows Vista had a bricking update to it for all AMD processors simply because Microsoft only made it on an Intel instruction set and never ported it to the AMD set, but released it to all platforms running Vista.)

The last 2 are driver related. Either the drivers are bad, or the hardware they are referencing is bad in some way. There should have been hex codes with most, if not all, of these blue screens that tell you exactly where to look for the problem (usually in sets of 3 hex codes). Without those, the best anyone can do is spitball and hope it sticks. And with Windows 10, you can not simply "reinstall". You have to completely wipe the installed partition, reset it up, and install Windows 10 fresh when trouble shooting problems from something major like switching processors that have different instruction sets (Yes AMD is Intel BASED, it is NOT 100% Intel instruction sets, that's what based means, they made some changes.) EDIT: Which I see by your last post you're saying you did a fresh install. Your IRQ related Bluescreens were hints towards needing the RMA for future reference at this point.

 

[giovany86]

Hello, in the end, after multiple test on the CPU, it appeared that it was defective, i sent it to AMD Support Center and they told me that my CPU was defective and they sent me a new one. Since i have the new CPU i haven't had any issue at all ans my computer is the most stable computer i ever had x) Thanks for all te informations