Random BSOD. Reports attached

Akira181 · Dec 18, 2010

Windows 7 professional x64
OEM Version
Hardware 6 months old
Install 2 weeks old

Getting a lot of BSOD with various error messages. Only overclocking I've done is setting the RAM to the max speed listed on the packaging (1066Mhz) but I left the NB voltage at stock.

DeanP · Dec 18, 2010

Hello Akira181 and welcome to Seven Forums!

1. sptd.sys
Please remove virtual CD program such as Daemons Tools and Alcohol 120%. They use a file "sptd.sys", which is a common reason of Blue Screen of Death. Use this tool when you're done: DuplexSecure - Downloads

Please remove that first. Will find more results of what is causing to crash your system.

Akira181 · Dec 19, 2010

so I can reinstall Daemon Tools after I've installed the DuplexSecure thing?

Thanks,
Akira

edit*
just noticed that Daemon Tools Lite doesn't even appear in the Uninstall Programs List. Weird.

Uninstalled it anyway but then the download will not work. When I download the x64 version and try to run it, it says it is not a valid Win32 application.

Tews · Dec 19, 2010

No.. what is the purpose of reinstalling it after you uninstall it?? Leave it uninstalled and see if it resolves your BSOD problems..

Akira181 · Dec 20, 2010

also noticed my firefox is crashing quite a lot, a lot more than it did with XP. Not sure if this is related to the BSOD instability though.

yowanvista · Dec 20, 2010

Akira181 said:
also noticed my firefox is crashing quite a lot, a lot more than it did with XP. Not sure if this is related to the BSOD instability though.

You may have unstable addons/plugins enabled

Akira181 · Dec 20, 2010

It's a fresh firefox install. Only addon's I have are Jave 6.0.22 and java 6.0.23 (not sure why both are installed, surely one is enough?).

DeanP · Dec 20, 2010

uninstall 6.0.22.
Also, try another web browser.

Akira181 · Jan 15, 2011

still getting a lot of blue screens, 4 today alone. And all I was doing was watching movies and some youtube clips and 1 BSOD from gathering the reports for this post.

Any further suggestions?

Thanks in advance!

CarlTR6 · Jan 15, 2011

I only see three dumps from today. All of them show sptd.sys still loaded on your system. You need to get rid of this driver. Have you run Duplex Secure and did you select "Uninstall" rather than "Reinstall"?

In all three dumps, I see an outdated driver involved in the crashes. This driver is quite obsolete. Update this driver or uninstall the software package.

ewusbmdm.sys Sun Mar 16 23:06:13 2008 - USB Modem/Serial Device Driver - "Huawei Mobile Connect" package. http://www.huawei.com/mobileweb/en/products/view.do?id=1503&pageId=null.

You have another outdated driver. Update the driver through the link provided or uninstall Easy saver.

gdrv.sys Thu Mar 12 23:22:29 2009 - Gigabyte Easy Saver - mobo power utility driver GIGABYTE - Support & Downloads - Downloads - Motherboard.

Two of your dumps blame NTFS.sys, which is your file system. I suggest that you run CheckDisk -

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).

Copy/paste the results into your next post.

Code:

