New Build, blue screen issues

[Su593ct]

Hello all, i recently just built a new pc; specs should be on my profile. Everything seems to be running smoothly, i ran several programs to check stability. RealTemp, 3D Vantage, Prime 95, CPU-Z and everything seems to check out. However, i keep getting a Blue screen from time to time, not sure what is wrong exactly.

Thanks in advance for all the help!


Windows 7 . . .
- x64
- Windows 7 Home Premium 64bit
- Full Retail Builders Edition
- OEM = came pre-installed on system
- Full Retail = you purchased it from retailer

- What is the age of system (hardware)? 5 Days
- What is the age of OS installation (have you re-installed the OS?) 5 Days, no

 

[Su593ct]

Alright, it crashed again during restart; started to load windows and restarted with a crash. Here are the two dumps, the old one as well as the newest one.

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

Additional information about the problem:
BCCode: 3b
BCP1: 00000000C0000005
BCP2: FFFFF88000CF867A
BCP3: FFFFF88009E53580
BCP4: 0000000000000000
OS Version: 6_1_7600
Service Pack: 0_0
Product: 768_1

Update: My memory seems to be running at 802 mhz as opposed to 1600...After running Memtest86, it went through one pass and i received an error on Test #7 and 2 errors on test #5. Also below on Errors per Memory slot, it states that the one error was found on my first chip.

I will continue to run tests to see what other errors come up; in the mean time any suggestions?

 

[CarlTR6]

Hi and welcome to the forum. I finally got the files to download. I was having a glitch. I will take a look and be back. I will edit this post; so please refresh this page in about 15 minutes.

Bugcheck 3B, SYSTEM_SERVICE_EXCEPTION. Usual causes: System service, Device driver, graphics driver, ?memory.

Bugcheck 7E, SYSTEM_THREAD_EXCEPTION_NOT_HANDLED. Usual causes: Insufficient disk space, Device driver, Video card, BIOS, Breakpoint with no debugger attached, Hardware incompatibility, Faulty system service, Memory, 3rd party remote control.

One dump blames CLFS.SYS, a Windows system driver which is highly unlikely to be the real cause, and the other blames RTKVHD64.sys, Realtek High Definition Audio Function Driver. This driver is up to date. Both dumps show memory corruption.

Although your version of Kaspersky generally runs well with Win 7, I recommend that you completely uninstall using this removal tool: Tool. Other versions of Kaspsersky are know to cause BSOD's on some Win 7 systems. I suggest that you eliminate this as a possible cause for trouble shooting purposes. Download and install Microsoft Security Essentials in its place. Once you get your system stable, you can certainly try Kaspsersky again.

See how your system does without Kaspersky. If you get another BSOD, upload it to us and test your RAM with Memtest 86 following the instructions in this tutorial: http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html. Run Memtest from a cold boot after you computer has been off for an hour or two. Let it run for at least 7 passes; this will take 6-8 hours. If you see errors, you can stop the test. Post back with your results.

Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02c07000 PsLoadedModuleList = 0xfffff800`02e44e50
Debug session time: Tue Jan 25 09:22:27.170 2011 (GMT-5)
System Uptime: 0 days 0:05:26.060
Loading Kernel Symbols
...............................................................
................................................................
...............................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff88000cf867a, fffff88009e53580, 0}

Probably caused by : CLFS.SYS ( CLFS!ClfsLsnInvalid+1a )

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

0: 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: fffff88000cf867a, Address of the exception record for the exception that caused the bugcheck
Arg3: fffff88009e53580, 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: 
CLFS!ClfsLsnInvalid+1a
fffff880`00cf867a 483901          cmp     qword ptr [rcx],rax

CONTEXT:  fffff88009e53580 -- (.cxr 0xfffff88009e53580)
rax=ffffffff00000000 rbx=0000000000000001 rcx=0000000000000024
rdx=fffff88000cff5e0 rsi=fffff8a000981ef0 rdi=fffff8a00a447c20
rip=fffff88000cf867a rsp=fffff88009e53f58 rbp=0000000000000000
 r8=0000000000000000  r9=fffff8a000981f00 r10=fffff80002df3720
