0x00000124 bluescreen error when playing guild wars 2

amodi103 · Dec 21, 2014

I believe it's a problem with the amd driver but was unsure on what to do, will attach minidump and sf files. This forum has been very helpful to me in the past and I know it will be and thank you for all of your help.

The computer has rebooted from a bugcheck. The bugcheck was: 0x00000124 (0x0000000000000000, 0xffffe000e3567588, 0x0000000000000000, 0x0000000000000000). A dump was saved in: C:\Windows\Minidump\122114-16046-01.dmp. Report Id: 122114-16046-01.
A fatal hardware error has occurred.

Component: AMD Northbridge
Error Source: Machine Check Exception
Error Type: 11
Processor APIC ID: 0

blueelvis · Dec 22, 2014

Hi Amodi103 & Welcome to the forums ^_^,

I have analysed your dump files and below has been provided an analysis of the same for informative purposes :-

Code:

**************************Mon Dec 22 09:05:41.877 2014 (UTC + 5:30)**************************
Loading Dump File [C:\SysnativeBSODApps\122114-16046-01.dmp]
 
Windows 8 Kernel Version 9600 MP (4 procs) Free x64
 
Built by: 9600.17328.amd64fre.winblue_r3.140827-1500
 
System Uptime: 0 days 0:00:04.570
 
Probably caused by : AuthenticAMD
 
BugCheck 124, {0, ffffe000e3567588, 0, 0}
BugCheck Info: [URL="http://www.carrona.org/bsodindx.html#0x00000124"]WHEA_UNCORRECTABLE_ERROR (124)[/URL]
 
Arguments: 
Arg1: 0000000000000000, Machine Check Exception
Arg2: ffffe000e3567588, Address of the WHEA_ERROR_RECORD structure.
Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value.
BUGCHECK_STR:  0x124_AuthenticAMD
 
PROCESS_NAME:  System
 
FAILURE_BUCKET_ID:  0x124_AuthenticAMD_PROCESSOR_BUS_PRV
 
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Dec 15 22:41:29.008 2014 (UTC + 5:30)**************************
Loading Dump File [C:\SysnativeBSODApps\121514-10515-01.dmp]
 
Windows 8 Kernel Version 9600 MP (4 procs) Free x64
 
Built by: 9600.16384.amd64fre.winblue_rtm.130821-1623
 
System Uptime: 0 days 0:00:04.697
 
Probably caused by : USBXHCI.SYS ( USBXHCI!Control_ProcessTransferEventWithED1+1cd )
 
BugCheck D1, {10, 2, 0, fffff80002ad2e15}
BugCheck Info: [URL="http://www.carrona.org/bsodindx.html#0x000000D1"]DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)[/URL]
 
Arguments: 
Arg1: 0000000000000010, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff80002ad2e15, address which referenced memory
BUGCHECK_STR:  AV
 
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
 
PROCESS_NAME:  System
 
FAILURE_BUCKET_ID:  AV_USBXHCI!Control_ProcessTransferEventWithED1
 
  BIOS Version                  FA
 
  BIOS Release Date             04/23/2013
 
  Manufacturer                  Gigabyte Technology Co., Ltd.
 
  Product Name                  GA-78LMT-USB3
 
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

Below is a list of your 3rd party drivers present on your system -

Code:

**************************Mon Dec 22 09:05:41.877 2014 (UTC + 5:30)**************************
[U][B]AtiPcie64.sys               Mon Jul 16 12:16:14 2012 (5003B8B6)
amd_sata.sys                Tue Jul 24 00:04:48 2012 (500D9948)
amd_xata.sys                Tue Jul 24 00:04:52 2012 (500D994C)
[/B][/U]¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Dec 15 22:41:29.008 2014 (UTC + 5:30)**************************
viahduaa.sys                Fri Aug  3 07:01:13 2012 (501B29E1)
Rt630x64.sys                Fri May 10 15:29:08 2013 (518CC4EC)
dump_storahci.sys           Thu Aug 22 17:10:39 2013 (5215F8B7)
AMDACPKSL.SYS               Sun Jun 22 08:01:43 2014 (53A6400F)
AtihdWB6.sys                Sun Jun 22 08:02:00 2014 (53A64020)
atikmpag.sys                Tue Sep 16 03:29:06 2014 (5417612A)
atikmdag.sys                Tue Sep 16 03:51:08 2014 (54176654)

