BSOD on Startup of PC SYSTEM_SERVICE_EXCEPTION and NTFS.sys

[Arc]

BugCheck 24, {1904fb, fffff88008cf88f8, fffff88008cf8150, fffff80002c968d0}

[COLOR=Red]Probably caused by : memory_corruption [/COLOR]( nt!MmCheckCachedPageStates+560 )

Followup: MachineOwner
---------

Can you follow the post #17 now?

 

[cav]

BugCheck 24, {1904fb, fffff88008cf88f8, fffff88008cf8150, fffff80002c968d0}

[COLOR=Red]Probably caused by : memory_corruption [/COLOR]( nt!MmCheckCachedPageStates+560 )

Followup: MachineOwner
---------

Can you follow the post #17 now?

kk will be running memtest86+ tonight for at least 8 passes/24 hours whatever comes first

 

[cav]

BugCheck 24, {1904fb, fffff88008cf88f8, fffff88008cf8150, fffff80002c968d0}

[COLOR=Red]Probably caused by : memory_corruption [/COLOR]( nt!MmCheckCachedPageStates+560 )

Followup: MachineOwner
---------

Can you follow the post #17 now?

kk will be running memtest86+ tonight for at least 8 passes/24 hours whatever comes first

Just finished witht he Memtest86+ test. I ran it for 21 hours and 11 passes. I got NO errors.

