BSOD Diagnosis

[SenojNW]

I have just started to get the occasional BSOD on Win7 64 Ultimate after installing some Windows updates a couple of days ago. I was installing these updates (in this order):

KB980182, KB976264, KB977863, KB978637, KB979099, KB980302.

I think I got the BSOD during KB980182. The updates succeeded installing after trying a second time.

It then gave me a BSOD while running Windows Media Player (music) and then as I started to run System Restore (to wind back the Windows Updates). After the second one I managed to get System Restore to work and rolled back to my pre-update system state. I then installed the updates again without any BSOD.

Since then I have had one BSOD as I selected "shut down" yesterday.

This all seemed to start with the updates but I would like to rule out hardware too?

Any advice appreciated. Error logs below. I don't know how to read them.

1st:

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.1
Locale ID: 3081

Additional information about the problem:
BCCode: a
BCP1: 0000000000000000
BCP2: 0000000000000002
BCP3: 0000000000000000
BCP4: FFFFF80001875AFB
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

2nd:

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.1
Locale ID: 3081

Additional information about the problem:
BCCode: 27
BCP1: 00000000BAAD0073
BCP2: FFFFF88008DEEC58
BCP3: FFFFF88008DEE4B0
BCP4: FFFFF8800182C07C
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

 

[SenojNW]

Here's the latest minidump file if that helps???

 

[SenojNW]

Anyone?

Appreciated if someone could take a look at the error reports and minidump and post some pointers...

 

[Capt.Jack Sparrow]

Here's the latest minidump file if that helps???

Hello Senoj Welcome to SF !!

The Dump is pointing to usbhub.sys that has casued the crash. But since you said that the update has caused the crash try to do a System Restore see whether that fixes the problem.

Run the Memory Diagnostic & HD Diagnostic

Also i would recommend to run System Integrity Checker
Start > Run > CMD >Right Click and Run as administrator > SFC/ SCANNOW

IRQL_NOT_LESS_OR_EQUAL (a)
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 a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000000000000000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, bitfield :
 bit 0 : value 0 = read operation, 1 = write operation
 bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff800018d24dc, address which referenced memory
Debugging Details:
------------------
 
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80001b050e0
 0000000000000000 
