BSOD on occasional start up, error 0x0000007a

LemonPower · 10 Aug 2013

Unexpected Blue Screen of Death's occur on occasional start ups, if the computer boots normally without a crash I experience little to no performance issues. However when it boots with issues the event logs state that the WUDFRd driver is unable to load successfully for

WpdBusEnumRoot\UMB\2&37c186b&0&STORAGE#VOLUME#_??_USBSTOR#DISK&VEN_GENERIC&PROD_CF_CARD_READER&REV_1 .00#058F63606476&0#

which is followed by another log seconds later that says that it's unable to find the assembly item Microsoft.VC80.MFC,processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",versio n="8.0.50727.762"

The last system crash occurred at (GMT +1) 15:12:36 op ‎10-‎8-‎2013. The two above seem to be the only thing the system actually logs before killing itself. I have no idea.

Requested information attached below.

LemonPower · 10 Aug 2013

Posting off my secondary computer.

As I was going through my desktop my monitor suddenly shut down and the sound cut out rendering my computer unresponsive. I turned it off by holding the power button before restarting it moments later. Doing this caused the same events half-way during start up. After restarting it again it said it couldn't start windows and I did the recommended action to have it run startup repair after which it did the same again. I left the computer off now to avoid damage, I have no idea what's causing this.

koolkat77 · 10 Aug 2013

Test your RAM and HDD:

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.

Upload a screenshot using:

CrystalDiskInfo

For how to upload a screenshot or file, read here

Test your Hard Drive by running:

Hard Drive Diagnostic Procedure

------------------------------------------

Use the System File Checker tool and Run Disk Check:

Repair Windows 7 System Files with System File Checker

Run Disk Check in Windows 7 for Bad Sectors & Errors

Uninstall your current antivirus as it is contributing to your BSOD's. Replace with Microsoft Security Essentials & the Free version of Malwarebytes, update and make full scans separately:

Uninstallers (removal tools) for common antivirus software - ESET Knowledgebase

Help protect your PC with Microsoft Security Essentials

Malwarebytes Free

Do not start the trial version of MalwareBytes

You may also take a look at:

Good & Free System Security Combination

Make scans with -

TDSSKiller Rootkit Removal Utility Free Download | Kaspersky Lab US

Online Virus Scanner Eset

Reduce items at start up:

Performing a Clean Startup in Windows 7

Add, or Remove Startup Programs in Windows 7

Your Antivirus software is basically whats just needed there.

BSOD SUMMARY:

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 7A, {fffff6fc400063a8, ffffffffc0000185, 8ddcd860, fffff88000c75008}

GetPointerFromAddress: unable to read from fffff80002ec4278
*** 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

Followup: memory_corruption
---------

2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KERNEL_DATA_INPAGE_ERROR (7a)
The requested page of kernel data could not be read in.  Typically caused by
a bad block in the paging file or disk controller error. Also see
KERNEL_STACK_INPAGE_ERROR.
If the error status is 0xC000000E, 0xC000009C, 0xC000009D or 0xC0000185,
it means the disk subsystem has experienced a failure.
If the error status is 0xC000009A, then it means the request failed because
a filesystem failed to make forward progress.
Arguments:
Arg1: fffff6fc400063a8, lock type that was held (value 1,2,3, or PTE address)
Arg2: ffffffffc0000185, error status (normally i/o status code)
Arg3: 000000008ddcd860, current process (virtual address for lock type 3, or PTE)
Arg4: fffff88000c75008, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)

Debugging Details:
------------------


ERROR_CODE: (NTSTATUS) 0xc0000185 - The I/O device reported an I/O error.

DISK_HARDWARE_ERROR: There was error with disk hardware

BUGCHECK_STR:  0x7a_c0000185

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

PROCESS_NAME:  System

CURRENT_IRQL:  0

TRAP_FRAME:  fffff880031a1a90 -- (.trap 0xfffff880031a1a90)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000001 rbx=0000000000000000 rcx=fffffa80047d81a0
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88000c75008 rsp=fffff880031a1c28 rbp=fffff80002e32200
 r8=fffffa800521fb10  r9=fffffa80039d3248 r10=0000000000000000
r11=fffff880031a1bc0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
ataport!IdePortScanChannel:
fffff880`00c75008 73b9            jae     ataport!__PchSym_ <PERF> (ataport+0x18fc3) (fffff880`00c74fc3) [br=1]
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002cff742 to fffff80002c8cc00