r11=fffffa8005ab7760 r12=0000000000000000 r13=0000000000000001
r14=0000000000000000 r15=0000000000000078
iopl=0         nv up ei ng nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010282
CLFS!ClfsLsnInvalid+0x1a:
fffff880`00cf867a 483901          cmp     qword ptr [rcx],rax ds:002b:00000000`00000024=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  svchost.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002f02a8d to fffff88000cf867a

STACK_TEXT:  
fffff880`09e53f58 fffff800`02f02a8d : fffff8a0`09ec5000 fffff800`02f00eb7 fffff8a0`0a822bf0 fffff800`02dac2dd : CLFS!ClfsLsnInvalid+0x1a
fffff880`09e53f60 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!CmpLogCheckpoint+0xf9


FOLLOWUP_IP: 
CLFS!ClfsLsnInvalid+1a
fffff880`00cf867a 483901          cmp     qword ptr [rcx],rax

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  CLFS!ClfsLsnInvalid+1a

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: CLFS

IMAGE_NAME:  CLFS.SYS

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc11d

STACK_COMMAND:  .cxr 0xfffff88009e53580 ; kb

FAILURE_BUCKET_ID:  X64_0x3B_CLFS!ClfsLsnInvalid+1a

BUCKET_ID:  X64_0x3B_CLFS!ClfsLsnInvalid+1a

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

Debug session time: Tue Jan 25 11:32:55.253 2011 (GMT-5)
System Uptime: 0 days 0:00:09.143
Loading Kernel Symbols
...............................................................
.......................................................
Loading User Symbols
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff80002f46a83, fffff88003b68778, fffff88003b67fe0}

Unable to load image \SystemRoot\system32\drivers\RTKVHD64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for RTKVHD64.sys
*** ERROR: Module load completed but symbols could not be loaded for RTKVHD64.sys
Probably caused by : RTKVHD64.sys ( RTKVHD64+1b1779 )

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

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

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
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.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80002f46a83, The address that the exception occurred at
Arg3: fffff88003b68778, Exception Record Address
Arg4: fffff88003b67fe0, Context Record Address

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!CmpDoCreateChild+133
fffff800`02f46a83 488b842460010000 mov     rax,qword ptr [rsp+160h]

EXCEPTION_RECORD:  fffff88003b68778 -- (.exr 0xfffff88003b68778)
ExceptionAddress: fffff80002f46a83 (nt!CmpDoCreateChild+0x0000000000000133)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: 0000000080044f04
Attempt to read from address 0000000080044f04

CONTEXT:  fffff88003b67fe0 -- (.cxr 0xfffff88003b67fe0)
rax=000000008002eee0 rbx=fffff88003b69120 rcx=0000000000000010
rdx=000000008002eee0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002f46a83 rsp=fffff88003b689b0 rbp=fffffa80046d2010
 r8=0000000000000001  r9=fffff80002c62000 r10=000000008002ef38
r11=0000000000000000 r12=0000000000000001 r13=0000000000000000
r14=0000000000000000 r15=fffff8a0012c2258
iopl=0         nv up ei ng nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010282
nt!CmpDoCreateChild+0x133:
fffff800`02f46a83 488b842460010000 mov     rax,qword ptr [rsp+160h] ss:0018:fffff880`03b68b10=fffff88003b68b34
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

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

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000080044f04

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002f0a0e0
 0000000080044f04 

FOLLOWUP_IP: 
RTKVHD64+1b1779
fffff880`08c2f779 ??              ???

BUGCHECK_STR:  0x7E

LAST_CONTROL_TRANSFER:  from fffff80002f476fc to fffff80002f46a83

