Solved BDOS when Idle - ntfs.sys and ntoskrnl.exe

[SganskeKRME]

We're experiencing intermittent BSODs on our SQL and document server.

Diagnostics attached.

I ran SeaTools on the HDD's and shows fine. First couple of passes on memtest 86+ were fine.

In over my head at this point. That's what I get for being the most tech savvy attorney in the office.

-SKG

Build Notes:

Win 7 Pro 64 bit
Intel Core i7-4770 Processor
Gigabyte GA-Z87-D3HP Z87 Motherboard
Patriot Viper Xtreme 4GB DDR3 times 4
Seagate Barracuda 1TB Hard Drive - 7200RPM, 64MB, SATA 6Gb/s - ST1000DM003 times 2 in raid 0

 

[Arc]

Hi SganskeKRME.

Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.

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 24, {1904fb, fffff880039ef758, fffff880039eefb0, fffff8800172c371}

Probably caused by : Ntfs.sys ( Ntfs+124371 )

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

BugCheck 1A, {41790, fffffa8001781880, ffff, 0}

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

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

RAID
​

 

[SganskeKRME]

It was the memory. Did 10 passes with Memtest but no bad sectors. We needed to server up and running asap, so we opted to install new memory prior to any further diagnostic testing. Took care of the problem. Thanks for you help.

 

[Arc]

Its OK.