CURRENT_IRQL:  2
FAULTING_IP: 
nt!KeWaitForMultipleObjects+202
fffff800`018d24dc 488908          mov     qword ptr [rax],rcx
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
TRAP_FRAME:  fffff880089e7430 -- (.trap 0xfffff880089e7430)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffffa8005007c68
rdx=fffffa80053cc1e0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800018d24dc rsp=fffff880089e75c0 rbp=fffffa8005007c80
 r8=fffff880089e78b0  r9=0000000000000001 r10=0000000000000002
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!KeWaitForMultipleObjects+0x202:
fffff800`018d24dc 488908          mov     qword ptr [rax],rcx ds:00000000`00000000=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER:  from fffff800018ce469 to fffff800018cef00
STACK_TEXT:  
fffff880`089e72e8 fffff800`018ce469 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`089e72f0 fffff800`018cd0e0 : 00000000`00000002 0000002a`e9ebf229 00000000`00000004 fffff800`01a022dd : nt!KiBugCheckDispatch+0x69
fffff880`089e7430 fffff800`018d24dc : 00000000`00000008 fffff800`0191a65c 00000000`00000001 00000000`00000009 : nt!KiPageFault+0x260
fffff880`089e75c0 fffff880`03e966c9 : 00000000`00000002 fffff880`089e78d0 0000002a`00000001 fffffa80`00000000 : nt!KeWaitForMultipleObjects+0x202
fffff880`089e7870 fffff880`03ea15bd : fffffa80`053cc000 fffffa80`053cc1d8 fffffa80`053cc000 fffffa80`0523a050 : usbhub!UsbhWaitEventWithTimeoutEx+0x279
fffff880`089e7920 fffff880`03ea0bd8 : 00000000`00000000 fffffa80`50447100 fffffa80`053cc000 00000000`00080000 : usbhub!Usbh_PCE_Disable_Action+0x4f1
fffff880`089e7980 fffff880`03ea5f7c : fffffa80`0523a050 00000000`00000001 00000000`00000001 fffffa80`0523a708 : usbhub!UsbhDispatch_PortChangeQueueEventEx+0x110
fffff880`089e79c0 fffff880`03e9e744 : fffffa80`0523a050 fffffa80`053cc000 fffffa80`053cc000 00000000`00000000 : usbhub!UsbhPCE_Disable+0xb4
fffff880`089e7a10 fffff880`03e9da3c : 00000000`00000007 00000000`00000003 fffffa80`0523a050 fffffa80`0523a708 : usbhub!UsbhBusPause_Action+0x184
fffff880`089e7a60 fffff880`03e9deb6 : fffffa80`0523a1a0 00000000`00000007 fffffa80`0523a050 00000000`00000000 : usbhub!Usbh_BS_BusRun+0x94
fffff880`089e7aa0 fffff880`03e9e92b : 00000000`00000003 fffffa80`0523a708 fffffa80`0523a050 00000000`00000000 : usbhub!UsbhDispatch_BusEvent+0x20e
fffff880`089e7af0 fffff880`03eb334a : fffffa80`04d4df70 fffffa80`05e9ef80 fffffa80`05e9ef80 fffffa80`04d4df70 : usbhub!UsbhSyncBusPause+0x4f
fffff880`089e7b30 fffff880`03eb1a7a : fffffa80`0523a050 fffffa80`0523a708 fffffa80`0523a708 00000000`00000004 : usbhub!UsbhFdoSetPowerDx_Action+0x9a
fffff880`089e7b90 fffff880`03eb070b : fffffa80`04d4df70 fffffa80`0523a1a0 fffffa80`0523a050 fffffa80`04d4de10 : usbhub!UsbhFdoDevicePowerState+0x206
fffff880`089e7be0 fffff880`03eaf9c7 : fffffa80`04d4de10 00000000`00000000 fffffa80`0523a050 fffff880`089e7d40 : usbhub!UsbhFdoPower_SetPower+0x93
fffff880`089e7c20 fffff880`03e96fdf : 00000000`00000001 fffffa80`0523a050 fffff880`089e7d40 fffffa80`04f24c10 : usbhub!UsbhFdoPower+0xaf
fffff880`089e7c60 fffff800`019e8e55 : 00000000`00000000 00000000`00000002 00000000`00000001 fffffa80`04d4deb8 : usbhub!UsbhGenDispatch+0x7f
fffff880`089e7c90 fffff800`01b72166 : ffffffff`fa0a1f00 fffffa80`05007b60 00000000`00000080 00000000`00000000 : nt!PopIrpWorker+0x3c5
fffff880`089e7d40 fffff800`018ad486 : fffff880`01e5d180 fffffa80`05007b60 fffffa80`03a32b60 00000000`00000246 : nt!PspSystemThreadStartup+0x5a
fffff880`089e7d80 00000000`00000000 : fffff880`089e8000 fffff880`089e2000 fffff880`089e79e0 00000000`00000000 : nt!KxStartSystemThread+0x16
 
STACK_COMMAND:  kb
FOLLOWUP_IP: 
usbhub!UsbhWaitEventWithTimeoutEx+279
fffff880`03e966c9 8be8            mov     ebp,eax
SYMBOL_STACK_INDEX:  4
SYMBOL_NAME:  usbhub!UsbhWaitEventWithTimeoutEx+279
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: usbhub
IMAGE_NAME:  usbhub.sys
DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bcc2d
FAILURE_BUCKET_ID:  X64_0xA_usbhub!UsbhWaitEventWithTimeoutEx+279
BUCKET_ID:  X64_0xA_usbhub!UsbhWaitEventWithTimeoutEx+279
Followup: MachineOwner

Hope this helps,
Captain

 

[SenojNW]

Thanks very much Captain!
I just ran your diagnostics tool and have attached the results of that too (minus the full dump file which was >100Mb) - just incase it provides more useful info.

I will try running those tests. So does this look like a driver rather then a hardware issue to you?

I've got those Win updates re-installed now and it hasn't had a BSOD for >24h so I might just leave it a bit longer and see if I get another BSOD.

 

[Capt.Jack Sparrow]

Thanks very much Captain!
I just ran your diagnostics tool and have attached the results of that too (minus the full dump file which was >100Mb) - just incase it provides more useful info.

I will try running those tests. So does this look like a driver rather then a hardware issue to you?

