Bsod - Any Clue?

Southman · Oct 11, 2010

Hi folks!

Bought some new components 3-4 weeks ago, motherboard, RAM, GPU & a CPU.

My "new" computer worked good some time, then these random Bsod's started to show up. Downloaded a program called bluescreenview to find out what the problem was, seemed to be a RAM issue. Googled it and spent many hours trying to fix it, I ran memtest for about 16-17 hours without any error. Also used Chkdsk on both of my harddrives, seemed to be zero errors aswell.

Also tried raising the Dram voltage & QPI voltage, seemed more stable after that, got one BSOD some days after but then it worked fine until today when i booted up....

I got 3 BSOD's in a row, one by simply right-clicking on the desktop.

So therefore I thought I'd see if you guys could help me fix this. I'd be really grateful!

Attached the files as the "Bsod posting instruction" told me. Hope i did it right!

CarlTR6 · Oct 11, 2010

Hi Southman and welcome to the forum.

Error code 50 (2X), PAGE_FAULT_IN_NONPAGED_AREA. Usual causes: Defective hardware (particularly memory - but not just RAM), Faulty system service, Antivirus, Device driver, NTFS corruption, BIOS

Error code 1A, MEMORY_MANAGEMENT. Usual Causes: Device driver, memory, kernel.

All three dumps indicate corrupted memory. The second dump indicates, nvSCPAPISvr.exe was involved. And the latest dump blames NTFS.sys, which is unlikely to be the cause. This is a Windows system driver.

Code:

Kernel base = 0xfffff800`02e16000 PsLoadedModuleList = 0xfffff800`03053e50
Debug session time: Mon Oct 11 09:56:33.385 2010 (GMT-4)
System Uptime: 0 days 0:01:22.493
Loading Kernel Symbols
...............................................................
................................................................
.......................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff6fc5402c380, 0, fffff80002f8cef7, 2}


Could not read faulting driver name
Probably caused by : memory_corruption ( nt!MiCaptureAndResetWorkingSetAccessBits+97 )

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

3: 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: fffff6fc5402c380, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff80002f8cef7, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000002, (reserved)

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


Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030be0e0
 fffff6fc5402c380 

FAULTING_IP: 
nt!MiCaptureAndResetWorkingSetAccessBits+97
fffff800`02f8cef7 488b5d00        mov     rbx,qword ptr [rbp]

MM_INTERNAL_CODE:  2

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  System

CURRENT_IRQL:  0

TRAP_FRAME:  fffff88003316850 -- (.trap 0xfffff88003316850)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000098000000000 rbx=0000000000000000 rcx=007ffffc5402c380
rdx=fffff8a005871000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002f8cef7 rsp=fffff880033169e0 rbp=fffff6fc5402c380
 r8=0000000000000001  r9=0000000000000014 r10=0000000000000014
r11=fffff8a00010c001 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe cy
nt!MiCaptureAndResetWorkingSetAccessBits+0x97:
fffff800`02f8cef7 488b5d00        mov     rbx,qword ptr [rbp] ss:0018:fffff6fc`5402c380=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002f058f2 to fffff80002e86740

STACK_TEXT:  
fffff880`033166e8 fffff800`02f058f2 : 00000000`00000050 fffff6fc`5402c380 00000000`00000000 fffff880`03316850 : nt!KeBugCheckEx
fffff880`033166f0 fffff800`02e8482e : 00000000`00000000 80000001`164a8121 fffff880`02fd5100 00000000`00000002 : nt! ?? ::FNODOBFM::`string'+0x40ec0
fffff880`03316850 fffff800`02f8cef7 : 04b00000`b5d0b005 fffff680`003abe38 fffff700`0108c6e8 fffff800`0302b740 : nt!KiPageFault+0x16e
fffff880`033169e0 fffff800`02f08a70 : 00000000`00000000 00000000`00000010 fffff880`03316ba0 fffff880`03316ba0 : nt!MiCaptureAndResetWorkingSetAccessBits+0x97
fffff880`03316ae0 fffff800`02e9aee2 : 00000000`0000004a 00000000`00000000 fffffa80`00000000 00000000`00000007 : nt! ?? ::FNODOBFM::`string'+0x496e8
fffff880`03316b80 fffff800`02e9b173 : 00000000`00000008 fffff880`03316c10 00000000`00000001 fffffa80`00000000 : nt!MmWorkingSetManager+0x6e
fffff880`03316bd0 fffff800`0312ac06 : fffffa80`03876680 00000000`00000080 fffffa80`0384d040 00000000`00000001 : nt!KeBalanceSetManager+0x1c3
fffff880`03316d40 fffff800`02e64c26 : fffff880`02f64180 fffffa80`03876680 fffff880`02f6efc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`03316d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiCaptureAndResetWorkingSetAccessBits+97
fffff800`02f8cef7 488b5d00        mov     rbx,qword ptr [rbp]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!MiCaptureAndResetWorkingSetAccessBits+97

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0x50_nt!MiCaptureAndResetWorkingSetAccessBits+97

BUCKET_ID:  X64_0x50_nt!MiCaptureAndResetWorkingSetAccessBits+97

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

Kernel base = 0xfffff800`02e17000 PsLoadedModuleList = 0xfffff800`03054e50
Debug session time: Mon Oct 11 11:05:24.287 2010 (GMT-4)
System Uptime: 0 days 0:33:05.770
Loading Kernel Symbols
...............................................................
................................................................
.......................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {41790, fffffa8003516120, ffff, 0}

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

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

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

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041790, The subtype of the bugcheck.
Arg2: fffffa8003516120
Arg3: 000000000000ffff
Arg4: 0000000000000000

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


BUGCHECK_STR:  0x1a_41790

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  nvSCPAPISvr.ex

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002efaf9e to fffff80002e87740

