Windows 10 NTFS.SYS BSOD Loop - Unique Situation.

[kemical]

Hi,
for some reason i didn't see your post till now.. Anyhoo, so you can now, at least, run the cpu at stock?

If this is the case why not try running the Intel diagnostic again?

Something else you could try is to keep everything at stock values and then stress test first the cpu and then the gpu.

Prime95 will help with the cpu.

Furmark you can use to test the gpu.

See if either crashes/blue screens when tested. (An hour should do)

Also if you could post a dump file or two or even run the app in the sticky that would be awesome.

 

[MNDMorris]

Hi,
for some reason i didn't see your post till now.. Anyhoo, so you can now, at least, run the cpu at stock?

If this is the case why not try running the Intel diagnostic again?

Something else you could try is to keep everything at stock values and then stress test first the cpu and then the gpu.

Prime95 will help with the cpu.

Furmark you can use to test the gpu.

See if either crashes/blue screens when tested. (An hour should do)

Also if you could post a dump file or two or even run the app in the sticky that would be awesome.

Hey Kemical

I ran a CPU stress test overnight at a manual clock of 3.8ghz. Which is stock, yes. I did however, disable any boost functions in the BIOS. The CPU stress test ran for around 4 hours. Finishing around 3:30am. There was a BSOD shortly after the test, followed by two more BSODs and a corrupt BSOD minidump. I was asleep at the time, so I came to a frozen BSOD screen in the morning.

I'll have to start putting the minidumps in to a folder and upload them to here. All the minidumps seem to be pointing towards drivers, specifically GPU drivers. A friend of mine has an Intel Z270 motherboard for me to use next weekend, so I'll carry out further testing then. I should be able to swap the motherboards through and determine whether it's the CPU or the motherboard. Fingers crossed it's the motherboard because it's still under warranty and my CPU isn't, due to the delid and overclock in the past.

I'll get some info over tonight

 

[kemical]

Morning MNDMorris,

so it sounds like from what you say above that the cpu didn't bsod during testing but did so (3 times) after?

So perhaps the cpu is ok after all?

Further testing will show either way and you getting the spare moBo will be a great help.

All the minidumps seem to be pointing towards drivers, specifically GPU drivers.

You could always try older gpu drivers. The following link has all recent Nvidia gpu drivers available for download:
Videocards - NVIDIA GeForce Windows 7 | 8 | 10

I always use the DDU when changing drivers just so nothing is left of the previous driver:
Display Driver Uninstaller (DDU) V18.0.0.1 Released. - Wagnardsoft Forum

Good luck with the testing.

 

[MNDMorris]

Morning MNDMorris,

so it sounds like from what you say above that the cpu didn't bsod during testing but did so (3 times) after?

So perhaps the cpu is ok after all?

Further testing will show either way and you getting the spare moBo will be a great help.


You could always try older gpu drivers. The following link has all recent Nvidia gpu drivers available for download:
Videocards - NVIDIA GeForce Windows 7 | 8 | 10

I always use the DDU when changing drivers just so nothing is left of the previous driver:
Display Driver Uninstaller (DDU) V18.0.0.1 Released. - Wagnardsoft Forum

Good luck with the testing.

I'm honestly not sure.

I'll run a stress test on the GPU and CPU again tonight, with the software you've recommended, to see if that shows any problems.

To reiterate, any issues i've had all seem to be relating to how the CPU is being ran. For instance, underclocking the CPU with everything else on Auto allows it to boot in to Windows fine. As soon as I attempt to run stock on Auto, or overclock manually, BSOD loops and issues occur immediately.

I have no confidence in what the BSOD minidumps are reporting, with regards to GPU/Driver issues. It's been SO varied in terms of which BSOD comes after the other. The motherboard is highlighting VGA and DRAM as being issues also, which doesn't help at all. It's just a general direction.

As is stands, the CPU won't run at stock settings. That indicates either the CPU or MoBo are at fault. The difficulty I have at the moment is confirming which one of them is at fault. I'm unable to send off the MoBo on a RMA because I have zero confidence in diagnosing the fault from my side. I don't want to waste potentially a month, for MSI to bounce the MoBo back to me saying it's fine.

Extremely frustrating scenario, to say the least.

Thanks for the support the last couple of days, i'll post back some results once i've tested this evening.

 

[kemical]

To reiterate, any issues i've had all seem to be relating to how the CPU is being ran. For instance, underclocking the CPU with everything else on Auto allows it to boot in to Windows fine. As soon as I attempt to run stock on Auto, or overclock manually, BSOD loops and issues occur immediately.

Agreed, it does sound more likely that the cpu is in error. I just hope testing will bring a definite answer, good luck!

 

[MNDMorris]

Agreed, it does sound more likely that the cpu is in error. I just hope testing will bring a definite answer, good luck!

Put my CPU in to another motherboard last night. BSOD's again on stock speeds. Only seems to run stable below 3.8ghz. Not sure how the CPU is damaged and i'm unable to confirm through means of testing, which part of the CPU is actually broken. I find it crazy how it's been sat at 5ghz overclocked at 1.29vcore for 10 months and it suddenly goes. I've only been using it for light gaming sessions and general use.

It also seems like a HUGE conincidence that this occurred on installing new drivers, Windows updates and installing Black Ops 4 on the same day. Bearing in mind the BSOD started occurring whilst playing Black Ops 4. God only knows how this has happened lol

 

[kemical]

Hi,

it might be the case that this particular cpu was gonna crap out on you whether you overclcocked it or not and it's simply a case of coincidence? (and the silicon lottery of course).
Is it too late to RMA? (I know overclocking is supposed to invalidate warranties but could be worth a try? Just don't tell em lol )

 

[MNDMorris]

Hi,

it might be the case that this particular cpu was gonna crap out on you whether you overclcocked it or not and it's simply a case of coincidence? (and the silicon lottery of course).
Is it too late to RMA? (I know overclocking is supposed to invalidate warranties but could be worth a try? Just don't tell em lol )

I've delidded the CPU to replace the TIM with liquid metal! Not a chance of an RMA unfortunately...I didn't even reseal the gasket and used the MoBo CPU clamp to hold it in place. Wanted to be able to replace the liquid metal in the future.

It STILL runs at 3ghz stable, it'll do the job until 9th gen Intel comes out or Zen 2. Honestly thinking about Zen 2 though

Thanks for the last week or so. Appreciate the help.

 

[kemical]

I've delidded the CPU to replace the TIM with liquid metal! Not a chance of an RMA unfortunately...I didn't even reseal the gasket and used the MoBo CPU clamp to hold it in place. Wanted to be able to replace the liquid metal in the future.

You fiend...

Best of luck with the new build and would love to see it once it's done. We never close threads so please always feel free to drop by if only to share some pics..

 

[MNDMorris]

You fiend...

Best of luck with the new build and would love to see it once it's done. We never close threads so please always feel free to drop by if only to share some pics..

My system is pretty nice at the moment, only difference with next gen intel or AMD will be the aethestics on the motherboard. I'd like a TUFF Asus board to be honest, they look amazing! Even a Maximus or Crosshair would be sick.

 

[kemical]

I have the Crosshair Hero which is my first ASUS moBo and I really like it. I always used Gigabyte in the past as their top boards are feature rich and usually hard to beat. Now would i go back to gigabyte now I've tried the Crosshair? No chance!