UPGRADE From INTEL to AMD and BSODs

giovany86 · Nov 17, 2019

Hello everyone.

I've upgraded my computer and now, i'm having BSODs everytimes, and randomly.

My specs are :
- i5 4690K @4.6GHz || Changed to AMD Ryzen 7 3700X @stock with LEPA AquaChanger 240
- 16Gb DDR3 1866MHz OC @2133MHz || Changed to 32Gb DDR4 3200MHz (listed compatible with the mobo)
- MSI Z97 PC Mate || Changed to MSI MPG X570 GAMING EDGE WIFI
- GTX 1080 8Go ASUS TURBO
- EVGA SuperNOVA 750W G1 80+Gold
- 2 x 2 Tb HDD
- 275Gb SSD (Crucial MX300)

I've tested everything :
- Ram test with memtest and no issue
- HDD and SSD test
- GPU test
- Power Supply test

The BSODs started literally one month after i've upgraded.

I've tried to reinstall Windows, something like 10 times, todays is the last windows install with all drivers updated.

BSODs are :
- SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
- PAGE_FAULT_IN_NON_PAGED_AREA
- KMODE_EXCEPTION_NOT_HANDLED
- SYSTEM_SERVICE_EXCEPTION
- IRQL_NOT_LESS_OR_EQUAL
- DRIVER_IRQL_NOT_LESS_OR_EQUAL

And sometimes, there is juste a fast blue screen, and then instant reboot, with no memory dump whatsoever.

The lastest bios (not beta) is installed on the motherboard, all drivers are updated and when no dll is specified on the memory dump, it just point "ntoskrnl.exe+1C14E0" :/

I've already tried "sfc /scannow" and DISM tool, but for them, nothing is wrong with my computer :/

Before that, the computer was running fine, every games were running fines, stability tests with Ryzen Master / OCCT / Prime95 are successfull, GPU Stability test are also successfull :/

Any idea / advise on how to fix it will be welcomed

paulttt · Nov 17, 2019

Have you tried running memtest?

I've had some weird and wonderful BSOD messages that was causes by Ram that decided to go faulty.

giovany86 · Nov 17, 2019

Yep, as i said, i did a memtest with Windows Memory Diagnostic Tool, tonight i think i'll let a memtest86+ run on the computer

FrankieDedo · Nov 18, 2019

Hi, i have got the same issue since a month or two now. In the beginning i started to think that it was my AMD Vega 56, flashed with Vega 64 bios, that was causing the problem, but after restoring the original vbios i got the same random BSODs as you. Same descriptions, same dump indications about "ntoskrnl.exe+1C14E0"

Based on what i've found googling around, this looks like a recent problem (at least the 1C14EO error) and i am starting to think that is linked to a Windows update of some kind, as it is the only thing that could have been changed in this months, inside my system.

My specs are those:
CPU: Ryzen 7 2700X
GPU: Vega 56, BSODs happening with and without Vega 64 bios
RAM: 32 GB G.Skill Ripjaws V 3200MHz (set to 2933 MHz)
Motherboard: Asus B450-F ROG
PSU: Mars Gaming 750W
SSD: Crucial MX500 500GB + Drevo X1 1TB
HDD: WD Red 3TB + Seagate green 2TB
Keyboard: Logitech G19 (has a mini-display so it could be factoring somehow in this)

Every driver is updated to latest versions. Some days i won't get a single BSOD and some days i get like 5-7 of them in a day. Maybe together we can find the issue!
Memtest won't bring out any errors, nor any other diagnostic i've ran.

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

giovany86 said:
Hello everyone.

My specs are :
- i5 4690K @4.6GHz || Changed to AMD Ryzen 7 3700X @stock with LEPA AquaChanger 240
- 16Gb DDR3 1866MHz OC @2133MHz || Changed to 32Gb DDR4 3200MHz (listed compatible with the mobo)
- MSI Z97 PC Mate || Changed to MSI MPG X570 GAMING EDGE WIFI
- GTX 1080 8Go ASUS TURBO
- EVGA SuperNOVA 750W G1 80+Gold
- 2 x 2 Tb HDD
- 275Gb SSD (Crucial MX300)

What RAMs do you have, exactly? And what frequency have you set in the bios? I am starting to think that it could be some problem with Ryzen's frequency management...

giovany86 · Nov 18, 2019