STACK_TEXT:  
fffff880`0790e828 fffff800`02efaf9e : 00000000`0000001a 00000000`00041790 fffffa80`03516120 00000000`0000ffff : nt!KeBugCheckEx
fffff880`0790e830 fffff800`02ebadf9 : 00000000`00000000 00000000`10397fff fffffa80`00000000 fffffa80`07a00000 : nt! ?? ::FNODOBFM::`string'+0x33906
fffff880`0790e9f0 fffff800`031a01d0 : fffffa80`08367410 0007ffff`00000000 00000000`00000000 00000000`00000000 : nt!MiRemoveMappedView+0xd9
fffff880`0790eb10 fffff800`031a05db : 00000980`00000000 00000000`10000000 fffffa80`00000001 fffffa80`07a0ecb0 : nt!MiUnmapViewOfSection+0x1b0
fffff880`0790ebd0 fffff800`02e86993 : 00000000`00000000 00000000`00000000 fffffa80`07a04b30 fffffa80`07a05b40 : nt!NtUnmapViewOfSection+0x5f
fffff880`0790ec20 00000000`773bfffa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0061e808 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x773bfffa


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+33906
fffff800`02efaf9e cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+33906

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9

FAILURE_BUCKET_ID:  X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+33906

BUCKET_ID:  X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+33906

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

Kernel base = 0xfffff800`02e19000 PsLoadedModuleList = 0xfffff800`03056e50
Debug session time: Mon Oct 11 11:08:15.513 2010 (GMT-4)
System Uptime: 0 days 0:01:15.996
Loading Kernel Symbols
...............................................................
................................................................
.......Unable to load image Unknown_Module_00000000`00000000, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
Unable to add module at 00000000`00000000

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

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff8a8015ef6a0, 0, fffff88001511535, 5}


Could not read faulting driver name
Probably caused by : Ntfs.sys ( Ntfs!NtfsExpandHashTable+75 )

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

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: fffff8a8015ef6a0, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff88001511535, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000005, (reserved)

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


Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030c10e0
 fffff8a8015ef6a0 

FAULTING_IP: 
Ntfs!NtfsExpandHashTable+75
fffff880`01511535 234110          and     eax,dword ptr [rcx+10h]

MM_INTERNAL_CODE:  5

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  AvastSvc.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff88008b325d0 -- (.trap 0xfffff88008b325d0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000000000007ff rbx=0000000000000000 rcx=fffff8a8015ef690
rdx=0000000000000800 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88001511535 rsp=fffff88008b32760 rbp=0000000036e564e0
 r8=fffff8a001c13b50  r9=fffff8a0037d2b50 r10=fffffa80037dd148
r11=0000000000000001 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
Ntfs!NtfsExpandHashTable+0x75:
fffff880`01511535 234110          and     eax,dword ptr [rcx+10h] ds:ab00:fffff8a8`015ef6a0=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002f088c1 to fffff80002e89740

STACK_TEXT:  
fffff880`08b32468 fffff800`02f088c1 : 00000000`00000050 fffff8a8`015ef6a0 00000000`00000000 fffff880`08b325d0 : nt!KeBugCheckEx
fffff880`08b32470 fffff800`02e8782e : 00000000`00000000 fffffa80`04a43350 00000001`8015fb00 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x40e8b
fffff880`08b325d0 fffff880`01511535 : 00000000`36e564e0 fffff8a0`015f6140 fffff8a0`036cded0 00000000`00000000 : nt!KiPageFault+0x16e
fffff880`08b32760 fffff880`0150a896 : fffffa80`04a43350 fffffa80`04a43350 00000000`36e564e0 00000000`00000000 : Ntfs!NtfsExpandHashTable+0x75
fffff880`08b32790 fffff880`0150caf4 : fffff8a0`035faed8 fffffa80`07e53c10 fffffa80`07389010 00000000`000007ff : Ntfs!NtfsInsertHashEntry+0x152
fffff880`08b32810 fffff880`014f3d7f : fffffa80`07389010 fffffa80`07389010 fffff8a0`01dce501 00000000`00000000 : Ntfs!NtfsCreateNewFile+0xc14
fffff880`08b32b50 fffff880`0145cc0d : fffffa80`07389010 fffffa80`07e53c10 fffff880`0804a4b0 fffffa80`07af6b00 : Ntfs!NtfsCommonCreate+0xecf
fffff880`08b32d30 fffff800`02e815c7 : fffff880`0804a420 00000000`00000000 00000000`00000000 00000000`00000000 : Ntfs!NtfsCommonCreateCallout+0x1d
fffff880`08b32d60 fffff800`02e81581 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KySwitchKernelStackCallout+0x27
fffff880`0804a2f0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSwitchKernelStackContinue


STACK_COMMAND:  kb

FOLLOWUP_IP: 
Ntfs!NtfsExpandHashTable+75
fffff880`01511535 234110          and     eax,dword ptr [rcx+10h]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  Ntfs!NtfsExpandHashTable+75

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Ntfs

IMAGE_NAME:  Ntfs.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc14f

FAILURE_BUCKET_ID:  X64_0x50_Ntfs!NtfsExpandHashTable+75

BUCKET_ID:  X64_0x50_Ntfs!NtfsExpandHashTable+75

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

