Windows 7 Forums

Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSOD CI.dll - The driver probably at fault is hardware_disk

17 Oct 2012   #1
shawnpederson

Windows 7 Professional x64
 
 
BSOD CI.dll - The driver probably at fault is hardware_disk

Hi all, received a BSOD this morning. Ran crash analyzer and it determined that the driver probably at fault is hardware disk. I can post the full analysis but it's big. Any one run into this before? I just want to be sure it's not a hardware issues (i.e. my drive).
Code:
 
==================================================
Dump File : 101712-14164-01.dmp
Crash Time : 10/17/2012 6:44:26 AM
Bug Check String : SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000007e
Parameter 1 : ffffffff`c0000006
Parameter 2 : fffff880`00cf90e9
Parameter 3 : fffff880`07891638
Parameter 4 : fffff880`07890e90
Caused By Driver : CI.dll
Caused By Address : CI.dll+110e9
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : CI.dll+110e9
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\101712-14164-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 7601
Dump File Size : 284,448
==================================================
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e)
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.
Arguments:
Arg1: ffffffffc0000006, The exception code that was not handled
Arg2: fffff88000cf90e9, The address that the exception occurred at
Arg3: fffff88007891638, Exception Record Address
Arg4: fffff88007890e90, Context Record Address



My System SpecsSystem Spec
.
17 Oct 2012   #2
shawnpederson

Windows 7 Professional x64
 
 

I should also mention, I will fire up Hiren's Boot CD tonight and run some physical hard drive tests. I also recently removed the Intel Rapid Storage driver to try to isolate some issues. Doesn't look like it helped much.
My System SpecsSystem Spec
17 Oct 2012   #3
koolkat77

Microsoft Community Contributor Award Recipient

Windows 10 Home 64Bit
 
 

Post screenshots of your hard drives using the crystal disk info:Run Disk Check on your hard disk for file system errors and bad sectors on it:Hard drive test both short and long with: Also the DOS version of:
My System SpecsSystem Spec
.

17 Oct 2012   #4
shawnpederson

Windows 7 Professional x64
 
 

Roger, will get back to you. Thanks.
My System SpecsSystem Spec
17 Oct 2012   #5
koolkat77

Microsoft Community Contributor Award Recipient

Windows 10 Home 64Bit
 
 

Take your time.

Just so you know the usual causes on your bug check:
Code:
STOP 0x0000007E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED  
Usual causes:  Insufficient disk space, Device driver, Video card, BIOS, 
Breakpoint with no debugger attached, Hardware incompatibility, 
Faulty system service, Memory, 3rd party remote control,
(Source: BSOD Index)

Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000006, fffff88000cf90e9, fffff88007891638, fffff88007890e90}

Probably caused by : hardware_disk

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

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

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: fffff88000cf90e9, The address that the exception occurred at
Arg3: fffff88007891638, Exception Record Address
Arg4: fffff88007890e90, Context Record Address

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000006 - 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.

FAULTING_IP: 
CI!MinCrypK_GetCertAlgId+45
fffff880`00cf90e9 66394104        cmp     word ptr [rcx+4],ax

EXCEPTION_RECORD:  fffff88007891638 -- (.exr 0xfffff88007891638)
ExceptionAddress: fffff88000cf90e9 (CI!MinCrypK_GetCertAlgId+0x0000000000000045)
   ExceptionCode: c0000006 (In-page I/O error)
  ExceptionFlags: 00000000
NumberParameters: 3
   Parameter[0]: 0000000000000000
   Parameter[1]: 00000000000ee204
   Parameter[2]: 00000000c0000185
Inpage operation failed at 00000000000ee204, due to I/O error 00000000c0000185

CONTEXT:  fffff88007890e90 -- (.cxr 0xfffff88007890e90)
rax=0000000000000200 rbx=0000000000000000 rcx=00000000000ee200
rdx=0000000000001c50 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88000cf90e9 rsp=fffff88007891870 rbp=0000000000000000
 r8=000007fffffeffff  r9=fffff88007891968 r10=0000000000000000
r11=0000000000000000 r12=fffff8a00000fef0 r13=0000000000000000
r14=0000000000000000 r15=fffff8800316a040
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
CI!MinCrypK_GetCertAlgId+0x45:
fffff880`00cf90e9 66394104        cmp     word ptr [rcx+4],ax ds:002b:00000000`000ee204=????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

ERROR_CODE: (NTSTATUS) 0xc0000006 - 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.

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  00000000000ee204

EXCEPTION_PARAMETER3:  00000000c0000185

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

BUGCHECK_STR:  0x7E

EXCEPTION_STR:  0xc0000006_c0000185

FOLLOWUP_IP: 
+45
00000000`000ee204 ??              ???

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware_disk

