Brand new build, BSoD with bccodes F4 and 7A

Hi there. I thought I was out of the woods, but I just received another blue screen (see attached file for details). This time I completely swapped out the SATA cable with a different one, and plugged it into a different port all together. I thought it was interesting that my startup was MUCH faster after the change (I don't know if this is related or not, thought I'd point it out anyway). Hopefully it was just a cable issue, I still have another week until my 30 day return policy is up with the store I bought it from, so if there another issue, I might just return the HD for a new one. Let me know what you think!

You can have different SATA port types, some specifications are faster than others. For example, SATA III is faster than SATA II.

Code:

BugCheck 7A, {fffff6fc40009a50, ffffffffc000000e, 1fac3d860, fffff8800134a748}

GetPointerFromAddress: unable to read from fffff80003105278
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption

Code:

Usual causes:  Memory, Paging file corruption, File system, Hard drive, Cabling, Virus infection, Improperly seated cards, BIOS, Bad motherboard, Missing Service Pack

Code:

3: kd> !error ffffffffc000000e
Error code: (NTSTATUS) 0xc000000e (3221225486) - A device which does not exist was specified.

Code:

DISK_HARDWARE_ERROR: There was error with disk hardware

It seems to be a hard-drive problem, but before you return the drive, I would attempt resetting the page file to ensure page file corruption isn't causing any problems:

1. Go to Start and type in "sysdm.cpl" (without the quotes) and press Enter
2. Click on the Advanced tab
3. Click on the Performance Settings button
4. Click on the Advanced tab
5. Click on the Virtual Memory Change button
6. Uncheck the "Automatically manage paging file size for all drives" box (it's the default)
7. If the above box isn't checked, then make a note of what the paging file settings are
8. Click on the "No paging file" radio button, then click on "Set"
9. Answer Yes to the confirmation dialog that pops up.
10. Click on OK 3 times (to close all the Windows)
11. Reboot the system (this will delete the paging file)
12. Once Windows starts, go to Start and type in "sysdm.cpl" (without the quotes) and press Enter
13. Click on the Advanced tab
14. Click on the Performance Settings button
15. Click on the Advanced tab
16. Click on the Virtual Memory Change button
17. Place a checkmark in the "Automatically manage paging file size for all drives" box (it's the default)
18. If the above box wasn't checked at first, then re-enter the paging file settings that you noted in Step 7
19. Click on "Set" (it'll be greyed out if you checked the box 2 steps earlier
20. Click on OK 3 times (to close all the Windows)
21. Reboot the system (this will recreate the paging file)

Okay I just did all that. Now I guess only time will tell. Anything else I could try while waiting to see if I get another blue screen?

Nothing which would be relevant for your situation I'm afraid, just use your computer as you normally would for now :)

Alright, I appreciate it. In the mean time, I registered my HD with Western Digital, and was told I have until 2016 to RMA the product if I need too. I don't really want to resort to that, as I would have to reinstall everything. Hopefully the fixes you have provided will work. Thanks for the help, mate!

Welcome, can you could create a system image now, and then just install that onto your new hard drive if need be :)

Imaging with free Macrium

or

Backup Complete Computer - Create an Image Backup

I apologize if this is improper etiquette, but I thought it would be better to bump and old thread rather than making a new one. I have been blue screen free for a multitude of days now, which is great! However, today I went to plug in a USB hard drive, and of course the system blue screen. This has happened before where the system blue screened after plugging something in. Something to note is that when I plug it in, Microsoft Security Essentials warns me that it is no longer protecting my computer, then the system freezes and blue screens. I have posted the dump file.

Code:

BugCheck F4, {3, fffffa8009a49350, fffffa8009a49630, fffff800031db0d0}

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

This bugcheck is usually related to storage related problems.

Code:

3: kd> !process fffffa8009a49350
GetPointerFromAddress: unable to read from fffff8000310c000
PROCESS fffffa8009a49350
    SessionId: none  Cid: 026c    Peb: 7fffffd4000  ParentCid: 01a8
    DirBase: 1ce700000  ObjectTable: fffff8a001b3d7e0  HandleCount: <Data Not Accessible>
    Image: wininit.exe
    VadRoot fffffa8009a491e0 Vads 68 Clone 0 Private 488. Modified 12. Locked 2.
    DeviceMap fffff8a000008e00
    Token                             fffff8a001b47c50
    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]         104232
    QuotaPoolUsage[NonPagedPool]      10696
    Working Set Sizes (now,min,max)  (1361, 50, 345) (5444KB, 200KB, 1380KB)
    PeakWorkingSetSize                1361
    VirtualSize                       49 Mb
    PeakVirtualSize                   53 Mb
    PageFaultCount                    1741
    MemoryPriority                    BACKGROUND
    BasePriority                      13
    CommitCharge                      602

        *** Error in reading nt!_ETHREAD @ fffffa8009a96920

Have you done with the other hard-drive? Replaced it? There was many errors with the hard-drive in the other dumps, and this may be contributing to the other present errors.

I haven't rid of the HDD yet on the grounds that with school starting, I didn't want to be waiting on a hard drive in case I need it. However, it looks like I have no other choice. I'm going to give the system a few more days, if I get even just one more error, I'll look into getting it replace.

Okay thanks, I think that may be your overall problem :)