0: kd> lmtsmn
start             end                 module name
fffff880`0107c000 fffff880`010d3000   ACPI     ACPI.sys     Mon Jul 13 19:19:34 2009 (4A5BC106)
fffff880`02d61000 fffff880`02deb000   afd      afd.sys      Mon Jul 13 19:21:40 2009 (4A5BC184)
fffff880`042cd000 fffff880`042e3000   AgileVpn AgileVpn.sys Mon Jul 13 20:10:24 2009 (4A5BCCF0)
fffff880`0102a000 fffff880`01035000   amdxata  amdxata.sys  Tue May 19 13:56:59 2009 (4A12F2EB)
fffff880`04271000 fffff880`042b6000   asb24faf asb24faf.SYS Tue Jul 14 17:12:55 2009 (4A5CF4D7)
fffff880`02deb000 fffff880`02df5000   aswRdr   aswRdr.SYS   Tue Sep 07 10:47:47 2010 (4C865093)
fffff880`03bd8000 fffff880`03bfb000   aswSP    aswSP.SYS    Tue Sep 07 10:52:07 2010 (4C865197)
fffff880`02d51000 fffff880`02d61000   aswTdi   aswTdi.SYS   Tue Sep 07 10:52:27 2010 (4C8651AB)
fffff880`011f4000 fffff880`011fd000   atapi    atapi.sys    Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`01000000 fffff880`0102a000   ataport  ataport.SYS  Mon Jul 13 19:19:52 2009 (4A5BC118)
fffff880`042c6000 fffff880`042cd000   bbcap    bbcap.sys    Fri Nov 02 03:30:12 2007 (472AD204)
fffff880`0121c000 fffff880`01223000   Beep     Beep.SYS     Mon Jul 13 20:00:13 2009 (4A5BCA8D)
fffff880`03bc7000 fffff880`03bd8000   blbdrive blbdrive.sys Mon Jul 13 19:35:59 2009 (4A5BC4DF)
fffff880`00cc0000 fffff880`00cea000   cdrom    cdrom.sys    Mon Jul 13 19:19:54 2009 (4A5BC11A)
fffff880`00c00000 fffff880`00cc0000   CI       CI.dll       Mon Jul 13 21:32:13 2009 (4A5BE01D)
fffff880`00dcf000 fffff880`00dff000   CLASSPNP CLASSPNP.SYS Mon Jul 13 19:19:58 2009 (4A5BC11E)
fffff880`00d42000 fffff880`00da0000   CLFS     CLFS.SYS     Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`012e7000 fffff880`0135a000   cng      cng.sys      Mon Jul 13 19:49:40 2009 (4A5BC814)
fffff880`042b6000 fffff880`042c6000   CompositeBus CompositeBus.sys Mon Jul 13 20:00:33 2009 (4A5BCAA1)
fffff880`0580c000 fffff880`0581a000   crashdmp crashdmp.sys Mon Jul 13 20:01:01 2009 (4A5BCABD)
fffff880`03b26000 fffff880`03ba9000   csc      csc.sys      Mon Jul 13 19:24:26 2009 (4A5BC22A)
fffff880`04968000 fffff880`0499d000   CT20XUT  CT20XUT.SYS  Wed May 05 09:01:28 2010 (4BE16C28)
fffff880`048ba000 fffff880`04968000   ctac32k  ctac32k.sys  Wed Jul 02 04:38:22 2008 (486B3E7E)
fffff880`03cf7000 fffff880`03d9c700   ctaud2k  ctaud2k.sys  Wed May 05 08:59:48 2010 (4BE16BC4)
fffff880`0581b000 fffff880`05978000   CTEXFIFX CTEXFIFX.SYS Wed May 05 09:01:21 2010 (4BE16C21)
fffff880`057e2000 fffff880`057fd000   CTHWIUT  CTHWIUT.SYS  Wed May 05 09:01:32 2010 (4BE16C2C)
fffff880`03a49000 fffff880`03a7a000   ctoss2k  ctoss2k.sys  Wed May 05 08:57:46 2010 (4BE16B4A)
fffff880`03c43000 fffff880`03c4b000   ctprxy2k ctprxy2k.sys Wed May 05 08:59:51 2010 (4BE16BC7)
fffff880`04882000 fffff880`048ba000   ctsfm2k  ctsfm2k.sys  Wed May 05 08:57:33 2010 (4BE16B3D)
fffff880`03ba9000 fffff880`03bc7000   dfsc     dfsc.sys     Mon Jul 13 19:23:44 2009 (4A5BC200)
fffff880`03b17000 fffff880`03b26000   discache discache.sys Mon Jul 13 19:37:18 2009 (4A5BC52E)
fffff880`01435000 fffff880`0144b000   disk     disk.sys     Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`03dda000 fffff880`03dfc000   drmk     drmk.sys     Mon Jul 13 21:01:25 2009 (4A5BD8E5)
fffff880`059f7000 fffff880`05a00000   dump_atapi dump_atapi.sys Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`0499d000 fffff880`049a9000   dump_dumpata dump_dumpata.sys Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`049a9000 fffff880`049bc000   dump_dumpfve dump_dumpfve.sys Mon Jul 13 19:21:51 2009 (4A5BC18F)
fffff880`05800000 fffff880`0580c000   Dxapi    Dxapi.sys    Mon Jul 13 19:38:28 2009 (4A5BC574)
fffff880`10a9a000 fffff880`10b8e000   dxgkrnl  dxgkrnl.sys  Thu Oct 01 21:00:14 2009 (4AC5509E)
fffff880`10b8e000 fffff880`10bd4000   dxgmms1  dxgmms1.sys  Mon Jul 13 19:38:32 2009 (4A5BC578)
fffff880`05600000 fffff880`0564a000   emupia2k emupia2k.sys Wed May 05 08:57:27 2010 (4BE16B37)
fffff880`01275000 fffff880`01289000   fileinfo fileinfo.sys Mon Jul 13 19:34:25 2009 (4A5BC481)
fffff880`01229000 fffff880`01275000   fltmgr   fltmgr.sys   Mon Jul 13 19:19:59 2009 (4A5BC11F)
fffff880`0142b000 fffff880`01435000   Fs_Rec   Fs_Rec.sys   Mon Jul 13 19:19:45 2009 (4A5BC111)
fffff880`01035000 fffff880`0106f000   fvevol   fvevol.sys   Fri Sep 25 22:34:26 2009 (4ABD7DB2)
fffff880`017a0000 fffff880`017ea000   fwpkclnt fwpkclnt.sys Mon Jul 13 19:21:08 2009 (4A5BC164)
fffff880`0564c000 fffff880`057cd000   ha20x2k  ha20x2k.sys  Wed May 05 08:59:10 2010 (4BE16B9E)
fffff800`033f5000 fffff800`0343e000   hal      hal.dll      Mon Jul 13 21:27:36 2009 (4A5BDF08)
fffff880`10bd4000 fffff880`10bf8000   HDAudBus HDAudBus.sys Mon Jul 13 20:06:13 2009 (4A5BCBF5)
fffff880`0599b000 fffff880`059f7000   HdAudio  HdAudio.sys  Mon Jul 13 20:06:59 2009 (4A5BCC23)
fffff880`0161a000 fffff880`01623000   hwpolicy hwpolicy.sys Mon Jul 13 19:19:22 2009 (4A5BC0FA)
fffff880`03a26000 fffff880`03a3c000   intelppm intelppm.sys Mon Jul 13 19:19:25 2009 (4A5BC0FD)
fffff880`011ba000 fffff880`011da000   jraid    jraid.sys    Wed Jan 27 03:58:17 2010 (4B600029)
fffff880`043a3000 fffff880`043b2000   kbdclass kbdclass.sys Mon Jul 13 19:19:50 2009 (4A5BC116)
fffff800`00bca000 fffff800`00bd4000   kdcom    kdcom.dll    Mon Jul 13 21:31:07 2009 (4A5BDFDB)
fffff880`03c00000 fffff880`03c43000   ks       ks.sys       Wed Mar 03 23:32:25 2010 (4B8F37D9)
fffff880`01400000 fffff880`0141a000   ksecdd   ksecdd.sys   Mon Jul 13 19:20:54 2009 (4A5BC156)
fffff880`01775000 fffff880`017a0000   ksecpkg  ksecpkg.sys  Fri Dec 11 01:03:32 2009 (4B21E0B4)
fffff880`03c4b000 fffff880`03c50200   ksthunk  ksthunk.sys  Mon Jul 13 20:00:19 2009 (4A5BCA93)
fffff880`00cea000 fffff880`00d2e000   mcupdate_GenuineIntel mcupdate_GenuineIntel.dll Mon Jul 13 21:29:10 2009 (4A5BDF66)
fffff880`043b2000 fffff880`043c1000   mouclass mouclass.sys Mon Jul 13 19:19:50 2009 (4A5BC116)
fffff880`011da000 fffff880`011f4000   mountmgr mountmgr.sys Mon Jul 13 19:19:54 2009 (4A5BC11A)
fffff880`02d0a000 fffff880`02d15000   Msfs     Msfs.SYS     Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`010d3000 fffff880`010dd000   msisadrv msisadrv.sys Mon Jul 13 19:19:26 2009 (4A5BC0FE)
fffff880`01289000 fffff880`012e7000   msrpc    msrpc.sys    Mon Jul 13 19:21:32 2009 (4A5BC17C)
fffff880`03b0c000 fffff880`03b17000   mssmbios mssmbios.sys Mon Jul 13 19:31:10 2009 (4A5BC3BE)
fffff880`01608000 fffff880`0161a000   mup      mup.sys      Mon Jul 13 19:23:45 2009 (4A5BC201)
fffff880`01623000 fffff880`01715000   ndis     ndis.sys     Mon Jul 13 19:21:40 2009 (4A5BC184)
fffff880`04307000 fffff880`04313000   ndistapi ndistapi.sys Mon Jul 13 20:10:00 2009 (4A5BCCD8)
fffff880`04313000 fffff880`04342000   ndiswan  ndiswan.sys  Mon Jul 13 20:10:11 2009 (4A5BCCE3)
fffff880`057cd000 fffff880`057e2000   NDProxy  NDProxy.SYS  Mon Jul 13 20:10:05 2009 (4A5BCCDD)
fffff880`02c8a000 fffff880`02c99000   netbios  netbios.sys  Mon Jul 13 20:09:26 2009 (4A5BCCB6)
fffff880`02c00000 fffff880`02c45000   netbt    netbt.sys    Mon Jul 13 19:21:28 2009 (4A5BC178)
fffff880`01715000 fffff880`01775000   NETIO    NETIO.SYS    Mon Jul 13 19:21:46 2009 (4A5BC18A)
fffff880`02d15000 fffff880`02d26000   Npfs     Npfs.SYS     Mon Jul 13 19:19:48 2009 (4A5BC114)
fffff880`03b00000 fffff880`03b0c000   nsiproxy nsiproxy.sys Mon Jul 13 19:21:02 2009 (4A5BC15E)
fffff800`02e19000 fffff800`033f5000   nt       ntkrnlmp.exe Sat Jun 19 00:16:41 2010 (4C1C44A9)
fffff880`0144b000 fffff880`015ee000   Ntfs     Ntfs.sys     Mon Jul 13 19:20:47 2009 (4A5BC14F)
fffff880`01213000 fffff880`0121c000   Null     Null.SYS     Mon Jul 13 19:19:37 2009 (4A5BC109)
fffff880`0486a000 fffff880`04882000   nusb3hub nusb3hub.sys Thu Apr 22 21:34:35 2010 (4BD0F92B)
fffff880`03cc5000 fffff880`03cf5000   nusb3xhc nusb3xhc.sys Thu Apr 22 21:34:36 2010 (4BD0F92C)
fffff880`10a98000 fffff880`10a99180   nvBridge nvBridge.kmd Fri Jul 09 17:07:54 2010 (4C378FAA)
fffff880`05978000 fffff880`0599b000   nvhda64v nvhda64v.sys Mon Jun 21 18:07:25 2010 (4C1FE29D)
fffff880`0fe06000 fffff880`10a97e00   nvlddmkm nvlddmkm.sys Fri Jul 09 17:15:58 2010 (4C37918E)
fffff880`02c4e000 fffff880`02c74000   pacer    pacer.sys    Mon Jul 13 20:09:41 2009 (4A5BCCC5)
fffff880`04254000 fffff880`04271000   parport  parport.sys  Mon Jul 13 20:00:40 2009 (4A5BCAA8)
fffff880`0111d000 fffff880`01132000   partmgr  partmgr.sys  Mon Jul 13 19:19:58 2009 (4A5BC11E)
fffff880`010ea000 fffff880`0111d000   pci      pci.sys      Mon Jul 13 19:19:51 2009 (4A5BC117)
fffff880`011a3000 fffff880`011aa000   pciide   pciide.sys   Mon Jul 13 19:19:49 2009 (4A5BC115)
fffff880`011aa000 fffff880`011ba000   PCIIDEX  PCIIDEX.SYS  Mon Jul 13 19:19:48 2009 (4A5BC114)
fffff880`0141a000 fffff880`0142b000   pcw      pcw.sys      Mon Jul 13 19:19:27 2009 (4A5BC0FF)
fffff880`03d9d000 fffff880`03dda000   portcls  portcls.sys  Mon Jul 13 20:06:27 2009 (4A5BCC03)
fffff880`00d2e000 fffff880`00d42000   PSHED    PSHED.dll    Mon Jul 13 21:32:23 2009 (4A5BE027)
fffff880`042e3000 fffff880`04307000   rasl2tp  rasl2tp.sys  Mon Jul 13 20:10:11 2009 (4A5BCCE3)
fffff880`04342000 fffff880`0435d000   raspppoe raspppoe.sys Mon Jul 13 20:10:17 2009 (4A5BCCE9)
fffff880`0435d000 fffff880`0437e000   raspptp  raspptp.sys  Mon Jul 13 20:10:18 2009 (4A5BCCEA)
fffff880`0437e000 fffff880`04398000   rassstp  rassstp.sys  Mon Jul 13 20:10:25 2009 (4A5BCCF1)
fffff880`03aaf000 fffff880`03b00000   rdbss    rdbss.sys    Mon Jul 13 19:24:09 2009 (4A5BC219)
fffff880`04398000 fffff880`043a3000   rdpbus   rdpbus.sys   Mon Jul 13 20:17:46 2009 (4A5BCEAA)
fffff880`02cef000 fffff880`02cf8000   RDPCDD   RDPCDD.sys   Mon Jul 13 20:16:34 2009 (4A5BCE62)
fffff880`02cf8000 fffff880`02d01000   rdpencdd rdpencdd.sys Mon Jul 13 20:16:34 2009 (4A5BCE62)
fffff880`02d01000 fffff880`02d0a000   rdprefmp rdprefmp.sys Mon Jul 13 20:16:35 2009 (4A5BCE63)
fffff880`013a6000 fffff880`013e0000   rdyboost rdyboost.sys Mon Jul 13 19:34:34 2009 (4A5BC48A)
fffff880`00da0000 fffff880`00dcf000   SCSIPORT SCSIPORT.SYS Mon Jul 13 20:01:04 2009 (4A5BCAC0)
fffff880`03c51000 fffff880`03c5d000   serenum  serenum.sys  Mon Jul 13 20:00:33 2009 (4A5BCAA1)
fffff880`02c99000 fffff880`02cb6000   serial   serial.sys   Mon Jul 13 20:00:40 2009 (4A5BCAA8)
fffff880`01600000 fffff880`01608000   spldr    spldr.sys    Mon May 11 12:56:27 2009 (4A0858BB)
fffff880`00eb9000 fffff880`00fdf000   sptd     sptd.sys     Sun Oct 11 16:55:14 2009 (4AD24632)
fffff880`043c1000 fffff880`043c2480   swenum   swenum.sys   Mon Jul 13 20:00:18 2009 (4A5BCA92)
fffff880`01802000 fffff880`019ff000   tcpip    tcpip.sys    Sun Jun 13 23:39:04 2010 (4C15A458)
fffff880`02d44000 fffff880`02d51000   TDI      TDI.SYS      Mon Jul 13 19:21:18 2009 (4A5BC16E)
fffff880`02d26000 fffff880`02d44000   tdx      tdx.sys      Mon Jul 13 19:21:15 2009 (4A5BC16B)
fffff880`03a9b000 fffff880`03aaf000   termdd   termdd.sys   Mon Jul 13 20:16:36 2009 (4A5BCE64)
fffff880`03a00000 fffff880`03a26000   tunnel   tunnel.sys   Mon Jul 13 20:09:37 2009 (4A5BCCC1)
fffff880`043c3000 fffff880`043d5000   umbus    umbus.sys    Mon Jul 13 20:06:56 2009 (4A5BCC20)
fffff880`03cf5000 fffff880`03cf6f00   USBD     USBD.SYS     Mon Jul 13 20:06:23 2009 (4A5BCBFF)
fffff880`03cb4000 fffff880`03cc5000   usbehci  usbehci.sys  Mon Jul 13 20:06:30 2009 (4A5BCC06)
fffff880`04810000 fffff880`0486a000   usbhub   usbhub.sys   Mon Jul 13 20:07:09 2009 (4A5BCC2D)
fffff880`03c5e000 fffff880`03cb4000   USBPORT  USBPORT.SYS  Mon Jul 13 20:06:31 2009 (4A5BCC07)
fffff880`03a3c000 fffff880`03a49000   usbuhci  usbuhci.sys  Mon Jul 13 20:06:27 2009 (4A5BCC03)
fffff880`010dd000 fffff880`010ea000   vdrvroot vdrvroot.sys Mon Jul 13 20:01:31 2009 (4A5BCADB)
fffff880`00fe8000 fffff880`00ff6000   vga      vga.sys      Mon Jul 13 19:38:47 2009 (4A5BC587)
fffff880`02cba000 fffff880`02cdf000   VIDEOPRT VIDEOPRT.SYS Mon Jul 13 19:38:51 2009 (4A5BC58B)
fffff880`017ea000 fffff880`017fa000   vmstorfl vmstorfl.sys Mon Jul 13 19:42:54 2009 (4A5BC67E)
fffff880`01132000 fffff880`01147000   volmgr   volmgr.sys   Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`01147000 fffff880`011a3000   volmgrx  volmgrx.sys  Mon Jul 13 19:20:33 2009 (4A5BC141)
fffff880`0135a000 fffff880`013a6000   volsnap  volsnap.sys  Mon Jul 13 19:20:08 2009 (4A5BC128)
fffff880`02c74000 fffff880`02c8a000   vwififlt vwififlt.sys Mon Jul 13 20:07:22 2009 (4A5BCC3A)
fffff880`03a80000 fffff880`03a9b000   wanarp   wanarp.sys   Mon Jul 13 20:10:21 2009 (4A5BCCED)
fffff880`02cdf000 fffff880`02cef000   watchdog watchdog.sys Mon Jul 13 19:37:35 2009 (4A5BC53F)
fffff880`00e06000 fffff880`00eaa000   Wdf01000 Wdf01000.sys Mon Jul 13 19:22:07 2009 (4A5BC19F)
fffff880`00eaa000 fffff880`00eb9000   WDFLDR   WDFLDR.SYS   Mon Jul 13 19:19:54 2009 (4A5BC11A)
fffff880`02c45000 fffff880`02c4e000   wfplwf   wfplwf.sys   Mon Jul 13 20:09:26 2009 (4A5BCCB6)
fffff960`000d0000 fffff960`003df000   win32k   win32k.sys   Sat Jun 19 00:31:59 2010 (4C1C483F)
fffff880`00fdf000 fffff880`00fe8000   WMILIB   WMILIB.SYS   Mon Jul 13 19:19:51 2009 (4A5BC117)

