BSOD on new components need help finding out why?

writhziden · 28 Feb 2012

Yes, updating the BIOS is recomended. Download your current version as well just in case you need to revert back.

Mikewix · 01 Mar 2012

another one...

writhziden · 01 Mar 2012

Code:


Loading Dump File [D:\Kingston\BSODDmpFiles\Mikewix\Windows_NT6_BSOD_jcgriff2\022912-27627-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02a15000 PsLoadedModuleList = 0xfffff800`02c5a670
Debug session time: Wed Feb 29 10:04:05.656 2012 (UTC - 7:00)
System Uptime: 0 days 1:32:54.248
Loading Kernel Symbols
...............................................................
................................................................
...........................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {ffffffffc0000005, fffff88004078f66, 0, ffffffffffffffff}

Probably caused by : USBPORT.SYS ( USBPORT!USBPORT_EndpointFromHandle+32 )

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

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

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: ffffffffc0000005, The exception code that was not handled
Arg2: fffff88004078f66, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: ffffffffffffffff, Parameter 1 of the exception

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
USBPORT!USBPORT_EndpointFromHandle+32
fffff880`04078f66 c3              ret

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  ffffffffffffffff

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cc4100
 ffffffffffffffff 

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

BUGCHECK_STR:  0x1E_c0000005

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80002add588 to fffff80002a91c40

STACK_TEXT:  
fffff800`00ba2448 fffff800`02add588 : 00000000`0000001e ffffffff`c0000005 fffff880`04078f66 00000000`00000000 : nt!KeBugCheckEx
fffff800`00ba2450 fffff800`02a912c2 : fffff800`00ba2c28 04083c7f`fffffa80 fffff800`00ba2cd0 fffffa80`0a359680 : nt! ?? ::FNODOBFM::`string'+0x4977d
fffff800`00ba2af0 fffff800`02a8fbca : 00000000`00000006 fffffa80`0687d7e8 fffffa80`095335c0 fffff880`040e3144 : nt!KiExceptionDispatch+0xc2
fffff800`00ba2cd0 fffff880`04078f66 : 07bc8050`fffff880 0a359680`fffffa80 0a1bdbc0`fffffa80 09533490`fffffa80 : nt!KiGeneralProtectionFault+0x10a
fffff800`00ba2e6c 07bc8050`fffff880 : 0a359680`fffffa80 0a1bdbc0`fffffa80 09533490`fffffa80 07bc8d28`fffffa80 : USBPORT!USBPORT_EndpointFromHandle+0x32
fffff800`00ba2e74 0a359680`fffffa80 : 0a1bdbc0`fffffa80 09533490`fffffa80 07bc8d28`fffffa80 040745c2`fffffa80 : 0x7bc8050`fffff880
fffff800`00ba2e7c 0a1bdbc0`fffffa80 : 09533490`fffffa80 07bc8d28`fffffa80 040745c2`fffffa80 068d1588`fffff880 : 0xa359680`fffffa80
fffff800`00ba2e84 09533490`fffffa80 : 07bc8d28`fffffa80 040745c2`fffffa80 068d1588`fffff880 00000022`fffffa80 : 0xa1bdbc0`fffffa80
fffff800`00ba2e8c 07bc8d28`fffffa80 : 040745c2`fffffa80 068d1588`fffff880 00000022`fffffa80 00000000`00000000 : 0x9533490`fffffa80
fffff800`00ba2e94 040745c2`fffffa80 : 068d1588`fffff880 00000022`fffffa80 00000000`00000000 ffffffff`00000000 : 0x7bc8d28`fffffa80
fffff800`00ba2e9c 068d1588`fffff880 : 00000022`fffffa80 00000000`00000000 ffffffff`00000000 07bc8d28`00000000 : 0x40745c2`fffffa80
fffff800`00ba2ea4 00000022`fffffa80 : 00000000`00000000 ffffffff`00000000 07bc8d28`00000000 04074f89`fffffa80 : 0x68d1588`fffff880
fffff800`00ba2eac 00000000`00000000 : ffffffff`00000000 07bc8d28`00000000 04074f89`fffffa80 07bc8050`fffff880 : 0x22`fffffa80


STACK_COMMAND:  kb

FOLLOWUP_IP: 
USBPORT!USBPORT_EndpointFromHandle+32
fffff880`04078f66 c3              ret

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  USBPORT!USBPORT_EndpointFromHandle+32

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: USBPORT

IMAGE_NAME:  USBPORT.SYS

DEBUG_FLR_IMAGE_TIMESTAMP:  4d8c0c08

FAILURE_BUCKET_ID:  X64_0x1E_c0000005_USBPORT!USBPORT_EndpointFromHandle+32

BUCKET_ID:  X64_0x1E_c0000005_USBPORT!USBPORT_EndpointFromHandle+32

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

Loading Dump File [D:\Kingston\BSODDmpFiles\Mikewix\Windows_NT6_BSOD_jcgriff2\022812-31153-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02a55000 PsLoadedModuleList = 0xfffff800`02c9a670
Debug session time: Tue Feb 28 13:51:44.981 2012 (UTC - 7:00)
System Uptime: 0 days 4:42:36.573
Loading Kernel Symbols
...............................................................
................................................................
...........................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa8007953028, b255c000, 175}

Probably caused by : hardware

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

3: 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: fffffa8007953028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000b255c000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000175, Low order 32-bits of the MCi_STATUS value.

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


BUGCHECK_STR:  0x124_AuthenticAMD

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  Skype.exe

CURRENT_IRQL:  f

STACK_TEXT:  
fffff880`02fdda88 fffff800`02a1ea3b : 00000000`00000124 00000000`00000000 fffffa80`07953028 00000000`b255c000 : nt!KeBugCheckEx
fffff880`02fdda90 fffff800`02be2513 : 00000000`00000001 fffffa80`07576ea0 00000000`00000000 fffffa80`07576ef0 : hal!HalBugCheckSystem+0x1e3
fffff880`02fddad0 fffff800`02a1e700 : 00000000`00000728 fffffa80`07576ea0 fffff880`02fdde30 fffffa80`0806ed00 : nt!WheaReportHwError+0x263
fffff880`02fddb30 fffff800`02a1e052 : fffffa80`07576ea0 fffff880`02fdde30 fffffa80`07576ea0 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff880`02fddc80 fffff800`02a11e8f : fffffa80`0ac8f010 00000000`00000001 fffff880`02fddeb0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff880`02fddcc0 fffff800`02ad052c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x47
fffff880`02fddcf0 fffff800`02ad0393 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`02fdde30 fffff880`066df8a3 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
fffff880`09088840 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : portcls!CPortFilterTopology::DeviceIoControl+0x12f


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_CACHE

BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_CACHE

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

USBPORT and 0x124 in the most recent crashes. Was the wireless device attached in both?

Mikewix · 01 Mar 2012

Ermmm, I'm pretty sure yeah, so what is the thing I'm gonna need to buy?

writhziden · 01 Mar 2012

What wireless network card do you recommend with Windows 7? may be helpful to follow.

Mikewix · 01 Mar 2012

Cheers dude, you've been really helpful I will try get my dad to fork out for one (im 15 y'see) ;D I will get back to you on any future updates :)

Dave76 · 03 Mar 2012

Are you going to replace (RMA) your RAM?

That is the most likely cause of your crashes.

Mikewix · 03 Mar 2012

I will look into it but its complicated because of it coming in a motherboard bundle and it is supposedly tested and tried for a long time by them so I'm not sure because they have had no complaints about it before?

Dave76 · 04 Mar 2012

Believe me, it wouldn't be the first time a OEM or computer shop made this kind of error.

It is a well known issue that Intel optimized RAM usually won't run on an AMD motherboard.
Actually AMD has started selling RAM under the AMD brand name (from third party RAM companies) to be sure AMD boards get the correct RAM.

If you have access to some known AMD RAM, running in a system, try installing it in your computer and see if there is a difference.
I have seen replacing Intel RAM with AMD RAM solve AMD system issues many times.

Mikewix · 04 Mar 2012

Okay I'll get them rung up and have a chat etc :)