Please Help Clean Install BSOD's

jco2274 · Jul 21, 2011

Hi, I have been having problems with this home built for a while tons of BSOD's and such. I did a complete clear of my HD and installed Windows 7 64 bit again yet still having issues I really need help. I have run Tests on my HD, RAM, and Video card not a problem that they have found. I dont know if i need new RAM or what. I get BSOD at random times but almost always when i play EVE Online. I have the most up to date driver for my graphics card but everywhere i turn ATI has crap drivers. Thanks for your time. Just need help badly. The only thing i have pluged into my computer is my mouse, keyboard, philips speakers, and 2 monitors HP and acer, if that helps.

My System

MB-ASUS M4A88TH-V EV0/USB3
CPU-AMD Phenom II x4 965 Black Edition 3.4
GPU-XFX Radeon HD 5830
Memory-G. SKILL Ripjaws Series 4GB 2x2
OS-Windows 7 64bit
PSU-Corsairs 650W

SledgeDG · Jul 21, 2011

Curiously none of the crashes were attributed to your GFX so I would put that behind for now.
Two of your dumps complain about your NTFS File system
So I would like you to open an Administrative command prompt and run the following
Chkdsk /f /r
Since the problem could also be caused by a failing hard drive,
You can read out/check the drives SMART status with this little gem
CrystalDiskInfo - Software - Crystal Dew World
The other crashes point more towards defective RAM (or Memory slots)
So you would want to follow this tut to check it out
http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

What puzzles me a bit (it might not be related) is the fact that the dump states that USB drivers are loaded while the event viewer complains about missing USB drivers. Do you use any USB device?

-DG

Code:

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\David\Desktop\jco2274\123101-17581-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Machine Name:
Kernel base = 0xfffff800`02a15000 PsLoadedModuleList = 0xfffff800`02c5a650
Debug session time: Tue Jan  1 02:02:18.059 2002 (GMT-4)
System Uptime: 0 days 0:00:12.589
Loading Kernel Symbols
...............................................................
................................................
Loading User Symbols
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 24, {1904fb, fffff88003dabb28, fffff88003dab380, fffff8800122d13d}

Probably caused by : Ntfs.sys ( Ntfs!NtfsCommonRead+91d )

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

1: 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: fffff88003dabb28
Arg3: fffff88003dab380
Arg4: fffff8800122d13d

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


EXCEPTION_RECORD:  fffff88003dabb28 -- (.exr 0xfffff88003dabb28)
ExceptionAddress: fffff8800122d13d (Ntfs!NtfsCommonRead+0x000000000000091d)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT:  fffff88003dab380 -- (.cxr 0xfffff88003dab380)
rax=0000000000000000 rbx=fffffa80049378c0 rcx=f8800127c1670000
rdx=0000000000000002 rsi=0000000000000001 rdi=fffffa8004931800
rip=fffff8800122d13d rsp=fffff88003dabd60 rbp=fffff88003dac090
 r8=0000000000000000  r9=0000000000000200 r10=fffff880061edc36
r11=0000000000000000 r12=0000000000060001 r13=ff00fa8005422c10
r14=0000000000001000 r15=fffff88003dabf30
iopl=0         nv up ei ng nz ac pe cy
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010293
Ntfs!NtfsCommonRead+0x91d:
fffff880`0122d13d 418b7530        mov     esi,dword ptr [r13+30h] ds:002b:ff00fa80`05422c40=????????
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_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 fffff80002cc4100
 ffffffffffffffff 

FOLLOWUP_IP: 
Ntfs!NtfsCommonRead+91d
fffff880`0122d13d 418b7530        mov     esi,dword ptr [r13+30h]

FAULTING_IP: 
Ntfs!NtfsCommonRead+91d
fffff880`0122d13d 418b7530        mov     esi,dword ptr [r13+30h]

BUGCHECK_STR:  0x24

LAST_CONTROL_TRANSFER:  from fffff8800122ea68 to fffff8800122d13d