Should I move on to driver verifier? Although I have a question about Driver Verifier. The last time I ran it, my pc did not BSOD within 24 hours at all. If I repeat the test, should I be home during those 24 hours just in case? I have my PC set to not reboot after a BSOD, I dont know if that would complicate things like for example, if I have multiple driver issues and my pc cant BSOD again because its stuck on the BSOD screen of the first BSOD (kinda hard to explain what i'm asking sorry :huh.

 

[Arc]

Try Driver Verifier one more time. While DV is on, try to replicate the crash .... perform the most crash prone actions like gaming, data streaming etc. See how it takes the pressure.

 

[cav]

BugCheck 24, {1904fb, fffff88008cf88f8, fffff88008cf8150, fffff80002c968d0}

[COLOR=Red]Probably caused by : memory_corruption [/COLOR]( nt!MmCheckCachedPageStates+560 )

Followup: MachineOwner
---------

Can you follow the post #17 now?

kk will be running memtest86+ tonight for at least 8 passes/24 hours whatever comes first

Try Driver Verifier one more time. While DV is on, try to replicate the crash .... perform the most crash prone actions like gaming, data streaming etc. See how it takes the pressure.

Im currently running driver verifier right now (for around 9 hours currently), however I noticed that dump_diskdump.sys and rtkvhd64.sys never loaded when i looked at the status of the verifier. Is this normal?

 

[Arc]

Im currently running driver verifier right now (for around 9 hours currently), however I noticed that dump_diskdump.sys and rtkvhd64.sys never loaded when i looked at the status of the verifier. Is this normal?

The first one should not be loaded. Andif the second one is out of DV's scope, IMHO it will not be very bad. So dont worry.

But if DV did not cause a BSOD within first 9 hours, there is a very little cahnce that will will cause a BSOD later. Still observe, and try to perform the most crash prone actions there so that the BSOD can be replicated.

 

[cav]

Im currently running driver verifier right now (for around 9 hours currently), however I noticed that dump_diskdump.sys and rtkvhd64.sys never loaded when i looked at the status of the verifier. Is this normal?

The first one should not be loaded. Andif the second one is out of DV's scope, IMHO it will not be very bad. So dont worry.

But if DV did not cause a BSOD within first 9 hours, there is a very little cahnce that will will cause a BSOD later. Still observe, and try to perform the most crash prone actions there so that the BSOD can be replicated.

I actually just finished the DV test just to round out the 24 hours. Got no BSODs like you said. I'll try the test the next time I BSOD. It's really weird how this issue comes and goes

 

[Arc]

In the mean time, take a disc check as it is also included in the scope of a stop 0x24. Try Seatools, take both the short generic and the long generic tests.

Let us know the results.

 

[cav]

In the mean time, take a disc check as it is also included in the scope of a stop 0x24. Try Seatools, take both the short generic and the long generic tests.

Let us know the results.

So I got another BSOD today. Here are the files using SF Diagnostic.

I ran a Disk Check on my SSD and got no errors after it was done (It finished kinda quickly and went straight to desktop, it didn't tell me anything afterwards is this supposed to happen?)

I then downloaded and ran SeaTools (although it took me a few tries because it kept crashing). I ran a long test on my primary SSD and it passed.

 

[Arc]

Please make it sure that your DDS is having the latest updated firmware.

• Crucial SSD Firmware Updates
• How to Upgrade Crucial SSD Firmware | StorageReview.com - Storage Reviews

 

[cav]

Please make it sure that your DDS is having the latest updated firmware.

• Crucial SSD Firmware Updates
• How to Upgrade Crucial SSD Firmware | StorageReview.com - Storage Reviews

I currently have a Crucial MX100 and there are no available firmware updates for it (mine is currently at MU01)

 

[Arc]

I currently have a Crucial MX100 and there are no available firmware updates for it (mine is currently at MU01)

That's good.

Do one more thing, let us see a screenshot of all your discs using Crystaldiscinfo.
CrystalDiskInfo - Software - Crystal Dew World

Also, report us for any further BSOD.

 

[cav]

I currently have a Crucial MX100 and there are no available firmware updates for it (mine is currently at MU01)

That's good.

Do one more thing, let us see a screenshot of all your discs using Crystaldiscinfo.
CrystalDiskInfo - Software - Crystal Dew World

Also, report us for any further BSOD.

Here you go

 

[Arc]

It also looks good.

One more thing ... dont let the SSD to sleep. Follow http://www.sevenforums.com/tutorials/778-power-plan-settings-change.html. At point 5 (B), you will get the way to set the Disc sleep time to Zero or Never.

Let us know how the computer is running after doing it.

 

[cav]

Shocking. Another BSOD on Startup. Do you think this issue is hardware related or driver related (maybe i didnt install all the drivers I needed to on accident, I have no idea)? This issue is so turbulent in when it occurs and I find that to be extremely strange.

 

[Arc]

Two more BSODs are there. Both reports some sort of NTFS issue.

BugCheck 24, {1904fb, fffff88009cf8bb8, fffff88009cf8410, fffff880012fa6c7}

Probably caused by : Ntfs.sys ( Ntfs!NtfsFindPrefixHashEntry+1fe )

Followup: MachineOwner
---------

It would be good to see how it goes when windows is installed on the HDD and the SSD with an unknown health status is not connected.

 

[cav]

Two more BSODs are there. Both reports some sort of NTFS issue.

BugCheck 24, {1904fb, fffff88009cf8bb8, fffff88009cf8410, fffff880012fa6c7}

Probably caused by : Ntfs.sys ( Ntfs!NtfsFindPrefixHashEntry+1fe )

Followup: MachineOwner
---------

It would be good to see how it goes when windows is installed on the HDD and the SSD with an unknown health status is not connected.

I already had windows installed on the hdd at one point and it yielded the same issue. its too much of a hassle for me right now to put it on my hdd again. Though I have a question. I'm only really using my HDD for storage and Im assuming that it has an issue since my SSD is brand new. Even if the HDD is only for storage and the SSD is the one actually running the OS, would the HDD's issues still cause a problem even if its not the drive running windows?

 

[Arc]

would the HDD's issues still cause a problem even if its not the drive running windows?

Multiple problematic storage drive is possible, if you are very unlucky.

Otherwise, some other thing is throwing the issue, say a failing SATA port as an example.

But, till now I dont have anything based on which I can point it to anything other than the primary storage, that is the SSD, with an unknown health status.

If I had a crash report with the HDD as the primary storage, there would have been more room to think on, but not right now.