BSOD on new components need help finding out why?

[writhziden]

022612-24429-01.dmp was another Hardware Stop 0x124. http://www.sevenforums.com/crash-lockup-debug-how/35349-stop-0x124-what-means-what-try.html

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


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

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 (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02a58000 PsLoadedModuleList = 0xfffff800`02c9d670
Debug session time: Sun Feb 26 04:58:06.591 2012 (UTC - 7:00)
System Uptime: 0 days 0:06:13.183
Loading Kernel Symbols
...............................................................
................................................................
...............................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa80074cd028, b6004000, 2a000175}

Unable to load image \SystemRoot\system32\DRIVERS\athurx.sys, Win32 error 0n2
[COLOR="red"][B]*** WARNING: Unable to verify timestamp for athurx.sys
*** ERROR: Module load completed but symbols could not be loaded for athurx.sys[/B][/COLOR]
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: fffffa80074cd028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000b6004000, High order 32-bits of the MCi_STATUS value.
Arg4: 000000002a000175, 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:  svchost.exe

CURRENT_IRQL:  f

STACK_TEXT:  
fffff880`02fdda88 fffff800`02a21a3b : 00000000`00000124 00000000`00000000 fffffa80`074cd028 00000000`b6004000 : nt!KeBugCheckEx
fffff880`02fdda90 fffff800`02be5513 : 00000000`00000001 fffffa80`07a44d30 00000000`00000000 fffffa80`07a44d80 : hal!HalBugCheckSystem+0x1e3
fffff880`02fddad0 fffff800`02a21700 : 00000000`00000728 fffffa80`07a44d30 fffff880`02fdde30 fffffa80`08651a00 : nt!WheaReportHwError+0x263
fffff880`02fddb30 fffff800`02a21052 : fffffa80`07a44d30 fffff880`02fdde30 fffffa80`07a44d30 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff880`02fddc80 fffff800`02a14e8f : fffffa80`08668a90 00000000`00000001 fffff880`02fddeb0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff880`02fddcc0 fffff800`02ad352c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x47
fffff880`02fddcf0 fffff800`02ad3393 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`02fdde30 fffff880`0461b805 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
fffff880`009b0a10 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : [COLOR="Red"][B]athurx+0x9805[/B][/COLOR]


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
---------

Ah, but the preceding one was actually due to your wireless USB adapter... I think we've narrowed down the hardware crashes as well to your USB adapter.

 

[Mikewix]

So its more than likely the adapter, it must have a problem with this OS then because it was great on my previous computers vista?

 

[writhziden]

Many of the adapters that worked in Vista do not work in 7. In most cases the drivers have not been updated to work with 7, but I do not know if that is the case with your adapter. It appears to have the proper drivers. It's possible that Windows 7 does something different with the power constraints for wireless adapters, and the USB connection is not enough to handle it.

 

[Mikewix]

Another error report here could be different not sure :/

 

[writhziden]

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


Loading Dump File [D:\Kingston\BSODDmpFiles\Mikewix\Windows_NT6_BSOD_jcgriff2\022712-28563-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`02a1e000 PsLoadedModuleList = 0xfffff800`02c63670
Debug session time: Mon Feb 27 15:57:20.822 2012 (UTC - 7:00)
System Uptime: 0 days 7:12:19.414
Loading Kernel Symbols
...............................................................
................................................................
.............................
Loading User Symbols
Loading unloaded module list
...........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {28, 2, 0, fffff880044025cd}

Probably caused by : USBPORT.SYS ( USBPORT!USBPORT_Xdpc_iSetState+35 )

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

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: 0000000000000028, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff880044025cd, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ccd100
 0000000000000028 

CURRENT_IRQL:  2

FAULTING_IP: 
USBPORT!USBPORT_Xdpc_iSetState+35
fffff880`044025cd 4c394a28        cmp     qword ptr [rdx+28h],r9

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  System

TRAP_FRAME:  fffff88002f1bae0 -- (.trap 0xfffff88002f1bae0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=00000000ffffffff
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880044025cd rsp=fffff88002f1bc70 rbp=fffffa8009b062b0
 r8=fffffa8007c7b1a0  r9=0000000000000000 r10=00000000ffffffff
r11=fffffa8007c7b1a0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
USBPORT!USBPORT_Xdpc_iSetState+0x35:
fffff880`044025cd 4c394a28        cmp     qword ptr [rdx+28h],r9 ds:ffff:00000000`00000028=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002a9a1e9 to fffff80002a9ac40

STACK_TEXT:  
fffff880`02f1b998 fffff800`02a9a1e9 : 00000000`0000000a 00000000`00000028 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`02f1b9a0 fffff800`02a98e60 : fffffa80`09741730 fffffa80`07c7b101 00000000`00000002 fffffa80`07c7bd28 : nt!KiBugCheckDispatch+0x69
fffff880`02f1bae0 fffff880`044025cd : fffff880`009eef40 00000000`00000022 00000000`00000000 00000000`ffffffff : nt!KiPageFault+0x260
fffff880`02f1bc70 fffff880`04402f89 : fffffa80`07c7b050 00000000`00000000 fffffa80`07c7bd02 fffffa80`07c7bd28 : USBPORT!USBPORT_Xdpc_iSetState+0x35
fffff880`02f1bca0 fffff800`02aa60ac : fffff880`009ea180 fffffa80`07c7bd28 fffffa80`07c7bd40 00000000`00000000 : USBPORT!USBPORT_Xdpc_Worker+0x1d9
fffff880`02f1bcd0 fffff800`02a9296a : fffff880`009ea180 fffff880`009f4fc0 00000000`00000000 fffff880`04402db0 : nt!KiRetireDpcList+0x1bc
fffff880`02f1bd80 00000000`00000000 : fffff880`02f1c000 fffff880`02f16000 fffff880`02f1bd40 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
USBPORT!USBPORT_Xdpc_iSetState+35
fffff880`044025cd 4c394a28        cmp     qword ptr [rdx+28h],r9

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  USBPORT!USBPORT_Xdpc_iSetState+35

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: USBPORT

IMAGE_NAME:  USBPORT.SYS

DEBUG_FLR_IMAGE_TIMESTAMP:  4d8c0c08

FAILURE_BUCKET_ID:  X64_0xD1_USBPORT!USBPORT_Xdpc_iSetState+35

BUCKET_ID:  X64_0xD1_USBPORT!USBPORT_Xdpc_iSetState+35

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

USB related crash. Different from the hardware crash, but still likely due to the USB wireless...
You did have a few more of the 0x124 crashes, as well.

 

[Dave76]

After looking at your CPUZ tabs, there are a couple things that may be causing your crash issues.

View attachment 200716
View attachment 200715 View attachment 200714

Your motherboard site Gigabyte GA-A55M-DS2 is showing a RAM fix (may not apply), Update CPU code and Improve system compatibility, BIOS updates. Newest version is F6, never use any Beta BIOS.
Don't like to recommend updating BIOS unless absolutely necessary, so may come back to this later.

Searching your RAM didn't find the exact match on the G. Skill site but, the other F3-12800CL9D-4GBXL and F3-12800CL9Q-16GBXL, XL part numbers are 'Designed For 2nd Generation Intel® Core™ Processors'.
This is a known issue for AMD systems, there is no mention of these kits being able to run on an AMD system and no mention of any AMD boards as compatible.
The 'XMP' listing on the CPUZ tab was the indication that these are Intel optimized RAM as 'XMP' is an Intel RAM timing setting.
Also no listing of the Mode, which should be 'Unganged', no NB frequency listed.
These are all important as there is another known issue with AMD systems and RAM frequency above 1333MHz.
I hope AMD has got this sorted out by now but, haven't seen any confirmation yet.

Can you RMA the RAM and get AMD RAM for your system?

This would be the first thing to do, with compatible RAM your system will be more stable and hopefully solve the crashing issues.

 

[Mikewix]

Well I actually bought it as a motherboard bundle from a trusted shop called CCL online and I have a 3 year warranty etc

http://www.cclonline.com/product/73...L-Elite-Eos-Motherboard-Bundle/MBB-AMDEL-ENT/

 

[Mikewix]

Would it be an idea to remove my adapter and clock it back up to default settings and play a few games to stress test it?

 

[writhziden]

I think that is a good idea. Load Setup Defaults in the BIOS and remove the USB adapter. See if it runs stable.

I think it is a good idea to look into the RAM compatibility as well.

 

[Mikewix]

Should I update my BIOS It only seems to make sense, is there any reason not to?

 

[writhziden]

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

 

[Mikewix]

another one...

 

[writhziden]

[list=1]
[*]
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
---------


[/list]

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

 

[Mikewix]

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

 

[writhziden]

http://www.sevenforums.com/hardware...etwork-card-do-you-recommend-windows-7-a.html may be helpful to follow.

 

[Mikewix]

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]

Are you going to replace (RMA) your RAM?

That is the most likely cause of your crashes.

 

[Mikewix]

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]

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]

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