Prime95 download site: http://www.mersenne.org/freesoft/
Prime95 Setup:
- extract the contents of the zip file to a location of your choice
- double click on the executable file
- select "Just stress testing"
- select the "Blend" test. If you've already run MemTest overnight please run the "Small FFTs" test instead. (run all 3 if you find a problem and note how long it takes to error out with each)
- "Number of torture test threads to run" should equal the number of CPU's times 2 (if you're using hyperthreading).
The easiest way to figure this out is to go to Task Manager...Performance tab - and see the number of boxes under CPU Usage History
Then run the test for 6 to 24 hours - or until you get errors (whichever comes first).
Monitor the CPU temperature and DON'T let it exceed 85ºC. If it does, then you probably have a CPU cooling problem.
- CPU temps exceeding 60ºC can cause errors in Prime95. Fix the cooling solution first, then run Prime95 again.
This won't necessarily crash the system - but check the output in the test window for errors.
The Test selection box and the stress.txt file describes what components that the program stresses.
NOTE: Errors should be considered when:
- the system BSOD's during Prime95
- the system freezes during Prime95 (this is different than the extreme slowness caused by the program using all your RAM and CPU)
- the Prime95 program crashes
- the Prime95 program shows errors in it's display
- there are errors in the Prime95 results file
More details on the use of this test: http://www.playtool.com/pages/prime95/prime95.html

Also, perform the Intel Burn Test using the below guide and post back the results -
http://www.xtremesystems.org/forums...-IntelBurnTest-The-new-stress-testing-program

Let me know how it goes ^_^

-Pranav

Mysers Briggs · Dec 22, 2014

Looks more like a failing motherboard to me.

Code:

Descriptor    @ ffffe000e3567698
Section       @ ffffe000e3567820
Offset        : 664
Length        : 264
Flags         : 0x00000000
Severity      : Fatal