STACK_TEXT:  
fffff880`03b689b0 fffff800`02f476fc : fffff8a0`00023160 fffffa80`00810ed8 fffff8a0`000543a0 fffffa80`046d2010 : nt!CmpDoCreateChild+0x133
fffff880`03b68ac0 fffff800`02fad125 : fffff8a0`03c6cedc fffff880`00810ed8 fffff880`03b68cc0 fffff880`03b68cc0 : nt!CmpDoCreate+0x268
fffff880`03b68c00 fffff800`02fcbe84 : fffff800`02fabcc0 00000000`00000001 fffffa80`046d2010 fffff880`03b69000 : nt!CmpParseKey+0x1465
fffff880`03b68ed0 fffff800`02fd0e4d : fffffa80`046d2010 fffff880`03b69030 fffff8a0`00000240 fffffa80`03998f30 : nt!ObpLookupObjectName+0x585
fffff880`03b68fd0 fffff800`02f70654 : 00000000`0002001f 00000000`00000000 fffff8a0`01292a00 fffff880`03b69100 : nt!ObOpenObjectByName+0x1cd
fffff880`03b69080 fffff800`02f7072e : fffff880`03b69498 fffff8a0`00020019 fffff880`03b694b0 fffff800`02fe8514 : nt!CmCreateKey+0x2e1
fffff880`03b691f0 fffff800`02cd1993 : fffffa80`039d1040 fffff800`02fb2fca fffff880`03b694d0 00000000`00020019 : nt!NtCreateKey+0x2e
fffff880`03b69240 fffff800`02ccdf30 : fffff800`02f43522 00000000`00320032 fffff800`02ccdf30 00000000`00000001 : nt!KiSystemServiceCopyEnd+0x13
fffff880`03b69448 fffff800`02f43522 : 00000000`00320032 fffff800`02ccdf30 00000000`00000001 00000000`00000000 : nt!KiServiceLinkage
fffff880`03b69450 fffff800`030ae4c6 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00020019 : nt!IopCreateRegistryKeyEx+0x7e
fffff880`03b69520 fffff800`030aea01 : 00000000`00000005 fffff880`03b69680 fffffa80`046f8990 00000000`00000004 : nt!IopProcessSetInterfaceState+0x126
fffff880`03b69620 fffff880`08c2f779 : fffffa80`046f8990 fffffa80`04708550 fffffa80`046f8990 fffffa80`04708550 : nt!IoSetDeviceInterfaceState+0x41
fffff880`03b69650 fffffa80`046f8990 : fffffa80`04708550 fffffa80`046f8990 fffffa80`04708550 fffff8a0`00000200 : RTKVHD64+0x1b1779
fffff880`03b69658 fffffa80`04708550 : fffffa80`046f8990 fffffa80`04708550 fffff8a0`00000200 fffff880`03b69820 : 0xfffffa80`046f8990
fffff880`03b69660 fffffa80`046f8990 : fffffa80`04708550 fffff8a0`00000200 fffff880`03b69820 fffff8a0`0120011e : 0xfffffa80`04708550
fffff880`03b69668 fffffa80`04708550 : fffff8a0`00000200 fffff880`03b69820 fffff8a0`0120011e fffff8a0`012cf700 : 0xfffffa80`046f8990
fffff880`03b69670 fffff8a0`00000200 : fffff880`03b69820 fffff8a0`0120011e fffff8a0`012cf700 00000000`00000000 : 0xfffffa80`04708550
fffff880`03b69678 fffff880`03b69820 : fffff8a0`0120011e fffff8a0`012cf700 00000000`00000000 fffff800`02dd38c6 : 0xfffff8a0`00000200
fffff880`03b69680 fffff8a0`0120011e : fffff8a0`012cf700 00000000`00000000 fffff800`02dd38c6 fffff880`03b69858 : 0xfffff880`03b69820
fffff880`03b69688 fffff8a0`012cf700 : 00000000`00000000 fffff800`02dd38c6 fffff880`03b69858 fffff880`03b697e8 : 0xfffff8a0`0120011e
fffff880`03b69690 00000000`00000000 : fffff800`02dd38c6 fffff880`03b69858 fffff880`03b697e8 00000000`00000000 : 0xfffff8a0`012cf700


SYMBOL_STACK_INDEX:  c

SYMBOL_NAME:  RTKVHD64+1b1779

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: RTKVHD64

IMAGE_NAME:  RTKVHD64.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4d1c020a

STACK_COMMAND:  .cxr 0xfffff88003b67fe0 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_RTKVHD64+1b1779

BUCKET_ID:  X64_0x7E_RTKVHD64+1b1779

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

 

[Su593ct]

Alright, i removed kaspersky and installed windows essentials. However, i keep getting crashes. Here are all the dumps. Would be greatly appreciated if someone can look them over.
http://www.newegg.com/Product/Produ...cm_re=g_skill_ripjaw_x-_-20-231-430-_-Product