Solved Random BSOD more prominent when under load with buzzing sound

[HiredMark]

Hi guys, I am a first timer at this forum, but I got nowhere else to ask.

So basically, I built myself a new PC from scratch, ordered all the parts and everything. There is no chance of damage from static as I used a band when I assembled it. I've had it for a couple of months now and I have been getting BSODs from day one. I though I had isolated it to an old version of Lucid Virtu and DeamonTools, but I am a still getting the problem.

I have ran thorough checks, CHKDSK /f , got myself a copy of TuneUp Utilities, benchmarked using a couple of Futuremark's benchmarks, also tried Heaven and I even borrowed a copy of SiSoft Sandra from a friend. Furthermore I went ahead and ran a memtest86+ for about 1 hour and 30 min . All the tests were AOK and no BSODs during.

There is no alterations to the BIOS and everything is running at stock, and I crosschecked all my parts twice, everything is compatible. Although the machine still crashed even when completely idle. Also sometimes there is a buzzing noise with a temporary screen freeze every so often, sometimes seconds before a blue screen and sometimes hours before.

The system runs very cool with only 30 degrees Celsius past ambient when under full load. And with 10 or so when idle.

Therefore went ahead and tried driver verifier. It took good 8 hours of operational time but the machine finally crashed to BSOD.

Here are some of the messages after the crashes:

Crashed during Idle

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 1033

Additional information about the problem:
BCCode: 1e
BCP1: 0000000000000000
BCP2: 0000000000000000
BCP3: 0000000000000000
BCP4: 0000000000000000
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

Crashed during CS:S

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 1033

Additional information about the problem:
BCCode: 1a
BCP1: 0000000000005003
BCP2: FFFFF70001080000
BCP3: 000000000003EA30
BCP4: FFFFF680002B4962
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

Crashed during the running of the driver verifier

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 1033

Additional information about the problem:
BCCode: 24
BCP1: 00000000001904FB
BCP2: FFFFF880045A4338
BCP3: FFFFF880045A3B90
BCP4: FFFFF80002EC4B65
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1


I normally would consider myself pretty tech savvy but I am out of options on this one. I have yet to reinstall Windows however as consider that to be turning the house to change a light bulb, and even if I do need to I would like to know what is causing the problem so I can then attend to the fault.

I am posting a zip file as requested by the pinned up thread. However the .zip includes 2 reports instead of 1, one before and one after the verifier ran.

I hope you guys can help me out!

 

[ePeen]

3 dumps, all core Windows files so it is more than likely those are not the cause of the crash itself. The verifier enabled dump(s) didn't show anything.

Run Memtest:

Read the following to test your memory for errors.

Drivers that need to be updated:

FNETURPX.SYS - Fri Oct 03 22:27:02 2008 (FNet Turbo HDD USB Driver - Also part of AsRock XFastUSB package). Update here, or here, or here.

Dumps for reference:

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