Error         : [COLOR=#ff0000]BUS[/COLOR][COLOR=#800080]LG[/COLOR]_[COLOR=#ff8c00]OBS[/COLOR]_ERR_*_[COLOR=#800000]NOTIMEOUT_ERR[/COLOR] (Proc 0 Bank 4)
  Status      : 0xfa000010000b0c0f

A generic nontimeout error was detected, although what's different is that the CPU was simply observing the issue, rather than being the reciever or sender for the request. This strongly suggests the CPU was not involved in the fault, but instead, simply detecting it.

Code:

3: kd> [COLOR=#008000]knL[/COLOR]
 # Child-SP          RetAddr           Call Site
00 ffffd000`206d7388 fffff802`f976cbe9 [COLOR=#0000ff]nt!KeBugCheckEx[/COLOR]
01 ffffd000`206d7390 fffff802`f976b43a [COLOR=#0000ff]nt!KiBugCheckDispatch+0x69[/COLOR]
02 ffffd000`206d74d0 fffff800`02ad2e15 [COLOR=#ff0000]nt!KiPageFault+0x23a[/COLOR]
03 ffffd000`206d7660 fffff800`02acb043 [COLOR=#ff0000]USBXHCI!Control_ProcessTransferEventWithED1+0x1cd[/COLOR]
04 ffffd000`206d76e0 fffff800`00369c81 [COLOR=#ff0000]USBXHCI!Interrupter_WdfEvtInterruptDpc+0x427[/COLOR]
05 ffffd000`206d77e0 fffff802`f9694e90 [COLOR=#ff8c00]Wdf01000!FxInterrupt::DpcHandler+0xc1[/COLOR]
06 ffffd000`206d7810 fffff802`f9694111 [COLOR=#800080]nt!KiExecuteAllDpcs+0x1b0[/COLOR]
07 ffffd000`206d7960 fffff802`f9764bea [COLOR=#ee82ee]nt!KiRetireDpcList+0xe1[/COLOR]
08 ffffd000`206d7be0 00000000`00000000 nt!KiIdleLoop+0x5a

What's strange is the USB extensible host controller interface driver directly calling into a page fault, very usual considering this is a Windows operating system driver.

I'm almost certain we have a failing motherboard, we might need more crashes to confirm this though.

A Kernel memory dump would be nice to play around with some USB data structures, I might be able to have a poke around and see what I can find.

Go the Start
Right click My Computer
Select Properties
Click Advanced system settings
Click on the Advanced tab
Select Settings under Startup and Recovery
Then under Write debugging information select Kernel memory dump.

Once a dump is created go to:

Code:

C:\Windows\memory.dmp

Copy the file to the desktop, zip it up and upload it to a file sharing site like Onedrive. After the upload is done post the download link in your next reply.

blueelvis · Dec 23, 2014

Thanks for the clear cut explanation mate ^_^.

Code:

Error         : [COLOR=#ff0000]BUS[/COLOR][COLOR=#800080]LG[/COLOR]_[COLOR=#ff8c00]OBS[/COLOR]_ERR_*_[COLOR=#800000]NOTIMEOUT_ERR[/COLOR] (Proc 0 Bank 4)

What would OBS and NOTIMEOUT would mean in this case?
I wonder if this is the same function as in Linux?
notimeout.3

According to that, if notimeout() is called then then input stream does not set any time limit before which one needs to enter a character(s).

Also by this statement -

What's strange is the USB extensible host controller interface driver directly calling into a page fault, very usual considering this is a Windows operating system driver.

You meant unusual right?

@amodi103 - Kindly follow Mysers Briggs instructions and provide us with the Complete Memory Dump.

-Pranav

Mysers Briggs · Dec 23, 2014

No timeout means it wasn't a timeout that caused the fault.
OBS means Observing, basically saying that the CPU found the error which wasn't related to any of the CPU's work.
SRC means the request was sent from the CPU. RES indicates the CPU responded to the request.
Not only this, the fact that we see an LG error (AFAIK) means the cause was related to the generic cache, usually RAM; that doesn't mean to say the RAM is faulty though. The actual cache cannot be identified, probably because it was observing the error rather than being involved.

I did mean unusual yes, thanks for the correction.

amodi103 · Dec 24, 2014

Sorry for taking forever to reply and thanks so much for your help guys, i've attached a complete dump file. It's probably worth mentioning the December 15 bsod was caused by a faulty wlan usb adapter inside the tower which I removed and havent had a problem with since. Also my usb 3.0 eXtensible host control driver was not updated until the guild wars related blue screen and I have updated it

https://onedrive.live.com/redir?resid=483F1F31D1588980!303&authkey=!AOV3AiItQvwk_YY&ithint=file,zip

blueelvis · Dec 29, 2014

Hi Amodi103 ^_^,

I have analysed your dump files and below has been provided an analysis of the same for informative purposes :-

Code:

3: kd> knL
 # Child-SP          RetAddr           Call Site
00 ffffd000`206d7388 fffff802`f976cbe9 nt!KeBugCheckEx
01 ffffd000`206d7390 fffff802`f976b43a nt!KiBugCheckDispatch+0x69
02 ffffd000`206d74d0 fffff800`02ad2e15 nt!KiPageFault+0x23a
03 ffffd000`206d7660 fffff800`02acb0[COLOR=#FF0000]43 USBXHCI!Control_ProcessTransferEventWithED1+0x[/COLOR]1cd
04 ffffd000`206d76e0 fffff800`00369c81 USBXHCI!Interrupter_WdfEvtInterruptDpc+0x427
05 ffffd000`206d77e0 fffff802`f9694e90 Wdf01000!FxInterrupt::DpcHandler+0xc1
06 ffffd000`206d7810 fffff802`f9694111 nt!KiExecuteAllDpcs+0x1b0
07 ffffd000`206d7960 fffff802`f9764bea nt!KiRetireDpcList+0xe1
08 ffffd000`206d7be0 00000000`00000000 nt!KiIdleLoop+0x5a

Like earlier, the USBXHCI.sys (Windows Component) is calling in a Page fault which is unusual.

Code:

3: kd> .trap 0xffffd000206d74d0
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffe00001db25f8 rbx=0000000000000000 rcx=ffffe00001db275c
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002ad2e15 rsp=ffffd000206d7660 rbp=ffffd000206d7700
 r8=0000000000000009  r9=0000000000000000 r10=0000000000000034
r11=ffffd000206d7650 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
USBXHCI!Control_ProcessTransferEventWithED1+0x1cd:
fffff800`02ad2e15 488b5210        mov     rdx,qword ptr [rdx+10h] ds:[COLOR=#0000FF]00000000`00000010[/COLOR]=??[COLOR=#0000FF][/COLOR]??????????????
3: kd> !pte [COLOR=#0000FF]00000000`00000010[/COLOR]
                                           VA 0000000000000010
PXE at FFFFF6FB7DBED000    PPE at FFFFF6FB7DA00000    PDE at FFFFF6FB40000000    PTE at FFFFF68000000000
contains 0250000101097867  contains 0000000000000000
pfn 101097    ---DA--UWEV  [U][B]not valid[/B][/U]

The memory which was being accessed is not valid and hence the bug check.
Like Mysers Briggs said, it is most likely a motherboard failure.

Make sure that you reset the BIOS settings and see how it goes.

Let me know how it goes ^_^

-Pranav

0x00000124 bluescreen error when playing guild wars 2

amodi103

New Member

My Computer

System One

blueelvis

OMG Debugger!

My Computer

System One

Mysers Briggs

Member

My Computer

System One

blueelvis

OMG Debugger!

My Computer

System One

Mysers Briggs

Member

My Computer

System One

amodi103

New Member

My Computer

System One

blueelvis

OMG Debugger!

My Computer

System One