STACK_TEXT:  
fffff880`031a1778 fffff800`02cff742 : 00000000`0000007a fffff6fc`400063a8 ffffffff`c0000185 00000000`8ddcd860 : nt!KeBugCheckEx
fffff880`031a1780 fffff800`02cb391f : fffffa80`03d99560 fffff880`031a18f0 fffff800`02ec7540 fffffa80`03d99560 : nt! ?? ::FNODOBFM::`string'+0x36c1a
fffff880`031a1860 fffff800`02c9a1b9 : 00000000`00000000 00000000`00000008 ffffffff`ffffffff 00000000`00000000 : nt!MiIssueHardFault+0x28b
fffff880`031a1930 fffff800`02c8ad2e : 00000000`00000008 fffff880`00c75008 00000000`00000000 00000000`00000004 : nt!MmAccessFault+0x1399
fffff880`031a1a90 fffff880`00c75008 : fffff880`00c7aea4 00000000`00000004 fffff800`02e32200 fffffa80`047d81a0 : nt!KiPageFault+0x16e
fffff880`031a1c28 fffff880`00c7aea4 : 00000000`00000004 fffff800`02e32200 fffffa80`047d81a0 fffff880`00e611da : ataport!IdePortScanChannel
fffff880`031a1c30 fffff800`02f84d73 : 00000000`00000001 00000000`00000004 fffffa80`05136780 fffff880`031a1c90 : ataport!ChannelQueryBusRelation+0xa0
fffff880`031a1c80 fffff800`02c96251 : fffff800`02e32200 fffff800`02f84d01 fffffa80`03a82000 fffff800`02e322d8 : nt!IopProcessWorkItem+0x23
fffff880`031a1cb0 fffff800`02f2aede : 00000000`00000000 fffffa80`03a82040 00000000`00000080 fffffa80`039d3040 : nt!ExpWorkerThread+0x111
fffff880`031a1d40 fffff800`02c7d906 : fffff880`02f63180 fffffa80`03a82040 fffff880`02f6dfc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`031a1d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND:  kb

CHKIMG_EXTENSION: !chkimg -lo 50 -d !ataport
    fffff88000c75000-fffff88000c7510c  269 bytes - ataport!__PchSym_ <PERF> (ataport+0x19000)
	[ 00 00 00 00 00 00 00 00:6b c4 d4 ad db 1a e4 e0 ]
    fffff88000c7510e-fffff88000c7531d  528 bytes - ataport!IdePortScanChannel+106 (+0x10e)
	[ e8 fd a2 ff ff 44 8a 9f:39 ad b8 88 3c f1 6d cf ]
    fffff88000c7531f-fffff88000c75392  116 bytes - ataport!IdePortScanChannel+317 (+0x211)
	[ ff 48 3b c8 74 51 0f ba:b6 e0 f0 92 52 1d b8 24 ]
    fffff88000c75394-fffff88000c755af  540 bytes - ataport!IdePortScanChannel+38c (+0x75)
	[ ff 48 8b cf e8 a3 6a 00:56 4d 07 49 06 9b ab 13 ]
    fffff88000c755b1-fffff88000c75633  131 bytes - ataport!IdeDiscoverDevice+105 (+0x21d)
	[ ff 48 81 c4 d0 00 00 00:3a dd 53 ff 3b de c8 15 ]
    fffff88000c75635-fffff88000c75677  67 bytes - ataport!IdeDiscoverDevice+189 (+0x84)
	[ 48 8b 0d 3c cb ff ff 89:24 e4 ef 12 48 58 48 5f ]
    fffff88000c75679-fffff88000c756c2  74 bytes - ataport!IdeDiscoverDevice+1cd (+0x44)
	[ 68 c7 44 24 68 08 00 00:e7 31 23 12 0e 01 52 4e ]
    fffff88000c756c4-fffff88000c75776  179 bytes - ataport!IdeDiscoverDevice+218 (+0x4b)
	[ a1 eb 0a c6 44 24 60 a1:64 6c e0 82 8d 3c fa 04 ]
    fffff88000c75778-fffff88000c75962  491 bytes - ataport!IdeDiscoverDevice+2cc (+0xb4)
	[ ec 74 07 83 a5 f8 03 00:5a b7 30 40 f1 78 6a 7f ]
    fffff88000c75964-fffff88000c75c5f  764 bytes - ataport!IdeDiscoverDevice+4b8 (+0x1ec)
	[ b6 c5 80 7c 04 60 ec 0f:a9 30 8b 1b 29 a2 43 81 ]
    fffff88000c75c61-fffff88000c75d1c  188 bytes - ataport!IdeEnableAtaTarget+71 (+0x2fd)
	[ 8d 8b 27 04 00 00 ba 04:74 63 a9 51 49 97 72 5c ]
    fffff88000c75d1e-fffff88000c75e6d  336 bytes - ataport!IdeUpdateRegistry+a (+0xbd)
	[ 57 48 83 ec 20 48 8b 79:88 47 ff 76 4f 07 19 fd ]
    fffff88000c75e6f-fffff88000c75ea9  59 bytes - ataport!ChannelQueryPcmciaParent+23 (+0x151)
	[ 84 24 98 00 00 00 33 db:a0 72 5c c4 45 89 e6 d3 ]
    fffff88000c75eab-fffff88000c75eae  4 bytes - ataport!ChannelQueryPcmciaParent+5f (+0x3c)
	[ 44 24 50 1b:1f 76 fc b8 ]
    fffff88000c75eb0-fffff88000c75fff  336 bytes - ataport!ChannelQueryPcmciaParent+64 (+0x05)
	[ 44 24 51 13 c7 44 24 30:d9 64 90 7f c5 d8 c4 27 ]
4082 errors : !ataport (fffff88000c75000-fffff88000c75fff)

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  LARGE_4096

FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_LARGE_4096

BUCKET_ID:  X64_MEMORY_CORRUPTION_LARGE_4096

Followup: memory_corruption
---------