BOSD while start using network(lan,wifi) via expl,fox - regular

[Pieohpah]

Hi,

I am getting constantly,regular BOSD when starting use network via explorer or firefox.
Appeared on wifi and wire network card. Also same when trying upgrade wifi drivers.

Strangely not happening when copying data in home network from another PCvia Total Commander.
Clearly could be damaged network controller, but two's (wifi and wire ) ?

Later managed to read dmp, not sure whre is problem, hardware ?

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\121415-16504-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: c:\Symbols;symsrv*symsrv.dll*C:\WindowsSymbols*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
Built by: 7601.18798.amd64fre.win7sp1_gdr.150316-1654
Machine Name:
Kernel base = 0xfffff800`02865000 PsLoadedModuleList = 0xfffff800`02aaa890
Debug session time: Mon Dec 14 22:05:58.006 2015 (UTC + 1:00)
System Uptime: 0 days 0:02:35.848
Loading Kernel Symbols
...............................................................
................................................................
.................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa8003730038, b2000040, 800}

Probably caused by : hardware

Followup: MachineOwner
---------

1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa8003730038, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000b2000040, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000800, Low order 32-bits of the MCi_STATUS value.

Debugging Details:
------------------


BUGCHECK_STR: 0x124_GenuineIntel

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: explorer.exe

CURRENT_IRQL: f

STACK_TEXT:
fffff880`009f39d8 fffff800`0282ea3b : 00000000`00000124 00000000`00000000 fffffa80`03730038 00000000`b2000040 : nt!KeBugCheckEx
fffff880`009f39e0 fffff800`029f19a3 : 00000000`00000001 fffffa80`03722620 00000000`00000000 fffffa80`03722670 : hal!HalBugCheckSystem+0x1e3
fffff880`009f3a20 fffff800`0282e700 : 00000000`00000728 fffffa80`03722620 fffff880`009f3db0 fffff880`009f3d00 : nt!WheaReportHwError+0x263
fffff880`009f3a80 fffff800`0282e052 : fffffa80`03722620 fffff880`009f3db0 fffffa80`03722620 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff880`009f3bd0 fffff800`0282df0d : 00000000`00000002 00000000`00000001 fffff880`009f3e30 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff880`009f3c10 fffff800`02821e88 : 00000000`0a5c0691 fffff880`047b4658 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
fffff880`009f3c40 fffff800`028d632c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff880`009f3c70 fffff800`028d6193 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`009f3db0 fffff800`028dd570 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
fffff880`047b4540 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeFlushMultipleRangeTb+0x260


STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: hardware

IMAGE_NAME: hardware

DEBUG_FLR_IMAGE_TIMESTAMP: 0

FAILURE_BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_BUS

BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_BUS

Followup: MachineOwner


Thank you for analyze
Petr

 

[axe0]

Hi Pieohpah,

The CPU send out a read request from the cache level 0 but there was no delay between another request.

BUSL0_SRC_ERR_M_NOTIMEOUT_ERR

This is persistent in the crashes.

Please check HP for BIOS updates

BIOS Version:              Hewlett-Packard 68PVU Ver. F.08, 9/24/2009

If a BIOS update doesn't help, monitor the CPU temperatures using Speccy



In case you want to know how we can get this data.
With a 0x124 we can use the !errrec command on the 'Address of the WHEA_ERROR_RECORD structure' parameter to find out what the problem is. The problem part is however different from the cause part, because a 0x124 usually doesn't reveal enough to find out what is causing problems. This is the reason why a 0x124 could be quite difficult to troubleshoot, it is a lot caused by hardware related what makes a 0x124 a hardware error.

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: [COLOR="red"]fffffa80037fe038[/COLOR], Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000b2000040, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000800, Low order 32-bits of the MCi_STATUS value.

In the result of the !errrec, I marked the part red that is important with a bus error.

0: kd> [COLOR="blue"]!errrec[/COLOR] [COLOR="red"]fffffa80037fe038[/COLOR]
===============================================================================
Common Platform Error Record @ fffffa80037fe038
-------------------------------------------------------------------------------
Record Id     : 01d13640293103e5
Severity      : Fatal (1)
Length        : 928
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 12/14/2015 18:15:05 (UTC)
Flags         : 0x00000000

===============================================================================
Section 0     : Processor Generic
-------------------------------------------------------------------------------
Descriptor    @ fffffa80037fe0b8
Section       @ fffffa80037fe190
Offset        : 344
Length        : 192
Flags         : 0x00000001 Primary
Severity      : Fatal

Proc. Type    : x86/x64
Instr. Set    : x64
[COLOR="Red"]Error Type    : BUS error[/COLOR]
Operation     : Generic
Flags         : 0x00
Level         : 0
CPU Version   : 0x00000000000006fd
Processor ID  : 0x0000000000000000

===============================================================================
Section 1     : x86/x64 Processor Specific
-------------------------------------------------------------------------------
Descriptor    @ fffffa80037fe100
Section       @ fffffa80037fe250
Offset        : 536
Length        : 128
Flags         : 0x00000000
Severity      : Fatal

Local APIC Id : 0x0000000000000000
CPU Id        : fd 06 00 00 00 08 02 00 - 9d e3 00 00 ff fb eb bf
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00

Proc. Info 0  @ fffffa80037fe250

===============================================================================
Section 2     : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor    @ fffffa80037fe148
Section       @ fffffa80037fe2d0
Offset        : 664
Length        : 264
Flags         : 0x00000000
Severity      : Fatal

[COLOR="Red"]Error         : BUSL0_SRC_ERR_M_NOTIMEOUT_ERR (Proc 0 Bank 0)[/COLOR]
  Status      : 0xb200004000000800