Solved BSOD few seconds after boot/login

[darkeagle]

Hello guys!
I'm experiencing a devastating BSOD on my system right a few seconds after windows boots.
I am an IT expert and have some kernel knowledge but I am unable to pinpoint the exact problem.

Windbg minidump output as follows:

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
 
 
Loading Dump File [C:\Windows\Minidump\070414-31387-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
 
Symbol search path is: [URL]http://msdl.microsoft.com/download/symbols[/URL]
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18409.x86fre.win7sp1_gdr.140303-2144
Machine Name:
Kernel base = 0x8343b000 PsLoadedModuleList = 0x835845b0
Debug session time: Fri Jul 4 17:16:46.766 2014 (GMT+3)
System Uptime: 0 days 0:02:08.327
Loading Kernel Symbols
...............................................................
................................................................
.................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
 
Use !analyze -v to get detailed debugging information.
 
BugCheck 1000007E, {c0000006, 83447f85, 90c69830, 90c69410}
 
Probably caused by : hardware_disk
 
Followup: MachineOwner
---------
 
3: 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: c0000006, The exception code that was not handled
Arg2: 83447f85, The address that the exception occurred at
Arg3: 90c69830, Exception Record Address
Arg4: 90c69410, 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: 
nt!KevSkipVerification+cc
83447f85 668b13 mov dx,word ptr [ebx]
 
EXCEPTION_RECORD: 90c69830 -- (.exr 0xffffffff90c69830)
ExceptionAddress: 83447f85 (nt!KevSkipVerification+0x000000cc)
ExceptionCode: c0000006 (In-page I/O error)
ExceptionFlags: 00000000
NumberParameters: 3
Parameter[0]: 00000000
Parameter[1]: 002c2000
Parameter[2]: c0000185
Inpage operation failed at 002c2000, due to I/O error c0000185
 
CONTEXT: 90c69410 -- (.cxr 0xffffffff90c69410)
eax=defa8000 ebx=002c1fff ecx=00000001 edx=00000000 esi=00234146 edi=0023415c
eip=83447f85 esp=90c698f8 ebp=00231060 iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
nt!KevSkipVerification+0xcc:
83447f85 668b13 mov dx,word ptr [ebx] ds:0023:002c1fff=????
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: 00000000
 
EXCEPTION_PARAMETER2: 002c2000
 
EXCEPTION_PARAMETER3: c0000185
 
IO_ERROR: (NTSTATUS) 0xc0000185 - The I/O device reported an I/O error.
 
BUGCHECK_STR: 0x7E
 
EXCEPTION_STR: 0xc0000006_c0000185
 
FOLLOWUP_IP: 
+6cd5952f0329dedc
002c2000 ?? ???
 
FOLLOWUP_NAME: MachineOwner
 
MODULE_NAME: hardware_disk
 
IMAGE_NAME: hardware_disk
 
DEBUG_FLR_IMAGE_TIMESTAMP: 0
 
STACK_COMMAND: kb
 
FAILURE_BUCKET_ID: 0x7E_IMAGE_hardware_disk
 
BUCKET_ID: 0x7E_IMAGE_hardware_disk
 
Followup: MachineOwner
---------

I can safely boot into safemode and cannot reproduce the BSOD in that state (tested about 36 hours of work).
I was checking the recently installed drivers and could not find anything installed at the last week.
I did run verifier and reproduced the BSOD with no additional info.
It seems as if it is a hard disk issue but I should note I'm running another windows installation on this same hard disk on another partition (windows 7 64 bit) with no interruptions at all and it works just fine.
I did uninstall McAfee anti virus just in case, but that did not solve the problem.

Anyone can shed some light?
Thanks in advance!

 

[Arc]

Hi darkeagle.

All the recent crash dumps report the same. Some sort of disc failure.

BugCheck 1000007E, {c0000006, 83447f85, 90c69830, 90c69410}
[COLOR=Red]
Probably caused by : hardware_disk[/COLOR]

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

THe computer is a ThinkPad T520, which comes with different disks, and as all the files are not included in the zip, we cannot decide more about the disk.

At a starting point, test the hdd using the manufacturers tool. 14 Free Hard Drive Testing Tools (Updated June 2014)

Let us know the result. Also upload your MSINFO32.nfo file.

1. Click on the start button
2. Type "msinfo32" (without quotes) in the search bar of the start menu, click the resulting link. It will open the System Information window.
3. File>Save. In the "File Name" filed, put "MSINFO32" (without Quote), give the save location to desktop, and click the "save" button.
4. Give the time for processing, it will save a .nfo file on your desktop.
5. Zip it, and upload it following the instruction.

 

[darkeagle]

Hey Arc.
Thanks for the fast response .

I would be running the Lenovo disk checking software in a jiffy.

I would however update that I was able to dig thro the eventlog to find a problem with a driver for Daemon Tools Lite that encounted a problem (stpd.sys).
I immediately deleted the driver and the whole daemon tools suite (the uninstaller didnt really work, said the installation of daemon tools is corrupt so I had to uninstall manually using: Removing DAEMON Tools Lite manually | daemon-help.com).

Sadly, that did not solve the BSODs .
These event log entries wouldnt show up anymore but again the BSODs continues.

Could daemon tools (virtual hardware devices and such) produce these BSODs?(hardware_disk errors).

 

[darkeagle]

Attaching MSINFO32.

Thanks again.

 

[Arc]

Yes, Daemon Tools can cause various issues.

Your HDD is a seagate one. Seagate Momentus 320 GB. So the best you run seatools. Both the short and long test. http://www.sevenforums.com/tutorials/313457-seatools-dos-windows-how-use.html

Also, the storage controller may fail and cause this issue. Get rid of intel rapid storage. First uninstall it from Control Panel > Programs and Features. Then Uninstall the driver from device manager.

1. Right click on "my computer" icon and click "manage" on the context menu.
2. It will open the "computer management" window.
3. Select "Device Manager" in the left pane, It will list all the existing devices up.
4. Expand "IDE ATA/ATAPI controllers" by clicking on the triangle in front of it.
5. Select one Intel device item under it, right click, uninstall.
6. Continue the process for all Intel items under "IDE ATA/ATAPI controllers"
7. Now restart the computer. At restart, windows will auto configure the appropriate native system driver.

Let us know the results.

 

[darkeagle]

I'm pleased to say its SOLVED

As you suggested, I did as follows:
Burned a linux live cd of Lenovo Solution Center bootable image.
Used the built-in tool to discover and fix bad sectors, the output was 16 bad sectors found and fixed.

The next boot everything works as for now (about 1 hour of work).

I do wonder however for the condition of this HDD... Do you think I should try and replace it anyways?:huh:

Thank you very much for all the help!

 

[Arc]

You are welcome.

I would suggest you to let seatools a go.