STACK_TEXT:  
fffff880`03dabd60 fffff880`0122ea68 : fffff880`03dabf30 fffffa80`05422c10 fffff880`03dac001 fffffa80`0541b201 : Ntfs!NtfsCommonRead+0x91d
fffff880`03dabf00 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : Ntfs!NtfsFsdRead+0x1b8


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  Ntfs!NtfsCommonRead+91d

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Ntfs

IMAGE_NAME:  Ntfs.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4d79997b

STACK_COMMAND:  .cxr 0xfffff88003dab380 ; kb

FAILURE_BUCKET_ID:  X64_0x24_Ntfs!NtfsCommonRead+91d

BUCKET_ID:  X64_0x24_Ntfs!NtfsCommonRead+91d

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

1: kd> lmntsm
start             end                 module name
fffff880`04567000 fffff880`045a5000   1394ohci 1394ohci.sys Sat Nov 20 05:44:56 2010 (4CE7A6A8)
fffff880`00e7f000 fffff880`00ed6000   ACPI     ACPI.sys     Sat Nov 20 04:19:16 2010 (4CE79294)
fffff880`01040000 fffff880`010c9000   afd      afd.sys      Sun Apr 24 22:33:58 2011 (4DB4DD96)
fffff880`045e4000 fffff880`045fa000   AgileVpn AgileVpn.sys Mon Jul 13 20:10:24 2009 (4A5BCCF0)
fffff880`051e4000 fffff880`051f8000   amdiox64 amdiox64.sys Thu Feb 18 10:17:53 2010 (4B7D5A21)
fffff880`02d8f000 fffff880`02da4000   amdppm   amdppm.sys   Mon Jul 13 19:19:25 2009 (4A5BC0FD)
fffff880`00e2a000 fffff880`00e35000   amdxata  amdxata.sys  Fri Mar 19 12:18:18 2010 (4BA3A3CA)
fffff880`04474000 fffff880`0447c000   ASACPI   ASACPI.sys   Sun Mar 27 22:30:36 2005 (42476C4C)
fffff880`00fe0000 fffff880`00fe9000   atapi    atapi.sys    Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`00e00000 fffff880`00e2a000   ataport  ataport.SYS  Sat Nov 20 04:19:15 2010 (4CE79293)
fffff880`04832000 fffff880`05171000   atikmdag atikmdag.sys Tue May 24 22:40:32 2011 (4DDC6C20)
fffff880`02da4000 fffff880`02df5000   atikmpag atikmpag.sys Tue May 24 22:25:42 2011 (4DDC68A6)
fffff880`01630000 fffff880`01638000   AtiPcie  AtiPcie.sys  Mon Aug 24 04:25:26 2009 (4A924E76)
fffff880`019ee000 fffff880`019f5000   Beep     Beep.SYS     Mon Jul 13 20:00:13 2009 (4A5BCA8D)
fffff880`02d58000 fffff880`02d69000   blbdrive blbdrive.sys Mon Jul 13 19:35:59 2009 (4A5BC4DF)
fffff880`0166e000 fffff880`01698000   cdrom    cdrom.sys    Sat Nov 20 04:19:20 2010 (4CE79298)
fffff880`00c86000 fffff880`00d46000   CI       CI.dll       Sat Nov 20 08:12:36 2010 (4CE7C944)
fffff880`01600000 fffff880`01630000   CLASSPNP CLASSPNP.SYS Sat Nov 20 04:19:23 2010 (4CE7929B)
fffff880`00c28000 fffff880`00c86000   CLFS     CLFS.SYS     Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`0118a000 fffff880`011fc000   cng      cng.sys      Sat Nov 20 05:08:45 2010 (4CE79E2D)
fffff880`045d4000 fffff880`045e4000   CompositeBus CompositeBus.sys Sat Nov 20 05:33:17 2010 (4CE7A3ED)
fffff880`01638000 fffff880`01646000   crashdmp crashdmp.sys Mon Jul 13 20:01:01 2009 (4A5BCABD)
fffff880`02d3a000 fffff880`02d58000   dfsc     dfsc.sys     Sat Nov 20 04:26:31 2010 (4CE79447)
fffff880`02d2b000 fffff880`02d3a000   discache discache.sys Mon Jul 13 19:37:18 2009 (4A5BC52E)
fffff880`019cf000 fffff880`019e5000   disk     disk.sys     Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`01652000 fffff880`0165b000   dump_atapi dump_atapi.sys Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`01646000 fffff880`01652000   dump_dumpata dump_dumpata.sys Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`0165b000 fffff880`0166e000   dump_dumpfve dump_dumpfve.sys Mon Jul 13 19:21:51 2009 (4A5BC18F)
fffff880`042fe000 fffff880`043f2000   dxgkrnl  dxgkrnl.sys  Sat Nov 20 04:50:50 2010 (4CE799FA)
fffff880`04200000 fffff880`04246000   dxgmms1  dxgmms1.sys  Sat Nov 20 04:49:53 2010 (4CE799C1)
fffff880`01118000 fffff880`0112c000   fileinfo fileinfo.sys Mon Jul 13 19:34:25 2009 (4A5BC481)
fffff880`010cc000 fffff880`01118000   fltmgr   fltmgr.sys   Sat Nov 20 04:19:24 2010 (4CE7929C)
fffff880`013f1000 fffff880`013fb000   Fs_Rec   Fs_Rec.sys   Mon Jul 13 19:19:45 2009 (4A5BC111)
fffff880`01995000 fffff880`019cf000   fvevol   fvevol.sys   Sat Nov 20 04:24:06 2010 (4CE793B6)
fffff880`018a2000 fffff880`018ec000   fwpkclnt fwpkclnt.sys Sat Nov 20 04:21:37 2010 (4CE79321)
fffff880`04467000 fffff880`04474000   GEARAspiWDM GEARAspiWDM.sys Mon May 18 08:17:04 2009 (4A1151C0)
fffff800`02ffe000 fffff800`03047000   hal      hal.dll      Sat Nov 20 08:00:25 2010 (4CE7C669)
fffff880`04246000 fffff880`0426a000   HDAudBus HDAudBus.sys Sat Nov 20 05:43:42 2010 (4CE7A65E)
fffff880`0198c000 fffff880`01995000   hwpolicy hwpolicy.sys Sat Nov 20 04:18:54 2010 (4CE7927E)
fffff880`0447c000 fffff880`0449a000   i8042prt i8042prt.sys Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`045b0000 fffff880`045bf000   kbdclass kbdclass.sys Mon Jul 13 19:19:50 2009 (4A5BC116)
fffff800`00b96000 fffff800`00ba0000   kdcom    kdcom.dll    Sat Feb 05 11:52:49 2011 (4D4D8061)
fffff880`051a1000 fffff880`051e4000   ks       ks.sys       Sat Nov 20 05:33:23 2010 (4CE7A3F3)
fffff880`013c5000 fffff880`013e0000   ksecdd   ksecdd.sys   Sat Nov 20 04:21:15 2010 (4CE7930B)
fffff880`01460000 fffff880`0148b000   ksecpkg  ksecpkg.sys  Sat Nov 20 05:10:34 2010 (4CE79E9A)
fffff880`00c07000 fffff880`00c14000   mcupdate_AuthenticAMD mcupdate_AuthenticAMD.dll Mon Jul 13 21:29:09 2009 (4A5BDF65)
fffff880`05192000 fffff880`051a1000   mouclass mouclass.sys Mon Jul 13 19:19:50 2009 (4A5BC116)
fffff880`00fc6000 fffff880`00fe0000   mountmgr mountmgr.sys Sat Nov 20 04:19:21 2010 (4CE79299)
fffff880`0148b000 fffff880`014bc000   MpFilter MpFilter.sys Wed Apr 06 16:07:29 2011 (4D9CC801)
fffff880`01212000 fffff880`0121d000   Msfs     Msfs.SYS     Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`00edf000 fffff880`00ee9000   msisadrv msisadrv.sys Mon Jul 13 19:19:26 2009 (4A5BC0FE)
fffff880`0112c000 fffff880`0118a000   msrpc    msrpc.sys    Sat Nov 20 04:21:56 2010 (4CE79334)
fffff880`02d20000 fffff880`02d2b000   mssmbios mssmbios.sys Mon Jul 13 19:31:10 2009 (4A5BC3BE)
fffff880`0197a000 fffff880`0198c000   mup      mup.sys      Mon Jul 13 19:23:45 2009 (4A5BC201)
fffff880`014d0000 fffff880`015c3000   ndis     ndis.sys     Sat Nov 20 04:23:30 2010 (4CE79392)
fffff880`0428e000 fffff880`0429a000   ndistapi ndistapi.sys Mon Jul 13 20:10:00 2009 (4A5BCCD8)
fffff880`0429a000 fffff880`042c9000   ndiswan  ndiswan.sys  Sat Nov 20 05:52:32 2010 (4CE7A870)
fffff880`05870000 fffff880`05885000   NDProxy  NDProxy.SYS  Sat Nov 20 05:52:20 2010 (4CE7A864)
fffff880`02c68000 fffff880`02c77000   netbios  netbios.sys  Mon Jul 13 20:09:26 2009 (4A5BCCB6)
fffff880`00e35000 fffff880`00e7a000   netbt    netbt.sys    Sat Nov 20 04:23:18 2010 (4CE79386)
fffff880`01400000 fffff880`01460000   NETIO    NETIO.SYS    Sat Nov 20 04:23:13 2010 (4CE79381)
fffff880`044a4000 fffff880`0455a000   netr28x  netr28x.sys  Fri Jun 19 03:56:06 2009 (4A3B4496)
fffff880`01000000 fffff880`01011000   Npfs     Npfs.SYS     Mon Jul 13 19:19:48 2009 (4A5BC114)
fffff880`02d14000 fffff880`02d20000   nsiproxy nsiproxy.sys Mon Jul 13 19:21:02 2009 (4A5BC15E)
fffff800`02a15000 fffff800`02ffe000   nt       ntkrnlmp.exe Sat Apr 09 00:15:23 2011 (4D9FDD5B)
fffff880`01222000 fffff880`013c5000   Ntfs     Ntfs.sys     Thu Mar 10 22:39:39 2011 (4D79997B)
fffff880`019e5000 fffff880`019ee000   Null     Null.SYS     Mon Jul 13 19:19:37 2009 (4A5BC109)
fffff880`02c2c000 fffff880`02c52000   pacer    pacer.sys    Sat Nov 20 05:52:18 2010 (4CE7A862)
fffff880`00f29000 fffff880`00f3e000   partmgr  partmgr.sys  Sat Nov 20 04:20:00 2010 (4CE792C0)
fffff880`00ee9000 fffff880`00f1c000   pci      pci.sys      Sat Nov 20 04:19:11 2010 (4CE7928F)
fffff880`00faf000 fffff880`00fb6000   pciide   pciide.sys   Mon Jul 13 19:19:49 2009 (4A5BC115)
fffff880`00fb6000 fffff880`00fc6000   PCIIDEX  PCIIDEX.SYS  Mon Jul 13 19:19:48 2009 (4A5BC114)
fffff880`013e0000 fffff880`013f1000   pcw      pcw.sys      Mon Jul 13 19:19:27 2009 (4A5BC0FF)
fffff880`00c14000 fffff880`00c28000   PSHED    PSHED.dll    Mon Jul 13 21:32:23 2009 (4A5BE027)
fffff880`0426a000 fffff880`0428e000   rasl2tp  rasl2tp.sys  Sat Nov 20 05:52:34 2010 (4CE7A872)
fffff880`042c9000 fffff880`042e4000   raspppoe raspppoe.sys Mon Jul 13 20:10:17 2009 (4A5BCCE9)
fffff880`05171000 fffff880`05192000   raspptp  raspptp.sys  Sat Nov 20 05:52:31 2010 (4CE7A86F)
fffff880`042e4000 fffff880`042fe000   rassstp  rassstp.sys  Mon Jul 13 20:10:25 2009 (4A5BCCF1)
fffff880`02cc3000 fffff880`02d14000   rdbss    rdbss.sys    Sat Nov 20 04:27:51 2010 (4CE79497)
fffff880`019f5000 fffff880`019fe000   RDPCDD   RDPCDD.sys   Mon Jul 13 20:16:34 2009 (4A5BCE62)
fffff880`01200000 fffff880`01209000   rdpencdd rdpencdd.sys Mon Jul 13 20:16:34 2009 (4A5BCE62)
fffff880`01209000 fffff880`01212000   rdprefmp rdprefmp.sys Mon Jul 13 20:16:35 2009 (4A5BCE63)
fffff880`01940000 fffff880`0197a000   rdyboost rdyboost.sys Sat Nov 20 04:43:10 2010 (4CE7982E)
fffff880`045bf000 fffff880`045cb000   serenum  serenum.sys  Mon Jul 13 20:00:33 2009 (4A5BCAA1)
fffff880`02c77000 fffff880`02c94000   serial   serial.sys   Mon Jul 13 20:00:40 2009 (4A5BCAA8)
fffff880`01938000 fffff880`01940000   spldr    spldr.sys    Mon May 11 12:56:27 2009 (4A0858BB)
fffff880`045fa000 fffff880`045fb480   swenum   swenum.sys   Mon Jul 13 20:00:18 2009 (4A5BCA92)
fffff880`0169e000 fffff880`018a2000   tcpip    tcpip.sys    Sun Apr 24 22:37:30 2011 (4DB4DE6A)
fffff880`01033000 fffff880`01040000   TDI      TDI.SYS      Sat Nov 20 04:22:06 2010 (4CE7933E)
fffff880`01011000 fffff880`01033000   tdx      tdx.sys      Sat Nov 20 04:21:54 2010 (4CE79332)
fffff880`02caf000 fffff880`02cc3000   termdd   termdd.sys   Sat Nov 20 06:03:40 2010 (4CE7AB0C)
fffff880`02d69000 fffff880`02d8f000   tunnel   tunnel.sys   Sat Nov 20 05:51:50 2010 (4CE7A846)
fffff880`04800000 fffff880`04812000   umbus    umbus.sys    Sat Nov 20 05:44:37 2010 (4CE7A695)
fffff880`04456000 fffff880`04467000   usbehci  usbehci.sys  Thu Mar 24 23:29:04 2011 (4D8C0C00)
fffff880`05816000 fffff880`05870000   usbhub   usbhub.sys   Thu Mar 24 23:29:25 2011 (4D8C0C15)
fffff880`045a5000 fffff880`045b0000   usbohci  usbohci.sys  Thu Mar 24 23:29:03 2011 (4D8C0BFF)
fffff880`04400000 fffff880`04456000   USBPORT  USBPORT.SYS  Thu Mar 24 23:29:12 2011 (4D8C0C08)
fffff880`00f1c000 fffff880`00f29000   vdrvroot vdrvroot.sys Mon Jul 13 20:01:31 2009 (4A5BCADB)
fffff880`014bc000 fffff880`014ca000   vga      vga.sys      Mon Jul 13 19:38:47 2009 (4A5BC587)
fffff880`015c3000 fffff880`015e8000   VIDEOPRT VIDEOPRT.SYS Mon Jul 13 19:38:51 2009 (4A5BC58B)
fffff880`00f3e000 fffff880`00f53000   volmgr   volmgr.sys   Sat Nov 20 04:19:28 2010 (4CE792A0)
fffff880`00f53000 fffff880`00faf000   volmgrx  volmgrx.sys  Sat Nov 20 04:20:43 2010 (4CE792EB)
fffff880`018ec000 fffff880`01938000   volsnap  volsnap.sys  Sat Nov 20 04:20:08 2010 (4CE792C8)
fffff880`0455a000 fffff880`04567000   vwifibus vwifibus.sys Mon Jul 13 20:07:21 2009 (4A5BCC39)
fffff880`02c52000 fffff880`02c68000   vwififlt vwififlt.sys Mon Jul 13 20:07:22 2009 (4A5BCC3A)
fffff880`02c94000 fffff880`02caf000   wanarp   wanarp.sys   Sat Nov 20 05:52:36 2010 (4CE7A874)
fffff880`015e8000 fffff880`015f8000   watchdog watchdog.sys Mon Jul 13 19:37:35 2009 (4A5BC53F)
fffff880`00d46000 fffff880`00dea000   Wdf01000 Wdf01000.sys Mon Jul 13 19:22:07 2009 (4A5BC19F)
fffff880`00dea000 fffff880`00df9000   WDFLDR   WDFLDR.SYS   Mon Jul 13 19:19:54 2009 (4A5BC11A)
fffff880`00fe9000 fffff880`00ff2000   wfplwf   wfplwf.sys   Mon Jul 13 20:09:26 2009 (4A5BCCB6)
fffff880`045cb000 fffff880`045d4000   wmiacpi  wmiacpi.sys  Mon Jul 13 19:31:02 2009 (4A5BC3B6)
fffff880`00ed6000 fffff880`00edf000   WMILIB   WMILIB.SYS   Mon Jul 13 19:19:51 2009 (4A5BC117)

jco2274 · Jul 21, 2011

Tests

The only thing currently I have attached to the USB is my Logitec Mouse. But I do have a SSD External Hard Drive i use but didnt seem to have a problem. I have a coolmaster case with USB 3 and USB ports on the front. No idea if that would cause the USB issue. I have ran the Ram test and got errors but when i ran the test on each single stick it had no errors on each. Is it the Motherboard? Should I try to move the memory from the primary to secondary slots? Ill run the HD test and get back to you. Also I was wondering if my Memory was rated at 2000 and my MB is rated at only 1333 that wont effect anything will it?

SledgeDG · Jul 21, 2011

The rating/Bus Speed doesn't cause trouble here... stick and board negotiate on 1333 in your case.
Run the test with a good stick on the second slot. if you get errors there it is the board. In that case you decide if you run the computer with just one stick or if you replace the board.

As for the USB I can see the drivers have been loaded. no idea why the System info reports problems
It might have been a USB stick or a camera etc. that hasn't been properly identified (I had that problem with my old Palm Pilot) Like I said that might be unrelated to the issue at hand

-DG

Britton30 · Jul 21, 2011

jco2274 said:
I have ran the Ram test and got errors but when i ran the test on each single stick it had no errors on each. Is it the Motherboard? Also I was wondering if my Memory was rated at 2000 and my MB is rated at only 1333 that wont effect anything will it?

This might be you have a bad slot or two as SledgeDG mentioned. AMD CPUs won't support RAM higher than DDR3 1600 MHz, and you'd have to adjust your BIOS settings to achieve that. since yours is 2000, the mobo and CPU may be "fighting" it.

jco2274 · Jul 21, 2011

Ok ill adjust my bios and see if that makes a difference. I am running the chkdsk currently do i need to upload my results to u guys after it finishes?

Britton30 · Jul 21, 2011

Sure the more info the experts have the better they do.

As for the BIOS, I can't give you specific setting. GSKill was nice to give me setting from their support site.

jco2274 · Jul 21, 2011

So i ran chkdsk and everthing was good. I set the ram speed to 1333 the base for this motherboard. I had the DRAM LED was red while i had one of my stick in and the light goes away with the other stick so i guess one was faulty? Also i just had another BSOD here is the info. Also i tried to download the system stability bios for asus idk if that would help or not. Still having the issue ATI driver failed to respond. Any idea on a good workable driver.

Britton30 · Jul 21, 2011

It is beyond me

Follow this: http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html and continue posting in this thread, you're in the right place.

Sorry, I see you have already done this.

SledgeDG · Jul 22, 2011

Granted it sometimes makes a difference if you test your RAMs cold or after the computer has worked for a while.
But in your case I don't think that we could fix the problem with some software tweaking. A bad RAM stick (or slot) is just that. You said

when i ran the test on each single stick it had no errors on each.

So what are the results if you take one of those sticks and test it in the second slot?

I just found a well known BSOD maker that I overlooked the first time

Code:

ASACPI.sys   Sun Mar 27 22:30:36 2005 (42476C4C)

. You could get an updated version from here ASUSTeK Computer Inc. -Support- Drivers and Download
But that wouldn't affect the RAM test anyways.
BTW: The last crash was attributed to memory corruption
-DG

Code:

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\David\Desktop\jco2274\Windows_NT6_BSOD_jcgriff2\072111-25396-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Machine Name:
Kernel base = 0xfffff800`02a1d000 PsLoadedModuleList = 0xfffff800`02c62650
Debug session time: Thu Jul 21 21:10:47.980 2011 (GMT-4)
System Uptime: 0 days 0:05:46.635
Loading Kernel Symbols
...............................................................
................................................................
.................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff80002b9ab7c, fffff88007deffa0, 0}

Probably caused by : memory_corruption ( nt!MiEmptyPageAccessLog+dc )

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

3: 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: fffff80002b9ab7c, Address of the exception record for the exception that caused the bugcheck
Arg3: fffff88007deffa0, 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!MiEmptyPageAccessLog+dc
fffff800`02b9ab7c 488b08          mov     rcx,qword ptr [rax]

