New
#11
Blue Screen of Death (BSOD) Posting Instructions
Use code tags when you paste the output
Attachment 385960
Blue Screen of Death (BSOD) Posting Instructions
Use code tags when you paste the output
Attachment 385960
Unfortunately, I'm having more crashes --
Code:******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck D1, {fffff880091289d0, 2, 0, fffff88005d3e420} *** WARNING: Unable to verify timestamp for AvidMboxPro.sys *** ERROR: Module load completed but symbols could not be loaded for AvidMboxPro.sys Probably caused by : AvidMboxPro.sys ( AvidMboxPro+1b420 ) Followup: MachineOwner --------- ************* Symbol Path validation summary ************** Response Time (ms) Location Deferred srv* 1: kd> .reload Loading Kernel Symbols ............................................................... ................................................................ ........................................ Loading User Symbols Loading unloaded module list ...... ************* Symbol Path validation summary ************** Response Time (ms) Location Deferred SRV*C:\symbols*http://msdl.microsoft.com/download/symbols 1: kd> .reload Loading Kernel Symbols ............................................................... ................................................................ ........................................ Loading User Symbols Loading unloaded module list ...... 1: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1) An attempt was made to access a pageable (or completely invalid) address at an interrupt request level (IRQL) that is too high. This is usually caused by drivers using improper addresses. If kernel debugger is available get stack backtrace. Arguments: Arg1: fffff880091289d0, memory referenced Arg2: 0000000000000002, IRQL Arg3: 0000000000000000, value 0 = read operation, 1 = write operation Arg4: fffff88005d3e420, address which referenced memory Debugging Details: ------------------ *** WARNING: Unable to verify timestamp for AvidMboxPro.sys *** ERROR: Module load completed but symbols could not be loaded for AvidMboxPro.sys DUMP_CLASS: 1 DUMP_QUALIFIER: 400 BUILD_VERSION_STRING: 7601.23392.amd64fre.win7sp1_ldr.160317-0600 SYSTEM_MANUFACTURER: Hewlett-Packard SYSTEM_PRODUCT_NAME: s5610y SYSTEM_SKU: BM414AA#ABA BIOS_VENDOR: American Megatrends Inc. BIOS_VERSION: 6.03 BIOS_DATE: 08/13/2010 BASEBOARD_MANUFACTURER: FOXCONN BASEBOARD_PRODUCT: 2AB7 BASEBOARD_VERSION: 1.00 DUMP_TYPE: 2 BUGCHECK_P1: fffff880091289d0 BUGCHECK_P2: 2 BUGCHECK_P3: 0 BUGCHECK_P4: fffff88005d3e420 READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80003cfa100 Unable to get MmSystemRangeStart fffff880091289d0 CURRENT_IRQL: 2 FAULTING_IP: AvidMboxPro+1b420 fffff880`05d3e420 418b07 mov eax,dword ptr [r15] CPU_COUNT: 2 CPU_MHZ: bb0 CPU_VENDOR: AuthenticAMD CPU_FAMILY: 10 CPU_MODEL: 6 CPU_STEPPING: 3 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT BUGCHECK_STR: 0xD1 PROCESS_NAME: System ANALYSIS_SESSION_HOST: HP-PC ANALYSIS_SESSION_TIME: 04-30-2016 22:29:34.0113 ANALYSIS_VERSION: 10.0.10586.567 amd64fre TRAP_FRAME: fffff8800331b510 -- (.trap 0xfffff8800331b510) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=00000000000001e0 rbx=0000000000000000 rcx=0000000000000040 rdx=0000000000000002 rsi=0000000000000000 rdi=0000000000000000 rip=fffff88005d3e420 rsp=fffff8800331b6a0 rbp=00000000007fffff r8=0000000000000000 r9=0000000000000024 r10=fffff880091289d0 r11=fffff88005e4e560 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl nz na pe nc AvidMboxPro+0x1b420: fffff880`05d3e420 418b07 mov eax,dword ptr [r15] ds:00000000`00000000=???????? Resetting default scope LAST_CONTROL_TRANSFER: from fffff80003abd929 to fffff80003abe380 STACK_TEXT: fffff880`0331b3c8 fffff800`03abd929 : 00000000`0000000a fffff880`091289d0 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx fffff880`0331b3d0 fffff800`03abc5a0 : fffffa80`08d4abc0 fffff880`00e90715 fffffa80`08d4abc0 00000000`00000008 : nt!KiBugCheckDispatch+0x69 fffff880`0331b510 fffff880`05d3e420 : 0000057f`f72b5438 fffffa80`08d21fc0 00000000`00000000 fffff880`04c10178 : nt!KiPageFault+0x260 fffff880`0331b6a0 0000057f`f72b5438 : fffffa80`08d21fc0 00000000`00000000 fffff880`04c10178 fffffa80`08038b00 : AvidMboxPro+0x1b420 fffff880`0331b6a8 fffffa80`08d21fc0 : 00000000`00000000 fffff880`04c10178 fffffa80`08038b00 fffffa80`08d4abc0 : 0x0000057f`f72b5438 fffff880`0331b6b0 00000000`00000000 : fffff880`04c10178 fffffa80`08038b00 fffffa80`08d4abc0 00000000`00000000 : 0xfffffa80`08d21fc0 STACK_COMMAND: kb THREAD_SHA1_HASH_MOD_FUNC: 442e2c46868cab74ff37a322837f78c1ba50ccc3 THREAD_SHA1_HASH_MOD_FUNC_OFFSET: f76bea7f3d8f4a875ffca83422665a3cd6408f85 THREAD_SHA1_HASH_MOD: 9f9fadb510acaa3a2c4e819d685427a7723832bf FOLLOWUP_IP: AvidMboxPro+1b420 fffff880`05d3e420 418b07 mov eax,dword ptr [r15] FAULT_INSTR_CODE: c1078b41 SYMBOL_STACK_INDEX: 3 SYMBOL_NAME: AvidMboxPro+1b420 FOLLOWUP_NAME: MachineOwner MODULE_NAME: AvidMboxPro IMAGE_NAME: AvidMboxPro.sys DEBUG_FLR_IMAGE_TIMESTAMP: 5335acc3 FAILURE_BUCKET_ID: X64_0xD1_AvidMboxPro+1b420 BUCKET_ID: X64_0xD1_AvidMboxPro+1b420 PRIMARY_PROBLEM_CLASS: X64_0xD1_AvidMboxPro+1b420 TARGET_TIME: 2016-04-26T08:10:48.000Z OSBUILD: 7601 OSSERVICEPACK: 1000 SERVICEPACK_NUMBER: 0 OS_REVISION: 0 SUITE_MASK: 784 PRODUCT_TYPE: 1 OSPLATFORM_TYPE: x64 OSNAME: Windows 7 OSEDITION: Windows 7 WinNt (Service Pack 1) TerminalServer SingleUserTS Personal OS_LOCALE: USER_LCID: 0 OSBUILD_TIMESTAMP: 2016-03-17 14:43:02 BUILDDATESTAMP_STR: 160317-0600 BUILDLAB_STR: win7sp1_ldr BUILDOSVER_STR: 6.1.7601.23392.amd64fre.win7sp1_ldr.160317-0600 ANALYSIS_SESSION_ELAPSED_TIME: 416d ANALYSIS_SOURCE: KM FAILURE_ID_HASH_STRING: km:x64_0xd1_avidmboxpro+1b420 FAILURE_ID_HASH: {b22be8ef-114b-0c1b-0202-b202db686ec9} Followup: MachineOwner
Last edited by TheSolution123; 01 May 2016 at 04:32. Reason: added attachment
I'm wondering why you reload a few times?
Although you need the software, it is clear that the drivers are causing you crashes, I recommend to remove it.
If I remove the drivers then I cannot use my Avid Mbox Pro soundcard.
I have the latest drivers and it should work with my system, according to Avid.
Reload what?
The symbols, what for did you reload the symbols twice?
Could you check Windows Update againCode:1: kd> .reload
Code:Hotfix(s): N/A
I don't know what happened- I was trying to set the symbol file path.
Windows updates -- I have them ALL except 5 optional ones.
For the configuration of Windbg, follow step 3 of the tutorial
WinDBG - Install and Configure for BSOD Analysis
Code:Loading Dump File [C:\Windows\Minidump\050116-20092-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available ************* Symbol Path validation summary ************** Response Time (ms) Location Deferred SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7601.23392.amd64fre.win7sp1_ldr.160317-0600 Machine Name: Kernel base = 0xfffff800`03a08000 PsLoadedModuleList = 0xfffff800`03c4a730 Debug session time: Sun May 1 01:49:07.247 2016 (UTC - 7:00) System Uptime: 0 days 0:56:15.190 Loading Kernel Symbols ............................................................... ................................................................ ...................................... Loading User Symbols Loading unloaded module list ....... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck D1, {fffff88003c9fad0, 2, 0, fffff88007c90420} *** WARNING: Unable to verify timestamp for AvidMboxPro.sys *** ERROR: Module load completed but symbols could not be loaded for AvidMboxPro.sys Probably caused by : AvidMboxPro.sys ( AvidMboxPro+1b420 ) Followup: MachineOwner ---------