New
#1
Please help with the following BSOD 0x00000c4
attached files needed ,
Thanks in advanced!
L,
attached files needed ,
Thanks in advanced!
L,
Not seeing any stop 0xc4 BSOD in the dump you uploaded, but it is usually caused by Driver Verifier. Have you anyhow enabled Driver verifier for any reason? If so, disable driver verifier following the option 2 of the tutorial Driver Verifier - Enable and Disable
The Other crash dumps present in the zip are stop 0x3B, and they are pointing out to failing Intel graphics driver.
And the driver is very old.Code:fffff880`03750118 fffff880`04bb0774Unable to load image \SystemRoot\system32\DRIVERS\igdkmd64.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for igdkmd64.sys *** ERROR: Module load completed but symbols could not be loaded for igdkmd64.sys igdkmd64+0x1a3774
Update the Intel HD Graphics Driver, either from our forum link, Latest Intel HD Graphics Driver for Windows 7, or You may get it from Intel Download Center.Code:fffff880`04a0d000 fffff880`055b7100 igdkmd64 T (no symbols) Loaded symbol image file: igdkmd64.sys Image path: \SystemRoot\system32\DRIVERS\igdkmd64.sys Image name: igdkmd64.sys Timestamp: Fri Jun 10 23:46:00 2011 (4DF25F60) CheckSum: 00BB2563 ImageSize: 00BAA100 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
Moreover, you may run the Intel (R) Driver Update Utility to auto detect the appropriate driver for your computer.
I would also suggest to get rid of intel rapid storage. First uninstall it from Control Panel > Programs and Features. Then Uninstall the driver from device manager.
- Right click on "my computer" icon and click "manage" on the context menu.
- It will open the "computer management" window.
- Select "Device Manager" in the left pane, It will list all the existing devices up.
- Expand "IDE ATA/ATAPI controllers" by clicking on the triangle in front of it.
- Select one Intel device item under it, right click, uninstall.
- Continue the process for all Intel items under "IDE ATA/ATAPI controllers"
- Now restart the computer. At restart, windows will auto configure the appropriate native system driver.
Free up the startup. Windows does not need any other program to auto start with it, but the auto start programs often conflicts and causes various problems including BSODs.
- Click on the Start button
- Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
- Select the “Startup” tab.
- Deselect all items other than the antivirus.
- Apply > OK
- Accept then restart.
Let us know the results.
______________________________________________________________________________
BSOD ANALYSIS:
Code:.......... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 3B, {c0000005, fffff8800477fba4, fffff88008549640, 0} Probably caused by : dxgkrnl.sys ( dxgkrnl!VIDPN_MGR::AddFunctionalPathToVidPnTopology+4e4 ) Followup: MachineOwner --------- 1: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* SYSTEM_SERVICE_EXCEPTION (3b) An exception happened while executing a system service routine. Arguments: Arg1: 00000000c0000005, Exception code that caused the bugcheck Arg2: fffff8800477fba4, Address of the instruction which caused the bugcheck Arg3: fffff88008549640, Address of the context record for the exception that caused the bugcheck Arg4: 0000000000000000, zero. Debugging Details: ------------------ EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. FAULTING_IP: dxgkrnl!VIDPN_MGR::AddFunctionalPathToVidPnTopology+4e4 fffff880`0477fba4 44397d48 cmp dword ptr [rbp+48h],r15d CONTEXT: fffff88008549640 -- (.cxr 0xfffff88008549640) rax=0000000000000003 rbx=fffff8a009b45810 rcx=0000000000000001 rdx=fffffa8006de9800 rsi=0000000000000000 rdi=fffff8a00bde35f0 rip=fffff8800477fba4 rsp=fffff8800854a020 rbp=0000000000000000 r8=0000000000147c35 r9=0000000000000003 r10=0000000000000000 r11=fffff88004086120 r12=fffff8800854a360 r13=fffff8800854a4d0 r14=0000000000000000 r15=0000000000000001 iopl=0 nv up ei ng nz na po nc cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010286 dxgkrnl!VIDPN_MGR::AddFunctionalPathToVidPnTopology+0x4e4: fffff880`0477fba4 44397d48 cmp dword ptr [rbp+48h],r15d ss:0018:00000000`00000048=???????? Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT BUGCHECK_STR: 0x3B PROCESS_NAME: csrss.exe CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff8800477fba4 STACK_TEXT: fffff880`0854a020 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : dxgkrnl!VIDPN_MGR::AddFunctionalPathToVidPnTopology+0x4e4 FOLLOWUP_IP: dxgkrnl!VIDPN_MGR::AddFunctionalPathToVidPnTopology+4e4 fffff880`0477fba4 44397d48 cmp dword ptr [rbp+48h],r15d SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: dxgkrnl!VIDPN_MGR::AddFunctionalPathToVidPnTopology+4e4 FOLLOWUP_NAME: MachineOwner MODULE_NAME: dxgkrnl IMAGE_NAME: dxgkrnl.sys DEBUG_FLR_IMAGE_TIMESTAMP: 5164dc49 STACK_COMMAND: .cxr 0xfffff88008549640 ; kb FAILURE_BUCKET_ID: X64_0x3B_dxgkrnl!VIDPN_MGR::AddFunctionalPathToVidPnTopology+4e4 BUCKET_ID: X64_0x3B_dxgkrnl!VIDPN_MGR::AddFunctionalPathToVidPnTopology+4e4 Followup: MachineOwner ---------