New
#11
Am not running Daemon Tools. SmuroOfNeves - I do not currently have SPD installed. To clarify, you want me to download that SPD program and install or you want it not on my PC in which case I do not need to do anything?
Am not running Daemon Tools. SmuroOfNeves - I do not currently have SPD installed. To clarify, you want me to download that SPD program and install or you want it not on my PC in which case I do not need to do anything?
Latest BSOD and dump file.
Also, this morning I had "This Driver cannot release to failure!!" error box upon boot to Windows. Google says that has to do with Gigabyte Easy Tune 6 which I have removed. Seems to cause no issues, but I'd like to get rid of the box.
Do not have DAEMON TOOLS so I downloaded and ran that STPD programme. Not sure if it has had any effect.
I think I misread your remarks re SPD and Daemon Tools. Will uninstall SPD tonight.
Gentlemen, do you think I should attempt a firmware update for my BIOS?
http://www.gigabyte.com/products/product-page.aspx?pid=3423#bios
I am thinking f4, perhaps? I don't want to run a beta like f5a.
Also, should I be running a BIOS update for the motherboard as listed on their site or should I be looking for BIOS update for the BIOS itself which is Award Modular BIOS v6.00PG.
Your HDAudBus.sys, sound driver is the cause, please update to the latest version
Code:******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1E, {ffffffffc000001d, fffff880051a0cb0, 0, fffffa8005780700} Probably caused by : HDAudBus.sys ( HDAudBus!GetChildDeviceExtension+10 ) KMODE_EXCEPTION_NOT_HANDLED (1e) 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. Arguments: Arg1: ffffffffc000001d, The exception code that was not handled Arg2: fffff880051a0cb0, The address that the exception occurred at Arg3: 0000000000000000, Parameter 0 of the exception Arg4: fffffa8005780700, Parameter 1 of the exception Debugging Details: ------------------ EXCEPTION_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION} Illegal Instruction An attempt was made to execute an illegal instruction. FAULTING_IP: HDAudBus!GetChildDeviceExtension+10 fffff880`051a0cb0 488b4c2430 mov rcx,qword ptr [rsp+30h] EXCEPTION_PARAMETER1: 0000000000000000 EXCEPTION_PARAMETER2: fffffa8005780700 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x1E PROCESS_NAME: System CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from fffff80002ee65d8 to fffff80002e9ad00 FAILED_INSTRUCTION_ADDRESS: HDAudBus!GetChildDeviceExtension+10 fffff880`051a0cb0 488b4c2430 mov rcx,qword ptr [rsp+30h] STACK_TEXT: fffff880`04519fb8 fffff800`02ee65d8 : 00000000`0000001e ffffffff`c000001d fffff880`051a0cb0 00000000`00000000 : nt!KeBugCheckEx fffff880`04519fc0 fffff800`02e9a382 : fffff880`0451a798 00000000`00000001 fffff880`0451a840 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x4987d fffff880`0451a660 fffff800`02e984df : fffff880`0451a840 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatch+0xc2 fffff880`0451a840 fffff880`051a0cb0 : fffff880`051ad9cb fffffa80`05b92788 fffff800`02e9f4aa 00000000`00000001 : nt!KiInvalidOpcodeFault+0x11f fffff880`0451a9d8 00000000`00000000 : 00000000`00000000 10020001`00000000 fffff880`009e8180 00000000`00000000 : HDAudBus!GetChildDeviceExtension+0x10 STACK_COMMAND: kb FOLLOWUP_IP: HDAudBus!GetChildDeviceExtension+10 fffff880`051a0cb0 488b4c2430 mov rcx,qword ptr [rsp+30h] SYMBOL_STACK_INDEX: 4 SYMBOL_NAME: HDAudBus!GetChildDeviceExtension+10 FOLLOWUP_NAME: MachineOwner MODULE_NAME: HDAudBus IMAGE_NAME: HDAudBus.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4ce7a65e FAILURE_BUCKET_ID: X64_0x1E_BAD_IP_HDAudBus!GetChildDeviceExtension+10 BUCKET_ID: X64_0x1E_BAD_IP_HDAudBus!GetChildDeviceExtension+10 Followup: MachineOwner ---------
Updated the drivers, and so far so good. Will post again if it starts BSODing again. Thanks very much! I appreciate it!