BSOD during windows update

Hi John :) .

The bugcheck seem to suggest a HDD hardware error, this could also mean
that the SATA data and power are not seated very well.
Start by opening up the PC and reseating the cables on both ends making sure there
aren't any obstructions most commonly dust.

Then test the drive for physical errors because trying to troubleshoot
failing hardware is not going to get us anywhere.

A question do you have all your data backed up?
Please answer before commencing with the steps below.

   Warning

The Following Method Should NOT Be Performed On An SSD!

Testing the HDD:

1. Perform a Disk Check | Disk Check - Use the /r switch, Follow OPTION TWO - command prompt at startup.
2. Then Post the results following | THIS METHOD
3. Download SeaTools for DOS if you don't want to use a CD to test the HDD you can use YUMI – Multiboot USB Creator to create a bootable USB (instructions are found at the bottom of both pages).
4. If SeaTools for Windows is unable to recognize your HDD visit HDDdiag and follow the instructions.

If SeaTools For DOS does not recognize the drive;
Boot into the BIOS using the *Fxkey.
Look for an entry called SATA Mode (or something similar), it should be set to IDE / AHCI.
It's probably set to AHCI which is why SeaTools doesn't recognize them in the DOS environment.
Set it to IDE then save and exit usually by pressing the F10 key.
Now boot into SeaTools and it should detect the drives.
Start the Long Test and let it run.
Upon completion don't try to boot into Windows as it will only result in a BSOD, go back into the BIOS
and change the SATA setting back to what it was in the first place.

• *Popular BIOS access keys.

If the HDD checks out to be in working condition check to see if Windows managed to create
any restore point despite the OS being so young.


Again follow option two;

• System Restore

As for the bugchecks, the one you woke up and saw is empty meaning it didn't pass the check-sum
so the it wasn't flushed to disk.
The second one is to be expected with regards to your description of the events.

Code:

BugCheck 1000007E, {ffffffffc0000006, fffff800028ac047, fffff880079cd828, fffff880079cd080}

Probably caused by : hardware_disk

Code:

Usual causes:  Insufficient disk space, Device driver, Video card, BIOS, Break point with no debugger attached, Hardware incompatibility, Faulty system service, Memory.

Code:

EXCEPTION_RECORD:  fffff880079cd828 -- (.exr 0xfffff880079cd828)
ExceptionAddress: fffff800028ac047 (nt!RtlImageNtHeaderEx+0x000000000000003f)
   ExceptionCode: c0000006 (In-page I/O error)
  ExceptionFlags: 00000000
NumberParameters: 3
   Parameter[0]: 0000000000000000
   Parameter[1]: 0000000000040000
   Parameter[2]: 00000000c0000185
Inpage operation failed at 0000000000040000, due to I/O error 00000000c0000185

By looking at the stack we can see the a start of a thread, then we're trying to verify
the boot drivers then paging them in is where it failed to do so.

Code:

               rsp : 0xfffff880079cda68 : 0xfffff800028ac0d2 : nt!RtlImageNtHeader+0x1e
0xfffff880079cda68 : 0xfffff800028ac0d2 : nt!RtlImageNtHeader+0x1e
0xfffff880079cda80 : 0xfffff880079cda98 : 0xfffff88000c16bb3 : CI!I_PEVerifyBootDrivers+0x2f3
0xfffff880079cda98 : 0xfffff88000c16bb3 : CI!I_PEVerifyBootDrivers+0x2f3
0xfffff880079cdc80 : 0xfffff80002a44e80 : nt!KiInitialPCR+0x180
0xfffff880079cdcb8 : 0xfffff88000c05cb0 : CI!g_PERunOnce
0xfffff880079cdcc8 : 0xfffff88000c168c0 : CI!I_PEVerifyBootDrivers
0xfffff880079cdce8 : 0xfffff88000c16875 : CI!PEWorkerThread+0xad
0xfffff880079cdd20 : 0xfffff88000c167c8 : CI!PEWorkerThread
0xfffff880079cdd38 : 0xfffff80002b6f166 : nt!PspSystemThreadStartup+0x5a
0xfffff880079cdd58 : 0xfffff800028c3d87 : nt!KxSwitchKernelStackCallout+0x27
0xfffff880079cdd78 : 0xfffff800028aa486 : nt!KiStartSystemThread+0x16
0xfffff880079cdd80 : 0xfffff80002a44e80 : nt!KiInitialPCR+0x180
0xfffff880079cdd90 : 0xfffff80002a52c40 : nt!KiInitialThread
0xfffff880079cdd98 : 0xfffff88001264bf0 : Ntfs!NtfsCommonCreateCallout

Because it's a page-in operation I would look into the RAM as well.

Testing the RAM:

koolkat77 said:

Test and Diagnose RAM Issues with Memtest86+:

• RAM - Test with Memtest86+

   Tip

• Pay close attention to part 3 of the tutorial "If you have errors"
• Test the RAM with Memtest86+ for at least 7-10 passes. It may take up to 22 passes to find problems. Make sure to run it once after the system has been on for a few hours and is warm, and then also run it again when the system has been off for a few hours and is cold.

When done with the testing procedure take a picture and upload it here.

Let us know how things are going.