My HP G62-455dx laptop began crashing last week. I finally restored it to factory settings,now it will only start in safe mode. When I try to start window normally, it just "thinks' for 10 mins or so and then crashes (blue screen of death). I read several suggestions on this site, and have tried a few, still no solution. It is only 2 years old.
Welcome to SevenForums.
There is only one dump files which blames an old driver from Intel Rapid Storage.
Please download the stable version of Intel Rapid Storage drivers from here:Code:*** WARNING: Unable to verify timestamp for iaStor.sys *** ERROR: Module load completed but symbols could not be loaded for iaStor.sys ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1000007E, {ffffffffc0000005, fffff8800114e5be, fffff88003727948, fffff880037271b0} Probably caused by : iaStor.sys ( iaStor+725be ) 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: ffffffffc0000005, The exception code that was not handled Arg2: fffff8800114e5be, The address that the exception occurred at Arg3: fffff88003727948, Exception Record Address Arg4: fffff880037271b0, Context Record Address Debugging Details: ------------------ OVERLAPPED_MODULE: Address regions for 'lltdio' and 'RtsUStor.sys' overlap EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. FAULTING_IP: iaStor+725be fffff880`0114e5be 8901 mov dword ptr [rcx],eax EXCEPTION_RECORD: fffff88003727948 -- (.exr 0xfffff88003727948) ExceptionAddress: fffff8800114e5be (iaStor+0x00000000000725be) ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 0000000000000000 Parameter[1]: ffffffffffffffff Attempt to read from address ffffffffffffffff CONTEXT: fffff880037271b0 -- (.cxr 0xfffff880037271b0) rax=0000000000000001 rbx=fffffa800494c210 rcx=1ffff88003720101 rdx=0000000000000000 rsi=fffffa80077028d0 rdi=fffffa8004945b00 rip=fffff8800114e5be rsp=fffff88003727b80 rbp=0000000000000000 r8=fffffa800494c210 r9=0000000000000000 r10=0000000000000001 r11=fffffa800494c210 r12=0000000000000001 r13=0000000000000000 r14=fffffa8004948000 r15=fffff88003720000 iopl=0 nv up ei pl zr na po nc cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246 iaStor+0x725be: fffff880`0114e5be 8901 mov dword ptr [rcx],eax ds:002b:1ffff880`03720101=???????? Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT PROCESS_NAME: System CURRENT_IRQL: 2 ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. EXCEPTION_PARAMETER1: 0000000000000000 EXCEPTION_PARAMETER2: ffffffffffffffff READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cf30e0 GetUlongFromAddress: unable to read from fffff80002cf3198 ffffffffffffffff FOLLOWUP_IP: iaStor+725be fffff880`0114e5be 8901 mov dword ptr [rcx],eax BUGCHECK_STR: 0x7E LAST_CONTROL_TRANSFER: from fffffa8004949000 to fffff8800114e5be STACK_TEXT: fffff880`03727b80 fffffa80`04949000 : fffffa80`0494c210 fffffa80`077028d0 fffffa80`04945b00 fffffa80`04945b01 : iaStor+0x725be fffff880`03727b88 fffffa80`0494c210 : fffffa80`077028d0 fffffa80`04945b00 fffffa80`04945b01 fffff880`0114e74f : 0xfffffa80`04949000 fffff880`03727b90 fffffa80`077028d0 : fffffa80`04945b00 fffffa80`04945b01 fffff880`0114e74f 1ffff880`03720101 : 0xfffffa80`0494c210 fffff880`03727b98 fffffa80`04945b00 : fffffa80`04945b01 fffff880`0114e74f 1ffff880`03720101 00000000`00000000 : 0xfffffa80`077028d0 fffff880`03727ba0 fffffa80`04945b01 : fffff880`0114e74f 1ffff880`03720101 00000000`00000000 fffffa80`0494c538 : 0xfffffa80`04945b00 fffff880`03727ba8 fffff880`0114e74f : 1ffff880`03720101 00000000`00000000 fffffa80`0494c538 fffff880`010e0302 : 0xfffffa80`04945b01 fffff880`03727bb0 1ffff880`03720101 : 00000000`00000000 fffffa80`0494c538 fffff880`010e0302 00000000`00000000 : iaStor+0x7274f fffff880`03727bb8 00000000`00000000 : fffffa80`0494c538 fffff880`010e0302 00000000`00000000 00000000`00000000 : 0x1ffff880`03720101 SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: iaStor+725be FOLLOWUP_NAME: MachineOwner MODULE_NAME: iaStor IMAGE_NAME: iaStor.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4bc49f60 STACK_COMMAND: .cxr 0xfffff880037271b0 ; kb FAILURE_BUCKET_ID: X64_0x7E_iaStor+725be BUCKET_ID: X64_0x7E_iaStor+725be Followup: MachineOwner --------- 2: kd> lmvm iaStor start end module name fffff880`010dc000 fffff880`012e6000 iaStor T (no symbols) Loaded symbol image file: iaStor.sys Image path: \SystemRoot\system32\DRIVERS\iaStor.sys Image name: iaStor.sys Timestamp: Tue Apr 13 22:44:16 2010 (4BC49F60) CheckSum: 00090C73 ImageSize: 0020A000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
Reduce items at start-up. Nothing except anti-virus is required plus improves the time for logging in windows.
Perform a System File Check:
- Click on the start
- Type CMD on Search
- Left click and Run as Administrator
- Type SFC /scannow
Full tutorial here:
Upload a screenshot of your hard disk using CrystalDiskInfo:
- CrystalDiskInfo - Software - Crystal Dew World
- Screenshots and Files - Upload and Post in Seven Forums
Make a hard drive test from the hard drive manufacturers website:
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:
Let us know the results.
I updated the driver as you suggested, but I still only start in safe mode. Screen shot is attached, don't know if you see it...I cannot as it will not work in safe mode.
Looks like I cannot do the sfc scan either
Just downloaded the sea gate tools...can't use that insafe mode either
Have you restarted and tried again
I think you should do a Clean Reinstall - Factory OEM Windows 7
I following the links in your post, but I can't download the tools in safe mode. It says I must restart in Windows 7, and I cannot get the machine to open it.
What tools are you trying to download?
I would start by testing the HD to get that out of the way so you can move on to get the best possible reinstall of Win7, which with HP's is not at all the bloated Factory preinstall.
Find another PC to download Seagate Seatools DOS scanner, rightclick the ISO to Open with Windows Image Burner, burn to CD, boot and run the Extended Scan.
Then download and burn to DVD the Win7 installer for your licensed version, boot it to Clean Reinstall - Factory OEM Windows 7. You'll get and keep a perfect install using the tools and methods in this tutorial.
Since Factory Recovery doesn't work correctly and is for the corrupt factory preinstall with all the bloatware, get the cleanest start by deleting all partiitons during reinstall, create new as you wish during Steps 6/7 of Clean Install Windows .
1. Please list the tool you were requested to download and use that didn't work/install for you.
2. Did you run sfc /scannow as per Tutorial, (how many times with reboots between each)?
----
SFC /SCANNOW Command - System File Checker
----
Did you try to download this and did it work/install for you?
Intel® Rapid Storage Technology Version:11.2.0.1006
----
We dearly like helping people but precise answers will be needed. Any test requested we will need the results.
Please go through koolkat77 post #2 step at a time and let us know the results.
-----------------------
Yussi and Greg.
Question. Could part of the mbr or uefi been damaged when doing a Factory Restore. Not allowing boot in normal mode.
Could be, Layback. When Factory Recovery stalls sometimes at startup an alternative is to use the Recovery Disks but first wipe the HD to clear the boot sector, using Diskpart Clean Command from the Win7 DVD or Repair CD, DBAN or Partition Wizard.
If the install finished it might even respond to Startup Repair run a few times.
However since this is the HP preinstall which has the worst load of bloatware in the industry, the Best Practice is surely to Clean Reinstall to get Win7's native performance without the corrupting crapware.
Quote