Multiple BSOD even after factory reset

Critthinker · 20 Nov 2013

This being a Dell machine, you could try running the built in diagnostics. These diagnostics are found in the one-boot menu and might find a failed hard drive. The minidump that I looked at was having issues with NTFS so I would verify that the HDD is still good before checking software. The hardware test takes about 15min to run.

Tap f12 at the Dell screen to get to the one-time boot menu and select diagnostics near the bottom of the screen. If it still under warranty then you should be able to call and get a hard drive shipped out next business-day.

*edit*
So I looked over the rest of them and found references to a McAfee driver as well. I think the hardware diagnostics are still a good idea though...

x BlueRobot · 22 Nov 2013

Code:

BugCheck 24, {3a0000, 0, 69448d0, fffff8a00b8d7930}

Probably caused by : Ntfs.sys ( Ntfs!NtfsAcquirePagingResourceExclusive+5e )

Code:

1: kd> k
 # Child-SP          RetAddr           Call Site
00 fffff880`060da478 fffff880`01465f2e nt!KeBugCheckEx
01 fffff880`060da480 fffff880`014d7374 Ntfs!NtfsAcquirePagingResourceExclusive+0x5e
02 fffff880`060da4c0 fffff880`0147a5df Ntfs!NtfsFlushVolume+0x154
03 fffff880`060da5f0 fffff880`01467c7f Ntfs!NtfsVolumeDasdIo+0x1d3
04 fffff880`060da6a0 fffff880`01469478 Ntfs!NtfsCommonRead+0x5bf
05 fffff880`060da810 fffff880`012c5bcf Ntfs!NtfsFsdRead+0x1b8
06 fffff880`060da8c0 fffff880`012c46df fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x24f
07 fffff880`060da950 fffff880`012c46af fltmgr!FltpDispatch+0xcf
08 fffff880`060da9b0 fffff800`02fe417b fltmgr!FltpDispatch+0x9f
09 fffff880`060daa10 fffff800`02fc3e53 nt!IopSynchronousServiceTail+0xfb
0a fffff880`060daa80 fffff800`02cd9e53 nt!NtReadFile+0x631
0b fffff880`060dab70 00000000`77c9131a nt!KiSystemServiceCopyEnd+0x13
0c 00000000`047ac338 00000000`00000000 0x77c9131a

Ntfs!NtfsFlushVolume is undocumentated within the WDK, however, I believe it may be part of some cache flushing. During this process, the Volume Control Block has to be locked, I'm assuming this is the reason for the above function call: Ntfs!NtfsAcquirePagingResourceExclusive, the file system is trying to obtain a Resource (synchronization mechanism) which is Exclusive, this acts like a standard Mutex.

In a other bugcheck, your Intel graphics driver seems to be very outdated, and potentially causing problems. Please update the driver from here: Intel® Driver Update Utility

Code:

0: kd> lmvm igdkmd64

start             end                 module name
fffff880`04ab5000 fffff880`051bc400   igdkmd64 T (no symbols)           
    Loaded symbol image file: igdkmd64.sys
    Image path: \SystemRoot\system32\DRIVERS\igdkmd64.sys
    Image name: igdkmd64.sys
    Timestamp:        Wed Sep 02 19:54:15 2009 (4A9EBF57)
    CheckSum:         00710FEA
    ImageSize:        00707400
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4