I've got those Win updates re-installed now and it hasn't had a BSOD for >24h so I might just leave it a bit longer and see if I get another BSOD.

Hello,

It's very less change to be Hardware issue but just to be on a Safe side i asked to run the Hardware diagnostics. Sinces its USB driver its pointing to it's worth update the Chipset drivers to make sure nothing is wrong with it. Here is the listing

VIA Rev 5 or later USB Universal Host Controller PCI\VEN_1106&DEV_3038&SUBSYS_30381106&REV_61\4&126EEA74&0&11F0
VIA USB Enhanced Host Controller PCI\VEN_1106&DEV_3104&SUBSYS_31041106&REV_63\4&126EEA74&0&12F0
Intel(R) 5 Series/3400 Series Chipset Family USB Enhanced Host Controller - 3B34 PCI\VEN_8086&DEV_3B34&SUBSYS_0DD4105B&REV_06\3&11583659&0&E8
Intel(R) 5 Series/3400 Series Chipset Family USB Enhanced Host Controller - 3B3C PCI\VEN_8086&DEV_3B3C&SUBSYS_0DD4105B&REV_06\3&11583659&0&D0
VIA Rev 5 or later USB Universal Host Controller PCI\VEN_1106&DEV_3038&SUBSYS_30381106&REV_61\4&126EEA74&0&10F0

Event Veiwer Logs

Event[381]:
  Log Name: Application
  Source: Windows Error Reporting
  Date: 2010-04-02T09:24:30.000
  Event ID: 1001
  Task: N/A
  Level: Information
  Opcode: Info
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: HTPC
  Description: 
Fault bucket X64_0x27_[B][FONT=Tahoma][COLOR=red]avgtdia!AvgTdiLookupTableEntry[/COLOR][/FONT][/B]+10, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

As you can see the Stack (avgtdia!AvgTdiLookupTableEntry) is pointing to AVG i would strongly recommend to uninstall that completetly. Since you had some faliures on Windows Update specifically CbsPackageServicingFailure2 Description of the System Update Readiness Tool for Windows Vista, for Windows Server 2008, for Windows 7, and for Windows Server 2008 R2 follow this Microsoft Document. It is System resources, such as file data, registry data, and even in-memory data, can develop inconsistencies during the lifetime of the operating system. These inconsistencies might be caused by various hardware failures or might be caused by software issues. In some cases, these inconsistencies can affect the Windows servicing store, and they can cause software updates not to work. The System Update Readiness Tool tries to resolve these inconsistencies.

Try these steps out and let us know how it goes !!

Hope this helps,
Captain

 

[SenojNW]

Uh oh...

I ran Memtest86 for a few hours last night and got these results attached. It didn't have any errors on the 4th pass though? Might run it again tonight.

Strange though that the error reports are pointing to driver issues - could it be both hardware and software causing this?

No BSOD for 2 days now by the way!

Your thoughts Captain?

 

[Capt.Jack Sparrow]

Uh oh...

I ran Memtest86 for a few hours last night and got these results attached. It didn't have any errors on the 4th pass though? Might run it again tonight.

Strange though that the error reports are pointing to driver issues - could it be both hardware and software causing this?

No BSOD for 2 days now by the way!

Your thoughts Captain?

Well it looks like Bad Memory !! I don't believe there is a way where we can fix it !! But if you never had BSOD then leave it alone. Only if you have issues then consider replacing it !!

Hope this helps,
Captain

 

[SenojNW]

Thanks Captain
Seeing the error reports are indicating multiple sources (USB driver, AVG etc.) do you think it's the bad RAM causing these software crashes? Might explain why the reports are indicating multiple sources rather than pointing to a single problem driver? Or do the error reports ever point to the RAM as a cause?

 

[Capt.Jack Sparrow]

Thanks Captain
Seeing the error reports are indicating multiple sources (USB driver, AVG etc.) do you think it's the bad RAM causing these software crashes? Might explain why the reports are indicating multiple sources rather than pointing to a single problem driver? Or do the error reports ever point to the RAM as a cause?

Yup .. I think it might be the RAM that was crashing other programs. But i suggested others because if its program it's less expensive that getting a hardware component. So its best to troubleshoot software and see whether that fixes the issue if not then go to hardware.

Hope this helps,
Captain