Windows 7 Kernel Version 7600 MP (3 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02c03000 PsLoadedModuleList = 0xfffff800`02e40e50
Debug session time: Sat Jan 15 11:17:08.989 2011 (GMT-5)
System Uptime: 0 days 1:27:12.628
Loading Kernel Symbols
...............................................................
................................................................
..........................
Loading User Symbols
Loading unloaded module list
.........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff80002f67bd2, fffff88003177968, fffff880031771d0}

Probably caused by : ntkrnlmp.exe ( nt!CmpDereferenceNameControlBlockWithLock+aa )

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

1: 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: fffff80002f67bd2, The address that the exception occurred at
Arg3: fffff88003177968, Exception Record Address
Arg4: fffff880031771d0, 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!CmpDereferenceNameControlBlockWithLock+aa
fffff800`02f67bd2 488b02          mov     rax,qword ptr [rdx]

EXCEPTION_RECORD:  fffff88003177968 -- (.exr 0xfffff88003177968)
ExceptionAddress: fffff80002f67bd2 (nt!CmpDereferenceNameControlBlockWithLock+0x00000000000000aa)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT:  fffff880031771d0 -- (.cxr 0xfffff880031771d0)
rax=8b44310f01b74025 rbx=0000000000000000 rcx=0000000000000c40
rdx=8b44310f01b7a22d rsi=fffff8a00757de38 rdi=fffff8a00757de30
rip=fffff80002f67bd2 rsp=fffff88003177ba0 rbp=0000000000006200
 r8=00000000b5cfec35  r9=0000000000000800 r10=fffff88003177c50
r11=fffff80002e78fa0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000001
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!CmpDereferenceNameControlBlockWithLock+0xaa:
fffff800`02f67bd2 488b02          mov     rax,qword ptr [rdx] ds:002b:8b44310f`01b7a22d=????????????????
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:  ffffffffffffffff

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002eab0e0
 ffffffffffffffff 

FOLLOWUP_IP: 
nt!CmpDereferenceNameControlBlockWithLock+aa
fffff800`02f67bd2 488b02          mov     rax,qword ptr [rdx]

BUGCHECK_STR:  0x7E

LAST_CONTROL_TRANSFER:  from fffff80002f67ac8 to fffff80002f67bd2

STACK_TEXT:  
fffff880`03177ba0 fffff800`02f67ac8 : fffff8a0`09d9ab98 fffff880`03177c44 00000000`00000001 00000000`00000000 : nt!CmpDereferenceNameControlBlockWithLock+0xaa
fffff880`03177bd0 fffff800`02ecbaee : fffff8a0`09d9ab98 fffff880`03177c44 00000000`00000000 fffff800`02e78f01 : nt!CmpCleanUpKcbCacheWithLock+0x34
fffff880`03177c00 fffff800`02c80961 : fffff800`02ecb7b4 fffff800`02e185f8 fffffa80`039e2b60 00000000`00000000 : nt!CmpDelayCloseWorker+0x33a
fffff880`03177cb0 fffff800`02f17c06 : 00000000`00000000 fffffa80`039e2b60 00000000`00000080 fffffa80`039cc040 : nt!ExpWorkerThread+0x111
fffff880`03177d40 fffff800`02c51c26 : fffff880`02f63180 fffffa80`039e2b60 fffff880`02f6df80 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`03177d80 00000000`00000000 : fffff880`03178000 fffff880`03172000 fffff880`031779f0 00000000`00000000 : nt!KxStartSystemThread+0x16


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!CmpDereferenceNameControlBlockWithLock+aa

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9

STACK_COMMAND:  .cxr 0xfffff880031771d0 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_nt!CmpDereferenceNameControlBlockWithLock+aa

BUCKET_ID:  X64_0x7E_nt!CmpDereferenceNameControlBlockWithLock+aa

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

1: kd> lmtsmn
start             end                 module name
fffff880`03f9d000 fffff880`03fdb000   1394ohci 1394ohci.sys Mon Jul 13 20:07:12 2009 (4A5BCC30)
fffff880`0119b000 fffff880`011f2000   ACPI     ACPI.sys     Mon Jul 13 19:19:34 2009 (4A5BC106)
fffff880`036f8000 fffff880`03782000   afd      afd.sys      Mon Jul 13 19:21:40 2009 (4A5BC184)
fffff880`03fdb000 fffff880`03ff1000   AgileVpn AgileVpn.sys Mon Jul 13 20:10:24 2009 (4A5BCCF0)
fffff880`03f5b000 fffff880`03f70000   amdppm   amdppm.sys   Mon Jul 13 19:19:25 2009 (4A5BC0FD)
fffff880`00e7d000 fffff880`00e88000   amdxata  amdxata.sys  Tue May 19 13:56:59 2009 (4A12F2EB)
fffff880`03f2d000 fffff880`03f35000   AppleCharger AppleCharger.sys Tue Apr 06 04:21:27 2010 (4BBAEF07)
fffff880`07a30000 fffff880`07a3b000   asyncmac asyncmac.sys Mon Jul 13 20:10:13 2009 (4A5BCCE5)
fffff880`00e4a000 fffff880`00e53000   atapi    atapi.sys    Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`00e53000 fffff880`00e7d000   ataport  ataport.SYS  Mon Jul 13 19:19:52 2009 (4A5BC118)
fffff960`00970000 fffff960`009d1000   ATMFD    ATMFD.DLL    unavailable (00000000)
fffff880`01239000 fffff880`01240000   Beep     Beep.SYS     Mon Jul 13 20:00:13 2009 (4A5BCA8D)
fffff880`03f1c000 fffff880`03f2d000   blbdrive blbdrive.sys Mon Jul 13 19:35:59 2009 (4A5BC4DF)
fffff880`02964000 fffff880`02982000   bowser   bowser.sys   Mon Jul 13 19:23:50 2009 (4A5BC206)
fffff960`00670000 fffff960`00697000   cdd      cdd.dll      unavailable (00000000)
fffff880`07a13000 fffff880`07a30000   cdfs     cdfs.sys     Mon Jul 13 19:19:46 2009 (4A5BC112)
fffff880`045c4000 fffff880`045ee000   cdrom    cdrom.sys    Mon Jul 13 19:19:54 2009 (4A5BC11A)
fffff880`00cd3000 fffff880`00d93000   CI       CI.dll       Mon Jul 13 21:32:13 2009 (4A5BE01D)
fffff880`01200000 fffff880`01230000   CLASSPNP CLASSPNP.SYS Mon Jul 13 19:19:58 2009 (4A5BC11E)
fffff880`00c75000 fffff880`00cd3000   CLFS     CLFS.SYS     Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`01549000 fffff880`015bc000   cng      cng.sys      Mon Jul 13 19:49:40 2009 (4A5BC814)
fffff880`041ee000 fffff880`041fe000   CompositeBus CompositeBus.sys Mon Jul 13 20:00:33 2009 (4A5BCAA1)
fffff880`06720000 fffff880`0672e000   crashdmp crashdmp.sys Mon Jul 13 20:01:01 2009 (4A5BCABD)
fffff880`03e7b000 fffff880`03efe000   csc      csc.sys      Mon Jul 13 19:24:26 2009 (4A5BC22A)
fffff880`03efe000 fffff880`03f1c000   dfsc     dfsc.sys     Mon Jul 13 19:23:44 2009 (4A5BC200)
fffff880`03e6c000 fffff880`03e7b000   discache discache.sys Mon Jul 13 19:37:18 2009 (4A5BC52E)
fffff880`015d7000 fffff880`015ed000   disk     disk.sys     Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`066f8000 fffff880`0671a000   drmk     drmk.sys     Mon Jul 13 21:01:25 2009 (4A5BD8E5)
fffff880`0673a000 fffff880`06743000   dump_atapi dump_atapi.sys Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`0672e000 fffff880`0673a000   dump_dumpata dump_dumpata.sys Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`06743000 fffff880`06756000   dump_dumpfve dump_dumpfve.sys Mon Jul 13 19:21:51 2009 (4A5BC18F)
fffff880`06771000 fffff880`0677d000   Dxapi    Dxapi.sys    Mon Jul 13 19:38:28 2009 (4A5BC574)
fffff880`04004000 fffff880`040f8000   dxgkrnl  dxgkrnl.sys  Mon Nov 01 22:51:31 2010 (4CCF7CB3)
fffff880`040f8000 fffff880`0413e000   dxgmms1  dxgmms1.sys  Mon Nov 01 22:50:56 2010 (4CCF7C90)
fffff880`02871000 fffff880`0288d280   ewusbmdm ewusbmdm.sys Sun Mar 16 23:06:13 2008 (47DDE025)
fffff880`00e88000 fffff880`00e9c000   fileinfo fileinfo.sys Mon Jul 13 19:34:25 2009 (4A5BC481)
fffff880`00d93000 fffff880`00ddf000   fltmgr   fltmgr.sys   Mon Jul 13 19:19:59 2009 (4A5BC11F)
fffff880`015cd000 fffff880`015d7000   Fs_Rec   Fs_Rec.sys   Mon Jul 13 19:19:45 2009 (4A5BC111)
fffff880`01486000 fffff880`014c0000   fvevol   fvevol.sys   Fri Sep 25 22:34:26 2009 (4ABD7DB2)
fffff880`01600000 fffff880`0164a000   fwpkclnt fwpkclnt.sys Mon Jul 13 19:21:08 2009 (4A5BC164)
fffff880`047f5000 fffff880`047fe000   gdrv     gdrv.sys     Thu Mar 12 23:22:29 2009 (49B9D175)
fffff800`031df000 fffff800`03228000   hal      hal.dll      Mon Jul 13 21:27:36 2009 (4A5BDF08)
fffff880`03f79000 fffff880`03f9d000   HDAudBus HDAudBus.sys Mon Jul 13 20:06:13 2009 (4A5BCBF5)
fffff880`067a8000 fffff880`067c1000   HIDCLASS HIDCLASS.SYS Mon Jul 13 20:06:21 2009 (4A5BCBFD)
fffff880`067c1000 fffff880`067c9080   HIDPARSE HIDPARSE.SYS Mon Jul 13 20:06:17 2009 (4A5BCBF9)
fffff880`0679a000 fffff880`067a8000   hidusb   hidusb.sys   Mon Jul 13 20:06:22 2009 (4A5BCBFE)
fffff880`0289c000 fffff880`02964000   HTTP     HTTP.sys     Mon Jul 13 19:22:16 2009 (4A5BC1A8)
fffff880`01674000 fffff880`0167d000   hwpolicy hwpolicy.sys Mon Jul 13 19:19:22 2009 (4A5BC0FA)
fffff880`00e10000 fffff880`00e30000   jraid    jraid.sys    Wed Jan 27 03:58:17 2010 (4B600029)
fffff880`045a4000 fffff880`045b3000   kbdclass kbdclass.sys Mon Jul 13 19:19:50 2009 (4A5BC116)
fffff880`067ca000 fffff880`067d8000   kbdhid   kbdhid.sys   Mon Jul 13 20:00:20 2009 (4A5BCA94)
fffff800`00b9c000 fffff800`00ba6000   kdcom    kdcom.dll    Mon Jul 13 21:31:07 2009 (4A5BDFDB)
fffff880`04400000 fffff880`04443000   ks       ks.sys       Wed Mar 03 23:32:25 2010 (4B8F37D9)
fffff880`0152f000 fffff880`01549000   ksecdd   ksecdd.sys   Mon Jul 13 19:20:54 2009 (4A5BC156)
fffff880`017d5000 fffff880`01800000   ksecpkg  ksecpkg.sys  Fri Dec 11 01:03:32 2009 (4B21E0B4)
fffff880`0671a000 fffff880`0671f200   ksthunk  ksthunk.sys  Mon Jul 13 20:00:19 2009 (4A5BCA93)
fffff880`06444000 fffff880`06459000   lltdio   lltdio.sys   Mon Jul 13 20:08:50 2009 (4A5BCC92)
fffff880`06400000 fffff880`06423000   luafv    luafv.sys    Mon Jul 13 19:26:13 2009 (4A5BC295)
fffff880`00c54000 fffff880`00c61000   mcupdate_AuthenticAMD mcupdate_AuthenticAMD.dll Mon Jul 13 21:29:09 2009 (4A5BDF65)
fffff880`06471000 fffff880`06480000   modem    modem.sys    Mon Jul 13 20:10:48 2009 (4A5BCD08)
fffff880`067e5000 fffff880`067f3000   monitor  monitor.sys  Mon Jul 13 19:38:52 2009 (4A5BC58C)
fffff880`045b3000 fffff880`045c2000   mouclass mouclass.sys Mon Jul 13 19:19:50 2009 (4A5BC116)
fffff880`067d8000 fffff880`067e5000   mouhid   mouhid.sys   Mon Jul 13 20:00:20 2009 (4A5BCA94)
fffff880`00e30000 fffff880`00e4a000   mountmgr mountmgr.sys Mon Jul 13 19:19:54 2009 (4A5BC11A)
fffff880`02982000 fffff880`0299a000   mpsdrv   mpsdrv.sys   Mon Jul 13 20:08:25 2009 (4A5BCC79)
fffff880`0299a000 fffff880`029c7000   mrxsmb   mrxsmb.sys   Sat Feb 27 02:52:19 2010 (4B88CF33)
fffff880`02800000 fffff880`0284e000   mrxsmb10 mrxsmb10.sys Sat Feb 27 02:52:28 2010 (4B88CF3C)
fffff880`0284e000 fffff880`02871000   mrxsmb20 mrxsmb20.sys Sat Feb 27 02:52:26 2010 (4B88CF3A)
fffff880`00c09000 fffff880`00c14000   Msfs     Msfs.SYS     Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`011f2000 fffff880`011fc000   msisadrv msisadrv.sys Mon Jul 13 19:19:26 2009 (4A5BC0FE)
fffff880`014d1000 fffff880`0152f000   msrpc    msrpc.sys    Mon Jul 13 19:21:32 2009 (4A5BC17C)
fffff880`036b8000 fffff880`036c3000   mssmbios mssmbios.sys Mon Jul 13 19:31:10 2009 (4A5BC3BE)
fffff880`01662000 fffff880`01674000   mup      mup.sys      Mon Jul 13 19:23:45 2009 (4A5BC201)
fffff880`01683000 fffff880`01775000   ndis     ndis.sys     Mon Jul 13 19:21:40 2009 (4A5BC184)
fffff880`04508000 fffff880`04514000   ndistapi ndistapi.sys Mon Jul 13 20:10:00 2009 (4A5BCCD8)
fffff880`04514000 fffff880`04543000   ndiswan  ndiswan.sys  Mon Jul 13 20:10:11 2009 (4A5BCCE3)
fffff880`044c6000 fffff880`044db000   NDProxy  NDProxy.SYS  Mon Jul 13 20:10:05 2009 (4A5BCCDD)
fffff880`03600000 fffff880`0360f000   netbios  netbios.sys  Mon Jul 13 20:09:26 2009 (4A5BCCB6)
fffff880`03782000 fffff880`037c7000   netbt    netbt.sys    Mon Jul 13 19:21:28 2009 (4A5BC178)
fffff880`01775000 fffff880`017d5000   NETIO    NETIO.SYS    Mon Jul 13 19:21:46 2009 (4A5BC18A)
fffff880`00c14000 fffff880`00c25000   Npfs     Npfs.SYS     Mon Jul 13 19:19:48 2009 (4A5BC114)
fffff880`036ac000 fffff880`036b8000   nsiproxy nsiproxy.sys Mon Jul 13 19:21:02 2009 (4A5BC15E)
fffff800`02c03000 fffff800`031df000   nt       ntkrnlmp.exe Sat Jun 19 00:16:41 2010 (4C1C44A9)
fffff880`01241000 fffff880`013e4000   Ntfs     Ntfs.sys     Mon Jul 13 19:20:47 2009 (4A5BC14F)
fffff880`013f7000 fffff880`01400000   Null     Null.SYS     Mon Jul 13 19:19:37 2009 (4A5BC109)
fffff880`04455000 fffff880`0446c000   nusb3hub nusb3hub.sys Fri Nov 20 05:15:57 2009 (4B066C5D)
fffff880`0413e000 fffff880`0416e000   nusb3xhc nusb3xhc.sys Fri Nov 20 05:16:01 2009 (4B066C61)
fffff880`053e1000 fffff880`053e2180   nvBridge nvBridge.kmd Sat Oct 16 13:06:16 2010 (4CB9DB88)
fffff880`04807000 fffff880`053e0a80   nvlddmkm nvlddmkm.sys Sat Oct 16 13:12:46 2010 (4CB9DD0E)
fffff880`037d0000 fffff880`037f6000   pacer    pacer.sys    Mon Jul 13 20:09:41 2009 (4A5BCCC5)
fffff880`053e3000 fffff880`05400000   parport  parport.sys  Mon Jul 13 20:00:40 2009 (4A5BCAA8)
fffff880`0100d000 fffff880`01022000   partmgr  partmgr.sys  Mon Jul 13 19:19:58 2009 (4A5BC11E)
fffff880`00f6a000 fffff880`00f9d000   pci      pci.sys      Mon Jul 13 19:19:51 2009 (4A5BC117)
fffff880`00ff9000 fffff880`01000000   pciide   pciide.sys   Mon Jul 13 19:19:49 2009 (4A5BC115)
fffff880`00e00000 fffff880`00e10000   PCIIDEX  PCIIDEX.SYS  Mon Jul 13 19:19:48 2009 (4A5BC114)
fffff880`015bc000 fffff880`015cd000   pcw      pcw.sys      Mon Jul 13 19:19:27 2009 (4A5BC0FF)
fffff880`04608000 fffff880`046ae000   peauth   peauth.sys   Mon Jul 13 21:01:19 2009 (4A5BD8DF)
fffff880`066bb000 fffff880`066f8000   portcls  portcls.sys  Mon Jul 13 20:06:27 2009 (4A5BCC03)
fffff880`00c61000 fffff880`00c75000   PSHED    PSHED.dll    Mon Jul 13 21:32:23 2009 (4A5BE027)
fffff880`044e4000 fffff880`04508000   rasl2tp  rasl2tp.sys  Mon Jul 13 20:10:11 2009 (4A5BCCE3)
fffff880`04543000 fffff880`0455e000   raspppoe raspppoe.sys Mon Jul 13 20:10:17 2009 (4A5BCCE9)
fffff880`0455e000 fffff880`0457f000   raspptp  raspptp.sys  Mon Jul 13 20:10:18 2009 (4A5BCCEA)
fffff880`0457f000 fffff880`04599000   rassstp  rassstp.sys  Mon Jul 13 20:10:25 2009 (4A5BCCF1)
fffff880`0365b000 fffff880`036ac000   rdbss    rdbss.sys    Mon Jul 13 19:24:09 2009 (4A5BC219)
fffff880`04599000 fffff880`045a4000   rdpbus   rdpbus.sys   Mon Jul 13 20:17:46 2009 (4A5BCEAA)
fffff880`00eaa000 fffff880`00eb3000   RDPCDD   RDPCDD.sys   Mon Jul 13 20:16:34 2009 (4A5BCE62)
fffff880`00def000 fffff880`00df8000   rdpencdd rdpencdd.sys Mon Jul 13 20:16:34 2009 (4A5BCE62)
fffff880`00c00000 fffff880`00c09000   rdprefmp rdprefmp.sys Mon Jul 13 20:16:35 2009 (4A5BCE63)
fffff880`0144c000 fffff880`01486000   rdyboost rdyboost.sys Mon Jul 13 19:34:34 2009 (4A5BC48A)
fffff880`06459000 fffff880`06471000   rspndr   rspndr.sys   Mon Jul 13 20:08:50 2009 (4A5BCC92)
fffff880`03e00000 fffff880`03e57000   Rt64win7 Rt64win7.sys Thu Mar 04 08:42:52 2010 (4B8FB8DC)
fffff880`0648b000 fffff880`066ba800   RTKVHD64 RTKVHD64.sys Wed Mar 17 04:49:15 2010 (4BA0978B)
fffff880`0116c000 fffff880`0119b000   SCSIPORT SCSIPORT.SYS Mon Jul 13 20:01:04 2009 (4A5BCAC0)
fffff880`046ae000 fffff880`046b9000   secdrv   secdrv.SYS   Wed Sep 13 09:18:38 2006 (4508052E)
fffff880`041e2000 fffff880`041ee000   serenum  serenum.sys  Mon Jul 13 20:00:33 2009 (4A5BCAA1)
fffff880`0360f000 fffff880`0362c000   serial   serial.sys   Mon Jul 13 20:00:40 2009 (4A5BCAA8)
fffff880`0165a000 fffff880`01662000   spldr    spldr.sys    Mon May 11 12:56:27 2009 (4A0858BB)
fffff880`0103d000 fffff880`01163000   sptd     sptd.sys     Sun Oct 11 16:55:14 2009 (4AD24632)
fffff880`0475f000 fffff880`047f5000   srv      srv.sys      Thu Aug 26 23:38:00 2010 (4C773318)
fffff880`046f8000 fffff880`0475f000   srv2     srv2.sys     Thu Aug 26 23:37:46 2010 (4C77330A)
fffff880`046b9000 fffff880`046e6000   srvnet   srvnet.sys   Thu Aug 26 23:37:24 2010 (4C7732F4)
fffff880`045c2000 fffff880`045c3480   swenum   swenum.sys   Mon Jul 13 20:00:18 2009 (4A5BCA92)
fffff880`01803000 fffff880`01a00000   tcpip    tcpip.sys    Sun Jun 13 23:39:04 2010 (4C15A458)
fffff880`046e6000 fffff880`046f8000   tcpipreg tcpipreg.sys Mon Jul 13 20:09:49 2009 (4A5BCCCD)
fffff880`036eb000 fffff880`036f8000   TDI      TDI.SYS      Mon Jul 13 19:21:18 2009 (4A5BC16E)
fffff880`036cd000 fffff880`036eb000   tdx      tdx.sys      Mon Jul 13 19:21:15 2009 (4A5BC16B)
fffff880`03647000 fffff880`0365b000   termdd   termdd.sys   Mon Jul 13 20:16:36 2009 (4A5BCE64)
fffff960`00470000 fffff960`0047a000   TSDDD    TSDDD.dll    unavailable (00000000)
fffff880`03f35000 fffff880`03f5b000   tunnel   tunnel.sys   Mon Jul 13 20:09:37 2009 (4A5BCCC1)
fffff880`04443000 fffff880`04455000   umbus    umbus.sys    Mon Jul 13 20:06:56 2009 (4A5BCC20)
fffff880`0677d000 fffff880`0679a000   usbccgp  usbccgp.sys  Mon Jul 13 20:06:45 2009 (4A5BCC15)
fffff880`0416e000 fffff880`0416ff00   USBD     USBD.SYS     Mon Jul 13 20:06:23 2009 (4A5BCBFF)
fffff880`041d1000 fffff880`041e2000   usbehci  usbehci.sys  Mon Jul 13 20:06:30 2009 (4A5BCC06)
fffff880`0446c000 fffff880`044c6000   usbhub   usbhub.sys   Mon Jul 13 20:07:09 2009 (4A5BCC2D)
fffff880`04170000 fffff880`0417b000   usbohci  usbohci.sys  Mon Jul 13 20:06:30 2009 (4A5BCC06)
fffff880`0417b000 fffff880`041d1000   USBPORT  USBPORT.SYS  Mon Jul 13 20:06:31 2009 (4A5BCC07)
fffff880`06756000 fffff880`06771000   USBSTOR  USBSTOR.SYS  Mon Jul 13 20:06:34 2009 (4A5BCC0A)
fffff880`01000000 fffff880`0100d000   vdrvroot vdrvroot.sys Mon Jul 13 20:01:31 2009 (4A5BCADB)
fffff880`00e9c000 fffff880`00eaa000   vga      vga.sys      Mon Jul 13 19:38:47 2009 (4A5BC587)
fffff880`00c2a000 fffff880`00c4f000   VIDEOPRT VIDEOPRT.SYS Mon Jul 13 19:38:51 2009 (4A5BC58B)
fffff880`0164a000 fffff880`0165a000   vmstorfl vmstorfl.sys Mon Jul 13 19:42:54 2009 (4A5BC67E)
fffff880`01022000 fffff880`01037000   volmgr   volmgr.sys   Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`00f9d000 fffff880`00ff9000   volmgrx  volmgrx.sys  Mon Jul 13 19:20:33 2009 (4A5BC141)
fffff880`01400000 fffff880`0144c000   volsnap  volsnap.sys  Mon Jul 13 19:20:08 2009 (4A5BC128)
fffff880`0362c000 fffff880`03647000   wanarp   wanarp.sys   Mon Jul 13 20:10:21 2009 (4A5BCCED)
fffff880`00ddf000 fffff880`00def000   watchdog watchdog.sys Mon Jul 13 19:37:35 2009 (4A5BC53F)
fffff880`00eb7000 fffff880`00f5b000   Wdf01000 Wdf01000.sys Mon Jul 13 19:22:07 2009 (4A5BC19F)
fffff880`00f5b000 fffff880`00f6a000   WDFLDR   WDFLDR.SYS   Mon Jul 13 19:19:54 2009 (4A5BC11A)
fffff880`037c7000 fffff880`037d0000   wfplwf   wfplwf.sys   Mon Jul 13 20:09:26 2009 (4A5BCCB6)
fffff960`00030000 fffff960`00340000   win32k   win32k.sys   unavailable (00000000)
fffff880`03f70000 fffff880`03f79000   wmiacpi  wmiacpi.sys  Mon Jul 13 19:31:02 2009 (4A5BC3B6)
fffff880`01163000 fffff880`0116c000   WMILIB   WMILIB.SYS   Mon Jul 13 19:19:51 2009 (4A5BC117)
fffff880`06423000 fffff880`06444000   WudfPf   WudfPf.sys   Mon Jul 13 20:05:37 2009 (4A5BCBD1)
fffff880`029c7000 fffff880`029f8000   WUDFRd   WUDFRd.sys   Mon Jul 13 20:06:06 2009 (4A5BCBEE)

Unloaded modules:
fffff880`07a3b000 fffff880`07aac000   spsys.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`06471000 fffff880`06480000   modem.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`02871000 fffff880`0288e000   ewusbmdm.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`07839000 fffff880`078aa000   spsys.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`015ed000 fffff880`015fb000   crashdmp.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`014c0000 fffff880`014cc000   dump_ataport
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`01230000 fffff880`01239000   dump_atapi.s
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`013e4000 fffff880`013f7000   dump_dumpfve
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`00c00000 fffff880`00c2a000   cdrom.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000

Debug session time: Sat Jan 15 11:25:20.127 2011 (GMT-5)
System Uptime: 0 days 0:07:11.501
Loading Kernel Symbols
...............................................................
................................................................
...........................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 24, {1904fb, fffff8800314d738, fffff8800314cfa0, fffff88001297655}

Probably caused by : Ntfs.sys ( Ntfs!NtfsDeleteNormalizedName+c5 )

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: fffff8800314d738
Arg3: fffff8800314cfa0
Arg4: fffff88001297655

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


EXCEPTION_RECORD:  fffff8800314d738 -- (.exr 0xfffff8800314d738)
ExceptionAddress: fffff88001297655 (Ntfs!NtfsDeleteNormalizedName+0x00000000000000c5)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT:  fffff8800314cfa0 -- (.cxr 0xfffff8800314cfa0)
rax=00010000000112b2 rbx=fffff8a007e8abc0 rcx=0000000000000000
rdx=000000002483a5a0 rsi=fffff8a007e8aaa0 rdi=fffff8a007e8aa70
rip=fffff88001297655 rsp=fffff8800314d970 rbp=0000000000000130
 r8=fffff8a007e8aa70  r9=0000000000000000 r10=fffff88002f646c0
r11=fffff8800314d940 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=fffff8a007e8aed0
iopl=0         nv up ei pl nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010202
Ntfs!NtfsDeleteNormalizedName+0xc5:
fffff880`01297655 488b4850        mov     rcx,qword ptr [rax+50h] ds:002b:00010000`00011302=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  1

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 fffff80002ec00e0
 ffffffffffffffff 

FOLLOWUP_IP: 
Ntfs!NtfsDeleteNormalizedName+c5
fffff880`01297655 488b4850        mov     rcx,qword ptr [rax+50h]

FAULTING_IP: 
Ntfs!NtfsDeleteNormalizedName+c5
fffff880`01297655 488b4850        mov     rcx,qword ptr [rax+50h]

BUGCHECK_STR:  0x24

LAST_CONTROL_TRANSFER:  from fffff880012a8cc7 to fffff88001297655

STACK_TEXT:  
fffff880`0314d970 fffff880`012a8cc7 : fffff880`0314da28 00000000`00000130 00000000`00000706 00000000`00000705 : Ntfs!NtfsDeleteNormalizedName+0xc5
fffff880`0314d9a0 fffff880`012a88d5 : 00000000`00000000 00000000`00000000 fffff800`02e2d500 00000000`00000001 : Ntfs!NtfsDeleteScb+0x203
fffff880`0314d9e0 fffff880`0121bcb4 : fffff8a0`07e8aac0 fffff8a0`07e8abc0 fffff800`02e2d500 fffff880`0314db52 : Ntfs!NtfsRemoveScb+0x61
fffff880`0314da20 fffff880`012a62dc : fffff8a0`07e8aa90 fffff800`02e2d5a0 fffff880`0314db52 fffffa80`03e5d240 : Ntfs!NtfsPrepareFcbForRemoval+0x50
fffff880`0314da50 fffff880`01224882 : fffffa80`03e5d240 fffffa80`03e5d240 fffff8a0`07e8aa90 fffff880`0314dc00 : Ntfs!NtfsTeardownStructures+0xdc
fffff880`0314dad0 fffff880`012bd813 : fffffa80`03e5d240 fffff800`02e2d5a0 fffff8a0`4946744e 00000000`00000009 : Ntfs!NtfsDecrementCloseCounts+0xa2
fffff880`0314db10 fffff880`0129738f : fffffa80`03e5d240 fffff8a0`07e8abc0 fffff8a0`07e8aa90 fffffa80`04a91180 : Ntfs!NtfsCommonClose+0x353
fffff880`0314dbe0 fffff800`02c95961 : 00000000`00000000 fffff800`02f84c00 fffffa80`039fab01 fffff800`00000003 : Ntfs!NtfsFspClose+0x15f
fffff880`0314dcb0 fffff800`02f2cc06 : 00000000`00000000 fffffa80`039fab60 00000000`00000080 fffffa80`039e7040 : nt!ExpWorkerThread+0x111
fffff880`0314dd40 fffff800`02c66c26 : fffff880`02f63180 fffffa80`039fab60 fffff880`02f6df80 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`0314dd80 00000000`00000000 : fffff880`0314e000 fffff880`03148000 fffff880`0314d9f0 00000000`00000000 : nt!KxStartSystemThread+0x16


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  Ntfs!NtfsDeleteNormalizedName+c5

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Ntfs

IMAGE_NAME:  Ntfs.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc14f

STACK_COMMAND:  .cxr 0xfffff8800314cfa0 ; kb

FAILURE_BUCKET_ID:  X64_0x24_Ntfs!NtfsDeleteNormalizedName+c5

BUCKET_ID:  X64_0x24_Ntfs!NtfsDeleteNormalizedName+c5

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

Akira181 · Jan 16, 2011

I uninstalled Daemon Tools and ran the Duplex Secure, but I think I hit install instead of uninstall. Updated all the drivers and removed the sptd.sys.

The 4th BSOD came while I was trying to upload the reports to here. Haven't ran the reports again, I think the BSOD mentioned something about drivers.

I'm struggling with the chkdsk part though. I have 4 hard drives in this system, when I follow the command prompt instructions, it only runs the chkdsk on my C: (which is a partition on one of the drives)

CarlTR6 · Jan 16, 2011

Try adding the volume to the chkdsk command: chkdsk c: /r /f where "c" is whatever drive you wish to check.

Akira181 · Jan 17, 2011

Things have gotten worse if that's even possible. I've never had a system bluescreen so much, including Windows ME. Starting to think I have got buggy RAM or something.

Attached another report and some of the CHKDSK log files. BSOD twice when I tried to run them.

C:

Code:

Chkdsk was executed in read-only mode on a volume snapshot.

Checking file system on C:
The type of the file system is NTFS.
Volume label is Boot Disk.

WARNING! F parameter not specified.
Running CHKDSK in read-only mode.

CHKDSK is verifying files (stage 1 of 3)...
144640 file records processed. File verification completed.
138 large file records processed. 0 bad file records processed. 2 EA records processed. 104 reparse records processed. CHKDSK is verifying indexes (stage 2 of 3)...
209984 index entries processed. Index verification completed.
0 unindexed files scanned. 0 unindexed files recovered. CHKDSK is verifying security descriptors (stage 3 of 3)...
144640 file SDs/SIDs processed. Cleaning up 342 unused index entries from index $SII of file 0x9.
Cleaning up 342 unused index entries from index $SDH of file 0x9.
Cleaning up 342 unused security descriptors.
Security descriptor verification completed.
32673 data files processed. CHKDSK is verifying Usn Journal...
36029256 USN bytes processed. Usn Journal verification completed.
Windows has checked the file system and found no problems.

83843203 KB total disk space.
37010812 KB in 111514 files.
81728 KB in 32674 indexes.
0 KB in bad sectors.
248763 KB in use by the system.
65536 KB occupied by the log file.
46501900 KB available on disk.

4096 bytes in each allocation unit.
20960800 total allocation units on disk.

2 logfiles for C: for some reason. Only remember running it once.

Code:

Chkdsk was executed in read-only mode on a volume snapshot.

Checking file system on C:
The type of the file system is NTFS.
Volume label is Boot Disk.

WARNING! F parameter not specified.
Running CHKDSK in read-only mode.

CHKDSK is verifying files (stage 1 of 3)...
144640 file records processed. File verification completed.
145 large file records processed. 0 bad file records processed. 2 EA records processed. 104 reparse records processed. CHKDSK is verifying indexes (stage 2 of 3)...
209944 index entries processed. Index verification completed.
0 unindexed files scanned. 0 unindexed files recovered. CHKDSK is verifying security descriptors (stage 3 of 3)...
144640 file SDs/SIDs processed. Cleaning up 328 unused index entries from index $SII of file 0x9.
Cleaning up 328 unused index entries from index $SDH of file 0x9.
Cleaning up 328 unused security descriptors.
Security descriptor verification completed.
32653 data files processed. CHKDSK is verifying Usn Journal...
37077856 USN bytes processed. Usn Journal verification completed.
Windows has checked the file system and found no problems.

83843203 KB total disk space.
37001652 KB in 111416 files.
81664 KB in 32654 indexes.
0 KB in bad sectors.
250039 KB in use by the system.
65536 KB occupied by the log file.
46509848 KB available on disk.

4096 bytes in each allocation unit.
20960800 total allocation units on disk.
11627462 allocation units available on disk.

D: (hard disk was formatted before the build and is still empty)

Code:

Chkdsk was executed in read/write mode.

Checking file system on D:
Volume dismounted. All opened handles to this volume are now invalid.
Volume label is busted.

CHKDSK is verifying files (stage 1 of 3)...
256 file records processed. File verification completed.
3 large file records processed. 0 bad file records processed. 0 EA records processed. 0 reparse records processed. CHKDSK is verifying indexes (stage 2 of 3)...
280 index entries processed. Index verification completed.


CHKDSK is verifying security descriptors (stage 3 of 3)...
256 file SDs/SIDs processed. Cleaning up 4 unused index entries from index $SII of file 0x9.
Cleaning up 4 unused index entries from index $SDH of file 0x9.
Cleaning up 4 unused security descriptors.
Security descriptor verification completed.
12 data files processed. Windows has checked the file system and found no problems.

244196000 KB total disk space.
21588 KB in 8 files.
16 KB in 14 indexes.
73660 KB in use by the system.
65536 KB occupied by the log file.
244099868 KB available on disk.

4096 bytes in each allocation unit.
61049000 total allocation units on disk.
61024967 allocation units available on disk.

E: (C: partition is on this disk. E: partition itself is also empty)

Code:

Chkdsk was executed in read/write mode.

Checking file system on E:
The type of the file system is NTFS.
Volume label is New Volume.

CHKDSK is verifying files (stage 1 of 5)...
256 file records processed. File verification completed.
0 large file records processed. 0 bad file records processed. 0 EA records processed. 0 reparse records processed. CHKDSK is verifying indexes (stage 2 of 5)...
280 index entries processed. Index verification completed.
0 unindexed files scanned. 0 unindexed files recovered. CHKDSK is verifying security descriptors (stage 3 of 5)...
256 file SDs/SIDs processed. Cleaning up 5 unused index entries from index $SII of file 0x9.
Cleaning up 5 unused index entries from index $SDH of file 0x9.
Cleaning up 5 unused security descriptors.
Security descriptor verification completed.
12 data files processed. CHKDSK is verifying file data (stage 4 of 5)...
240 files processed. File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
40065023 free clusters processed. Free space verification is complete.
Windows has checked the file system and found no problems.

160352797 KB total disk space.
21588 KB in 8 files.
16 KB in 14 indexes.
0 KB in bad sectors.
71097 KB in use by the system.
65536 KB occupied by the log file.
160260096 KB available on disk.

4096 bytes in each allocation unit.
40088199 total allocation units on disk.
40065024 allocation units available on disk.

F: (pretty much full)

Code:

Chkdsk was executed in read/write mode.  

Checking file system on F:
The type of the file system is NTFS.
Volume label is Anime.

CHKDSK is verifying files (stage 1 of 5)...
  21504 file records processed.                                          File verification completed.
  7 large file records processed.                                      0 bad file records processed.                                        0 EA records processed.                                              0 reparse records processed.                                       CHKDSK is verifying indexes (stage 2 of 5)...
  29044 index entries processed.                                         Index verification completed.
  0 unindexed files scanned.                                           0 unindexed files recovered.                                       CHKDSK is verifying security descriptors (stage 3 of 5)...
  21504 file SDs/SIDs processed.                                         Security descriptor verification completed.
  3771 data files processed.                                            CHKDSK is verifying Usn Journal...
  6649392 USN bytes processed.                                             Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
  21488 files processed.                                                 File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
  203430 free clusters processed.                                         Free space verification is complete.
Windows has checked the file system and found no problems.

 244198552 KB total disk space.
 243272212 KB in 17462 files.
     11044 KB in 3772 indexes.
         0 KB in bad sectors.
    101576 KB in use by the system.
     65536 KB occupied by the log file.
    813720 KB available on disk.

      4096 bytes in each allocation unit.
  61049638 total allocation units on disk.
    203430 allocation units available on disk.

CarlTR6 · Jan 17, 2011

The file system looks fine. CheckDisk did some cleaning up. Can you boot and run in the Safe mode without BSOD's?

One of your dumps contains no data. Of the other two latest dumps, one blames your NTFS file system; the other blames hardware. All of your drivers look up to date. Let's start checking hardware. Test your RAM with Memtest86 following the instructions in this tutorial: http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html. Run Memtest from a cold boot after your computer has been off for an hour or two. Let it run for a minimum of 7 passes. This will take 6-8 hours. If you see any errors, you can stop the test. Post back with your results.

Code:

Windows 7 Kernel Version 7600 MP (3 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02c1b000 PsLoadedModuleList = 0xfffff800`02e58e50
Debug session time: Mon Jan 17 14:49:18.567 2011 (GMT-5)
System Uptime: 0 days 0:00:27.190
Loading Kernel Symbols
...............................................................
................................................................
..........
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff80002f67f0c, fffff8800249c770, 0}

