Whenever I turn my PC on, I will more than likely get the BSOD error 0x7E, sometimes I can restart my computer and it will work but more often than not it will blue screen again, and sometimes this can happen upwards of 15 times before it will eventually load up.
It was Intel Rapid Storage causing the problem.
It happened again, followed the steps to remove Intel Rapid Storage and restarted my computer just to test if it worked which it did the first time, then I came to turn it on this morning and I got multiple blue screens.
Thought it might have been Avast (Anti-Virus I was using) but don't think it was. Still a mystery what is causing it.
Make sure your dump logging is enabled.
- Click Start, point to Settings, and then click Control Panel.
- Double-click System.
- Click the Advanced tab, and then click Settings under Startup and Recovery.
- Check Write an even to the system log, and Automatically restart.
- In the Write debugging information list, click Small memory dump (256k).
Location of Dumps:
C:\Windows\minidump
Allot of important info is missing from your zip, please follow Blue Screen of Death (BSOD) Posting Instructions to grab all and upload a new report here.
Code:Microsoft (R) Windows Debugger Version 6.2.9200.20512 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\admin\Downloads\MY-PC-22_11_2014_174433_13\112014-9063-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850 Machine Name: Kernel base = 0xfffff800`02c08000 PsLoadedModuleList = 0xfffff800`02e4de90 Debug session time: Thu Nov 20 19:02:31.630 2014 (UTC + 6:00) System Uptime: 0 days 0:00:07.505 Loading Kernel Symbols ............................................................... ................................................................ ....... Loading User Symbols Loading unloaded module list ..... *** WARNING: Unable to verify timestamp for igdkmd64.sys *** ERROR: Module load completed but symbols could not be loaded for igdkmd64.sys ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1000007E, {ffffffffc0000005, fffff88004997db9, fffff880055bb2b8, fffff880055bab10} Probably caused by : igdkmd64.sys ( igdkmd64+18edb9 ) Followup: MachineOwner --------- 1: 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: fffff88004997db9, The address that the exception occurred at Arg3: fffff880055bb2b8, Exception Record Address Arg4: fffff880055bab10, Context Record Address Debugging Details: ------------------ EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. FAULTING_IP: igdkmd64+18edb9 fffff880`04997db9 41ff5148 call qword ptr [r9+48h] EXCEPTION_RECORD: fffff880055bb2b8 -- (.exr 0xfffff880055bb2b8) ExceptionAddress: fffff88004997db9 (igdkmd64+0x000000000018edb9) ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 0000000000000000 Parameter[1]: 0000000000000048 Attempt to read from address 0000000000000048 CONTEXT: fffff880055bab10 -- (.cxr 0xfffff880055bab10) rax=00000000c0000001 rbx=00000000c0000001 rcx=0000000000000000 rdx=0000000000000000 rsi=fffffa8008466150 rdi=fffff880055bb5e4 rip=fffff88004997db9 rsp=fffff880055bb4f0 rbp=0000000000000006 r8=0000000000000000 r9=0000000000000000 r10=fffffa80082349e0 r11=fffff880055bb380 r12=0000000000000001 r13=0000000000000000 r14=fffffa8008466080 r15=0000000000000057 iopl=0 nv up ei pl zr na po nc cs=0010 ss=0000 ds=002b es=002b fs=0053 gs=002b efl=00010246 igdkmd64+0x18edb9: fffff880`04997db9 41ff5148 call qword ptr [r9+48h] ds:002b:00000000`00000048=???????????????? Resetting default scope CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: csrss.exe CURRENT_IRQL: 0 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: 0000000000000048 READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002eb90e8 GetUlongFromAddress: unable to read from fffff80002eb9198 0000000000000048 Nonpaged pool FOLLOWUP_IP: igdkmd64+18edb9 fffff880`04997db9 41ff5148 call qword ptr [r9+48h] BUGCHECK_STR: 0x7E DEFAULT_BUCKET_ID: NULL_CLASS_PTR_DEREFERENCE LAST_CONTROL_TRANSFER: from fffff880055bb5b0 to fffff88004997db9 STACK_TEXT: fffff880`055bb4f0 fffff880`055bb5b0 : 00000000`c0000001 00000000`00000000 00000000`00000006 00000000`00000000 : igdkmd64+0x18edb9 fffff880`055bb4f8 00000000`c0000001 : 00000000`00000000 00000000`00000006 00000000`00000000 00000000`00000000 : 0xfffff880`055bb5b0 fffff880`055bb500 00000000`00000000 : 00000000`00000006 00000000`00000000 00000000`00000000 00000000`00000003 : 0xc0000001 SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: igdkmd64+18edb9 FOLLOWUP_NAME: MachineOwner MODULE_NAME: igdkmd64 IMAGE_NAME: igdkmd64.sys DEBUG_FLR_IMAGE_TIMESTAMP: 5376e2df STACK_COMMAND: .cxr 0xfffff880055bab10 ; kb FAILURE_BUCKET_ID: X64_0x7E_igdkmd64+18edb9 BUCKET_ID: X64_0x7E_igdkmd64+18edb9 Followup: MachineOwner --------- 1: kd> lmvm igdkmd64 start end module name fffff880`04809000 fffff880`04bc2000 igdkmd64 T (no symbols) Loaded symbol image file: igdkmd64.sys Image path: \SystemRoot\system32\DRIVERS\igdkmd64.sys Image name: igdkmd64.sys Timestamp: Sat May 17 10:17:35 2014 (5376E2DF) CheckSum: 0039E1ED ImageSize: 003B9000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4Clean boot
Reduce items at start-up. No software except anti-virus is required plus doing this improves the time for logging into windows:
Run the System File Checker that scans the of all protected Windows 7 system files and replaces incorrect corrupted, changed/modified, or damaged versions with the correct versions if possible:
- Click on the
- Type CMD on Search
- Left click and Run as Administrator
- Type SFC /scannow
Full tutorial here:
Run Disk Check on your Hard Drive for file system errors and bad sectors on it.
Hard Drive Diagnostics
- Double click and open my computer.
- Right click on desired drive and hit properties.
- Click on tools tab and Check now.
Read complete instructions on the tutorial: Disk Check
Other Tests:
Temp Monitoring
Check for heating issues using Speccy or HWMonitor.
- Speccy - System Information - Free Download
- HWMonitor CPUID - System & hardware benchmark, monitoring, reporting
Upload a screen shot with either of the tools: Screenshots and Files - Upload and Post in Seven Forums
Did all of the tests that you mentioned and disabled something called "File Association Helped" from running on start up, checked my SSD and hard drive and there was no problems on either. Also uploaded a screenshot of CPUID HWMonitor.
Thanks for help.
Quote