Unloaded modules:
fffff880`015ee000 fffff880`015fc000   crashdmp.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`013e0000 fffff880`013ec000   dump_ataport
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`013ec000 fffff880`013f5000   dump_atapi.s
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`01200000 fffff880`01213000   dump_dumpfve
    Timestamp: unavailable (00000000)
    Checksum:  00000000

I find an almost guaranteed cause of BSOD's on your system. Please uninstall any CD virtualization programs such as Daemon Tools and Alcohol 120%. They use a driver, found in your dump, sptd.sys, which is notorious for causing BSODs. Use this SPTD uninstaller when you're done: DuplexSecure - Downloads. Select delete; do not select reinstall.

Here is an alternative virtualization program that does not user the sptd.sys driver:
Freeware MagicISO Virtual CD/DVD-ROM(MagicDisc) Overview

nvSCPAPISvr.exe - NVidia Stereoscopic 3D Vision support service. Background service installed by the drivers of NVidia cards introduced from August 2009 onwards. This service supports the new NVidia Stereoscopic 3D Vision feature for gamers who want to use 3D wireless glasses when playing their games. I have seen reports via Google that folks are having trouble with this software. Suggest you visit the NVidia site and see if there is a fix, an upgrade, etc.

I see you have some out of date drivers on your system. Old drivers can and do cause memory corruption and crashes. Update these drivers.