Probably caused by : hardware ( nt!CmpKcbCacheLookup+99c )

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: fffff80002f67f0c, Address of the exception record for the exception that caused the bugcheck
Arg3: fffff8800249c770, 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!CmpKcbCacheLookup+99c
fffff800`02f67f0c 8e01            mov     es,word ptr [rcx]

CONTEXT:  fffff8800249c770 -- (.cxr 0xfffff8800249c770)
rax=0000000000000001 rbx=0000000000000000 rcx=fffff80002e90f3f
rdx=fffff8a0012058f8 rsi=fffffa8005af2690 rdi=fffff8a001205850
rip=fffff80002f67f0c rsp=fffff8800249d140 rbp=fffff8a000009a01
 r8=0000000000000000  r9=000000000000fffe r10=0000000000000000
r11=fffff8800249d2f0 r12=fffff8a001205820 r13=0000000000000001
r14=fffff8a0000224a8 r15=fffff8a0000224a8
iopl=0         ov up ei pl zr na po cy
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010a47
nt!CmpKcbCacheLookup+0x99c:
fffff800`02f67f0c 8e01            mov     es,word ptr [rcx] ds:002b:fffff800`02e90f3f=????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  LogonUI.exe

CURRENT_IRQL:  0

MISALIGNED_IP: 
nt!CmpKcbCacheLookup+99c
fffff800`02f67f0c 8e01            mov     es,word ptr [rcx]

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff80002f67f0c