Loading Dump File [C:\Users\Icarus\Downloads\Windows_NT6_BSOD_jcgriff2 - Copy\032312-32604-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02e50000 PsLoadedModuleList = 0xfffff800`03095670
Debug session time: Fri Mar 23 12:30:04.302 2012 (UTC - 4:00)
System Uptime: 0 days 0:33:16.083
Loading Kernel Symbols
...............................................................
................................................................
..............................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 24, {1904fb, fffff880045a4338, fffff880045a3b90, fffff80002ec4b65}

Probably caused by : Ntfs.sys ( Ntfs!NtfsCommonRead+1ff )

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

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

NTFS_FILE_SYSTEM (24)
    If you see NtfsExceptionFilter on the stack then the 2nd and 3rd
    parameters are the exception record and context record. Do a .cxr
    on the 3rd parameter and then kb to obtain a more informative stack
    trace.
Arguments:
Arg1: 00000000001904fb
Arg2: fffff880045a4338
Arg3: fffff880045a3b90
Arg4: fffff80002ec4b65

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


EXCEPTION_RECORD:  fffff880045a4338 -- (.exr 0xfffff880045a4338)
ExceptionAddress: fffff80002ec4b65 (nt!ExpInterlockedPopEntrySListFault16)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT:  fffff880045a3b90 -- (.cxr 0xfffff880045a3b90)
rax=000000011e230003 rbx=fffff8a012fecc70 rcx=fffff88001264780
rdx=ff000000ff000001 rsi=fffff8a00279d280 rdi=fffff8a012fecb40
rip=fffff80002ec4b65 rsp=fffff880045a4570 rbp=fffff880045a4750
 r8=ff000000ff000000  r9=0000000000000000 r10=fffff88001264780
r11=fffffa8011bda9c8 r12=0000000040060401 r13=0000000000000001
r14=fffffa8011bdaa38 r15=fffffa8011bda9c0
iopl=0         nv up ei ng nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010286
nt!ExpInterlockedPopEntrySListFault16:
fffff800`02ec4b65 498b08          mov     rcx,qword ptr [r8] ds:002b:ff000000`ff000000=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

PROCESS_NAME:  avp.exe

CURRENT_IRQL:  0

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

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

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  ffffffffffffffff

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030ff100
 ffffffffffffffff 

FOLLOWUP_IP: 
Ntfs!NtfsCommonRead+1ff
fffff880`01213a1f 4885c0          test    rax,rax

FAULTING_IP: 
nt!ExpInterlockedPopEntrySListFault16+0
fffff800`02ec4b65 498b08          mov     rcx,qword ptr [r8]

BUGCHECK_STR:  0x24

LAST_CONTROL_TRANSFER:  from fffff88001213a1f to fffff80002ec4b65

STACK_TEXT:  
fffff880`045a4570 fffff880`01213a1f : fffff880`045a4620 fffff880`01073aae fffffa80`0ea0e730 fffff880`045a46c0 : nt!ExpInterlockedPopEntrySListFault16
fffff880`045a4580 fffff880`01215a68 : fffffa80`11bda9c0 fffffa80`12358010 fffff880`045a4700 fffffa80`0ee6f001 : Ntfs!NtfsCommonRead+0x1ff
fffff880`045a4720 fffff800`03372c16 : fffffa80`12358010 fffffa80`12358010 fffffa80`0ee6f030 fffffa80`11b26b70 : Ntfs!NtfsFsdRead+0x1b8
fffff880`045a47d0 fffff880`01071bcf : fffffa80`12358368 fffff880`045a4880 fffffa80`1212c010 fffffa80`11b26b70 : nt!IovCallDriver+0x566
fffff880`045a4830 fffff880`010706df : fffffa80`0f007950 fffffa80`0f007950 fffffa80`0f007900 fffffa80`12358010 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x24f
fffff880`045a48c0 fffff800`03372c16 : fffffa80`12358010 00000000`00000002 fffffa80`0ea0e730 fffffa80`0db35298 : fltmgr!FltpDispatch+0xcf
fffff880`045a4920 fffff800`02ef4bc5 : fffffa80`12358030 fffffa80`0f010c30 fffffa80`0f010b00 fffffa80`0ebc7d40 : nt!IovCallDriver+0x566
fffff880`045a4980 fffff800`03169417 : fffffa80`0f010b00 fffffa80`0f010b00 fffffa80`0ea0e732 fffffa80`0fc0c060 : nt!IoPageRead+0x255
fffff880`045a4a10 fffff800`03169511 : fffffa80`12267210 fffffa80`0fc0c060 fffff880`045a4b48 00000000`00000005 : nt!MiPfExecuteReadList+0xff
fffff880`045a4a70 fffff800`02ebbc8d : fffffa80`12267210 00000000`00000000 00000000`0000a000 00000000`00000000 : nt!MmPrefetchForCacheManager+0xb5
fffff880`045a4ac0 fffff800`031b6e10 : 00000000`00000000 00000000`00000000 fffffa80`0ea0e730 fffff8a0`12fce000 : nt!CcFetchDataForRead+0x17d
fffff880`045a4b20 fffff880`01213730 : fffff8a0`00000000 00000000`00000005 fffffa80`00040000 fffff880`01266001 : nt!CcCopyRead+0x180
fffff880`045a4be0 fffff880`01213da3 : 00000000`00000000 fffff8a0`12fecc70 fffff880`045a4e10 fffff8a0`12fecb40 : Ntfs!NtfsCachedRead+0x180
fffff880`045a4c40 fffff880`01215a68 : fffffa80`12127aa0 fffffa80`0ea9c010 fffff880`045a4e01 fffffa80`0ee6f000 : Ntfs!NtfsCommonRead+0x583
fffff880`045a4de0 fffff800`03372c16 : fffffa80`0ea9c010 fffffa80`0ea9c010 fffffa80`0ee6f030 fffffa80`11bc3c60 : Ntfs!NtfsFsdRead+0x1b8
fffff880`045a4e90 fffff880`01071bcf : fffffa80`0ea9c368 fffff880`045a4f40 fffffa80`12257530 fffffa80`11bc3c60 : nt!IovCallDriver+0x566
fffff880`045a4ef0 fffff880`01074aea : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`12257530 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x24f
fffff880`045a4f80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : fltmgr!FltPerformSynchronousIo+0x2ca


SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  Ntfs!NtfsCommonRead+1ff

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Ntfs

IMAGE_NAME:  Ntfs.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4d79997b

STACK_COMMAND:  .cxr 0xfffff880045a3b90 ; kb

FAILURE_BUCKET_ID:  X64_0x24_VRF_Ntfs!NtfsCommonRead+1ff

BUCKET_ID:  X64_0x24_VRF_Ntfs!NtfsCommonRead+1ff

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

2: kd> !thread
GetPointerFromAddress: unable to read from fffff800030ff000
THREAD fffffa800fc0c060  Cid 0784.0524  Teb: 000000007efd8000 Win32Thread: 0000000000000000 RUNNING on processor 2
IRP List:
    Unable to read nt!_IRP @ fffffa8012358010
Not impersonating
GetUlongFromAddress: unable to read from fffff8000303eba4
Owning Process            fffffa800fb8e060       Image:         avp.exe
Attached Process          N/A            Image:         N/A
fffff78000000000: Unable to get shared data
Wait Start TickCount      127953       
Context Switch Count      25             
ReadMemory error: Cannot get nt!KeMaximumIncrement value.
UserTime                  00:00:00.000
KernelTime                00:00:00.000
Win32 Start Address 0x00000000675e4e30
Stack Init fffff880045a6c70 Current fffff8800b76d1c0
Base fffff880045a7000 Limit fffff880045a1000 Call 0
Priority 9 BasePriority 8 UnusualBoost 0 ForegroundBoost 0 IoPriority 2 PagePriority 5
Child-SP          RetAddr           : Args to Child                                                           : Call Site
fffff880`045a3328 fffff880`0120ea88 : 00000000`00000024 00000000`001904fb fffff880`045a4338 fffff880`045a3b90 : nt!KeBugCheckEx
fffff880`045a3330 fffff880`01222f3d : fffff880`01254f8c fffff880`045a4750 fffff880`045a4720 00000000`00000000 : Ntfs! ?? ::FNODOBFM::`string'+0x2b49
fffff880`045a3370 fffff800`02ef8a7c : 00000000`00000000 fffffa80`112a6900 fffff800`031c44f4 00000000`000034c0 : Ntfs! ?? ::FNODOBFM::`string'+0x12c6
fffff880`045a33b0 fffff880`012225c5 : fffff880`01254f94 fffff880`045a4720 fffff880`045a4338 fffff880`045a4720 : nt!_C_specific_handler+0x8c
fffff880`045a3420 fffff800`02ef84fd : fffff880`01254f80 00000000`00000000 fffff880`01209000 00000000`00000000 : Ntfs!_GSHandlerCheck_SEH+0x75
fffff880`045a3450 fffff800`02ef72d5 : fffff880`01254f80 fffff880`045a34c8 fffff880`045a4338 fffff880`01209000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`045a3480 fffff800`02f08361 : fffff880`045a4338 fffff880`045a3b90 fffff880`00000000 fffff8a0`12fecb40 : nt!RtlDispatchException+0x415
fffff880`045a3b60 fffff800`02ecc2c2 : fffff880`045a4338 fffff8a0`12fecc70 fffff880`045a43e0 fffff8a0`0279d280 : nt!KiDispatchException+0x135
fffff880`045a4200 fffff800`02ecabca : fffffa80`0e99c0e0 fffffa80`1249cea0 00000000`00b600b6 fffff8a0`02ae5d00 : nt!KiExceptionDispatch+0xc2
fffff880`045a43e0 fffff800`02ec4b65 : fffff8a0`12fecc70 fffff880`01213a1f fffff880`045a4620 fffff880`01073aae : nt!KiGeneralProtectionFault+0x10a (TrapFrame @ fffff880`045a43e0)
fffff880`045a4570 fffff880`01213a1f : fffff880`045a4620 fffff880`01073aae fffffa80`0ea0e730 fffff880`045a46c0 : nt!ExpInterlockedPopEntrySListFault16
fffff880`045a4580 fffff880`01215a68 : fffffa80`11bda9c0 fffffa80`12358010 fffff880`045a4700 fffffa80`0ee6f001 : Ntfs!NtfsCommonRead+0x1ff
fffff880`045a4720 fffff800`03372c16 : fffffa80`12358010 fffffa80`12358010 fffffa80`0ee6f030 fffffa80`11b26b70 : Ntfs!NtfsFsdRead+0x1b8
fffff880`045a47d0 fffff880`01071bcf : fffffa80`12358368 fffff880`045a4880 fffffa80`1212c010 fffffa80`11b26b70 : nt!IovCallDriver+0x566
fffff880`045a4830 fffff880`010706df : fffffa80`0f007950 fffffa80`0f007950 fffffa80`0f007900 fffffa80`12358010 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x24f
fffff880`045a48c0 fffff800`03372c16 : fffffa80`12358010 00000000`00000002 fffffa80`0ea0e730 fffffa80`0db35298 : fltmgr!FltpDispatch+0xcf
fffff880`045a4920 fffff800`02ef4bc5 : fffffa80`12358030 fffffa80`0f010c30 fffffa80`0f010b00 fffffa80`0ebc7d40 : nt!IovCallDriver+0x566
fffff880`045a4980 fffff800`03169417 : fffffa80`0f010b00 fffffa80`0f010b00 fffffa80`0ea0e732 fffffa80`0fc0c060 : nt!IoPageRead+0x255
fffff880`045a4a10 fffff800`03169511 : fffffa80`12267210 fffffa80`0fc0c060 fffff880`045a4b48 00000000`00000005 : nt!MiPfExecuteReadList+0xff
fffff880`045a4a70 fffff800`02ebbc8d : fffffa80`12267210 00000000`00000000 00000000`0000a000 00000000`00000000 : nt!MmPrefetchForCacheManager+0xb5
fffff880`045a4ac0 fffff800`031b6e10 : 00000000`00000000 00000000`00000000 fffffa80`0ea0e730 fffff8a0`12fce000 : nt!CcFetchDataForRead+0x17d
fffff880`045a4b20 fffff880`01213730 : fffff8a0`00000000 00000000`00000005 fffffa80`00040000 fffff880`01266001 : nt!CcCopyRead+0x180
fffff880`045a4be0 fffff880`01213da3 : 00000000`00000000 fffff8a0`12fecc70 fffff880`045a4e10 fffff8a0`12fecb40 : Ntfs!NtfsCachedRead+0x180
fffff880`045a4c40 fffff880`01215a68 : fffffa80`12127aa0 fffffa80`0ea9c010 fffff880`045a4e01 fffffa80`0ee6f000 : Ntfs!NtfsCommonRead+0x583
fffff880`045a4de0 fffff800`03372c16 : fffffa80`0ea9c010 fffffa80`0ea9c010 fffffa80`0ee6f030 fffffa80`11bc3c60 : Ntfs!NtfsFsdRead+0x1b8
fffff880`045a4e90 fffff880`01071bcf : fffffa80`0ea9c368 fffff880`045a4f40 fffffa80`12257530 fffffa80`11bc3c60 : nt!IovCallDriver+0x566
fffff880`045a4ef0 fffff880`01074aea : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`12257530 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x24f
fffff880`045a4f80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : fltmgr!FltPerformSynchronousIo+0x2ca


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


