BSOD code 1e,a and 50

[hsp25]

This is following a previous thread here http://forums.tweaktown.com/asrock/5...-freezing.html

I'm hoping someone can decipher these.

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


Loading Dump File [C:\Windows\Minidump\020614-22495-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 (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
Machine Name:
Kernel base = 0xfffff800`03062000 PsLoadedModuleList = 0xfffff800`032a56d0
Debug session time: Thu Feb 6 18:29:42.817 2014 (UTC + 11:00)
System Uptime: 0 days 0:20:23.034
Loading Kernel Symbols
.................................................. .............
.................................................. ..............
..............................
Loading User Symbols
Loading unloaded module list
..........
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffffffffffffff8, 0, fffff800030e0387, 0}


Could not read faulting driver name
Probably caused by : memory_corruption

Followup: memory_corruption
---------

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

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffffffffffffff8, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff800030e0387, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000000, (reserved)

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


Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff8000330f100
fffffffffffffff8

FAULTING_IP:
nt!PoIdle+1a7
fffff800`030e0387 c83b4318 enter 433Bh,18h

MM_INTERNAL_CODE: 0

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: CODE_CORRUPTION

BUGCHECK_STR: 0x50

PROCESS_NAME: System

CURRENT_IRQL: 0

TRAP_FRAME: fffff80000b9c9d0 -- (.trap 0xfffff80000b9c9d0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000c64 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800030e0387 rsp=fffff80000b9cb60 rbp=0000000000000000
r8=0000000000000000 r9=00000000d4b07661 r10=0000000000003224
r11=fffffa8009304168 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up di ng nz na po cy
nt!PoIdle+0x1a7:
fffff800`030e0387 c83b4318 enter 433Bh,18h
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff80003155bf0 to fffff800030d7bc0

STACK_TEXT:
fffff800`00b9c868 fffff800`03155bf0 : 00000000`00000050 ffffffff`fffffff8 00000000`00000000 fffff800`00b9c9d0 : nt!KeBugCheckEx
fffff800`00b9c870 fffff800`030d5cee : 00000000`00000000 ffffffff`fffffff8 00000000`00000000 fffffa80`07da22d0 : nt! ?? ::FNODOBFM::`string'+0x4518f
fffff800`00b9c9d0 fffff800`030e0387 : 00000000`00340b18 fffffa80`07da22d0 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
fffff800`00b9cb60 fffff800`030cf89c : fffff800`03252e80 fffff800`00000001 00000000`00000001 fffff880`00000000 : nt!PoIdle+0x1a7
fffff800`00b9cc40 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cc00 00000000`00000000 : nt!KiIdleLoop+0x2c


STACK_COMMAND: kb

CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
fffff800030e0387 - nt!PoIdle+1a7
[ 48:c8 ]
1 error : !nt (fffff800030e0387)

MODULE_NAME: memory_corruption

IMAGE_NAME: memory_corruption

FOLLOWUP_NAME: memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP: 0

MEMORY_CORRUPTOR: ONE_BIT

FAILURE_BUCKET_ID: X64_MEMORY_CORRUPTION_ONE_BIT

BUCKET_ID: X64_MEMORY_CORRUPTION_ONE_BIT


and this one

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


Loading Dump File [C:\Windows\Minidump\020614-15756-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 (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
Machine Name:
Kernel base = 0xfffff800`03050000 PsLoadedModuleList = 0xfffff800`032936d0
Debug session time: Thu Feb 6 16:49:21.263 2014 (UTC + 11:00)
System Uptime: 0 days 0:21:16.104
Loading Kernel Symbols
.

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

.................................................. ............
.................................................. ..............
............................
Loading User Symbols
Loading unloaded module list
......
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {0, 0, 0, 0}

Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )

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

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


EXCEPTION_CODE: (Win32) 0 (0) - The operation completed successfully.

FAULTING_IP:
+3766663365313335
00000000`00000000 ?? ???

EXCEPTION_PARAMETER1: 0000000000000000

EXCEPTION_PARAMETER2: 0000000000000000

ERROR_CODE: (NTSTATUS) 0 - STATUS_WAIT_0

BUGCHECK_STR: 0x1E_0

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 2

EXCEPTION_RECORD: fffff80000b9c8b8 -- (.exr 0xfffff80000b9c8b8)
ExceptionAddress: fffff800030d0595 (nt!KiTimerExpiration+0x0000000000000175)
ExceptionCode: c000001d (Illegal instruction)
ExceptionFlags: 00000000
NumberParameters: 0

TRAP_FRAME: fffff80000b9c960 -- (.trap 0xfffff80000b9c960)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000081000000 rbx=0000000000000000 rcx=fffff800032443a8
rdx=0000000000000089 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800030d0595 rsp=fffff80000b9caf0 rbp=0000000000013f89
r8=fffffa80074ec860 r9=00000000000000c1 r10=0000000000000089
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
nt!KiTimerExpiration+0x175:
fffff800`030d0595 f0413100 lock xor dword ptr [r8],eax ds:7460:fffffa80`074ec860=????????
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff800030bd5be to fffff800030c5b90

STACK_TEXT:
fffff800`00b9b998 fffff800`030bd5be : fffffa80`0740bb40 fffff800`00b9bc90 fffff800`00b9c110 fffff800`030f0a90 : nt!KeBugCheck
fffff800`00b9b9a0 fffff800`030f075d : fffff800`032d4380 fffff800`03211260 fffff800`03050000 fffff800`00b9c8b8 : nt!KiKernelCalloutExceptionHandler+0xe
fffff800`00b9b9d0 fffff800`030ef535 : fffff800`03215038 fffff800`00b9ba48 fffff800`00b9c8b8 fffff800`03050000 : nt!RtlpExecuteHandlerForException+0xd
fffff800`00b9ba00 fffff800`031004c1 : fffff800`00b9c8b8 fffff800`00b9c110 fffff800`00000000 fffff800`03240e80 : nt!RtlDispatchException+0x415
fffff800`00b9c0e0 fffff800`030c5242 : fffff800`00b9c8b8 00000002`f89e2388 fffff800`00b9c960 fffff800`032443a8 : nt!KiDispatchException+0x135
fffff800`00b9c780 fffff800`030c339f : fffff800`00b9c960 fffff780`00000302 00000000`00013f00 fffff800`00000000 : nt!KiExceptionDispatch+0xc2
fffff800`00b9c960 fffff800`030d0595 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00da7a64 : nt!KiInvalidOpcodeFault+0x11f
fffff800`00b9caf0 fffff800`030d03c7 : 00000000`eee120c1 00000000`00013f89 00000000`eee12015 00000000`00000089 : nt!KiTimerExpiration+0x175
fffff800`00b9cb90 fffff800`030bd8ca : fffff800`03240e80 fffff800`0324ecc0 00000000`00000001 fffff880`00000000 : nt!KiRetireDpcList+0x277
fffff800`00b9cc40 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cc00 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!KiKernelCalloutExceptionHandler+e
fffff800`030bd5be 90 nop

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!KiKernelCalloutExceptionHandler+e

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 521ea035

FAILURE_BUCKET_ID: X64_0x1E_0_nt!KiKernelCalloutExceptionHandler+e

BUCKET_ID: X64_0x1E_0_nt!KiKernelCalloutExceptionHandler+e

[wazza300]

Re: BSOD code 1e,a and 50

I think bsod 50 is memory related

[hsp25]

Re: BSOD code 1e,a and 50

Still testing atm but it seems like it is a memory compatibility issue. Seems like the same sticks placed in slot 1+4 (unganged) works but it's a bit early to tell.

Here are the codes Bug Check Code Reference (Windows Debuggers) but it doesn't give clear cut answers.

Edit: nope no good like that. memtast86 error @17hours. Running dual ganged in either slot pairs usually fails around 8 hours. I'm tempted to buy a new MB as it's cheaper than ram.

[wazza300]

Re: BSOD code 1e,a and 50

list your pc parts,it might need more dram voltage or cpu/vtt voltage

and you can return/rma the memory if its faulty

two sticks in dual channel mode should be in the second and last ram sockets from cpu to front of case, so 0/x/0/x x being installed ram,0 being empty ram slot

[hsp25]

Re: BSOD code 1e,a and 50

Asrock 970 Pro3 2.0 latest bios on asrock site and default bios settings
Kingston KVR13N9S8K2/8G 2x4gb ram
FX-6300 6 Core AMD with stock cooler
Saphire HD7790 2GB OC edition
120 GB Corsair Vengence SSD
1 TB WD Blue HDD
CD/dvd drive
650 Watt gaming Modular OCZ PSU

"two sticks in dual channel mode should be in the second and last ram sockets from cpu to front of case" I tried that but still fails memtest. If you run it long enough both sticks fail if just used by themselves in slot 1 (closest to cpu).
I ran memtest86 with a pair of cmz8gx3m2a1600c8 that has been stable in another pc for 2 years. It failed in this rig (Asrock 970 Pro3 2.0) also. I've swapped the kingston into the other pc (Gigabyte GA-970A-D3 Motherboard) to see if it fails there too. I dont think it is ram tbh but of coarse failing the memtest is sure to make it BSOD.

[wazza300]

Re: BSOD code 1e,a and 50

idk much about amd systems

tried enabling xmp memory profile if it supports xmp? touch more cpu northbridge voltage might help,it could also be down to faulty cpu memory controller inside the cpu?

[hsp25]

Re: BSOD code 1e,a and 50

The cmz8gx3m2a1600c8 has XMP and it is enable automatically I think. KVR13N9S8K2/8G doesn't have XMP

Sounds like a faulty memory controller to me but it's the second brand new cpu that does the same thing so it is very unlikely isn't it? I don't normally touch voltages and wouldn't know what to do there.

wardog said in another thread "From where I sit here and only knowing what you've posted, I'd lean towards the IMHO weak 4+1 power section as the culprit." That is why I'm thinking another MB. I've got me eye on a secondhand GA-990FXA-UD5 rev 1 or maybe a new GA-990FXA-UD3 rev 4.

Is there any drivers run in memtest86 or does it just use cpu?

[wazza300]

Re: BSOD code 1e,a and 50

it just uses the cpu I think,could be the board its hard to say,esp seeing as you've tried two cpu's

[hsp25]

Re: BSOD code 1e,a and 50

Yeah it's doing my head in while constantly kicking me in the butt. Other than buying QVL ram ($200) or another MB (also $200) I don't see a solution.

Pretty sure it even BSOD when I used a 1090t cpu which has been faultless for many years in my ud7 rig.

I used a later version of memtest86 last run (5.01) and it tells me both sticks (cmz8gx3m2a1600c8) failed, at the same time i think, so it seems to be either cpu or MB related as I doubt both sticks would have an error in the same spot. Besides that these stick have had zero issues running for 2 years in another pc.

On the other pc testing Kingston KVR13N9S8K2/8G it has no errors so far.

I dunno that anyone can actually help fix it tbh but it does help me to talk over scenarios of events with others. At times I feel like I'm doing allot of guessing with to many variables.

Thanks