BSOD on Startup of PC SYSTEM_SERVICE_EXCEPTION and NTFS.sys

Arc said:

Code:

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

Probably caused by : memory_corruption ( 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 said:

Arc said:

Code:

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

Probably caused by : memory_corruption ( 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 ).

cav said:

Arc said:

Code:

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

Probably caused by : memory_corruption ( 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

Arc said:

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 said:

cav said:

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 said:

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.