CONTEXT:  fffff88007deffa0 -- (.cxr 0xfffff88007deffa0)
rax=ff00fa800463b290 rbx=00000000000f1004 rcx=0000000000000008
rdx=fffff8a002205788 rsi=fffffa8001b83138 rdi=0000000000000000
rip=fffff80002b9ab7c rsp=fffff88007df0980 rbp=fffffa8001ad9000
 r8=fffffa8003ea0004  r9=fffffa8001b83048 r10=fffffa800463b210
r11=fffffa8004631d10 r12=0000000000000000 r13=fffffa8001b83000
r14=fffff8a002205798 r15=00ff000000000001
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!MiEmptyPageAccessLog+0xdc:
fffff800`02b9ab7c 488b08          mov     rcx,qword ptr [rax] ds:002b:ff00fa80`0463b290=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  CarboniteServi

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff80002b9ab7c

STACK_TEXT:  
fffff880`07df0980 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MiEmptyPageAccessLog+0xdc


FOLLOWUP_IP: 
nt!MiEmptyPageAccessLog+dc
fffff800`02b9ab7c 488b08          mov     rcx,qword ptr [rax]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!MiEmptyPageAccessLog+dc

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4d9fdd5b

STACK_COMMAND:  .cxr 0xfffff88007deffa0 ; kb

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0x3B_nt!MiEmptyPageAccessLog+dc