My rams are 2 stick of 16Gb each.
Ref : CMW32GX4M2C3200C16
They are running at 3200MHz (set Ram frequency in bios to 3200MHz), Enabling / Disabling XMP does literally nothing to BSODs :/

As you said, i'm thinking the same thing :/

Edgarska · Nov 18, 2019

Aside from the frequency, check your timings. Sometimes the mobo can screw up and apply timings meant for lower frequency into a higher frequency, which causes instability which might not be caught by memtest in a small amount of time.

giovany86 · Nov 18, 2019

I've checked all my timings, they are the same as precognized for these ram stick :/

Edgarska · Nov 18, 2019

Well, so far all your error codes seem to be linked to RAM or GPU driver issues, but windows isn't very specific about them. It would help if you had the minidumps to see which component is causing the error. Though technically any driver could be causing some of those errors, but GPU is more common. but I've had SATA drivers be at fault too.

I would recommend going through your device manager, uninstall the drivers for all the components that can work with just the default windows drivers, see if it keeps crashing.

FrankieDedo · Nov 18, 2019

Edgarska said:
Well, so far all your error codes seem to be linked to RAM or GPU driver issues, but windows isn't very specific about them. It would help if you had the minidumps to see which component is causing the error. Though technically any driver could be causing some of those errors, but GPU is more common. but I've had SATA drivers be at fault too.

I would recommend going through your device manager, uninstall the drivers for all the components that can work with just the default windows drivers, see if it keeps crashing.

If this can help both of us, i have uploaded my last five minidumps, but later i will check that RAM timings and clocks will comply to ideal settings. Yes, this could be a GPU issue, but recently i have noticed that some random page on Chrome will crash randomly as well. Yesterday, for example, a page crashed chrome. Reopening it caused a BSOD. This happened some times in the last few days, even in almost plain text pages like wikipedia and such. If it's a GPU issue, it should be related to VRAM anyway, but in that case, shouldn't be marked as a GPU driver error?

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

giovany86 said:
My rams are 2 stick of 16Gb each.
Ref : CMW32GX4M2C3200C16
They are running at 3200MHz (set Ram frequency in bios to 3200MHz), Enabling / Disabling XMP does literally nothing to BSODs :/

As you said, i'm thinking the same thing :/

I don't know 3xxx Ryzens, but mine couldn't run RAM sticks to 3200MHz, it needed a slightly lower frequency. Also XMP should be an Intel-only technology, you shouldn't even be able to enable it. If you are talking about DOCP, that is a similar solution for AMD CPUs, you should try to set to a 2866 or 2933 profile (if i remember the frequency steps correctly)

Nemi6 · Nov 18, 2019

I have the exact same problem on a Ryzen 3600 + B450 Tomahawk setup. I have an RTX2060S and am getting the exact same errors as of the last couple of weeks. Tried altering XMP profiles (which was fine for about 2 months) updating drivers etc. I have no idea what's changed. Weirdly enough I find having something like the League of Legends client open or something stops it from crashing. Apparently it might be to do with the PC going into idle? I'm gonna keep looking but thought it might help to know it's not just you.

Edgarska · Nov 18, 2019

FrankieDedo said:
If this can help both of us, i have uploaded my last five minidumps, but later i will check that RAM timings and clocks will comply to ideal settings. Yes, this could be a GPU issue, but recently i have noticed that some random page on Chrome will crash randomly as well. Yesterday, for example, a page crashed chrome. Reopening it caused a BSOD. This happened some times in the last few days, even in almost plain text pages like wikipedia and such. If it's a GPU issue, it should be related to VRAM anyway, but in that case, shouldn't be marked as a GPU driver error?

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

I don't know 3xxx Ryzens, but mine couldn't run RAM sticks to 3200MHz, it needed a slightly lower frequency. Also XMP should be an Intel-only technology, you shouldn't even be able to enable it. If you are talking about DOCP, that is a similar solution for AMD CPUs, you should try to set to a 2866 or 2933 profile (if i remember the frequency steps correctly)

Unfortunately this doesn't really tell us anything, I was hoping a specific driver would be flagged as culprit in at least one dump, but they all list just ntoskrnl.exe, which means it's a memory problem, or it could be caused by any driver. The only advice I can give is the same, try to uninstall every driver that is not necessary and use just the windows default drivers, and also double check your timings, disable any kind of automatic RAM speed features.

giovany86 · Nov 19, 2019