STACK_TEXT:  
fffff880`0249d140 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!CmpKcbCacheLookup+0x99c


FOLLOWUP_IP: 
nt!CmpKcbCacheLookup+99c
fffff800`02f67f0c 8e01            mov     es,word ptr [rcx]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!CmpKcbCacheLookup+99c

FOLLOWUP_NAME:  MachineOwner

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

STACK_COMMAND:  .cxr 0xfffff8800249c770 ; kb

MODULE_NAME: hardware

FAILURE_BUCKET_ID:  X64_IP_MISALIGNED

BUCKET_ID:  X64_IP_MISALIGNED

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

Debug session time: Sun Jan 16 20:16:31.101 2011 (GMT-5)
System Uptime: 0 days 1:44:26.725
Loading Kernel Symbols
...............................................................
................................................................
............................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 24, {1904fb, fffff88003138878, fffff880031380e0, fffff88001347063}

Probably caused by : Ntfs.sys ( Ntfs!NtfsPerformVerify+23 )

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: fffff88003138878
Arg3: fffff880031380e0
Arg4: fffff88001347063

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


EXCEPTION_RECORD:  fffff88003138878 -- (.exr 0xfffff88003138878)
ExceptionAddress: fffff88001347063 (Ntfs!NtfsPerformVerify+0x0000000000000023)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: 00000000000000b8
Attempt to read from address 00000000000000b8