bbcap.sys Fri Nov 02 03:30:12 2007 - Mirror Miniport Driver belonging to BB Flash Recorder. This is XP software. Try to update this drivers from Microsoft or uninstall the the flash recorder and upgrade to one compatible with Win 7. Windows Update.

ctac32k.sys Wed Jul 02 04:38:22 2008 - Creative Audio Driver Creative Worldwide Support

How to find Drivers:

- I have listed links to most of the drivers in the code box below. Please use the links there to see what info I've found about those drivers.
- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.

- - The most common drivers are listed on this page: Driver Reference
- - Driver manufacturer links are on this page: Drivers and Downloads

Uninstall SPTD, update the above drivers (or uninstall), reboot your system and let's see how it does. If you get another BSOD, upload the dump to us and test your RAM following the instructions in this tutorial:

http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

Southman · Oct 11, 2010

Hi and thank you!

Thx for the incredible fast help, really appreciated!

Hope there is a solution to this problem, guess I should add that the BIOS is updated to the latest version also.

//South

CarlTR6 · Oct 11, 2010

I have finished; you can refresh your page. And you are welcome. I think you will be able to solve your problem.

Southman · Oct 11, 2010

Ohh, Thanks a lot! Awesome!

Uninstalled Daemon tools, and used SPTDINST to "clean" the drivers. Restarted and got 2 Bsods, guess it was some kind of reaction or something :O

