BSOD's ntfs.sys and ntoskrnl.exe

[Robwan]

Hello all.

Ok so unfortunately I only have one of the two minidump files available from the last two BSOD's I've had. I have the one from about a month ago because I saved it to my USB stick, however I had another BSOD last night, which created a new dumpfile as expected, but today it's now gone....maybe it was running ccleaner after the BSOD.

Anyway, none the less I will supply you with as much info as I can including the info in the dmp file from month ago.

---------------------------------------------------------------------------------------------------------

1st BSOD happened about a month ago. I ran bluescreenview-x64 and it pointed to ntoskrnl.exe being the issue (but you can see this with the files I included) I ran the diagnostic today using SF_Diagnostic_Tool by taking the old dmp file from my usb and placing to the \windows\minidump, therefore I have renamed the folder to correspond with the date when it happened but of course other settings will be relevant to today.

Nature of BSOD = Computer had been idol then suddenly turned off and rebooted only to be greeted with a message stating an unexpected shutdown. The computer is set to sleep after an hour and this may have been around the time when it was meant to sleep. But since the crash it has gone to sleep many times ok.

My first suspicion was any software or changes I had made to the computer in last few days, so I made a system restore as far back as I could, which was probably about a week.

I also used seagete HDD tools to check the health of my HDD and everything stated fine.


Everything ran fine from there up until last night when same thing happened again in very similar way, but different error this time.


2nd BSOD. I am missing the dmp file for this one now, but I did run bluescreenview-x64 after it happened and it pointed to ntfs.sys being the issue.

Nature of BSOD = Verymuch the same as 1st BSOD, computer had been idol for about and hour, then shutdown unexpectedly and greeted me with crash message upon restarting to desktop.

I have not done a system restore this time, but I have now unistalled java as It it the only change I have made in last few days.

-------------------------------------------------------------------------------------------------

I should also note even though I am sure it is not the cause:
I have a custom start orb so I'm pretty sure I patched the system for third party themes (but I've had this for years)

When the bsod happened last night I had My usb sticked connected, xbox 360 wireless receiver and a wacom tablet


-------------------------------------------------------------------------------------------------

What would you all suggest my next steps are? It may never happen again, but I am thinking memory test and of course backup.

Thank you in advance for any help

 

[Arc]

Hi Robwan.

Depending on the crash dump, it appears to be some sort of memory malfunction. Either the RAM is failing or any driver is passing some bad info to the memory.

Test your RAM modules for possible errors.

How to Test and Diagnose RAM Issues with Memtest86+
​

Run memtest86+ for at least 8 consecutive passes.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

If it does not show any error, enable Driver Verifier to monitor the drivers.

Driver Verifier - Enable and Disable
​

Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

   Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

   Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

   Tip

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any.
_____________________________________________

BugCheck 1A, {5003, fffff780c0000000, 4dee, 4df00000bbdc}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+29aa9 )

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

4: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

[COLOR=Red]MEMORY_MANAGEMENT (1a)[/COLOR]
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000005003, The subtype of the bugcheck.
Arg2: fffff780c0000000
Arg3: 0000000000004dee
Arg4: 00004df00000bbdc

 

[Robwan]

Thanks for you reply, Just downloaded memtest and will run when I have get a chance. So far ever since posting it has not done it again, but then I haven't left the computer idle for more than an hour which has been the pattern the last two times it crashed. But that could just be coincidence.

I did however defrag as the HDD was 11% fragmented.

How long can I expect the memory test to take roughly if I do 8 consectutive passes and I have 6gb ddr3 tri channel ram?

Thanks again

p.s I would give you rep but I can't as I 'need to spread more rep around first' :/

 

[Arc]

For 6 GB RAM, memtest86+ may take nearly 6-7 hours. Better you leave it overnight with memtest86+ running.