CONTEXT:  fffff880031380e0 -- (.cxr 0xfffff880031380e0)
rax=fffff88003138ae8 rbx=0000000000000000 rcx=fffffa8003c710d0
rdx=0000000000000000 rsi=0000000000000000 rdi=fffffa8003c710d0
rip=fffff88001347063 rsp=fffff88003138ab0 rbp=fffff80002e285a0
 r8=00000000ffffffff  r9=fffff88003138dd8 r10=0000000000000005
r11=fffff88001295018 r12=fffff88001295000 r13=0000000000000000
r14=fffff88003138c48 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0000  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
Ntfs!NtfsPerformVerify+0x23:
fffff880`01347063 488b8ab8000000  mov     rcx,qword ptr [rdx+0B8h] ds:002b:00000000`000000b8=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

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_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  00000000000000b8

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ebb0e0
 00000000000000b8 

FOLLOWUP_IP: 
Ntfs!NtfsPerformVerify+23
fffff880`01347063 488b8ab8000000  mov     rcx,qword ptr [rdx+0B8h]

FAULTING_IP: 
Ntfs!NtfsPerformVerify+23
fffff880`01347063 488b8ab8000000  mov     rcx,qword ptr [rdx+0B8h]

BUGCHECK_STR:  0x24

DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE

LAST_CONTROL_TRANSFER:  from fffff8800123e4e6 to fffff88001347063

STACK_TEXT:  
fffff880`03138ab0 fffff880`0123e4e6 : 00000000`00000000 fffff800`02e285a0 00000000`00000000 fffffa80`03c710d0 : Ntfs!NtfsPerformVerify+0x23
fffff880`03138af0 fffff880`012bb358 : fffffa80`03c710d0 00000000`00000000 00000000`00000000 fffff800`02c8e2a1 : Ntfs! ?? ::FNODOBFM::`string'+0x90c0
fffff880`03138be0 fffff800`02c90961 : 00000000`00000000 fffff880`012bb200 fffff800`02e28500 00000000`00000002 : Ntfs!NtfsFspClose+0x128
fffff880`03138cb0 fffff800`02f27c06 : 00000000`00000000 fffffa80`039e7b60 00000000`00000080 fffffa80`039cc040 : nt!ExpWorkerThread+0x111
fffff880`03138d40 fffff800`02c61c26 : fffff880`02f63180 fffffa80`039e7b60 fffff880`02f6df80 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`03138d80 00000000`00000000 : fffff880`03139000 fffff880`03133000 fffff880`031389f0 00000000`00000000 : nt!KxStartSystemThread+0x16


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  Ntfs!NtfsPerformVerify+23

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Ntfs

