BSOD code f4 during sleep

[shandeleo]

My computer failed to start the first time I pushed the power button, and since, every now and then I get the above-mentioned bluescreen. I disconnect and uninistall a few things and then it starts, and keeps going for long enough to make me think I've fixed it, then it happens again. It usually happens after letting it sleep overnight.
My Setup:
asus z87-k mobo
i5 4430
Corsair xms3 2x8GB DDR3 RAM
Nvidia Quadro k-600 GPU
Samsung 840 128GB SSD (System Drive)
1TB ST1000DM003-1CH1 HD (Unknown manufacturer, but problem persisted with it disconnected and uninstalled)
Corsair HX 650 PSU
ASUS PCI-E wireless card
Logitech wireless mouse and KB

Things that seemed to work but really didn't: disconnecting and uninstalling HDD, GPU, wireless card, and mouse/keyboard (I really thought the mouse was the problem, since changing it seemed to work for a couple of weeks), Updating all drivers though device manager. Re-seating switching RAM slots, changing SATA ports for HDs.

I don't know if it's the problem, but DriverHub says that two drivers are out of date ( Intel 82801 PCI Bridge - 244E, Intel 8 Series/C220 Chipset Family SATA AHCI Controller) But the Windows and Intel update utilities said that those things were up to date, and I couldn't find newer ones manually. Everything else is up to date as far as I can tell.
Enclosed are the last few minidumps. Anyone with help or advice may feel free to talk down to me, 'cause I really don't know what I'm doing
ntoskrnl.exe" and address "ntoskrnl.exe+75b80"
Parameter 1 00000000`00000003
Parameter 2 fffffa80`0e5ebb30
Parameter 3 fffffa80`0e5ebe10
Parameter 4 fffff800`031d40d0.) Thanks.

 

[x BlueRobot]

Please follow - http://www.sevenforums.com/bsod-help-support/96879-blue-screen-death-bsod-posting-instructions.html

 

[shandeleo]

Enclosed are my dump files using the posting instructions

 

[x BlueRobot]

[COLOR=Red]BugCheck F4[/COLOR], {[COLOR=Blue]3[/COLOR], [COLOR=SeaGreen]fffffa800ff40b30[/COLOR], fffffa800ff40e10, fffff800033800d0}

----- ETW minidump data unavailable-----
Probably caused by : wininit.exe

2: kd> [COLOR=SeaGreen]!process fffffa800ff40b30 3[/COLOR]
GetPointerFromAddress: unable to read from fffff800032b1000
PROCESS fffffa800ff40b30
    SessionId: none  Cid: 0230    Peb: 7fffffd4000  ParentCid: 0194
    DirBase: 3b7155000  ObjectTable: fffff8a000e5c1c0  HandleCount: <Data Not Accessible>
    Image: wininit.exe
    VadRoot fffffa800ff409c0 Vads 66 Clone 0 Private 484. Modified 326. Locked 2.
    DeviceMap fffff8a000008c10
    Token                             fffff8a000df5060
    ReadMemory error: Cannot get nt!KeMaximumIncrement value.
fffff78000000000: Unable to get shared data
    ElapsedTime                       00:00:00.000
    UserTime                          00:00:00.000
    KernelTime                        00:00:00.000
    QuotaPoolUsage[PagedPool]         103848
    QuotaPoolUsage[NonPagedPool]      10712
    Working Set Sizes (now,min,max)  ([COLOR=Red]312[/COLOR], 50, [COLOR=Red]345[/COLOR]) (1248KB, 200KB, 1380KB)
    PeakWorkingSetSize                1175
    VirtualSize                       49 Mb
    PeakVirtualSize                   52 Mb
    PageFaultCount                    1703
    MemoryPriority                    BACKGROUND
    BasePriority                      13
    CommitCharge                      599

There doesn't appear to be any problems related to your working set, however, there does seem to be problem related to paging.

[COLOR=SeaGreen]!error 0xc0000006[/COLOR]
Error code: (NTSTATUS) 0xc0000006 (3221225478) - The instruction at 0x%p referenced memory at 0x%p. The required data was not placed into memory because of an I/O error status of 0x%x.

2: kd> [COLOR=SeaGreen]!dpx[/COLOR]
Start memory scan  : 0xfffff8800d46ce38 ($csp)
End memory scan    : 0xfffff8800d46e000 (Stack Base)

               rax : 0xfffff8800d46cec8 : 0xfffff80003333ec4 : nt!NtTerminateProcess+0xf4
               rsp : 0xfffff8800d46ce38 : 0xfffff80003407d92 : nt!PspCatchCriticalBreak+0x92
               rbp : 0xfffff800033800d0 :  !da ""Terminating critical process 0x%p (%s).""
               rsi : 0xfffffa800ff40e10 :  !da "wininit.exe"
                r9 : 0xfffffa800ff40e10 :  !da "wininit.exe"
               r11 : 0xfffff8800d46cf48 : 0xfffff80003078e13 : nt!KiSystemServiceCopyEnd+0x13