Looked quickly in bluescreenview to see what it was, one of the Bsods were the same as before "Page_Fault....." error code 50 and the other I haven't seen before: "NTFS_FILE_SYSTEM" error code 24. The files highlighted on the NTFS-bsod were ataport.sys, NTFS.sys and Ntoskrnl.exe.

Guess I'll have to wait and see how it works.

Also uninstalled Nvidia 3d drivers, have no use for them. Also BB flashback recoder i removed. The ctac32k.sys was a little more trickier, checked creative auto update and it told me that I had the latest drivers. So nothing to do about that I guess.

But what do you think about the pauge_fault & memory management error? Can bad programs/drivers cause the memory functionality to fail? Like sptd.sys for example

Thx for everything so far!

//South

(Uploaded the minidump just in case..)

CarlTR6 · Oct 11, 2010

Upload those dumps to us and we can see what they show. Because one of the dumps is blaming NTFS.sys, which is a Microsoft system driver and not likely to be the real cause, let's start checking hardware.

First, run Check Disk.

Run CHKDSK /R /F from an elevated (Run as adminstrator) Command Prompt. Please do this for each hard drive on your system.
When it tells you it can't do it right now - and asks you if you'd like to do it at the next reboot - answer Y (for Yes) and press Enter. Then reboot and let the test run. It may take a while for it to run, but keep an occasional eye on it to see if it generates any errors. See "CHKDSK LogFile" below in order to check the results of the test.

Elevated Command Prompt:
Go to Start and type in "cmd.exe" (without the quotes)
At the top of the Search Box, right click on Cmd.exe and select "Run as administrator"

CHKDSK LogFile:
Go to Start and type in "eventvwr.msc" (without the quotes) and press Enter
Expand the Windows logs heading, then select the Application log file entry.
Double click on the Source column header.
Scroll down the list until you find the Chkdsk entry (wininit for Windows 7) (winlogon for XP).

Copy/paste the results into your next post.

Next, test your RAM. This test will take about 7 hours. Follow the instructions in this tutorial:

[FONT=&quot]http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html[/FONT]

Errors will show up on your screen in red. Post the results of Memtest.

I know you have previously run these tests; but let's do it again.

CarlTR6 · Oct 11, 2010

Since it may be a RAM problem, I am going to ask the hardware experts for some help with this. I am not an expert with RAM by any stretch of the imagination.

Southman · Oct 11, 2010

Rebooted the computer once more and got a BSOD again but with a registry_error this time with ntoskrnl.exe highlighted in bluescreen view.

Will upload the minidump for this one too.

/ Okay, I'll do the test tonight/tomorrow.

Thx!