Well, after 2 hours of BEat Saber / Super HOT, no BSOD at all.
Before that, i tried something.

I tried to playe my sticks to A1 B1, at first my mobo was stuck on the CPU led, then i removed the B2 stick and it booted but it said that my stick wasn't in the optimized slot, i cleaned my other stick, putted it back in B1 and then it posted. Saying again that my sticks aren't in the optimized slot and recommended me to put them in A2 B2 order.
I replaced again in the A2 B2 order and then i haven't had any BSOD (for the moment).

Lexford · Nov 21, 2019

Nemi6 said:
I have the exact same problem on a Ryzen 3600 + B450 Tomahawk setup. I have an RTX2060S and am getting the exact same errors as of the last couple of weeks. Tried altering XMP profiles (which was fine for about 2 months) updating drivers etc. I have no idea what's changed. Weirdly enough I find having something like the League of Legends client open or something stops it from crashing. Apparently it might be to do with the PC going into idle? I'm gonna keep looking but thought it might help to know it's not just you.

Me too! I've been having this issue for months since building my computer in August. Ryzen 5 3600, Asrock B450 board, and a GTX 1070ti. I think the common denominator here is Ryzen, not a graphics issue. I've tried everything from switching ram slots, to only using one stick, to to changing which SATA ports my drives are connected to, to disconnecting my second drive, and reinstalling windows from a clean USB. The problem still persists, which makes me think it's a firmware issue, probably some sort of incompatibility between Ryzen and whatever RAM I'm using. I also have the same thing where crashes never occur when I'm gaming, regardless of what game I'm playing. It's only when I leave the computer idle for a time or am browsing the web on Chrome or something like that.

Is the RAM you're using on the QVL list for your mobo?

Also, any other similarities we can establish? Are you using a hard drive, SSD, or both? Antivirus?

For me, I've got windows installed on a 500 gb ssd with a 2 tb hard drive as well for additional storage, I'm using Malwarebytes, and i've got 16 gigs of Team Tforce Delta RGB 3200 mhz RAM

giovany86 · Nov 21, 2019

Yes, my rams are listed on the compatible list of my mobo, yesterday i had a BSOD when playing KSP (last update), with KSP v1.7.1 i havn't had any issue even after many hours of gaming.

Currently i'm using a 275Gb CRUCIAL MX300 SSD for Windows, and 2 2Tb HDD for my storage (Games, Documents, Etc).
No Antivirus Except Windows Defender built-in Windows 10.
Today, after 2+hours of Pavlov VR and SuperHOT, no issue at all.
I'm on the "7C37v15" bios revision from MSI's Website.

Something i've noticed, when browsing facebook, the page will randomly crash with just "oops, something went wrong", a refresh solve this but it happen sometimes.

Ergomix · Nov 23, 2019

I only had bsod on idle with my b450 tomahawk non-max and ryzen 3600. I RMA'd the mobo and cpu and they replaced the cpu. Everything works fine now with default settings. I advice you do the same. Good luck!

giovany86 · Nov 23, 2019

2 BSOD today. That's it, i'm going to email the MSI's support center to get it fixed.

giovany86 · Nov 30, 2019

New MSI Board, everything installed, fresh windows install...and BSOD again.
Tested my SSD with my i7 6700K setup, my hdd, my ram, everything is fine on the 6700K :/
Does anyone has an idea of what component should be responsible for my BSODs ?

Lexford · Nov 30, 2019

giovany86 said:
New MSI Board, everything installed, fresh windows install...and BSOD again.
Tested my SSD with my i7 6700K setup, my hdd, my ram, everything is fine on the 6700K :/
Does anyone has an idea of what component should be responsible for my BSODs ?

I would first make sure your BIOS is the latest version, and ensure that all drivers are up to date. If you're still experiencing crashes at that point, I would bet it's your RAM's fault. It may be on the motherboard QVL but just not playing nicely with Ryzen. I've got a Ryzen 5 3600 in an Asrock B450m Steel Legend, and 16 gigs of Delta T-Force RGB RAM. I went to microcenter a few days ago, bought 16 gigs of trusty Corsair Vengeance LPX, and tried that instead. I had one crash, but I think it was a random windows thing, not the same problem I was experiencing because after that I left the computer idle for ~16 hrs and it did not BSOD. What RAM are you using? Otherwise it could be a cheap powersupply crapping out on you, either too low voltage or it's old (or dusty and needs to be cleaned). But if updating the BIOS and checking all your drivers doesn't fix it, I'd peg your RAM as the culprit. I was getting a lot of the same BSODs as you, mostly PAGE_FAULT_IN_NON_PAGED_AREA, IRQL_NOT_LESS_OR_EQUAL, and DRIVER_IRQL_NOT_LESS_OR_EQUAL.