IMAGE_NAME:  hardware_disk

DEBUG_FLR_IMAGE_TIMESTAMP:  0

STACK_COMMAND:  kb

FAILURE_BUCKET_ID:  X64_0x7E_IMAGE_hardware_disk

BUCKET_ID:  X64_0x7E_IMAGE_hardware_disk

Followup: MachineOwner
My System SpecsSystem Spec
17 Oct 2012   #6
shawnpederson

Windows 7 Professional x64
 
 

I'm hoping software (i.e. drivers, OS). I could use a format.
My System SpecsSystem Spec
17 Oct 2012   #7
koolkat77

Microsoft Community Contributor Award Recipient

Windows 10 Home 64Bit
 
 

Quote   Quote: Originally Posted by shawnpederson View Post
I'm hoping software (i.e. drivers, OS). I could use a format.
Sorry, I'm not sure I understand what you mean? How old are your hard drives?
You should follow the tutorials below "just in case"
Prefer an external hard drive for the backup
My System SpecsSystem Spec
17 Oct 2012   #8
shawnpederson

Windows 7 Professional x64
 
 

Sorry, that was more of a joke then anything. I meant, I it would give me a reason to re-build my OS... it's got a lot of junk on it. Always refreshing after a format. But I also want to know what caused the BSOD. I will test the physical drive tonight.
My System SpecsSystem Spec
17 Oct 2012   #9
koolkat77

Microsoft Community Contributor Award Recipient

Windows 10 Home 64Bit
 
 

Ah okay, we'll be waiting for the results. Let us know the "how old/young" your hard drives are
My System SpecsSystem Spec
17 Oct 2012   #10
shawnpederson

Windows 7 Professional x64
 
 

Here are my CrystalDiskInfo results and SeaTools short test. The Sea tools long test is currently running.
My System SpecsSystem Spec
Reply

 BSOD CI.dll - The driver probably at fault is hardware_disk




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
BSOD at random times, maybe new graphics driver is at fault?
I attached like 7 different crash files, I hope someone can help me out.. Thanks a lot in advance!
BSOD Help and Support
Driver IRQL Not Less or Equal BSOD followed by Page Fault in Non-Paged
Lately I've been having all the games on my computer crash within about 2-3 minutes of starting them, and sometimes I get a Driver IRQL Not Less or Equal BSOD in place of a crash. I had two of these BSOD's last week, and all of them seem to be followed by a Page Fault in Non-Paged Area BSOD. I've...
BSOD Help and Support
BSOD after Windows 7 install, plus display driver fault
Hi, I just uploaded Windows 7 professional yesterday (clean install, using windows xp previously). Everything went smoothly as far as I could tell and Windows 7 is now running on my laptop. However every 10 minutes or so the screen freezes, goes black for a second and than returns to normal...
BSOD Help and Support
BSOD after driver updates. No idea which driver is at fault
Hi, I've recently been using drivermax to update my drivers. After my updates, I've been randomly getting BSODs then and now. I looked into the minidump with bluescreenviewer but cannot find a fix to the problem. I've uploaded the minidump. Please help! I'm using a shared a computer so I don't know...
BSOD Help and Support
BSOD - maybe display driver's fault?
I've been having frequent BSODs for a while now. They happen intermittently, usually when I'm doing something graphical such as using skype, or streaming a video. I've tried a number of different versions of ATI's graphics drivers, to no avail. I've tried reinstalling them several times. I...
BSOD Help and Support
Daily BSOD, ntoskrnl.exe driver fault?
Hey guys, Recently got my new computer, and it is amazing! Only problem is that 2 or 3 times a day i get a BSOD...:( I checked the Minidump files and it's saying something about VISTA_DRIVER_FAULT and ntoskrnl.exe driver fault. This is what the Dump File reads: Loading Dump File Mini...
BSOD Help and Support


Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 06:03.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App