Can't understand though why these Bsods has started to occure today... Nuts!

CarlTR6 · Oct 11, 2010

Error code 51, REGISTRY_ERROR: Usual causes: Hardware failure, File system corruption, Security issues.

Code:

Kernel base = 0xfffff800`02e0a000 PsLoadedModuleList = 0xfffff800`03047e50
Debug session time: Mon Oct 11 14:47:09.689 2010 (GMT-4)
System Uptime: 0 days 0:01:08.172
Loading Kernel Symbols
...............................................................
................................................................
....................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 51, {1, fffff8a0000230d0, 10df000, 374}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::NNGAKEGL::`string'+9b6a )

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

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

REGISTRY_ERROR (51)
[B]Something has gone badly wrong with the registry[/B].  If a kernel debugger
is available, get a stack trace. [B]It can also indicate that the registry got
an I/O error while trying to read one of its files, so it can be caused by
hardware problems or filesystem corruption.[/B]
It may occur due to a failure in a refresh operation, which is used only
in by the security system, and then only when resource limits are encountered.
Arguments:
Arg1: 0000000000000001, (reserved)
Arg2: fffff8a0000230d0, (reserved)
Arg3: 00000000010df000, depends on where Windows bugchecked, may be pointer to hive
Arg4: 0000000000000374, depends on where Windows bugchecked, may be return code of
    HvCheckHive if the hive is corrupt.

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


CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x51

PROCESS_NAME:  services.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff800031a8f78 to fffff80002e7a740

STACK_TEXT:  
fffff880`029ef438 fffff800`031a8f78 : 00000000`00000051 00000000`00000001 fffff8a0`000230d0 00000000`010df000 : nt!KeBugCheckEx
fffff880`029ef440 fffff800`031181c4 : 00000000`00298b49 00000000`000086f7 00000000`00000000 fffffa80`00000004 : nt! ?? ::NNGAKEGL::`string'+0x9b6a
fffff880`029ef4a0 fffff800`031173db : fffff8a0`000230d0 fffff8a0`000230d0 fffff8a0`00034f40 00000000`002fa840 : nt!HvMarkDirty+0x125
fffff880`029ef500 fffff800`030d9ccb : 00000000`00000001 fffff8a0`04edf114 fffff8a0`0479af0c fffff8a0`000230d0 : nt!HvMarkCellDirty+0x13b
fffff880`029ef550 fffff800`030d9aa4 : fffff8a0`0479af0c 00000000`ffffffff fffff8a0`0479af0c fffff8a0`000230d0 : nt!CmpMarkKeyValuesDirty+0x14b
fffff880`029ef5f0 fffff800`030d91aa : fffff8a0`000230d0 00000000`ffffffff fffff8a0`0479af0c fffff8a0`000230d0 : nt!CmpFreeKeyValues+0x24
fffff880`029ef620 fffff800`030d8ed8 : fffff8a0`000230d0 00000000`0087f7c8 fffff8a0`0479af0c fffff8a0`00a3cf08 : nt!CmpSyncKeyValues+0x7a
fffff880`029ef700 fffff800`030db79e : fffff8a0`023f8000 00000000`003fa3b8 fffffa80`00000000 00000000`00000000 : nt!CmpCopySyncTree2+0x2a8
fffff880`029ef7b0 fffff800`030db6b7 : 00000000`00000000 00000000`00000002 fffff8a0`02931c90 fffff8a0`02381a50 : nt!CmpCopySyncTree+0x6e
fffff880`029ef800 fffff800`030db286 : fffff8a0`01bf0360 00000000`00000000 00000000`00000001 00000000`00000000 : nt!CmpSaveBootControlSet+0x307
fffff880`029ef9e0 fffff800`02e79993 : fffffa80`06ff2610 00000000`0040d1f0 fffff880`029efab0 00000000`00000001 : nt!NtInitializeRegistry+0xc6
fffff880`029efa30 fffff800`02e75f30 : fffff800`030db22f 00000000`00000220 00000000`0015f788 00000000`0015fab8 : nt!KiSystemServiceCopyEnd+0x13
fffff880`029efbc8 fffff800`030db22f : 00000000`00000220 00000000`0015f788 00000000`0015fab8 00000000`000a001f : nt!KiServiceLinkage
fffff880`029efbd0 fffff800`02e79993 : fffffa80`06ff2610 fffff880`029efca0 fffff880`029efca0 00000000`00000002 : nt!NtInitializeRegistry+0x6f
fffff880`029efc20 00000000`774f0afa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0015fa38 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x774f0afa


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::NNGAKEGL::`string'+9b6a
fffff800`031a8f78 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::NNGAKEGL::`string'+9b6a

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9

FAILURE_BUCKET_ID:  X64_0x51_nt!_??_::NNGAKEGL::_string_+9b6a

BUCKET_ID:  X64_0x51_nt!_??_::NNGAKEGL::_string_+9b6a

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

I suggest that you also run Prime to test your CPU. We need to check all hardware.

http://www.sevenforums.com/tutorials/100352-cpu-stress-test-prime95.html

Dave76 · Oct 12, 2010

Hi Southman, can you tell us what you changed your Dram voltage & QPI voltage to?

When you run memtest86+ you are looking for bad RAM card, bad motherboard slot, so you need to follow the testing procedure in the tutorial.
Sometimes errors from these tests can be corrected by adjusting the settings.

Can you download CPUZ and post a snip of the CPU, Mainboard, Memory, and SPD tabs.

For posting the information , enter 'Snipping tool' in the Start button > Search box, hit enter. Select the area you want to post and save to a convenient place.
How to Post a Screenshot in Seven Forums

Have you been checking your temperatures?

Use Speed Fan or Real Temp , run one of these and check the CPU temps when at idle, under load and/or testing.
Let us know the minimum and maximum temps you get.

Southman · Oct 12, 2010

Thx for the replies!

Will update this post until I get all the pics & data needed... Will do as much as possible today!

When I increased my Dram volt/QPI volt it was with only a tiny bit. Memory voltage I increased to 1.56v from 1.50v originally. And QPI to 1.2v with 1.1v originally. But yesterday when all the bsods appeared I put them back to auto. (Loaded optimized defaults to see if it would make any difference to the current Bsods.)

(My RAM-memmory is specified at 1.65v @1600Mhz, but in bios they currently are on 1.5v @1333Mhz. I can activate XMP to get them on 1600Mhz, but that also effects my bclk to 160 (133 standard) mhz while the multiplier goes down to 18x which gets my cpu to 2.88ghz. Tested that once but got temperatures like 50C idle on my CPU so i loaded the default settings.)

# Posted the cpu-z pics

# Temps:
Idle: 29-35c.
Load: 42-49.

# Chkdsk:
Have completed chkdsk on both of my harddrives now, none of them had any errors according to chkdsk. Was able to find the logfile for my second hdd, but not the system harddrive. How can that be? But is there any use to paste the logs here if there were no errors?

# Memtest:
Ran memtest for 10 hrs - 15 pass total... No errors!"
Settings: Auto voltage, auto timings (9-9-9-24) & cmd rate 1.

//South

Dave76 · Oct 13, 2010

You're welcome, good information.

The temps look good, a bit concerning about the temps when you set the RAM at 1600, leave it at 1333 for now.

No need to post the Chkdsk logs as long as there are no errors.

Good job on the DRAM & QPI voltage increase, best to keep them at small increaments, especially the QPI, for future reference max is 1.2V.
You must keep the voltage difference between the DRAM and the QPI no more than 0.5v, this is due to the integrated memory controller.

Manually set the first four RAM timings to the SPD recommended 1333MHz, of 9-9-9-24 and change the 'Command Rate' to 2. Leave the rest on Auto.

Then, run memtest86+ as per the tutorial:

How to Test and Diagnose RAM Issues with Memtest86+

Be sure to run for 7 passes, run overnight if possible. Note any errors and post here.
You can stop the test if you get any errors.

If you get errors, then proceed as per Part 3 of the tutorial.
This is important, you need to be sure you test for bad RAM cards and bad motherboard slots.

If you get errors you can stop the test and let us know the results.

Next step, if required, will be to set the QPI voltage to 1.2v and the DRAM voltage to 1.56v and run memtest86+ again.

Southman · Oct 13, 2010

Okay good to know about the QPI!

thx

The standard settings for the RAM was 1333 mhz 9-9-9-24 and cmd rate 2 when i started the computer for the first time, so will keep those settings as you said and put all voltages to auto. Have gotten 8 Bsods today, just in about an hour. Removed one ramstick and now it seems stable. Are going to put it in again when i am going to do the memtest.

I'm getting more and more certain that it's either the bios-settings or a hardware problem. Don't think that it's caused by bad drivers. But who knows, I might just be surprised... We'll find out, i hope!

Southman · Oct 13, 2010

Was wrong, the cmd rate was 1 from the start and still is. Why chould i change this?

//South

Have searched the web and many people say that 2t will be more stable and better, som people also got rid of bsods using 2t.. Could this be my issue? :O

Southman · Oct 14, 2010

Finished the memtest! Updated the top-post .

No errors found. I think it is the dram voltage/qpi voltage causing bsods, cause' when i think about it, nearly all bsods have occured on "coold boot". Then one-two hours later it's stable as hell!

What do you think about it?

And is my next step to run prime 95?

CarlTR6 · Oct 14, 2010

Did you run Memtest from a cold boot? If not, try that.

Dave76 · Oct 14, 2010

You are right about the cmd rate, when set at 2 it will help if you're having stability problems.

Tell us the RAM timing settings and voltages when it passed the memtest86+, just for confirmation.
1333MHz, of 9-9-9-24 and the 'Command Rate' to 2, is this correct?
DRAM 1.5v and QPI 1.1v, correct?
Also confirm if you have set the RAM timings manually, voltages manually.
This issue has been attributed at least partially due to auto settings, set the above manually.

Run memtest86+ at the cold boot scenario, this is important.
This will help to pinpoint the cause, sometimes this can be fixed by adjusting the settings. If that doesn't do it then you need to RMA the RAM.
If you end up returning the RAM, be sure to get RAM from your motherboard compatible list.

Let us know the results from the cold boot memtest86+.

Southman · Oct 16, 2010

Okay, thx for reply!

The ram-timings were on auto, 9-9-9-24 cmd rate 1. Didn't see the point to change the timings manually to 9-9-9-24 when they already were on that settings, and I also kept the cmd rate at 1. I figured that if i would get any errors then I could change the cmd rate to 2 and do memtest again.

Will do the coldboot test soon.

Thx guys!

Southman · Oct 27, 2010

Sorry for this late update, have been away for a little vacation.

Ran the memtest on coldboot also now, no errors.

And also with a lot of testing with different voltages I don't anymore think that they are causing it. Getting bsods with both raised & auto voltages.

I'm also a little concerned cause i'm missing one cable from the front panel, the "sleep led" i dont have, but from what i've rad the front panel shouldn't be likely to cause any bsods.

Started to look inside my computer, and noticed that i had a 8-pin powersupply-connector on my mobo, but with only 4 pins inserted. Googled it and it seems like there should be 8-pins connected instead of my 4. So I decided to connect all 8 of them and do a fresh install, have had the feeling that all the bsods screwed up my hdd a bit.

So a fresh start it is!

What do you think I should do next if the bsods still appears? Any suggestions?

Thanks so far, you guys have been really helpful!!

CarlTR6 · Oct 27, 2010

What you are saying is that you think it is possibly a power supply problem - and that could be. Power supply do weird things cause all sorts of varied symptoms.

Bsod - Any Clue?

New member

My Computer

Antique Senior Member

My Computer

New member

My Computer

Antique Senior Member

My Computer

New member

My Computer

Antique Senior Member

My Computer

Antique Senior Member

My Computer

New member

My Computer

Antique Senior Member

My Computer

Endeavor to Persevere

My Computer

New member

My Computer

Endeavor to Persevere

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

Antique Senior Member

My Computer

Endeavor to Persevere

My Computer

New member

My Computer

New member

My Computer

Antique Senior Member

My Computer