BSOD at random times, PFN_LIST_CORRUPT & SYSTEM_SERVICE_EXCEPTION

[Lonrandir]

Hello. My PC seems to be BSOD'ing at random times (Although only when in use by me, I leave it on overnight without problem), with either the codes "PFN_LIST_CORRUPT" or "SYSTEM_SERVICE_EXCEPTION". The two times I've seen the codes, it's been 0x0000003B or 0x0000004E I think it was.

Info:
OS: Windows Professional x64
Original OS: See above.
OS origin: Got it from student software site.

Hardware age: 3 months at most.
OS installation age: 3 months at most.

 

[Maguscreed]

*******************************************************************************
*                                                                             *
*                        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: fffffa8004e5e708, 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.

That debug code is very specific you really only see it in instances where the system is overclocked and it has caused problems, in which case removing the overclock should solve the issue.
The other possibility is that you have hardware damage somewhere.
http://www.sevenforums.com/crash-lockup-debug-how/35349-stop-0x124-what-means-what-try.html

 

[Lonrandir]

Is it possible to judge which hardware part is damaged based on the error code? Unless the machine was overclocked by the guys who put it together, it shouldn't be.

 

[Maguscreed]

follow the link at the bottom of that post. It's the best start I can give you.

 

[Lonrandir]

A bit of a difference now. I no longer get BSOD, rather a rainbow screen for a second, before crashing.

Is it still Stop 0x124 error? I did a harddrive check, and it showed no errors, so otherwise it's time for new RAM.

 

[writhziden]

Security Software:

avastsvc.exe	c:\program files\avast software\avast\avastsvc.exe	1508	8	200	1380	2012-03-16 15:43	7.0.1426.0	43,72 KB (44*768 bytes)	2012-03-16 15:07
avastui.exe	c:\program files\avast software\avast\avastui.exe	3096	8	200	1380	2012-03-16 15:43	7.0.1426.0	4,05 MB (4*241*512 bytes)	2012-03-16 15:07

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


Loading Dump File [D:\Kingston\BSODDmpFiles\Lonrandir\Windows_NT6_BSOD_jcgriff2\031612-20857-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 (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Machine Name:
Kernel base = 0xfffff800`02e14000 PsLoadedModuleList = 0xfffff800`03058650
Debug session time: Fri Mar 16 08:41:51.203 2012 (UTC - 6:00)
System Uptime: 0 days 4:42:29.639
Loading Kernel Symbols
...............................................................
................................................................
................................
Loading User Symbols
Loading unloaded module list
..........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff880010a8bd9, fffff8800b5fba70, 0}

Unable to load image aswTdi.SYS, Win32 error 0n2
*** WARNING: Unable to verify timestamp for aswTdi.SYS
*** ERROR: Module load completed but symbols could not be loaded for aswTdi.SYS
Probably caused by : tdx.sys ( tdx!TdxCreateControlChannel+a9 )

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

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

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff880010a8bd9, Address of the instruction which caused the bugcheck
Arg3: fffff8800b5fba70, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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


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

FAULTING_IP: 
tdx!TdxCreateControlChannel+a9
fffff880`010a8bd9 48895e18        mov     qword ptr [rsi+18h],rbx

CONTEXT:  fffff8800b5fba70 -- (.cxr 0xfffff8800b5fba70)
rax=0000000000000001 rbx=fffffa8006a3e5c0 rcx=fffffa8004cd5b60
rdx=fffffa80062c6500 rsi=000000000012fabc rdi=0000000000000000
rip=fffff880010a8bd9 rsp=fffff8800b5fc450 rbp=fffff8800b5fc548
 r8=fffffa8004cd5c00  r9=fffffa8006a3e5d8 r10=fffff880009e8b80
r11=0000000000000000 r12=fffffa8004cd5b00 r13=fffffa8004cd5b50
r14=000000000012fabc r15=fffffa8003ebc820
iopl=0         nv up ei pl nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010206
tdx!TdxCreateControlChannel+0xa9:
fffff880`010a8bd9 48895e18        mov     qword ptr [rsi+18h],rbx ds:002b:00000000`0012fad4=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  uTorrent.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff880010a266c to fffff880010a8bd9

STACK_TEXT:  
fffff880`0b5fc450 fffff880`010a266c : fffffa80`03ebc820 00000000`00000000 fffffa80`03ebc6c0 ffff0000`0b809741 : tdx!TdxCreateControlChannel+0xa9
fffff880`0b5fc490 fffff880`010b97d4 : fffffa80`03ebc6c0 00000000`00000000 fffffa80`04d91060 fffffa80`03ebc820 : tdx! ?? ::FNODOBFM::`string'+0x42ba
fffff880`0b5fc530 fffffa80`03ebc6c0 : 00000000`00000000 fffffa80`04d91060 fffffa80`03ebc820 fffffa80`04e4ef20 : aswTdi+0x17d4
fffff880`0b5fc538 00000000`00000000 : fffffa80`04d91060 fffffa80`03ebc820 fffffa80`04e4ef20 fffff880`010b9bff : 0xfffffa80`03ebc6c0


FOLLOWUP_IP: 
tdx!TdxCreateControlChannel+a9
fffff880`010a8bd9 48895e18        mov     qword ptr [rsi+18h],rbx

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  tdx!TdxCreateControlChannel+a9

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: tdx

IMAGE_NAME:  tdx.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce79332

STACK_COMMAND:  .cxr 0xfffff8800b5fba70 ; kb

FAILURE_BUCKET_ID:  X64_0x3B_tdx!TdxCreateControlChannel+a9

BUCKET_ID:  X64_0x3B_tdx!TdxCreateControlChannel+a9

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

The crash is pointing to your avast! software as the cause. Make sure your network drivers are up to date through Realtek, your audio drivers are up to date through Realtek, and that avast! software is up to date. If all are up to date, uninstall and re-install avast! To uninstall, make sure to use the avast! uninstall utility.


Also uninstall Todos Data System:

shbecr	fffff880`067a5000	fffff880`067b7000	Fri May 30 06:28:27 2008 (483ff2eb)	00014042		shbecr.sys