Sorry this is happening to you too, I know how infuriating it is.

giovany86 · Dec 1, 2019

Well, memtest86 said that my ram hasn't any problem.
New test, since yesterday i'm running some Prime95 tests.
All tests says the same thing :

[Sun Dec 01 21:26:58 2019]
FATAL ERROR: Rounding was 8.345872188e+011, expected less than 0.4
Hardware failure detected, consult stress.txt file.
FATAL ERROR: Rounding was 1.129761873e+018, expected less than 0.4
Hardware failure detected, consult stress.txt file.
[Sun Dec 01 14:03:40 2019]
FATAL ERROR: Rounding was 265214677.4, expected less than 0.4
Hardware failure detected, consult stress.txt file.
FATAL ERROR: Rounding was 2009.213887, expected less than 0.4
Hardware failure detected, consult stress.txt file.
[Sun Dec 01 14:17:18 2019]
FATAL ERROR: Rounding was 0.5, expected less than 0.4
Hardware failure detected, consult stress.txt file.
FATAL ERROR: Rounding was 0.4996505353, expected less than 0.4
Hardware failure detected, consult stress.txt file.
[Sun Dec 01 14:18:57 2019]
FATAL ERROR: Rounding was 0.5, expected less than 0.4
Hardware failure detected, consult stress.txt file.
FATAL ERROR: Rounding was 0.470703125, expected less than 0.4
Hardware failure detected, consult stress.txt file.
[Sun Dec 01 15:10:26 2019]
FATAL ERROR: Rounding was 0.5, expected less than 0.4
Hardware failure detected, consult stress.txt file.
[Sun Dec 01 15:12:33 2019]
FATAL ERROR: Rounding was 0.5, expected less than 0.4
Hardware failure detected, consult stress.txt file.
FATAL ERROR: Rounding was 0.5, expected less than 0.4
Hardware failure detected, consult stress.txt file.
[Sun Dec 01 15:13:27 2019]
FATAL ERROR: Rounding was 0.5, expected less than 0.4
Hardware failure detected, consult stress.txt file.
FATAL ERROR: Rounding was 0.5, expected less than 0.4
Hardware failure detected, consult stress.txt file.
[Sun Dec 01 15:14:16 2019]
FATAL ERROR: Rounding was 0.5, expected less than 0.4
Hardware failure detected, consult stress.txt file.
FATAL ERROR: Final result was 00000000, expected: 3D4F6CBB.
[Sun Dec 01 19:20:38 2019]
FATAL ERROR: Rounding was 0.4867342586, expected less than 0.4
Hardware failure detected, consult stress.txt file.
[Sun Dec 01 21:15:33 2019]
FATAL ERROR: Rounding was 0.5, expected less than 0.4
Hardware failure detected, consult stress.txt file.
FATAL ERROR: Rounding was 0.4996329275, expected less than 0.4
Hardware failure detected, consult stress.txt file.
[Sun Dec 01 21:17:17 2019]
FATAL ERROR: Rounding was 1.243106557e+011, expected less than 0.4
Hardware failure detected, consult stress.txt file.
FATAL ERROR: Rounding was 0.5, expected less than 0.4
Hardware failure detected, consult stress.txt file.
[Sun Dec 01 21:18:31 2019]
FATAL ERROR: Rounding was 0.5, expected less than 0.4

And it's always the same core, Physical Core #1 seems to be defective, even when multi-threading is disabled i have this error in Prime95, all other cores are okay :/

pcwizard7 · Dec 1, 2019

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

UPGRADE From INTEL to AMD and BSODs

Well-Known Member

Well-Known Member

Well-Known Member

Member

Well-Known Member

Conjurer of cheap tricks

Well-Known Member

Conjurer of cheap tricks

Member

Attachments

New Member

Conjurer of cheap tricks

Well-Known Member

Member

Well-Known Member

New Member

Well-Known Member

Well-Known Member

Member

Well-Known Member

Well-Known Member

Similar threads

Popular threads in this forum