IMAGE_NAME:  Ntfs.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc14f

STACK_COMMAND:  .cxr 0xfffff880031380e0 ; kb

FAILURE_BUCKET_ID:  X64_0x24_Ntfs!NtfsPerformVerify+23

BUCKET_ID:  X64_0x24_Ntfs!NtfsPerformVerify+23

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

Akira181 · Jan 18, 2011

I had one BSOD when windows was starting up. It was the windows loading splash screen then the bsod came up with system error or something. First time that's happened so I assume that one is the empty dump.

Never did try the safe mode thing. I'll give it a try tonight when I get home from work.

CarlTR6 · Jan 18, 2011

That would explain the empty dmp file.

Akira181 · Jan 18, 2011

well, 8 minutes in and 35% into pass 1, 3 errors. Will do the troubleshooting tomorrow, gotta get some sleep before work

With all the bluescreens I was getting and the positive hype on Windows 7, I'm not surprised with the memtest result. I just hope it's the RAM and not the motherboard that's broken (both are still covered under warranty). This computer has taken so long to get working, I just don't have the will to take it apart anymore.

Thanks for the help though, it's definitely been appreciated! I will post the results of the troubleshooting tomorrow.

*edit
Just remembered that I cannot remove the stick of RAM in the first slot without removing the heatskink first. Talk about demotivating. Maybe time to throw it out and buy a Mac... okay, won't go that far. I'll never buy a Mac in a sound state of mind.

