BSOD during Windows Update after fresh SSD install

[n3wpv]

Hello everyone. Some background: I wanted to redo a fresh install of Windows 7 onto a Samsung 850 EVO SSD. After using DISKPART to set up the SSD the installation went flawlessly. Of note, I have the Users folder on a separate Toshiba 1TB HDD using Audit Mode instructions I found here. I installed my monitor drivers, mobo drivers, wifi adapter, webcam, HP printer drivers and Google Chrome.

I then proceeded to do the Windows Update. It updated to SP1 fine. I continued Windows Update and it was in the process of installing more critical updates when my BSOD occurred. The necessary files are attached. Thanks for taking time to review my case.

 

[n3wpv]

So I just experienced a second BSOD, also while performing Windows Update. Latest log files are attached. I've also been experiencing errors with some Windows Update files.

 

[n3wpv]

And yet a third BSOD while trying Windows Updates that keep failing.

 

[derekimo]

You have disk and/or file corruption problems,

Two of the dumps are these,

NTFS_FILE_SYSTEM (24)
    If you see NtfsExceptionFilter on the stack then the 2nd and 3rd
    parameters are the exception record and context record. Do a .cxr
    on the 3rd parameter and then kb to obtain a more informative stack
    trace.

All three are riddled with NTFS references.

Not sure if it's related to your install method or not but I would perform the following tests,

chkdsk /r

http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

Someone else might come along with more info but that's a good start.

 

[n3wpv]

You have disk and/or file corruption problems,

Two of the dumps are these,

NTFS_FILE_SYSTEM (24)
    If you see NtfsExceptionFilter on the stack then the 2nd and 3rd
    parameters are the exception record and context record. Do a .cxr
    on the 3rd parameter and then kb to obtain a more informative stack
    trace.

All three are riddled with NTFS references.

Not sure if it's related to your install method or not but I would perform the following tests,

chkdsk /r

http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

Someone else might come along with more info but that's a good start.

Can you tell which drive it is? The OS is on the SSD but the user folder is on the HDD.

 

[derekimo]

I can't myself, I would just check both to rule them out.

Someone else might be able to, I'm just pointing out the obvious stuff.

 

[n3wpv]

So I ran chkdsk on both drives. Here are the results:

SSD chkdsk results
View attachment 388111

HDD chkdsk results
View attachment 388112


I tried to run sfc /scannow but encountered another BSOD. Log files are attached. I'll try to run it again. Can you run it on a non-OS drive, meaning my HDD used for storage only?

 

[n3wpv]

Ok, so I was able to run sfc /scannow on both drives with the following results:

SSD SFC Results
View attachment 388115

HDD SFC Results
View attachment 388116

 

[derekimo]

This new one doesn't have much info but does blame memory corruption,

BugCheck 3B, {c0000005, fffff8000300d29f, fffff880078d7af0, 0}

Probably caused by : memory_corruption ( nt!MmHardFaultBytesRequired+3f )

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

This couldn't hurt to make sure your RAM is alright,

   Information

MemTest86+

Run a minimum of 8 passes, preferably overnight, or until errors occur using MemTest86+.

Use this tutorial to help you use MemTest86+:
RAM - Test with MemTest86+

 

[axe0]

I hope you don't mind me bumping in derekimo

Running memory test would be optionality, but not a necessity, both 0x3B crashes give indications of memory access violations & show file system drivers in the raw stack. Together with the 0x24 I think we should focus more on the hard drives.

N3wpv, please check your SSD for firmware updates with Samsung Magician and try to update your system. Some Windows drivers are being flagged too but I believe it is because of the missing updates.
Please check Intel for BIOS updates.

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: [COLOR="red"]00000000c0000005[/COLOR], Exception code that caused the bugcheck
Arg2: fffff80002cd8ef0, Address of the instruction which caused the bugcheck
Arg3: fffff88006387d20, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

fffff880`078d79d8  fffff880`01253000 [COLOR="red"]Ntfs[/COLOR]!RtlULongLongToULong <PERF> (Ntfs+0x0)
fffff880`078d79e0  fffff880`012be984 [COLOR="red"]Ntfs[/COLOR]!__PchSym_ <PERF> (Ntfs+0x6b984)
fffff880`078d79e8  fffff880`01052000 [COLOR="red"]fltmgr[/COLOR]!ExFreeToNPagedLookasideList <PERF> (fltmgr+0x0)
fffff880`078d79f0  fffff880`0107000c [COLOR="red"]fltmgr[/COLOR]!__PchSym_ <PERF> (fltmgr+0x1e00c)
fffff880`078d79f8  fffff880`01052000 [COLOR="red"]fltmgr[/COLOR]!ExFreeToNPagedLookasideList <PERF> (fltmgr+0x0)
fffff880`078d7a00  fffff880`01070240 [COLOR="red"]fltmgr[/COLOR]!__PchSym_ <PERF> (fltmgr+0x1e240)
fffff880`078d7a08  fffff880`01052000 [COLOR="red"]fltmgr[/COLOR]!ExFreeToNPagedLookasideList <PERF> (fltmgr+0x0)
fffff880`078d7a10  fffff880`0107120c [COLOR="Red"]fltmgr[/COLOR]!__PchSym_ <PERF> (fltmgr+0x1f20c)

fffff880`06388228  fffff880`0114e31a*** WARNING: Unable to verify timestamp for MpFilter.sys
*** ERROR: Module load completed but symbols could not be loaded for MpFilter.sys
 MpFilter+0x1031a

I'm not sure what device this event log is pointing to.

Event[1920]:
  Log Name: System
  Source: atapi
  Date: 2016-06-15T15:59:49.495
  Event ID: 11
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: SzantoFamily-PC
  Description: 
The driver detected a controller error on \Device\Ide\IdePort3.

Can you tell which drive it is?

The dumps do not indicate a specific drive, if Windows detects errors on the hard drives it can be found in the event logs.

 

[n3wpv]

I hope you don't mind me bumping in derekimo

Running memory test would be optionality, but not a necessity, both 0x3B crashes give indications of memory access violations & show file system drivers in the raw stack. Together with the 0x24 I think we should focus more on the hard drives.

N3wpv, please check your SSD for firmware updates with Samsung Magician and try to update your system. Some Windows drivers are being flagged too but I believe it is because of the missing updates.
Please check Intel for BIOS updates.

Can you tell which drive it is?

The dumps do not indicate a specific drive, if Windows detects errors on the hard drives it can be found in the event logs.

So here's an update. The BIOS and SSD are already current. Windows Update keeps failing but I'll keep trying. I ran the memory test and have the following results so far:

Stick #1 Slot 2 +errors at test #5 (I aborted the test)
Stick #1 Slot 4 +errors at test #5 (I aborted the test)
Stick #1 Slot 1 +errors at test #5 (I aborted the test)
Stick #1 Slot 3 +errors at test #5 (I aborted the test)

Stick #2 Slot 2 -errors after 10 passes
Stick #2 Slot 4 test currently in progress
Stick #2 Slot 1 test yet to be done
Stick #2 Slot 3 test yet to be done

Something interesting regarding Stick #2 is that the timings listed in the memory test (6-6-6-20) don't match what's on the label (9-9-9-24). That was not the case with Stick #1

Right now I'm going to assume the memory is bad and just replace it and go from there.

 

[axe0]

That is the difficulty with BSOD debugging, when it looks like to be a specific thing it can be something else.

 

[derekimo]

I hope you don't mind me bumping in derekimo

Not at all, I was hoping you would.