Loading Dump File [C:\Users\Icarus\Downloads\Windows_NT6_BSOD_jcgriff2 - Copy\032112-28579-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02e06000 PsLoadedModuleList = 0xfffff800`0304b670
Debug session time: Wed Mar 21 16:46:13.891 2012 (UTC - 4:00)
System Uptime: 0 days 5:01:18.561
Loading Kernel Symbols
...............................................................
................................................................
................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {5003, fffff70001080000, 3ea30, fffff680002b4962}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+2a001 )

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

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

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000005003, The subtype of the bugcheck.
Arg2: fffff70001080000
Arg3: 000000000003ea30
Arg4: fffff680002b4962

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


BUGCHECK_STR:  0x1a_5003

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  TribesAscend.e

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002eed969 to fffff80002e82c40

STACK_TEXT:  
fffff880`049d1748 fffff800`02eed969 : 00000000`0000001a 00000000`00005003 fffff700`01080000 00000000`0003ea30 : nt!KeBugCheckEx
fffff880`049d1750 fffff800`02ea153f : 00000000`00000000 00000003`f514d121 00000000`00000000 fffffa80`128363f8 : nt! ?? ::FNODOBFM::`string'+0x2a001
fffff880`049d17e0 fffff800`02ea0053 : 00000000`0042203c 00000000`751b3495 fffff680`003a8d98 fffffa80`128363f8 : nt!MiResolveProtoPteFault+0x1cf
fffff880`049d1870 fffff800`02e8ff19 : 00000000`00000000 00000000`751b3495 ffffffff`ffffffff 00000000`00000000 : nt!MiDispatchFault+0x1c3
fffff880`049d1980 fffff800`02e80d6e : 00000000`00000000 00000000`751b3495 fffff880`00000001 00000000`00000000 : nt!MmAccessFault+0x359
fffff880`049d1ae0 00000000`751b3495 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
00000000`0b50f3e8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x751b3495


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+2a001
fffff800`02eed969 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+2a001

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3

FAILURE_BUCKET_ID:  X64_0x1a_5003_nt!_??_::FNODOBFM::_string_+2a001

BUCKET_ID:  X64_0x1a_5003_nt!_??_::FNODOBFM::_string_+2a001

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


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


Loading Dump File [C:\Users\Icarus\Downloads\Windows_NT6_BSOD_jcgriff2 - Copy\032112-16785-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02e53000 PsLoadedModuleList = 0xfffff800`03098670
Debug session time: Wed Mar 21 11:44:07.660 2012 (UTC - 4:00)
System Uptime: 0 days 3:08:00.457
Loading Kernel 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
---------

1: 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: 
+3132613965316666
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:  0

EXCEPTION_RECORD:  fffff8800371ba08 -- (.exr 0xfffff8800371ba08)
ExceptionAddress: fffff80002ec7942 (nt!KiIdleLoop+0x0000000000000032)
   ExceptionCode: c0000096
  ExceptionFlags: 00000000
NumberParameters: 0

TRAP_FRAME:  fffff8800371bab0 -- (.trap 0xfffff8800371bab0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000001 rbx=0000000000000000 rcx=0000000000000002
rdx=0000000000033508 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002ec7942 rsp=fffff8800371bc40 rbp=0000000000000000
 r8=0000000000016fcf  r9=0000000000000000 r10=0000000000000000
r11=0000000000000002 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
nt!KiIdleLoop+0x32:
fffff800`02ec7942 440f22c1        mov     cr8,rcx
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002ec75fe to fffff80002ecfc10

STACK_TEXT:  
fffff880`0371aae8 fffff800`02ec75fe : fffffa80`0f230000 00000000`01840800 fffff880`0371b260 fffff800`02efb830 : nt!KeBugCheck
fffff880`0371aaf0 fffff800`02efb4fd : 00000000`0010001f fffff880`0371b260 fffff880`0371bab0 fffff880`0371ba08 : nt!KiKernelCalloutExceptionHandler+0xe
fffff880`0371ab20 fffff800`02efa2d5 : fffff800`0301a0fc fffff880`0371ab98 fffff880`0371ba08 fffff800`02e53000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`0371ab50 fffff800`02f0b361 : fffff880`0371ba08 fffff880`0371b260 fffff880`00000000 fffff880`009f50c0 : nt!RtlDispatchException+0x415
fffff880`0371b230 fffff800`02ecf2c2 : fffff880`0371ba08 fffff880`009ea180 fffff880`0371bab0 00000000`00000000 : nt!KiDispatchException+0x135
fffff880`0371b8d0 fffff800`02ecdbca : fffff880`009ea180 fffff880`0371bb30 fffff880`009f50c0 000023d2`14ec1fec : nt!KiExceptionDispatch+0xc2
fffff880`0371bab0 fffff800`02ec7942 : fffff880`009ea180 fffff880`00000001 00000000`00000001 fffff880`00000000 : nt!KiGeneralProtectionFault+0x10a
fffff880`0371bc40 00000000`00000000 : fffff880`0371c000 fffff880`03716000 fffff880`0371bc00 00000000`00000000 : nt!KiIdleLoop+0x32


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiKernelCalloutExceptionHandler+e
fffff800`02ec75fe 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:  4e02aaa3

FAILURE_BUCKET_ID:  X64_0x1E_0_nt!KiKernelCalloutExceptionHandler+e

BUCKET_ID:  X64_0x1E_0_nt!KiKernelCalloutExceptionHandler+e

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

 

[HiredMark]

Thank you for your quick reply I am gonna update and run memtest86+ again!

 

[ePeen]

Keep me updated

 

[HiredMark]

Still testing it but it isn't showing up with anything... I have been testing it in odd bouts of time as it is the end of the year and Uni is ripping me up with work, but I got 8 passes already.
I updated and I still get these crashes though. Sometimes even the BSOD freezes which is worrying.

 

[writhziden]

You may not have things configured properly to run that much RAM. Do the following steps in this order:

1. Download and install CPU-Z and Upload screenshots of the CPU, Mainboard, Memory, and SPD tabs. In the SPD tab, upload an image of each slot. Do this with all 16 GB of RAM installed.
   
   
2. Remove two RAM modules and run with 8 GB of RAM. See if that pair is good by doing your normal routine for as long as it usually takes to get a crash. Then, swap that set of 8 GB with the other set and do the same testing by doing your normal routine for as long as it usually takes to get a crash. See if you have a bad set of RAM first. Then we can try all 16 GB and work to set up the correct settings for them. Make sure you load setup defaults in the BIOS before testing so you are running with a clean slate.

 

[HiredMark]

Set the memory to factory specification in BIOS. Here are the images from CPUID afterwards.
Sorry for the massive delay, by the way.

 

[writhziden]

Are all of your modules identical? Check them very carefully. Even if bought at the same time by the same manufacturer, occasionally kits have slight variations of the RAM and those can conflict.

Are you now running with 8 GB?

 

[HiredMark]

All of them are identical. Bought at the same place at the same time. Currently running with 16GBs.

 

[writhziden]

How is the system responding to the CMOS reset through loading default settings in the BIOS?

 

[HiredMark]

The problem originates at default settings. I started having these without touching anything crucial for overclocking, or further specification. ALL of it is normally on auto. Couple of days ago. I manually set the memory to factory specifications it seemed to make it more unstable.

I also noticed programs that tend to crash, freeze or have BSOD occur run on my C: drive. So I went ahead and re-installed the SSD's firmware, couple of hours ago. I've yet to crash since, so it seems as if it has had a stabilizing effect, still sometimes there can be a few days in between BSODs, so I'll wait and check back in on that.

 

[writhziden]

We have seen a lot of problems resolved with SSD firmware updates, BIOS updates, chipset drivers updates, and hard drive controller updates when dealing with SSDs. All components associated with SSDs seem to need to be up to date for stability. Hopefully that helps your situation. Let us know how the system responds over the next few days. You can wait longer to be sure if you want, as well. I will keep an eye out for your response for however long you need to feel comfortable that the system is running as it should.

 

[HiredMark]

Sadly. My BSOD problem seems to persist although with diminished intensity.

 

[HiredMark]

Is there a way to test the integrity of the built-in sound card? It is the only suspicion I have left, as even though it is properly connected through an HDAUDIO cable, I can't get the front audio ports to work (I have checked and it is enabled in BIOS). Of course I don't really mind, since I don't plan on using them any time soon, but that is me out of ideas.

 

[writhziden]

Loading Dump File [D:\Kingston\BSODDmpFiles\HiredMark\Windows_NT6_BSOD_jcgriff2\040912-15397-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 (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02e1e000 PsLoadedModuleList = 0xfffff800`03063670
Debug session time: Mon Apr  9 07:16:40.768 2012 (UTC - 6:00)
System Uptime: 0 days 2:07:54.564
Loading Kernel Symbols
...............................................................
................................................................
...............................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff80002e91a23, fffff88002bf9d80, 0}

Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceHandler+7c )

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