BUCKET_ID:  X64_0x3B_nt!MiEmptyPageAccessLog+dc

Followup: MachineOwner

jco2274 · Jul 22, 2011

Here are the results from the RAM test. Stick 1 passed in SLOT 1, Stick 2 Failed in SLOT 1(Had like 80000k errors or somthing like that), Stick 1 and 2 both passed in Slot 2. I have ran the chkdsk i think the results are good, not sure how to find the report or if there is one. If there is do i need to attach it? Not sure how to find the report. Not really sure what to make of the ram test. Somtimes the DRAM LED will show solid red but other times it will remain off. Also i used Crystal Disk and health status is good at 32C.

SledgeDG · Jul 24, 2011

Well Stick 2 failed so there is a high probability that it is defective. how long/how many passes did you ran the test with stick 2 in slot 2? Like I suggested before, run the machine with only the one good stick in slot 1 and see if the BSOD reoccurs.
Here is a nice tot how to review your chkdsk logs through event viewer
View your CHKDSK report on Windows 7
You don't need to attach the chkdsk results. Just for your own peace of mind see if windows found errors and made changes (corrections) to the file system (after discovering a defective RAM I kind of expect that chkdsk didn't find anything wrong)

Britton30 · Jul 24, 2011

Still this could point to a bad slot 1.

jco2274 · Jul 25, 2011

I put the Working RAM from slot 2 into slot 1 and upon startup the red DRAM LED was on, after that windows would not boot from RAM only in slot 1. As for the passes I ran that test for 3hours or so. But since I have been running the "Good" RAM in slot 2 I have not had a BSOD. So that is good news.

Britton30 · Jul 25, 2011

Good news, sort of. That would seem to condemn the slot 1 as being bad.

Please Help Clean Install BSOD's

New member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

R.I.P. 7/09/2014

My Computer

New member

My Computer

R.I.P. 7/09/2014

My Computer

New member

My Computer

R.I.P. 7/09/2014

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

R.I.P. 7/09/2014

My Computer

New member

My Computer

R.I.P. 7/09/2014

My Computer