0xfffff8800d46ce38 : 0xfffff80003407d92 : nt!PspCatchCriticalBreak+0x92
0xfffff8800d46ce58 : 0xfffffa800ff40e10 :  !da "wininit.exe"
0xfffff8800d46ce60 : 0xfffff800033800d0 :  !da ""Terminating critical process 0x%p (%s).""
0xfffff8800d46cec8 : 0xfffff80003333ec4 : nt!NtTerminateProcess+0xf4
0xfffff8800d46cf48 : 0xfffff80003078e13 : nt!KiSystemServiceCopyEnd+0x13
0xfffff8800d46d0b8 : 0xfffff800030753d0 : nt!KiServiceLinkage
0xfffff8800d46d3f8 : 0xfffff8800162485c : Ntfs!NtfsExtendedCompleteRequestInternal+0x11c
0xfffff8800d46d438 : 0xfffff8800162df89 : [COLOR=Red]Ntfs!NtfsProcessException+0x829[/COLOR]
0xfffff8800d46d518 : 0xfffff88001621594 :[COLOR=Red] Ntfs!NtfsFsdRead+0x2d4[/COLOR]
0xfffff8800d46d5b8 : 0xfffff8000305ea42 : nt!EtwpReserveTraceBuffer+0xe2
0xfffff8800d46d628 : 0xfffff80003004000 : "nt!KiSelectNextThread <PERF> (nt+0x0)"
0xfffff8800d46d830 : 0xfffff800030b46f4 : nt!KiDispatchException+0x348
0xfffff8800d46d8f8 : 0xfffff80003079202 : nt!KiExceptionDispatch+0xc2
0xfffff8800d46dad8 : 0xfffff80003077d7a : [COLOR=Red]nt!KiPageFault+0x23a[/COLOR]

Run some hard-drive diagnostics and follow these steps:

• Hard Drive Diagnostic Procedure

Find your hard-drive manufacturer and run their tests.

Additional Tests:

• SeaTools for DOS | Seagate
• CrystalDiskInfo - Software - Crystal Dew World

Post a screenshot of Crystal Disk Info summary:

• http://www.sevenforums.com/tutorials/9733-screenshots-files-upload-post-seven-forums.html

If you have an SSD, make sure the following are up to date:

• SSD firmware
• BIOS Version
• Chipset Drivers
• Hard disk controller drivers/SATA drivers
• If you have a Marvell IDE ATA/ATAPI device, make sure the drivers are up to date from the Intel site or Marvell site and not from your motherboard/vendor support site.

Check for any file system errors and bad sectors using Option #2 of:

• http://www.sevenforums.com/tutorials/433-disk-check.html

Use this command with Disk Check:

chkdsk C: /f /r

Note: Do not run the hard-drive tests on the SSD, check your SSD support page for appropriate testing tools if any.

 

[shandeleo]

Thanks very much for your response.
Samsung utility reported firmware up to date, no errors on SSD.
ASUS utility reported BIOS up to date, and my version is the newest one available from ASUS site.
The newest chipset drivers on the ASUS site were actually older than my installed ones.
Disk Check reported no errors on Seagate drive. Did not not it on SSD as per instructions.
SeaTools did not find a supported drive.
CrystalDiskInfo found no errors on either drive. Screenshots below.
View attachment 292191

View attachment 292192

Thanks very much

 

[shandeleo]

Addition. Booting from iso of Samsung utilities, program ran, but was illegible. Reported information was from the windows-based Samsung utility.

 

[x BlueRobot]

That's fine, I always post the bootable DOS based tools first, since some people may not be able to boot into Windows.

Your hard-drive and SSD seem to be fine, therefore I would suggest testing the RAM, which is another exhaustive process unfortunately.

• http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

Run Memtest86+ for least 9-10 passes, and preferably overnight as it can take a while to fully complete.

Test each RAM stick individually, if an error is found then move the same RAM stick into the next DIMM slot and test again, if errors are found for the same RAM stick in every available slot then you have a faulty RAM module. On the other hand, if no errors are found in the next slot or the other slots for the same RAM module, then you have a faulty DIMM slot.

Test each RAM stick and every motherboard DIMM slot available.

test|Slot1|Slot2
RAM1| Error | Error
RAM2|Good|Good

It is a RAM, a bad RAM.

But if you have got a result like that:

test|Slot1|Slot2
RAM1| Error |Good
RAM2| Error |Good

It is a motherboard issue. The particular slot is bad.