6: 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: fffff80002e91a23, Address of the instruction which caused the bugcheck
Arg3: fffff88002bf9d80, 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: 
nt!memcmp+93
fffff800`02e91a23 483b040a        cmp     rax,qword ptr [rdx+rcx]

CONTEXT:  fffff88002bf9d80 -- (.cxr 0xfffff88002bf9d80)
rax=44890c54e46eead8 rbx=0000000000000000 rcx=fffff88002bfa8d8
rdx=0000077ffd40573c rsi=fffff88002bfa8d8 rdi=fffff80003042be0
rip=fffff80002e91a23 rsp=fffff88002bfa768 rbp=0000000000000000
 r8=0000000000000010  r9=0000000000000002 r10=00000000000003ac
r11=fffff88002bfaa10 r12=0000000000000000 r13=fffff88002bfa8c0
r14=fffff88002bfa8d8 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010202
nt!memcmp+0x93:
fffff800`02e91a23 483b040a        cmp     rax,qword ptr [rdx+rcx] ds:002b:00000000`00000014=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  firefox.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff80002e91a23

STACK_TEXT:  
fffff880`02bf94b8 fffff800`02e9a1e9 : 00000000`0000003b 00000000`c0000005 fffff800`02e91a23 fffff880`02bf9d80 : nt!KeBugCheckEx
fffff880`02bf94c0 fffff800`02e99b3c : fffff880`02bf9700 fffff800`02e72971 fffff800`02fe268c fffff880`02bfb870 : nt!KiBugCheckDispatch+0x69
fffff880`02bf9600 fffff800`02ec64fd : fffff800`030a3fd8 fffff800`02fe51e4 fffff800`02e1e000 fffff880`02bfa528 : nt!KiSystemServiceHandler+0x7c
fffff880`02bf9640 fffff800`02ec52d5 : fffff800`02fe5788 fffff880`02bf96b8 fffff880`02bfa528 fffff800`02e1e000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`02bf9670 fffff800`02ed6361 : fffff880`02bfa528 fffff880`02bf9d80 fffff880`00000000 fffff800`03042be0 : nt!RtlDispatchException+0x415
fffff880`02bf9d50 fffff800`02e9a2c2 : fffff880`02bfa528 00000000`00000000 fffff880`02bfa5d0 fffff880`02bfa8d8 : nt!KiDispatchException+0x135
fffff880`02bfa3f0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatch+0xc2


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiSystemServiceHandler+7c
fffff800`02e99b3c b801000000      mov     eax,1

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  nt!KiSystemServiceHandler+7c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3

FAILURE_BUCKET_ID:  X64_0x3B_nt!KiSystemServiceHandler+7c

BUCKET_ID:  X64_0x3B_nt!KiSystemServiceHandler+7c

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

Still crash points to hardware and probably memory. Have you tried running with 8 GB at a time as suggested earlier in this thread?

 

[HiredMark]

Yeah, I did that. Unfortunately the system wouldn't POST with Dr. Debug code of 45. When I tried to return it to its original setup it gave me code 2E. Both times there was and is no video output, although all fans spin up. CMOS reset doesn't help.

Before I did any of that I went for another go at memtest. That was in my original 16gb system, it was rather unusual and you can find it attached to this.

Since I am now stuck with my box of misery, that is my old system. I'd really appreciate if we can solve this.

 

[HiredMark]

K. One problem solved. I am now writing from my good PC. It appears a memory module had been dislodged somehow, causing the problem. I put all 16GBs back in there in the end, with a CMOS reset to follow suit. I am going to continue testing the system using memtest86+, this time trying to get all the tests in one straight run, although I don't think that should make a difference, but an error has popped up at random, and I want to make sure of it.

 

[writhziden]

Even one error in Memtest86+ is too many. If you get any errors with the RAM firmly in place, it is likely that you have a bad module somewhere down the line.

 

[HiredMark]

It isn't a normal memtest error though. If it were a memory error it would just list it and carry on. I left it overnight and I found my PC fully booted in the morning. Presumably the memtest halted again. Any idea where the error occurs or if there is other software to test my system with?

 

[writhziden]

If memtest86+ is halting, you likely have a hardware fault. These types of crashes typically indicate hardware. Do some hardware checks.

• If you are overclocking any hardware, please stop.
  
  
• Monitor temperatures during the following tests.
  Use the following programs to monitor the temperatures.​
  • Real Temp is a good CPU temperature monitor.
  • Speccy - System Information - Free Download will monitor all hardware temperatures.
  • HWiNFO, HWiNFO32 & HWiNFO64 - Hardware Information and Analysis Tools can be inaccurate for CPU temperatures, but is a good program for GPU temperature monitoring.
  
  

  • Use FurMark: VGA Stress Test, Graphics Card and GPU Stability Test, Burn-in Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net to test the graphics card GPU. Let it run until the GPU temperatures even out or until the GPU temperatures reach a dangerous level (you can find the max temperature for your card on either the nVidia or AMD sites; if you are not sure, ask us). The goal is to get a steady temperature, find out if the GPU is overheating, or to see if there are any artifacts present in the test itself: look for strange pixelated patterns on the screen or colors that do not look like they belong. Then use the |MG| Video Memory Stress Test 1.7.116 Download to test your graphics card memory. Let the memory test run for at least seven passes; the more the better.
  • Run http://www.sevenforums.com/tutorials/100352-hardware-stress-test-prime95.html to determine any hardware problems. Run all three tests for a few hours each. If you get errors, stop the test and post back here.
  • Follow the steps for doing a CPU stress test using IntelBurnTest