Akira181 · Jan 19, 2011

Okay. Still running MemTest but summary of results so far

The RAM I have is: Corsair DDR3 PC3-12800 (1600) CAS 9-9-9-24 RAM 2x 2GB 1.65V

Stick 1 - Slot 1 - all settings on AUTO (1333 and 9-9-9-24) - No Errors
Stick 1 - Slot 2 - all settings on AUTO (1333 and 9-9-9-24) - No Errors
Stick 1 - Slot 2 - dram increased from 1.5V to 1.64V. Memory clock increased to 1600. Timings left on AUTO (11-11-11-29) - No Errors
Stick 1 - Slot 2 - dram increased from 1.5V to 1.64V. Memory clock increased to 1600. Timings increased to 9-9-9-24 - 3 errors before 1 pass was complete

Stick 2 - Slot 1 - all settings on AUTO (1333 and 9-9-9-24) - No Errors
Stick 2 - Slot 1 - dram increased from 1.5V to 1.64V. Memory clock increased to 1600. Timings left on AUTO (11-11-11-29) - still running. On pass 3, no errors

This is getting confusing. Pass 3 with no errors, I'll assume the RAM is okay. So both sticks and both slots are fine but errors when installed together??

Once this has reached 7 passes, I will install both sticks again, put all settings to AUTO and run again. Maybe one stick was not seated correctly the first time.

But the question remains, if the RAM is specified to be PC3-12800 (1600) CAS 9-9-9-24, why do I get errors at those settings? Okay, voltage says 1.65 but my motherboard goes up in 0.02, so either 1.64 or 1.66. Surely a difference of 0.01V can't make it go from stable to unstable?

CarlTR6 · Jan 19, 2011

I need to ask the hardware Gurus to take a look at your results. I am far from an expert on RAM, voltages and timings. They are going to want some information. Please post your CPUZ, Mainboard, Memory, and SPD tabs. This will give everyone the basic info, Mainboard for the motherboard though the revision is usually not listed, Memory tab can indicate wrong OC attempts or wrong settings, confirmed by the SPD tab which is the JEDEC settings for the RAM. JEDEC is the industry standard that the RAM manufactures use to get stable settings for default.

We will also need the voltage settings for the CPU, RAM and NB or equivalent.
NB or memory controller is important. CPU voltage is listed on the CPU tab, RAM voltage is listed but it's not the actual voltage; it's the recommended voltage.

Akira181 · Jan 19, 2011

okay, I will post them tomorrow.

Just installed both sticks of ram again, set everything to auto and will leave it overnight. Gotta say, both RAM chips fit very snug into the slots. Never had to push on RAM so hard before to get it to sit correctly. I was worried that I'd break the motherboard.

Hopefully it was just me installing it wrong the first time and not faulty after all.

*edit
first pass completed, no errors. Fingers crossed!

Spoke too soon. 2nd pass brought a bunch of errors. Completely confused as to what the problem is now...

Random BSOD. Reports attached

New member

My Computer

Banned

My Computer

New member

My Computer

Professional Lurker

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

Banned

My Computer

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

New member

My Computer

Antique Senior Member

My Computer

New member

My Computer

New member

My Computer

Antique Senior Member

My Computer

New member

My Computer