Windows Vista Forums

Random BSOD think memory related?
  1. #1



    Junior Member
    Join Date : Dec 2010
    Posts : 10
    Vista ultimate x64
    Local Time: 11:58 PM

    Random BSOD think memory related?

    Hey guys, sorry to bother but I need some help assessing a problem I have been having. Machine is 2 weeks old and I keep getting random freezes no BSOD for since day 2 of the build. Today I got my first BSOD crash and this is what was in the dump file.




    Code:
    ++++Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Windows\Minidump\Mini123010-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    Symbol search path is: SRV*c:\symbols*Symbol information
    Executable search path is: 
    Windows Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (6 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 6002.18267.amd64fre.vistasp2_gdr.100608-0458
    Machine Name:
    Kernel base = 0xfffff800`02c5d000 PsLoadedModuleList = 0xfffff800`02e21dd0
    Debug session time: Thu Dec 30 12:02:10.751 2010 (UTC - 5:00)
    System Uptime: 0 days 0:00:59.423
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ....................
    Loading User Symbols
    Loading unloaded module list
    ......
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 1000007E, {ffffffffc0000005, fffffa6000fb27d2, fffffa60026759d8, fffffa60026753b0}
    
    Probably caused by : ecache.sys ( ecache!EcCacheUpdateBufferCommit+86 )
    
    Followup: MachineOwner
    ---------
    
    5: 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: fffffa6000fb27d2, The address that the exception occurred at
    Arg3: fffffa60026759d8, Exception Record Address
    Arg4: fffffa60026753b0, 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: 
    ecache!EcCacheUpdateBufferCommit+86
    fffffa60`00fb27d2 448b432c        mov     r8d,dword ptr [rbx+2Ch]
    
    EXCEPTION_RECORD:  fffffa60026759d8 -- (.exr 0xfffffa60026759d8)
    ExceptionAddress: fffffa6000fb27d2 (ecache!EcCacheUpdateBufferCommit+0x0000000000000086)
       ExceptionCode: c0000005 (Access violation)
      ExceptionFlags: 00000000
    NumberParameters: 2
       Parameter[0]: 0000000000000000
       Parameter[1]: ffffffffffffffff
    Attempt to read from address ffffffffffffffff
    
    CONTEXT:  fffffa60026753b0 -- (.cxr 0xfffffa60026753b0)
    rax=fffffa8005b90000 rbx=ff00fa8004f99dc0 rcx=fffffa8005b90000
    rdx=0000000000096a00 rsi=fffffa8004dbee48 rdi=fffffa8005a89ac0
    rip=fffffa6000fb27d2 rsp=fffffa6002675c10 rbp=00000000000f2000
     r8=0000000000000000  r9=fffffa8005a89ac0 r10=0000000000001fff
    r11=0000000000000000 r12=0000000000000368 r13=fffffa8004dbe4b0
    r14=000000000000005c r15=fffffa8008b776f0
    iopl=0         nv up ei ng nz na po cy
    cs=0010  ss=0000  ds=002b  es=002b  fs=0053  gs=002b             efl=00010287
    ecache!EcCacheUpdateBufferCommit+0x86:
    fffffa60`00fb27d2 448b432c        mov     r8d,dword ptr [rbx+2Ch] ds:002b:ff00fa80`04f99dec=32aa2fd8
    Resetting default scope
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  2
    
    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 fffff80002e84080
     ffffffffffffffff 
    
    FOLLOWUP_IP: 
    ecache!EcCacheUpdateBufferCommit+86
    fffffa60`00fb27d2 448b432c        mov     r8d,dword ptr [rbx+2Ch]
    
    BUGCHECK_STR:  0x7E
    
    LAST_CONTROL_TRANSFER:  from fffffa6000fb2db2 to fffffa6000fb27d2
    
    STACK_TEXT:  
    fffffa60`02675c10 fffffa60`00fb2db2 : fffffa80`04dbe4b0 fffffa60`00fc1fd0 fffffa80`08a68480 00000000`00000001 : ecache!EcCacheUpdateBufferCommit+0x86
    fffffa60`02675c60 fffff800`02ec1f57 : 00000000`0667bdaa fffffa80`04d46bb0 00000000`00000080 fffffa60`00fc1fd0 : ecache!EcCacheIoWorker+0x33e
    fffffa60`02675d50 fffff800`02cf4656 : fffff800`02dd0680 fffffa80`04d46bb0 fffff800`02dd5b80 fffffa80`039ba138 : nt!PspSystemThreadStartup+0x57
    fffffa60`02675d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16
    
    
    SYMBOL_STACK_INDEX:  0
    
    SYMBOL_NAME:  ecache!EcCacheUpdateBufferCommit+86
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: ecache
    
    IMAGE_NAME:  ecache.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  49e02c52
    
    STACK_COMMAND:  .cxr 0xfffffa60026753b0 ; kb
    
    FAILURE_BUCKET_ID:  X64_0x7E_ecache!EcCacheUpdateBufferCommit+86
    
    BUCKET_ID:  X64_0x7E_ecache!EcCacheUpdateBufferCommit+86
    
    Followup: MachineOwner
    ---------+++++++

    I don't know anything about how to read this or what it means so any help would be appreciated, thanks in advance.

      My System SpecsSystem Spec

  2. #2
    richc46's Avatar

    BSOD Squad




    Join Date : Dec 2008
    Fairfield County, CT
    Posts : 19,261
    Windows 7 SP1 x64
    Local Time: 12:58 AM
    usa us connecticut

     

    Re: Random BSOD think memory related?

      My System SpecsSystem Spec

  3. #3



    Junior Member
    Join Date : Dec 2010
    Posts : 10
    Vista ultimate x64
    Local Time: 11:58 PM


      Thread Starter

    Re: Random BSOD think memory related?

    Ok sorry.

    I am running vista ultimate x64 full retail purchase about 2 years old.

    Newly installed on a 2 week old pc all parts/hardware was bought 2 weeks ago.

      My System SpecsSystem Spec

  4. #4
    richc46's Avatar

    BSOD Squad




    Join Date : Dec 2008
    Fairfield County, CT
    Posts : 19,261
    Windows 7 SP1 x64
    Local Time: 12:58 AM
    usa us connecticut

     

    Re: Random BSOD think memory related?

    First no reason for you to be sorry, you are new.

    The real problem is that you did something wrong, I cannot open the files.

    Follow instructions as carefully as you can.

      My System SpecsSystem Spec

  5. #5



    Junior Member
    Join Date : Dec 2010
    Posts : 10
    Vista ultimate x64
    Local Time: 11:58 PM


      Thread Starter

    Re: Random BSOD think memory related?

    I can open on my end even from the zip i have... I used 7zip any other programs I should use?

      My System SpecsSystem Spec

  6. #6
    richc46's Avatar

    BSOD Squad




    Join Date : Dec 2008
    Fairfield County, CT
    Posts : 19,261
    Windows 7 SP1 x64
    Local Time: 12:58 AM
    usa us connecticut

     

    Re: Random BSOD think memory related?

    Follow these instructions for zip.

    Use the zip that is part of the OS
    Dump files - Upload to Seven Forums - Windows 7 Forums

      My System SpecsSystem Spec

  7. #7



    Junior Member
    Join Date : Dec 2010
    Posts : 10
    Vista ultimate x64
    Local Time: 11:58 PM


      Thread Starter

    Re: Random BSOD think memory related?

    this work?

      My System SpecsSystem Spec

  8. #8
    richc46's Avatar

    BSOD Squad




    Join Date : Dec 2008
    Fairfield County, CT
    Posts : 19,261
    Windows 7 SP1 x64
    Local Time: 12:58 AM
    usa us connecticut

     

    Re: Random BSOD think memory related?

    STOP 0x0000007E: 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,

    Code:
     Copyright (c) Microsoft Corporation. All rights reserved.
     
    Loading Dump File [C:\Users\richc46\AppData\Local\Temp\Temp1_Windows_NT6_BSOD_jcgriff2.zip\Windows_NT6_BSOD_jcgriff2\Mini123010-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 Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (6 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 6002.18267.amd64fre.vistasp2_gdr.100608-0458
    Machine Name:
    Kernel base = 0xfffff800`02c5d000 PsLoadedModuleList = 0xfffff800`02e21dd0
    Debug session time: Thu Dec 30 12:02:10.751 2010 (GMT-5)
    System Uptime: 0 days 0:00:59.423
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ....................
    Loading User Symbols
    Loading unloaded module list
    ......
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    Use !analyze -v to get detailed debugging information.
    BugCheck 1000007E, {ffffffffc0000005, fffffa6000fb27d2, fffffa60026759d8, fffffa60026753b0}
    Probably caused by : ecache.sys ( ecache!EcCacheUpdateBufferCommit+86 )
    Followup: MachineOwner
    ---------
    5: 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: fffffa6000fb27d2, The address that the exception occurred at
    Arg3: fffffa60026759d8, Exception Record Address
    Arg4: fffffa60026753b0, 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: 
    ecache!EcCacheUpdateBufferCommit+86
    fffffa60`00fb27d2 448b432c        mov     r8d,dword ptr [rbx+2Ch]
    EXCEPTION_RECORD:  fffffa60026759d8 -- (.exr 0xfffffa60026759d8)
    ExceptionAddress: fffffa6000fb27d2 (ecache!EcCacheUpdateBufferCommit+0x0000000000000086)
       ExceptionCode: c0000005 (Access violation)
      ExceptionFlags: 00000000
    NumberParameters: 2
       Parameter[0]: 0000000000000000
       Parameter[1]: ffffffffffffffff
    Attempt to read from address ffffffffffffffff
    CONTEXT:  fffffa60026753b0 -- (.cxr 0xfffffa60026753b0)
    rax=fffffa8005b90000 rbx=ff00fa8004f99dc0 rcx=fffffa8005b90000
    rdx=0000000000096a00 rsi=fffffa8004dbee48 rdi=fffffa8005a89ac0
    rip=fffffa6000fb27d2 rsp=fffffa6002675c10 rbp=00000000000f2000
     r8=0000000000000000  r9=fffffa8005a89ac0 r10=0000000000001fff
    r11=0000000000000000 r12=0000000000000368 r13=fffffa8004dbe4b0
    r14=000000000000005c r15=fffffa8008b776f0
    iopl=0         nv up ei ng nz na po cy
    cs=0010  ss=0000  ds=002b  es=002b  fs=0053  gs=002b             efl=00010287
    ecache!EcCacheUpdateBufferCommit+0x86:
    fffffa60`00fb27d2 448b432c        mov     r8d,dword ptr [rbx+2Ch] ds:002b:ff00fa80`04f99dec=32aa2fd8
    Resetting default scope
    CUSTOMER_CRASH_COUNT:  1
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  System
    CURRENT_IRQL:  2
    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 fffff80002e84080
     ffffffffffffffff 
    FOLLOWUP_IP: 
    ecache!EcCacheUpdateBufferCommit+86
    fffffa60`00fb27d2 448b432c        mov     r8d,dword ptr [rbx+2Ch]
    BUGCHECK_STR:  0x7E
    LAST_CONTROL_TRANSFER:  from fffffa6000fb2db2 to fffffa6000fb27d2
    STACK_TEXT:  
    fffffa60`02675c10 fffffa60`00fb2db2 : fffffa80`04dbe4b0 fffffa60`00fc1fd0 fffffa80`08a68480 00000000`00000001 : ecache!EcCacheUpdateBufferCommit+0x86
    fffffa60`02675c60 fffff800`02ec1f57 : 00000000`0667bdaa fffffa80`04d46bb0 00000000`00000080 fffffa60`00fc1fd0 : ecache!EcCacheIoWorker+0x33e
    fffffa60`02675d50 fffff800`02cf4656 : fffff800`02dd0680 fffffa80`04d46bb0 fffff800`02dd5b80 fffffa80`039ba138 : nt!PspSystemThreadStartup+0x57
    fffffa60`02675d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16
     
    SYMBOL_STACK_INDEX:  0
    SYMBOL_NAME:  ecache!EcCacheUpdateBufferCommit+86
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: ecache
    IMAGE_NAME:  ecache.sys
    DEBUG_FLR_IMAGE_TIMESTAMP:  49e02c52
    STACK_COMMAND:  .cxr 0xfffffa60026753b0 ; kb
    FAILURE_BUCKET_ID:  X64_0x7E_ecache!EcCacheUpdateBufferCommit+86
    BUCKET_ID:  X64_0x7E_ecache!EcCacheUpdateBufferCommit+86
    Followup: MachineOwner
    ---------
    5: kd> lmtsmn
    start             end                 module name
    fffffa60`076f8000 fffffa60`07707f00   1394BUS  1394BUS.SYS  Sat Jan 19 01:34:04 2008 (479199DC)
    fffffa60`008f6000 fffffa60`0094c000   acpi     acpi.sys     Sat Apr 11 01:03:26 2009 (49E0249E)
    fffffa60`08c01000 fffffa60`08c6c000   afd      afd.sys      Sat Apr 11 01:44:21 2009 (49E02E35)
    fffffa60`076de000 fffffa60`076e6000   ASACPI   ASACPI.sys   Mon Oct 30 22:09:12 2006 (4546B048)
    fffffa60`08e2f000 fffffa60`08e35000   AsIO     AsIO.sys     Mon Aug 03 03:03:16 2009 (4A768BB4)
    fffffa60`08f78000 fffffa60`08f81000   aswFsBlk aswFsBlk.SYS Tue Sep 07 10:47:09 2010 (4C86506D)
    fffffa60`08f3e000 fffffa60`08f78000   aswMonFlt aswMonFlt.sys Tue Sep 07 10:47:32 2010 (4C865084)
    fffffa60`08c6c000 fffffa60`08c76000   aswRdr   aswRdr.SYS   Tue Sep 07 10:47:47 2010 (4C865093)
    fffffa60`08e0c000 fffffa60`08e2f000   aswSP    aswSP.SYS    Tue Sep 07 10:52:07 2010 (4C865197)
    fffffa60`07d4a000 fffffa60`07d5a000   aswTdi   aswTdi.SYS   Tue Sep 07 10:52:27 2010 (4C8651AB)
    fffffa60`0e4c6000 fffffa60`0e4d1000   asyncmac asyncmac.sys Sat Jan 19 01:37:27 2008 (47919AA7)
    fffffa60`009ef000 fffffa60`009f7000   atapi    atapi.sys    Sat Apr 11 01:34:19 2009 (49E02BDB)
    fffffa60`007d9000 fffffa60`007fd000   ataport  ataport.SYS  Sat Apr 11 01:34:25 2009 (49E02BE1)
    fffffa60`08ee5000 fffffa60`08ef2000   bcgame   bcgame.sys   Thu Feb 16 12:34:05 2006 (43F4B78D)
    fffffa60`0db95000 fffffa60`0dbb3000   bowser   bowser.sys   Sat Jan 19 00:54:51 2008 (479190AB)
    fffff960`00680000 fffff960`00691000   cdd      cdd.dll      unavailable (00000000)
    fffffa60`07637000 fffffa60`07653000   cdrom    cdrom.sys    Sat Apr 11 01:34:39 2009 (49E02BEF)
    fffffa60`00680000 fffffa60`00732000   CI       CI.dll       Sat Apr 11 03:08:09 2009 (49E041D9)
    fffffa60`00dcb000 fffffa60`00df7000   CLASSPNP CLASSPNP.SYS Sat Apr 11 01:34:15 2009 (49E02BD7)
    fffffa60`00623000 fffffa60`00680000   CLFS     CLFS.SYS     Sat Apr 11 00:54:21 2009 (49E0227D)
    fffffa60`08e35000 fffffa60`08e43000   crashdmp crashdmp.sys Sat Apr 11 01:34:31 2009 (49E02BE7)
    fffffa60`00b9a000 fffffa60`00ba4000   crcdisk  crcdisk.sys  Sat Jan 19 01:30:12 2008 (479198F4)
    fffffa60`08d5b000 fffffa60`08dd1000   csc      csc.sys      Sat Apr 11 00:56:24 2009 (49E022F8)
    fffffa60`08dd1000 fffffa60`08dee000   dfsc     dfsc.sys     Sat Apr 11 00:54:44 2009 (49E02294)
    fffffa60`011e5000 fffffa60`011f9000   disk     disk.sys     Sat Apr 11 01:34:38 2009 (49E02BEE)
    fffffa60`07cc5000 fffffa60`07ce8000   drmk     drmk.sys     Sat Jan 19 02:20:04 2008 (4791A4A4)
    fffffa60`08e4f000 fffffa60`08e57000   dump_atapi dump_atapi.sys Sat Apr 11 01:34:19 2009 (49E02BDB)
    fffffa60`08e43000 fffffa60`08e4f000   dump_dumpata dump_dumpata.sys Sat Apr 11 01:34:22 2009 (49E02BDE)
    fffffa60`08e57000 fffffa60`08e6a000   dump_dumpfve dump_dumpfve.sys Sat Jan 19 00:52:25 2008 (47919019)
    fffffa60`08efd000 fffffa60`08f09000   Dxapi    Dxapi.sys    Sat Jan 19 01:08:00 2008 (479193C0)
    fffffa60`07404000 fffffa60`074e5000   dxgkrnl  dxgkrnl.sys  Sat Apr 11 01:10:13 2009 (49E02635)
    fffffa60`00fa8000 fffffa60`00fd4000   ecache   ecache.sys   Sat Apr 11 01:36:18 2009 (49E02C52)
    fffffa60`00a56000 fffffa60`00a6a000   fileinfo fileinfo.sys Sat Jan 19 01:05:23 2008 (47919323)
    fffffa60`00a0f000 fffffa60`00a56000   fltmgr   fltmgr.sys   Sat Apr 11 00:54:38 2009 (49E0228E)
    fffffa60`07d37000 fffffa60`07d41000   Fs_Rec   Fs_Rec.SYS   Sat Jan 19 00:53:41 2008 (47919065)
    fffffa60`00fd4000 fffffa60`00ffd000   fvevol   fvevol.sys   Sat Apr 11 00:52:54 2009 (49E02226)
    fffffa60`00f7c000 fffffa60`00fa8000   fwpkclnt fwpkclnt.sys Sat Apr 11 01:42:44 2009 (49E02DD4)
    fffff800`02c17000 fffff800`02c5d000   hal      hal.dll      Sat Apr 11 03:04:56 2009 (49E04118)
    fffffa60`074f5000 fffffa60`075e2000   HDAudBus HDAudBus.sys Sat Apr 11 01:39:38 2009 (49E02D1A)
    fffffa60`07cee000 fffffa60`07d37000   HdAudio  HdAudio.sys  Sat Apr 11 01:39:51 2009 (49E02D27)
    fffffa60`08e83000 fffffa60`08e95000   HIDCLASS HIDCLASS.SYS Sat Apr 11 01:39:32 2009 (49E02D14)
    fffffa60`07d6b000 fffffa60`07d72b80   HIDPARSE HIDPARSE.SYS Sat Jan 19 01:33:51 2008 (479199CF)
    fffffa60`08e7a000 fffffa60`08e83000   hidusb   hidusb.sys   Sat Apr 11 01:39:32 2009 (49E02D14)
    fffffa60`0dac9000 fffffa60`0db6c000   HTTP     HTTP.sys     Sat Feb 20 16:30:05 2010 (4B80545D)
    fffffa60`009cf000 fffffa60`009ef000   jraid    jraid.sys    Mon Jan 11 06:28:18 2010 (4B4B0B52)
    fffffa60`0795d000 fffffa60`0796b000   kbdclass kbdclass.sys Sat Jan 19 01:28:05 2008 (47919875)
    fffffa60`08ef2000 fffffa60`08efd000   kbdhid   kbdhid.sys   Sat Apr 11 01:33:40 2009 (49E02BB4)
    fffffa60`00605000 fffffa60`0060f000   kdcom    kdcom.dll    Sat Apr 11 03:07:57 2009 (49E041CD)
    fffffa60`07979000 fffffa60`079ad000   ks       ks.sys       Sat Apr 11 01:33:51 2009 (49E02BBF)
    fffffa60`00a6a000 fffffa60`00af1000   ksecdd   ksecdd.sys   Mon Jun 15 09:15:18 2009 (4A364966)
    fffffa60`07ce8000 fffffa60`07ced180   ksthunk  ksthunk.sys  Sat Jan 19 01:28:14 2008 (4791987E)
    fffffa60`08e95000 fffffa60`08eaa000   LHidFilt LHidFilt.Sys Tue Aug 24 13:21:36 2010 (4C73FFA0)
    fffffa60`0da9d000 fffffa60`0dab1000   lltdio   lltdio.sys   Sat Jan 19 01:35:48 2008 (47919A44)
    fffffa60`08eb5000 fffffa60`08ec9000   LMouFilt LMouFilt.Sys Tue Aug 24 13:21:43 2010 (4C73FFA7)
    fffffa60`08f1c000 fffffa60`08f3e000   luafv    luafv.sys    Sat Jan 19 00:59:06 2008 (479191AA)
    fffffa60`08e6a000 fffffa60`08e7a000   LUsbFilt LUsbFilt.Sys Tue Aug 24 13:21:47 2010 (4C73FFAB)
    fffffa60`08f09000 fffffa60`08f1c000   monitor  monitor.sys  Sat Jan 19 01:32:34 2008 (47919982)
    fffffa60`0796b000 fffffa60`07977000   mouclass mouclass.sys Sat Jan 19 01:28:05 2008 (47919875)
    fffffa60`08eaa000 fffffa60`08eb5000   mouhid   mouhid.sys   Sat Jan 19 01:28:10 2008 (4791987A)
    fffffa60`007c6000 fffffa60`007d9000   mountmgr mountmgr.sys Sat Jan 19 01:28:01 2008 (47919871)
    fffffa60`0dbb3000 fffffa60`0dbcd000   mpsdrv   mpsdrv.sys   Sat Jan 19 01:35:28 2008 (47919A30)
    fffffa60`0dbcd000 fffffa60`0dbf4000   mrxdav   mrxdav.sys   Sat Apr 11 00:55:42 2009 (49E022CE)
    fffffa60`08f81000 fffffa60`08faa000   mrxsmb   mrxsmb.sys   Tue Feb 23 06:32:22 2010 (4B83BCC6)
    fffffa60`08faa000 fffffa60`08ff3000   mrxsmb10 mrxsmb10.sys Tue Feb 23 06:32:21 2010 (4B83BCC5)
    fffffa60`00ba4000 fffffa60`00bc3000   mrxsmb20 mrxsmb20.sys Tue Feb 23 06:32:20 2010 (4B83BCC4)
    fffffa60`07db8000 fffffa60`07dc3000   Msfs     Msfs.SYS     Sat Jan 19 00:53:55 2008 (47919073)
    fffffa60`00955000 fffffa60`0095f000   msisadrv msisadrv.sys Sat Jan 19 01:02:50 2008 (4791928A)
    fffffa60`07762000 fffffa60`0779b000   msiscsi  msiscsi.sys  Sat Apr 11 01:36:09 2009 (49E02C49)
    fffffa60`00af1000 fffffa60`00b41000   msrpc    msrpc.sys    Sat Apr 11 01:32:13 2009 (49E02B5D)
    fffffa60`079ad000 fffffa60`079b8000   mssmbios mssmbios.sys Sat Jan 19 01:02:54 2008 (4791928E)
    fffffa60`011d3000 fffffa60`011e5000   mup      mup.sys      Sat Apr 11 00:54:47 2009 (49E02297)
    fffffa60`00c08000 fffffa60`00dcb000   ndis     ndis.sys     Sat Apr 11 01:43:15 2009 (49E02DF3)
    fffffa60`0782d000 fffffa60`07839000   ndistapi ndistapi.sys Sat Jan 19 01:37:22 2008 (47919AA2)
    fffffa60`07839000 fffffa60`0786a000   ndiswan  ndiswan.sys  Sat Apr 11 01:43:39 2009 (49E02E0B)
    fffffa60`07c4d000 fffffa60`07c61000   NDProxy  NDProxy.SYS  Sat Jan 19 01:37:26 2008 (47919AA6)
    fffffa60`08cd8000 fffffa60`08ce7000   netbios  netbios.sys  Sat Jan 19 01:36:35 2008 (47919A73)
    fffffa60`08c76000 fffffa60`08cba000   netbt    netbt.sys    Sat Apr 11 01:42:31 2009 (49E02DC7)
    fffffa60`00b41000 fffffa60`00b9a000   NETIO    NETIO.SYS    Sat Apr 11 01:43:34 2009 (49E02E06)
    fffffa60`07dc3000 fffffa60`07dd4000   Npfs     Npfs.SYS     Sat Apr 11 00:54:22 2009 (49E0227E)
    fffffa60`08d4f000 fffffa60`08d5b000   nsiproxy nsiproxy.sys Sat Jan 19 01:36:45 2008 (47919A7D)
    fffff800`02c5d000 fffff800`03174000   nt       ntkrnlmp.exe Tue Jun 08 10:59:47 2010 (4C0E5AE3)
    fffffa60`01007000 fffffa60`01187000   Ntfs     Ntfs.sys     Sat Apr 11 00:55:38 2009 (49E022CA)
    fffffa60`07d41000 fffffa60`07d4a000   Null     Null.SYS     Thu Nov 02 05:37:15 2006 (4549BC4B)
    fffffa60`079c8000 fffffa60`079e0000   nusb3hub nusb3hub.sys Thu Jan 21 22:22:18 2010 (4B5919EA)
    fffffa60`07605000 fffffa60`07635000   nusb3xhc nusb3xhc.sys Thu Jan 21 22:22:21 2010 (4B5919ED)
    fffffa60`073e7000 fffffa60`073e8180   nvBridge nvBridge.kmd Sat Oct 16 13:06:16 2010 (4CB9DB88)
    fffffa60`07c61000 fffffa60`07c8a000   nvhda64v nvhda64v.sys Tue Sep 07 16:08:40 2010 (4C869BC8)
    fffffa60`0680d000 fffffa60`073e6a80   nvlddmkm nvlddmkm.sys Sat Oct 16 13:12:46 2010 (4CB9DD0E)
    fffffa60`076e6000 fffffa60`076f7b00   ohci1394 ohci1394.sys Sat Apr 11 01:39:49 2009 (49E02D25)
    fffffa60`08cba000 fffffa60`08cd8000   pacer    pacer.sys    Sat Apr 11 01:42:56 2009 (49E02DE0)
    fffffa60`0098f000 fffffa60`009a4000   partmgr  partmgr.sys  Sat Apr 11 01:34:51 2009 (49E02BFB)
    fffffa60`0095f000 fffffa60`0098f000   pci      pci.sys      Sat Apr 11 01:03:33 2009 (49E024A5)
    fffffa60`009b8000 fffffa60`009bf000   pciide   pciide.sys   Sat Apr 11 01:34:28 2009 (49E02BE4)
    fffffa60`009bf000 fffffa60`009cf000   PCIIDEX  PCIIDEX.SYS  Sat Apr 11 01:34:22 2009 (49E02BDE)
    fffffa60`0e4d1000 fffffa60`0e587000   peauth   peauth.sys   Mon Oct 23 07:57:00 2006 (453CAE0C)
    fffffa60`07c8a000 fffffa60`07cc5000   portcls  portcls.sys  Sat Apr 11 01:39:36 2009 (49E02D18)
    fffffa60`00be6000 fffffa60`00bf9000   processr processr.sys Sat Jan 19 00:52:45 2008 (4791902D)
    fffffa60`0060f000 fffffa60`00623000   PSHED    PSHED.dll    Sat Apr 11 03:08:17 2009 (49E041E1)
    fffffa60`07dd4000 fffffa60`07ddd000   rasacd   rasacd.sys   Sat Jan 19 01:37:30 2008 (47919AAA)
    fffffa60`0780a000 fffffa60`0782d000   rasl2tp  rasl2tp.sys  Sat Apr 11 01:43:37 2009 (49E02E09)
    fffffa60`0786a000 fffffa60`0787a000   raspppoe raspppoe.sys Sat Apr 11 01:43:33 2009 (49E02E05)
    fffffa60`0787a000 fffffa60`07898000   raspptp  raspptp.sys  Sat Apr 11 01:43:38 2009 (49E02E0A)
    fffffa60`07898000 fffffa60`078b0000   rassstp  rassstp.sys  Sat Apr 11 01:43:46 2009 (49E02E12)
    fffffa60`08d02000 fffffa60`08d4f000   rdbss    rdbss.sys    Sat Apr 11 00:55:21 2009 (49E022B9)
    fffffa60`07da6000 fffffa60`07daf000   RDPCDD   RDPCDD.sys   Sat Jan 19 01:42:04 2008 (47919BBC)
    fffffa60`078b0000 fffffa60`0794a000   rdpdr    rdpdr.sys    Sat Apr 11 01:49:54 2009 (49E02F82)
    fffffa60`07daf000 fffffa60`07db8000   rdpencdd rdpencdd.sys Sat Jan 19 01:42:03 2008 (47919BBB)
    fffffa60`0dab1000 fffffa60`0dac9000   rspndr   rspndr.sys   Sat Jan 19 01:35:48 2008 (47919A44)
    fffffa60`07708000 fffffa60`07759000   Rtlh64   Rtlh64.sys   Thu Mar 04 08:50:10 2010 (4B8FBA92)
    fffffa60`00798000 fffffa60`007c6000   SCSIPORT SCSIPORT.SYS Sat Jan 19 01:28:52 2008 (479198A4)
    fffffa60`0e587000 fffffa60`0e592000   secdrv   secdrv.SYS   Wed Sep 13 09:18:38 2006 (4508052E)
    fffffa60`076d2000 fffffa60`076de000   serenum  serenum.sys  Sat Jan 19 01:28:36 2008 (47919894)
    fffffa60`076b5000 fffffa60`076d2000   serial   serial.sys   Sat Jan 19 01:28:41 2008 (47919899)
    fffffa60`079e0000 fffffa60`079fb000   smb      smb.sys      Sat Apr 11 01:42:19 2009 (49E02DBB)
    fffffa60`011cb000 fffffa60`011d3000   spldr    spldr.sys    Mon Jan 12 16:51:29 2009 (496BBB61)
    fffffa60`0da03000 fffffa60`0da9d000   spsys    spsys.sys    Tue Mar 10 13:16:43 2009 (49B6A07B)
    fffffa60`0e432000 fffffa60`0e4c6000   srv      srv.sys      Mon Sep 06 11:34:12 2010 (4C8509F4)
    fffffa60`0e400000 fffffa60`0e432000   srv2     srv2.sys     Mon Sep 06 11:33:50 2010 (4C8509DE)
    fffffa60`0db6c000 fffffa60`0db95000   srvnet   srvnet.sys   Mon Sep 06 11:33:48 2010 (4C8509DC)
    fffffa60`0779b000 fffffa60`077f8000   storport storport.sys Sat Apr 11 01:34:45 2009 (49E02BF5)
    fffffa60`07977000 fffffa60`07978480   swenum   swenum.sys   Thu Nov 02 05:37:33 2006 (4549BC5D)
    fffffa60`00e06000 fffffa60`00f7c000   tcpip    tcpip.sys    Wed Jun 16 10:51:56 2010 (4C18E50C)
    fffffa60`0e592000 fffffa60`0e5a2000   tcpipreg tcpipreg.sys Tue Dec 08 12:55:32 2009 (4B1E9314)
    fffffa60`075e2000 fffffa60`075ef000   TDI      TDI.SYS      Sat Apr 11 01:44:14 2009 (49E02E2E)
    fffffa60`07ddd000 fffffa60`07dfa000   tdx      tdx.sys      Sat Apr 11 01:43:00 2009 (49E02DE4)
    fffffa60`0794a000 fffffa60`0795d000   termdd   termdd.sys   Sat Apr 11 01:48:13 2009 (49E02F1D)
    fffff960`00440000 fffff960`0044a000   TSDDD    TSDDD.dll    unavailable (00000000)
    fffffa60`00bdd000 fffffa60`00be6000   tunmp    tunmp.sys    Sat Jan 19 01:36:30 2008 (47919A6E)
    fffffa60`00bd1000 fffffa60`00bdd000   tunnel   tunnel.sys   Sat Jan 19 01:36:44 2008 (47919A7C)
    fffffa60`079b8000 fffffa60`079c8000   umbus    umbus.sys    Sat Jan 19 01:34:16 2008 (479199E8)
    fffffa60`08ec9000 fffffa60`08ee5000   usbccgp  usbccgp.sys  Sat Jan 19 01:34:04 2008 (479199DC)
    fffffa60`07635000 fffffa60`07636e00   USBD     USBD.SYS     Sat Jan 19 01:33:53 2008 (479199D1)
    fffffa60`076a4000 fffffa60`076b5000   usbehci  usbehci.sys  Sat Apr 11 01:39:36 2009 (49E02D18)
    fffffa60`07c05000 fffffa60`07c4d000   usbhub   usbhub.sys   Sat Apr 11 01:39:52 2009 (49E02D28)
    fffffa60`07653000 fffffa60`0765e000   usbohci  usbohci.sys  Sat Apr 11 01:39:36 2009 (49E02D18)
    fffffa60`0765e000 fffffa60`076a4000   USBPORT  USBPORT.SYS  Sat Apr 11 01:39:39 2009 (49E02D1B)
    fffffa60`07d73000 fffffa60`07d81000   vga      vga.sys      Sat Jan 19 01:32:21 2008 (47919975)
    fffffa60`07d81000 fffffa60`07da6000   VIDEOPRT VIDEOPRT.SYS Sat Jan 19 01:32:25 2008 (47919979)
    fffffa60`009a4000 fffffa60`009b8000   volmgr   volmgr.sys   Sat Apr 11 01:34:49 2009 (49E02BF9)
    fffffa60`00732000 fffffa60`00798000   volmgrx  volmgrx.sys  Sat Apr 11 01:35:14 2009 (49E02C12)
    fffffa60`01187000 fffffa60`011cb000   volsnap  volsnap.sys  Sat Apr 11 01:35:33 2009 (49E02C25)
    fffffa60`08ce7000 fffffa60`08d02000   wanarp   wanarp.sys   Sat Apr 11 01:43:38 2009 (49E02E0A)
    fffffa60`074e5000 fffffa60`074f5000   watchdog watchdog.sys Sat Apr 11 01:09:16 2009 (49E025FC)
    fffffa60`0080e000 fffffa60`008e8000   Wdf01000 Wdf01000.sys Sat Jan 19 01:33:27 2008 (479199B7)
    fffffa60`008e8000 fffffa60`008f6000   WDFLDR   WDFLDR.SYS   Sat Jan 19 01:32:33 2008 (47919981)
    fffff960`00050000 fffff960`00304000   win32k   win32k.sys   unavailable (00000000)
    fffffa60`07759000 fffffa60`07762000   wmiacpi  wmiacpi.sys  Sat Jan 19 01:02:42 2008 (47919282)
    fffffa60`0094c000 fffffa60`00955000   WMILIB   WMILIB.SYS   Sat Jan 19 01:33:45 2008 (479199C9)
    Outdated Drivers
    Code:
     bcgame.sys   Thu Feb 16 12:34:05 2006
    peauth.sys   Mon Oct 23 07:57:00 2006
    ASACPI.sys   Mon Oct 30 22:09:12 2006
    Null.SYS     Thu Nov 02 05:37:15 2006

    The reports that you have submitted reveal clues to the cause of your problem. They do not give a definitive answer. The more reports that we receive the more clues are made available improving our chances of finding a solution to your problem. You may have to experience several more BSODs until the final answer is discovered.

    If overclocking restore normal settings

    SFC /scannow
    System Files - SFC Command


    Scan with your Anti Virus

    Update outdated listed drivers. If I have inadvertently listed any Microsoft Drivers, they can be ignored. If the list is extensive I have included the driver verifier test so that you may determine which drivers are in need of immediate attention.
    Asacpi.sys is a driver from the Austek Computer Corp. Your driver is very old and is known to cause BSOD's in current Windows versions; it must be updated
    http://support.asus.com/download/dow...Language=en-us

    How to Find Drivers
    search Google for the name of the driver
    - compare the Google results with what's installed on your system to figure out which device/program it belongs to
    - visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
    - if there are difficulties in locating them, post back with questions and someone - will help you search Google for the name of the driver
    - compare the Google results with what's installed on your system to figure out which device/program it belongs to
    - - if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.
    - The most common drivers are listed on this page: http://www.carrona.org/dvrref.html
    - - Driver manufacturer links are on this page: http://www.carrona.org/drvrdown.html
    and here
    http://www.edbott.com/weblog/the-vista-master-driver-list/
    To remove any left over driver remnants, especially from graphics cards, use driver sweeper
    www.guru3d.com/category/driversweeper/
    You can also locate information about your driver using this information
    http://www.sevenforums.com/tutorials/96442-device-manager-finding-unknown-devices.html

      My System SpecsSystem Spec

  9. #9



    Junior Member
    Join Date : Dec 2010
    Posts : 10
    Vista ultimate x64
    Local Time: 11:58 PM


      Thread Starter

    Re: Random BSOD think memory related?

    Thank you for the help I will get on it and let you know what is up... still no bsod will post if I get one though

      My System SpecsSystem Spec

  10. #10
    richc46's Avatar

    BSOD Squad




    Join Date : Dec 2008
    Fairfield County, CT
    Posts : 19,261
    Windows 7 SP1 x64
    Local Time: 12:58 AM
    usa us connecticut

     

    Re: Random BSOD think memory related?

    Ill be honest, I think that you will get more. Each report gives a few clues. The things that I told you to do have to be done to avoid the problem in the future, even if it does not solve the immediate probelem

      My System SpecsSystem Spec

Page 1 of 2 12 LastLast
Random BSOD think memory related? problems?

Similar Threads
Thread Thread Starter Forum Replies Last Post
BSOD related to BCWML6.sys veomega Vista performance & maintenance 1 14 Feb 2009
Solved Nv4-mini.sys bsod driver related vistablackben Drivers 11 25 Dec 2008
BSOD - probably related to Network Store Interface Service Bhimasena Network & Sharing 10 05 Oct 2008
IRQL BSOD - SATA drive related? Nintari General Discussion 4 27 Mar 2008
memory related problem in vista rgcoleman Vista General 3 22 Mar 2007