BSOD - Blue screen view dump file

DarkMario616

Estimable
Jun 28, 2015
4
0
4,510
ASUS X45a with Win8 64 bit cannot boot into OS. I get the error SYSTEM THREAD EXCEPTION NOT HANDLED.

I can boot into safe mode and I ran bluescreenview.

==================================================
Dump File : 062815-38000-01.dmp
Crash Time : 6/28/2015 12:12:42 PM
Bug Check String : SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000007e
Parameter 1 : ffffffff`c0000006
Parameter 2 : fffff803`440c295e
Parameter 3 : ffffd000`a9272648
Parameter 4 : ffffd000`a9271e50
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+24895e
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+24895e
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\062815-38000-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 9600
Dump File Size : 278,496
Dump File Time : 6/28/2015 12:15:31 PM
==================================================

Not sure what this means.
 

DarkMario616

Estimable
Jun 28, 2015
4
0
4,510
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000006, The exception code that was not handled
Arg2: fffff802b74cc95e, The address that the exception occurred at
Arg3: ffffd000219ce648, Exception Record Address
Arg4: ffffd000219cde50, Context Record Address

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

TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

EXCEPTION_CODE: (NTSTATUS) 0xc0000006 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The required data was not placed into memory because of an I/O error status of "0x%08lx".

FAULTING_IP:
nt!XpressDecodeCreate+7a
fffff802`b74cc95e 0fb702 movzx eax,word ptr [rdx]

EXCEPTION_RECORD: ffffd000219ce648 -- (.exr 0xffffd000219ce648)
ExceptionAddress: fffff802b74cc95e (nt!XpressDecodeCreate+0x000000000000007a)
ExceptionCode: c0000006 (In-page I/O error)
ExceptionFlags: 00000000
NumberParameters: 3
Parameter[0]: 0000000000000000
Parameter[1]: 000000d0bfbe5000
Parameter[2]: 00000000c000009c
Inpage operation failed at 000000d0bfbe5000, due to I/O error 00000000c000009c

CONTEXT: ffffd000219cde50 -- (.cxr 0xffffd000219cde50)
rax=00000000ffffff10 rbx=0000000000000000 rcx=0000000000000000
rdx=000000d0bfbe4fff rsi=0000000000004bd3 rdi=0000000000000001
rip=fffff802b74cc95e rsp=ffffd000219ce888 rbp=ffffd000219ce939
r8=000000d0bfa87649 r9=ffffc00149013500 r10=00000000effc0000
r11=0000000000000000 r12=0000000000093299 r13=000000d0bfbe2c1f
r14=0000000000000035 r15=ffffc00149013500
iopl=0 nv up ei ng nz na po cy
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010287
nt!XpressDecodeCreate+0x7a:
fffff802`b74cc95e 0fb702 movzx eax,word ptr [rdx] ds:002b:000000d0`bfbe4fff=????
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP

PROCESS_NAME: System

CURRENT_IRQL: 0

ERROR_CODE: (NTSTATUS) 0xc0000006 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The required data was not placed into memory because of an I/O error status of "0x%08lx".

EXCEPTION_PARAMETER1: 0000000000000000

EXCEPTION_PARAMETER2: 000000d0bfbe5000

EXCEPTION_PARAMETER3: 00000000c000009c

IO_ERROR: (NTSTATUS) 0xc000009c - STATUS_DEVICE_DATA_ERROR

BUGCHECK_STR: AV

FOLLOWUP_IP:
+7a
000000d0`bfbe5000 ?? ???

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: hardware_disk

IMAGE_NAME: hardware_disk

DEBUG_FLR_IMAGE_TIMESTAMP: 0

STACK_COMMAND: kb

FAILURE_BUCKET_ID: X64_AV_VRF_IMAGE_hardware_disk

BUCKET_ID: X64_AV_VRF_IMAGE_hardware_disk

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

Adding this as per someone else
 

johnbl

Honorable
Nov 4, 2012
140
1
10,710
some data could not be read from storage.

I would check the data cables from the motherboard to the drive, maybe change the connection to another port or a different controller if your system has two sata controlers. (try the slower one). Also check the power to the drive and make sure it has power, and is spinning if it is a mechanical drive.

you may also delete your system pagefile.sys and create an new one. (turn off virutal memory reboot, remove the hidden c:\pagefile.sys and then turn it back on to make another one). maybe run seatools to test your drive if it is old and might be causing errors

0: kd> !error 0xc000021a
Error code: (NTSTATUS) 0xc000021a (3221226010) - {Fatal System Error} The %hs system process terminated unexpectedly with a status of 0x%08x (0x%08x 0x%08x). The system has been shut down.
0: kd> !error 0xc0000006
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.
0: kd> !error 0xc000009c
Error code: (NTSTATUS) 0xc000009c (3221225628) - STATUS_DEVICE_DATA_ERROR

Note: this can also just be a bad connection on your hard drive date cable. just check or replace the cable.
 

DarkMario616

Estimable
Jun 28, 2015
4
0
4,510
I guess I should have mentioned this is a laptop. I do not believe it has any cables connecting it from mobo. I believe it's usually just attached to the mobo so I will try adjusting it.