BSOD/Driver Update issues :*(

Discussion in 'Windows 7 Blue Screen of Death (BSOD)' started by Nocturnal77, Feb 12, 2011.

  1. Nocturnal77

    Nocturnal77 New Member

    Joined:
    Feb 12, 2011
    Messages:
    38
    Likes Received:
    0
    Good Evening.

    I am having BSOD issues. I am trying to find out if this is a software issue.
    My system is a little over 2 years old, and I have had two HDD replaced, along with a motherboard. This was all covered under warranty *when pushed* and my warranty ends 8/11.

    The original OS is Vista. I was upgraded last summer to W7 do to the issues I was having.

    I have attached the following images you have requested. The SF tool crashed when gathering information. I have attached that as well, with a minidmp crash report.

    I beyond comprehension on how to update my drivers. I have tried several times. PLEASE, if this is requested, can you break it down for me? Apparently I have drivers going back to the year 1996. Why my drivers are not getting updated on it's own I am not sure.

    I will be happy to provide any other information you need.

    Now, I am off to take a Xanax.
    :furious:

    ~Brie

    ***I forgot to mention that I have ran a memtest86 overnight about a week ago. It had several passes and came back with no errors. Also I used Seatools to check the hdd, did the SMART/long checks and that also came back with no errors.***

    I know that I need to update my drivers, but going to Toshiba does not help since I do not know what to download. I have gone into update drivers on Windows. Everything that I select to update seems to come back with the same 'windows has detected you have the most updated driver for this program'- Again, if this needs to happen, please please don't just tell me to "update this driver"- I need you to break it down as if I just opened a computer for the first time kinda thing.

    Thanks in advance for your help.
     

    Attached Files:

    #1 Nocturnal77, Feb 12, 2011
    Last edited: Feb 12, 2011
  2. Nocturnal77

    Nocturnal77 New Member

    Joined:
    Feb 12, 2011
    Messages:
    38
    Likes Received:
    0
    bahkeru645;

    Thanks for your suggestion. Windows update does nothing. I have tried this. I have drivers that are as old as 1996, which I am totally confused about. I am not understanding your second suggestion. If you are speaking of going to Toshiba, I have done this with failed response. I do not know what drivers to update so I do not know which ones to select.
     
  3. cybercore

    cybercore New Member

    Joined:
    Jul 7, 2009
    Messages:
    15,823
    Likes Received:
    321
    --> 1. Disable Driver Verifier - otherwise bsod's will never stop.
    verifier.exe /reset


    --> 2. Update drivers:

    Eset
    eamon.sys Fri Sep 11 01:12:15 2009
    Or replace it with MSE https://www.microsoft.com/security_essentials/.

    analog devices inc.
    giveio.sys Wed Apr 03 22:33:25 1996


    Intel GMA
    igdkmd32.sys Wed Sep 23 15:18:09 2009
    IntelĀ® Driver Update Utility


    Intel WiFi
    netw5v32.sys Thu Mar 26 12:10:37 2009
    IntelĀ® Driver Update Utility


    Realtek LAN
    Rt86win7.sys Thu Feb 26 04:04:22 2009
    Realtek


    Touchpad
    SynTP.sys Thu Apr 12 19:02:11 2007


    Toshiba ODD Writing Driver (CD/DVD)
    tdcmdpst.sys Tue Oct 17 22:50:02 2006
    Toshiba Support - Homepage


    TOSHIBA ACPI-Based Value Added Logical and General Purpose Device Driver
    TVALZ_O.SYS Thu Oct 05 09:22:13 2006
    Toshiba Support - Homepage


    Chicony USB 2.0 Camera
    UVCFTR_S.SYS Fri Apr 13 22:32:08 2007
    Untitled Document






    Crash Dumps:

    Code:
    
    Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [F:\a\Minidump\D M P\DMP\021011-19843-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 7600.16695.x86fre.win7_gdr.101026-1503
    Machine Name:
    Kernel base = 0x82a45000 PsLoadedModuleList = 0x82b8d810
    Debug session time: Thu Feb 10 18:50:53.161 2011 (UTC - 5:00)
    System Uptime: 0 days 14:10:18.065
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ..........................
    Loading User Symbols
    Loading unloaded module list
    ........
    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    KERNEL_DATA_INPAGE_ERROR (7a)
    The requested page of kernel data could not be read in.  Typically caused by
    a bad block in the paging file or disk controller error. Also see
    KERNEL_STACK_INPAGE_ERROR.
    If the error status is 0xC000000E, 0xC000009C, 0xC000009D or 0xC0000185,
    it means the disk subsystem has experienced a failure.
    If the error status is 0xC000009A, then it means the request failed because
    a filesystem failed to make forward progress.
    Arguments:
    Arg1: c0559f60, lock type that was held (value 1,2,3, or PTE address)
    Arg2: c000000e, error status (normally i/o status code)
    Arg3: 2d2968c0, current process (virtual address for lock type 3, or PTE)
    Arg4: ab3ec3c6, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)
    
    Debugging Details:
    ------------------
    
    
    ERROR_CODE: (NTSTATUS) 0xc000000e - A device which does not exist was specified.
    
    DISK_HARDWARE_ERROR: There was error with disk hardware
    
    BUGCHECK_STR:  0x7a_c000000e
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
    
    PROCESS_NAME:  wmpnetwk.exe
    
    CURRENT_IRQL:  0
    
    TRAP_FRAME:  b73b0ae4 -- (.trap 0xffffffffb73b0ae4)
    ErrCode = 00000000
    eax=ab3ec3c6 ebx=ab3c5003 ecx=887e5000 edx=00001804 esi=ab3ec3c6 edi=8ea3dbb0
    eip=82cce321 esp=b73b0b58 ebp=b73b0b60 iopl=0         nv up ei ng nz na pe nc
    cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010286
    nt!MiApplyCompressedFixups+0x15:
    82cce321 8a06            mov     al,byte ptr [esi]          ds:0023:ab3ec3c6=00
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from 82af970a to 82b21dfc
    
    STACK_TEXT:  
    b73b093c 82af970a 0000007a c0559f60 c000000e nt!KeBugCheckEx+0x1e
    b73b09b0 82af11d5 8ab24cdc b73b0a08 82b79300 nt!MiWaitForInPageComplete+0x2fd
    b73b0a44 82accf47 82b79300 ab3ec3c6 8ab24c48 nt!MiIssueHardFault+0x3b2
    b73b0acc 82a8b628 00000000 ab3ec3c6 00000000 nt!MmAccessFault+0x2656
    b73b0acc 82cce321 00000000 ab3ec3c6 00000000 nt!KiTrap0E+0xdc
    b73b0b60 82cce4c8 887e5000 34b20000 c0443f28 nt!MiApplyCompressedFixups+0x15
    b73b0b9c 82cce2c2 8ea3dbb0 34b20000 00000001 nt!MiPerformFixups+0x6d
    b73b0bc0 82af9563 8ea3dbb0 00000000 00000601 nt!MiRelocateImagePfn+0x105
    b73b0c30 82af11d5 8ab0f564 b73b0c58 8250a220 nt!MiWaitForInPageComplete+0x156
    b73b0c94 82acd530 8250a220 65a2107c 8ab0f4d1 nt!MiIssueHardFault+0x3b2
    b73b0d1c 82a8b628 00000000 65a2107c 00000001 nt!MmAccessFault+0x2c3a
    b73b0d1c 73ec5ae2 00000000 65a2107c 00000001 nt!KiTrap0E+0xdc
    WARNING: Frame IP not in any known module. Following frames may be wrong.
    0263f6d0 00000000 00000000 00000000 00000000 0x73ec5ae2
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    nt!MiWaitForInPageComplete+2fd
    82af970a cc              int     3
    
    SYMBOL_STACK_INDEX:  1
    
    SYMBOL_NAME:  nt!MiWaitForInPageComplete+2fd
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nt
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4cc78ed4
    
    IMAGE_NAME:  memory_corruption
    
    FAILURE_BUCKET_ID:  0x7a_c000000e_VRF_nt!MiWaitForInPageComplete+2fd
    
    BUCKET_ID:  0x7a_c000000e_VRF_nt!MiWaitForInPageComplete+2fd
    
    Followup: MachineOwner
    ---------
    
    
    
    



    Drivers:

    Code:
    start    end        module name
    8e61f000 8e64b000   1394ohci 1394ohci.sys Mon Jul 13 19:51:59 2009 (4A5BC89F)
    854a6000 854ee000   ACPI     ACPI.sys     Mon Jul 13 19:11:11 2009 (4A5BBF0F)
    8cab2000 8cb0c000   afd      afd.sys      Mon Jul 13 19:12:34 2009 (4A5BBF62)
    8e725000 8e737000   AgileVpn AgileVpn.sys Mon Jul 13 19:55:00 2009 (4A5BC954)
    96429000 9652f000   AGRSM    AGRSM.sys    Mon Nov 10 09:56:37 2008 (49184BA5)
    853cf000 853d8000   amdxata  amdxata.sys  Tue May 19 13:57:35 2009 (4A12F30F)
    aad27000 aad30000   asyncmac asyncmac.sys Mon Jul 13 19:54:46 2009 (4A5BC946)
    85416000 8541f000   atapi    atapi.sys    Mon Jul 13 19:11:15 2009 (4A5BBF13)
    853ac000 853cf000   ataport  ataport.SYS  Mon Jul 13 19:11:18 2009 (4A5BBF16)
    96a40000 96a8d000   ATMFD    ATMFD.DLL    unavailable (00000000)
    8554d000 85558000   BATTC    BATTC.SYS    Mon Jul 13 19:19:15 2009 (4A5BC0F3)
    85611000 85618000   Beep     Beep.SYS     Mon Jul 13 19:45:00 2009 (4A5BC6FC)
    8d404000 8d412000   blbdrive blbdrive.sys Mon Jul 13 19:23:04 2009 (4A5BC1D8)
    852b7000 852bf000   BOOTVID  BOOTVID.dll  Mon Jul 13 21:04:34 2009 (4A5BD9A2)
    a8a90000 a8aa9000   bowser   bowser.sys   Mon Jul 13 19:14:21 2009 (4A5BBFCD)
    96a20000 96a3e000   cdd      cdd.dll      unavailable (00000000)
    853d8000 853f7000   cdrom    cdrom.sys    Mon Jul 13 19:11:24 2009 (4A5BBF1C)
    85301000 853ac000   CI       CI.dll       Mon Jul 13 21:09:28 2009 (4A5BDAC8)
    857cc000 857f1000   CLASSPNP CLASSPNP.SYS Mon Jul 13 19:11:20 2009 (4A5BBF18)
    852bf000 85301000   CLFS     CLFS.SYS     Mon Jul 13 19:11:10 2009 (4A5BBF0E)
    8e6b0000 8e6b3700   CmBatt   CmBatt.sys   Mon Jul 13 19:19:18 2009 (4A5BC0F6)
    85808000 85865000   cng      cng.sys      Mon Jul 13 19:32:55 2009 (4A5BC427)
    85545000 8554d000   compbatt compbatt.sys Mon Jul 13 19:19:18 2009 (4A5BC0F6)
    8e718000 8e725000   CompositeBus CompositeBus.sys Mon Jul 13 19:45:26 2009 (4A5BC716)
    965d5000 965e2000   crashdmp crashdmp.sys Mon Jul 13 19:45:50 2009 (4A5BC72E)
    85213000 8522b000   dfsc     dfsc.sys     Mon Jul 13 19:14:16 2009 (4A5BBFC8)
    8cbea000 8cbf6000   discache discache.sys Mon Jul 13 19:24:04 2009 (4A5BC214)
    85a00000 85a11000   disk     disk.sys     Mon Jul 13 19:11:28 2009 (4A5BBF20)
    8d5e1000 8d5fa000   drmk     drmk.sys     Mon Jul 13 20:36:05 2009 (4A5BD2F5)
    965e2000 965ed000   dump_dumpata dump_dumpata.sys Mon Jul 13 19:11:16 2009 (4A5BBF14)
    96400000 96411000   dump_dumpfve dump_dumpfve.sys Mon Jul 13 19:12:47 2009 (4A5BBF6F)
    965ed000 965f7000   dump_msahci dump_msahci.sys Mon Jul 13 19:45:50 2009 (4A5BC72E)
    9653c000 96546000   Dxapi    Dxapi.sys    Mon Jul 13 19:25:25 2009 (4A5BC265)
    8e115000 8e1cc000   dxgkrnl  dxgkrnl.sys  Mon Nov 01 22:37:53 2010 (4CCF7981)
    8d445000 8d47e000   dxgmms1  dxgmms1.sys  Wed Feb 02 22:34:49 2011 (4D4A2259)
    8f642000 8f70e000   eamon    eamon.sys    Fri Sep 11 01:12:15 2009 (4AA9DC2F)
    8ca08000 8ca25000   ehdrv    ehdrv.sys    Fri Sep 11 01:12:49 2009 (4AA9DC51)
    a8b4c000 a8b66000   epfwwfpr epfwwfpr.sys Fri Sep 11 01:07:03 2009 (4AA9DAF7)
    8564e000 8565f000   fileinfo fileinfo.sys Mon Jul 13 19:21:51 2009 (4A5BC18F)
    8561a000 8564e000   fltmgr   fltmgr.sys   Mon Jul 13 19:11:13 2009 (4A5BBF11)
    85873000 8587c000   Fs_Rec   Fs_Rec.sys   Mon Jul 13 19:11:14 2009 (4A5BBF12)
    859c3000 859f5000   fvevol   fvevol.sys   Fri Sep 25 22:24:21 2009 (4ABD7B55)
    85b5b000 85b8c000   fwpkclnt fwpkclnt.sys Mon Jul 13 19:12:03 2009 (4A5BBF43)
    85bf2000 85bf2680   giveio   giveio.sys   Wed Apr 03 22:33:25 1996 (316334F5)
    82a0e000 82a45000   hal      halmacpi.dll Mon Jul 13 19:11:03 2009 (4A5BBF07)
    8d4c9000 8d4e8000   HDAudBus HDAudBus.sys Mon Jul 13 19:50:55 2009 (4A5BC85F)
    8d562000 8d5b2000   HdAudio  HdAudio.sys  Mon Jul 13 19:51:46 2009 (4A5BC892)
    a8a0b000 a8a90000   HTTP     HTTP.sys     Mon Jul 13 19:12:53 2009 (4A5BBF75)
    85bea000 85bf2000   hwpolicy hwpolicy.sys Mon Jul 13 19:11:01 2009 (4A5BBF05)
    8e6b4000 8e6cc000   i8042prt i8042prt.sys Mon Jul 13 19:11:23 2009 (4A5BBF1B)
    8dc0c000 8e115000   igdkmd32 igdkmd32.sys Wed Sep 23 15:18:09 2009 (4ABA7471)
    855b3000 855ba000   intelide intelide.sys Mon Jul 13 19:11:19 2009 (4A5BBF17)
    8d433000 8d445000   intelppm intelppm.sys Mon Jul 13 19:11:03 2009 (4A5BBF07)
    8e6cc000 8e6d9000   kbdclass kbdclass.sys Mon Jul 13 19:11:15 2009 (4A5BBF13)
    80bc7000 80bcf000   kdcom    kdcom.dll    Mon Jul 13 21:08:58 2009 (4A5BDAAA)
    8e7c4000 8e7f8000   ks       ks.sys       Wed Mar 03 22:57:52 2010 (4B8F2FC0)
    857b9000 857cc000   ksecdd   ksecdd.sys   Mon Jul 13 19:11:56 2009 (4A5BBF3C)
    85971000 85996000   ksecpkg  ksecpkg.sys  Thu Dec 10 23:04:22 2009 (4B21C4C6)
    8f728000 8f738000   lltdio   lltdio.sys   Mon Jul 13 19:53:18 2009 (4A5BC8EE)
    8f627000 8f642000   luafv    luafv.sys    Mon Jul 13 19:15:44 2009 (4A5BC020)
    8522e000 852a6000   mcupdate_GenuineIntel mcupdate_GenuineIntel.dll Mon Jul 13 21:06:41 2009 (4A5BDA21)
    9652f000 9653c000   modem    modem.sys    Mon Jul 13 19:55:24 2009 (4A5BC96C)
    96586000 96591000   monitor  monitor.sys  Mon Jul 13 19:25:58 2009 (4A5BC286)
    8e707000 8e714000   mouclass mouclass.sys Mon Jul 13 19:11:15 2009 (4A5BBF13)
    85400000 85416000   mountmgr mountmgr.sys Mon Jul 13 19:11:27 2009 (4A5BBF1F)
    85200000 85213000   mozy     mozy.sys     Mon Nov 08 17:26:36 2010 (4CD8791C)
    a8aa9000 a8abb000   mpsdrv   mpsdrv.sys   Mon Jul 13 19:52:52 2009 (4A5BC8D4)
    a8abb000 a8ade000   mrxsmb   mrxsmb.sys   Sat Feb 27 02:32:02 2010 (4B88CA72)
    a8ade000 a8b19000   mrxsmb10 mrxsmb10.sys Sat Feb 27 02:32:21 2010 (4B88CA85)
    a8b19000 a8b34000   mrxsmb20 mrxsmb20.sys Sat Feb 27 02:32:11 2010 (4B88CA7B)
    855f6000 85600000   msahci   msahci.sys   Mon Jul 13 19:45:50 2009 (4A5BC72E)
    8ca77000 8ca82000   Msfs     Msfs.SYS     Mon Jul 13 19:11:26 2009 (4A5BBF1E)
    854f7000 854ff000   msisadrv msisadrv.sys Mon Jul 13 19:11:09 2009 (4A5BBF0D)
    8578e000 857b9000   msrpc    msrpc.sys    Mon Jul 13 19:11:59 2009 (4A5BBF3F)
    8cbe0000 8cbea000   mssmbios mssmbios.sys Mon Jul 13 19:19:25 2009 (4A5BC0FD)
    85bda000 85bea000   mup      mup.sys      Mon Jul 13 19:14:14 2009 (4A5BBFC6)
    8587c000 85933000   ndis     ndis.sys     Mon Jul 13 19:12:24 2009 (4A5BBF58)
    8e74f000 8e75a000   ndistapi ndistapi.sys Mon Jul 13 19:54:24 2009 (4A5BC930)
    8f77e000 8f78e000   ndisuio  ndisuio.sys  Mon Jul 13 19:53:51 2009 (4A5BC90F)
    8e75a000 8e77c000   ndiswan  ndiswan.sys  Mon Jul 13 19:54:34 2009 (4A5BC93A)
    8d551000 8d562000   NDProxy  NDProxy.SYS  Mon Jul 13 19:54:27 2009 (4A5BC933)
    8cb64000 8cb72000   netbios  netbios.sys  Mon Jul 13 19:53:54 2009 (4A5BC912)
    8cb0c000 8cb3e000   netbt    netbt.sys    Mon Jul 13 19:12:18 2009 (4A5BBF52)
    85933000 85971000   NETIO    NETIO.SYS    Mon Jul 13 19:12:35 2009 (4A5BBF63)
    8e20c000 8e61f000   netw5v32 netw5v32.sys Thu Mar 26 12:10:37 2009 (49CBA8FD)
    8ca82000 8ca90000   Npfs     Npfs.SYS     Mon Jul 13 19:11:31 2009 (4A5BBF23)
    8cbd6000 8cbe0000   nsiproxy nsiproxy.sys Mon Jul 13 19:12:08 2009 (4A5BBF48)
    82a45000 82e55000   nt       ntkrpamp.exe Tue Oct 26 22:30:44 2010 (4CC78ED4)
    8565f000 8578e000   Ntfs     Ntfs.sys     Mon Jul 13 19:12:05 2009 (4A5BBF45)
    85800000 85807000   Null     Null.SYS     Mon Jul 13 19:11:12 2009 (4A5BBF10)
    8f738000 8f77e000   nwifi    nwifi.sys    Mon Jul 13 19:51:59 2009 (4A5BC89F)
    8cb45000 8cb64000   pacer    pacer.sys    Mon Jul 13 19:53:58 2009 (4A5BC916)
    85534000 85545000   partmgr  partmgr.sys  Mon Jul 13 19:11:35 2009 (4A5BBF27)
    854ff000 85529000   pci      pci.sys      Mon Jul 13 19:11:16 2009 (4A5BBF14)
    855ba000 855c8000   PCIIDEX  PCIIDEX.SYS  Mon Jul 13 19:11:15 2009 (4A5BBF13)
    855c8000 855f6000   pcmcia   pcmcia.sys   Mon Jul 13 19:19:29 2009 (4A5BC101)
    85865000 85873000   pcw      pcw.sys      Mon Jul 13 19:11:10 2009 (4A5BBF0E)
    a8b66000 a8bfd000   peauth   peauth.sys   Mon Jul 13 20:35:44 2009 (4A5BD2E0)
    8d5b2000 8d5e1000   portcls  portcls.sys  Mon Jul 13 19:51:00 2009 (4A5BC864)
    852a6000 852b7000   PSHED    PSHED.dll    Mon Jul 13 21:09:36 2009 (4A5BDAD0)
    8e737000 8e74f000   rasl2tp  rasl2tp.sys  Mon Jul 13 19:54:33 2009 (4A5BC939)
    8e77c000 8e794000   raspppoe raspppoe.sys Mon Jul 13 19:54:53 2009 (4A5BC94D)
    8e794000 8e7ab000   raspptp  raspptp.sys  Mon Jul 13 19:54:47 2009 (4A5BC947)
    8e7ab000 8e7c2000   rassstp  rassstp.sys  Mon Jul 13 19:54:57 2009 (4A5BC951)
    8cb95000 8cbd6000   rdbss    rdbss.sys    Mon Jul 13 19:14:26 2009 (4A5BBFD2)
    8ca5f000 8ca67000   RDPCDD   RDPCDD.sys   Mon Jul 13 20:01:40 2009 (4A5BCAE4)
    8ca67000 8ca6f000   rdpencdd rdpencdd.sys Mon Jul 13 20:01:39 2009 (4A5BCAE3)
    8ca6f000 8ca77000   rdprefmp rdprefmp.sys Mon Jul 13 20:01:41 2009 (4A5BCAE5)
    85996000 859c3000   rdyboost rdyboost.sys Mon Jul 13 19:22:02 2009 (4A5BC19A)
    8f78e000 8f7a1000   rspndr   rspndr.sys   Mon Jul 13 19:53:20 2009 (4A5BC8F0)
    8d4e8000 8d50d000   Rt86win7 Rt86win7.sys Thu Feb 26 04:04:22 2009 (49A65B16)
    8e697000 8e6b0000   sdbus    sdbus.sys    Mon Jul 13 19:19:26 2009 (4A5BC0FE)
    a8a00000 a8a0a000   secdrv   secdrv.SYS   Wed Sep 13 09:18:32 2006 (45080528)
    85bd8000 85bd9480   speedfan speedfan.sys Sun Sep 24 09:28:47 2006 (4516880F)
    85bd0000 85bd8000   spldr    spldr.sys    Mon May 11 12:13:47 2009 (4A084EBB)
    aac6a000 aacbb000   srv      srv.sys      Thu Aug 26 23:31:26 2010 (4C77318E)
    aac1b000 aac6a000   srv2     srv2.sys     Thu Aug 26 23:30:45 2010 (4C773165)
    8f7a1000 8f7c2000   srvnet   srvnet.sys   Thu Aug 26 23:30:39 2010 (4C77315F)
    8e7c2000 8e7c3380   swenum   swenum.sys   Mon Jul 13 19:45:08 2009 (4A5BC704)
    8e6d9000 8e704e00   SynTP    SynTP.sys    Thu Apr 12 19:02:11 2007 (461EBA73)
    85a12000 85b5b000   tcpip    tcpip.sys    Sun Jun 13 23:36:59 2010 (4C15A3DB)
    a8b34000 a8b41000   tcpipreg tcpipreg.sys Mon Jul 13 19:54:14 2009 (4A5BC926)
    8e714000 8e717f00   tdcmdpst tdcmdpst.sys Tue Oct 17 22:50:02 2006 (4535965A)
    8caa7000 8cab2000   TDI      TDI.SYS      Mon Jul 13 19:12:12 2009 (4A5BBF4C)
    8ca90000 8caa7000   tdx      tdx.sys      Mon Jul 13 19:12:10 2009 (4A5BBF4A)
    8cb85000 8cb95000   termdd   termdd.sys   Mon Jul 13 20:01:35 2009 (4A5BCADF)
    8e64b000 8e697000   tifm21   tifm21.sys   Wed Jan 24 15:34:40 2007 (45B7C2E0)
    96df0000 96df9000   TSDDD    TSDDD.dll    unavailable (00000000)
    8d412000 8d433000   tunnel   tunnel.sys   Mon Jul 13 19:54:03 2009 (4A5BC91B)
    85bcb000 85bcf180   TVALZ_O  TVALZ_O.SYS  Thu Oct 05 09:22:13 2006 (45250705)
    96546000 96586000   udfs     udfs.sys     Mon Jul 13 19:14:09 2009 (4A5BBFC1)
    8e1e6000 8e1f4000   umbus    umbus.sys    Mon Jul 13 19:51:38 2009 (4A5BC88A)
    96591000 965a8000   usbccgp  usbccgp.sys  Mon Jul 13 19:51:31 2009 (4A5BC883)
    8e705000 8e706700   USBD     USBD.SYS     Mon Jul 13 19:51:05 2009 (4A5BC869)
    8e1d7000 8e1e6000   usbehci  usbehci.sys  Mon Jul 13 19:51:14 2009 (4A5BC872)
    8d50d000 8d551000   usbhub   usbhub.sys   Mon Jul 13 19:52:06 2009 (4A5BC8A6)
    8d47e000 8d4c9000   USBPORT  USBPORT.SYS  Mon Jul 13 19:51:13 2009 (4A5BC871)
    8e1cc000 8e1d7000   usbuhci  usbuhci.sys  Mon Jul 13 19:51:10 2009 (4A5BC86E)
    965b1000 965d4b80   usbvideo usbvideo.sys Wed Mar 03 23:04:40 2010 (4B8F3158)
    965a8000 965b1000   UVCFTR_S UVCFTR_S.SYS Fri Apr 13 22:32:08 2007 (46203D28)
    85529000 85534000   vdrvroot vdrvroot.sys Mon Jul 13 19:46:19 2009 (4A5BC74B)
    8ca25000 8ca31000   vga      vga.sys      Mon Jul 13 19:25:50 2009 (4A5BC27E)
    8ca31000 8ca52000   VIDEOPRT VIDEOPRT.SYS Mon Jul 13 19:25:49 2009 (4A5BC27D)
    85558000 85568000   volmgr   volmgr.sys   Mon Jul 13 19:11:25 2009 (4A5BBF1D)
    85568000 855b3000   volmgrx  volmgrx.sys  Mon Jul 13 19:11:41 2009 (4A5BBF2D)
    85b8c000 85bcb000   volsnap  volsnap.sys  Mon Jul 13 19:11:34 2009 (4A5BBF26)
    8cb72000 8cb85000   wanarp   wanarp.sys   Mon Jul 13 19:55:02 2009 (4A5BC956)
    8ca52000 8ca5f000   watchdog watchdog.sys Mon Jul 13 19:24:10 2009 (4A5BC21A)
    85427000 85498000   Wdf01000 Wdf01000.sys Mon Jul 13 19:11:36 2009 (4A5BBF28)
    85498000 854a6000   WDFLDR   WDFLDR.SYS   Mon Jul 13 19:11:25 2009 (4A5BBF1D)
    8cb3e000 8cb45000   wfplwf   wfplwf.sys   Mon Jul 13 19:53:51 2009 (4A5BC90F)
    96b90000 96ddb000   win32k   win32k.sys   unavailable (00000000)
    854ee000 854f7000   WMILIB   WMILIB.SYS   Mon Jul 13 19:11:22 2009 (4A5BBF1A)
    8f70e000 8f728000   WudfPf   WudfPf.sys   Mon Jul 13 19:50:13 2009 (4A5BC835)
    
    Unloaded modules:
    aacbd000 aad27000   spsys.sys
        Timestamp: unavailable (00000000)
        Checksum:  00000000
        ImageSize:  0006A000
    aad30000 aad32000   MSPQM.sys
        Timestamp: unavailable (00000000)
        Checksum:  00000000
        ImageSize:  00002000
    aacbb000 aacbd000   MSPQM.sys
        Timestamp: unavailable (00000000)
        Checksum:  00000000
        ImageSize:  00002000
    a8b34000 a8b4c000   parport.sys
        Timestamp: unavailable (00000000)
        Checksum:  00000000
        ImageSize:  00018000
    85bf3000 85c00000   crashdmp.sys
        Timestamp: unavailable (00000000)
        Checksum:  00000000
        ImageSize:  0000D000
    859f5000 85a00000   dump_pciidex
        Timestamp: unavailable (00000000)
        Checksum:  00000000
        ImageSize:  0000B000
    857f1000 857fb000   dump_msahci.
        Timestamp: unavailable (00000000)
        Checksum:  00000000
        ImageSize:  0000A000
    85600000 85611000   dump_dumpfve
        Timestamp: unavailable (00000000)
        Checksum:  00000000
        ImageSize:  00011000
    
    
     
    1 person likes this.
  4. Nocturnal77

    Nocturnal77 New Member

    Joined:
    Feb 12, 2011
    Messages:
    38
    Likes Received:
    0
    Cybercore-

    Thanks for your help. I am running into some issues. How do I "reset" the verifier.exe? I went to command prompt. Is this where I should be? And do I select "delete settings?"

    Also will reseting this driver not warn me of other issues? Sorry for the dumb questions. :)
     
    #4 Nocturnal77, Feb 13, 2011
    Last edited: Feb 13, 2011
  5. cybercore

    cybercore New Member

    Joined:
    Jul 7, 2009
    Messages:
    15,823
    Likes Received:
    321


    Start -> In the search box type -> verifier.exe /reset -> Hit 'Enter'.

    I wonder how and why did you enable it?



    Just disable it.
     
    1 person likes this.
  6. Nocturnal77

    Nocturnal77 New Member

    Joined:
    Feb 12, 2011
    Messages:
    38
    Likes Received:
    0
    Cybercore!

    Hey, to answer your question I don't think I enabled it? Is it possible that when my hdd/motherboard were replaced they did this? :confused:

    Also following your directions- Start--Type-- verifier.exe /reset -- when I click on it, it looks like the command prompt comes up for about .1 second and disappears. It does not give me an option, or anything for that matter before it vanishes.

    Went to command prompt and this came up again. THIS time though it showed not "enabled"- wheres prior to updating my drivers this these were enables- also it showed in the right had column selected crash info. I am ASSUMING at this point it has taken care of itself? I have attached a .png to make sure that it has.

    I am still looking to update ESET. This is the one thing I have not figured out how to do. Otherwise YOU HAVE BEEN AWESOME. :star:

    Please let me know if the .verifier.exe is all set. (and also if you could direct me to the ESET driver?) :teeth:

    Much applause and gratitude-

    Sabrina
     

    Attached Files:

  7. cybercore

    cybercore New Member

    Joined:
    Jul 7, 2009
    Messages:
    15,823
    Likes Received:
    321
    Hi Sab,

    Pleasure. [​IMG][​IMG]


    If you get more crash dumps, just attach them so I can see how you're doing.

    ~~~~~

    On driver verifier:

    Driver Verifier - Enable and Disable - Windows 7 Forums

    Using Driver Verifier to identify issues with Windows drivers for advanced users


    Not possible, the necessary actions had to be taken to enable it. :nerdie:


    1. Start > Eset program group > Click to uninstall.
    2. Reboot.
    3. Download from here Best Free Antivirus Software Trial: Free Home, Business and Gaming Download from ESET
    4. Install and enjoy.


    Don't forget 'bout the drivers I listed:

     
  8. Nocturnal77

    Nocturnal77 New Member

    Joined:
    Feb 12, 2011
    Messages:
    38
    Likes Received:
    0
    Cybercore -

    Thanks! I did get all those drivers. I was not really sure on how to do it at first but figured it all out. It's all about weeding through.

    As for ESET, I actually bought a 4 year plan and have the cd/dvds (you are not allowed to make fun!) can I still use the same code if I uninstall it to reinstall? *Edit* Yes, yes you can.

    So I went ahead and did this. My system still seems to be running a lot slower than it was prior to these updates. It is taking over an hour to scan my system. Things seem to be lagging. I have more than enough space on my hdd, deleted programs, but now at a loss.

    Another question. I have Tune Up Utilities and was told to remove it due to W7 not needing it, and add CCleaner. Since my system was Vista once upon a time, does this matter? I find that Tune Up has some basic 101 steps that I like. Does it slow my system down? I have reinstalled it at this point. Would like your opinion.

    Thank You Wise One, ;)

    Sabrina
     
    #8 Nocturnal77, Feb 14, 2011
    Last edited: Feb 14, 2011
  9. cybercore

    cybercore New Member

    Joined:
    Jul 7, 2009
    Messages:
    15,823
    Likes Received:
    321
    BSOD/Driver Update issues :*

    Reinstalling will give you nothing, you'll get the same old driver as before:

    eamon.sys Fri Sep 11 01:12:15 2009
    Excellent, go update your version at the official Eset site, it'll cost you nothing:

    Download from ESET

    Click on "I have already purchased ... Take me to my download".
     
    1 person likes this.
  10. cybercore

    cybercore New Member

    Joined:
    Jul 7, 2009
    Messages:
    15,823
    Likes Received:
    321
    Re: BSOD/Driver Update issues :*

    Not necessarily, but possibly TUU and CC can slow you down if you mess up the system. Such as changing registry, disabling certain dependant services, etc.

    I personally don't need them.
     
  11. Nocturnal77

    Nocturnal77 New Member

    Joined:
    Feb 12, 2011
    Messages:
    38
    Likes Received:
    0
    Re: BSOD/Driver Update issues :*

    You rock my cyber world Cybercore.

    Okay that was lame. But Thanks Again. Everything looks good. The ESET is still kind slow on the scan but it is what it is.

    You don't need these "Internetz 4 dummiez" programs, my friend, because you know what your doing.

    I know a little and it's growing every friggen day I turn this laptop on.

    Someday, I will be like you. ;)

    Have a awesome week my friend. I am sure I will be back to bother you soon.

    Sab
     
  12. cybercore

    cybercore New Member

    Joined:
    Jul 7, 2009
    Messages:
    15,823
    Likes Received:
    321
    Re: BSOD/Driver Update issues :*

    Thanks Sab. You're welcome. [​IMG]


    I too use Eset and it's blazing fast on my RAID0 of 2 Sata's. Have got my drivers up to date 2010 and later, all's fine. Eset is (one of) the fastest and most reliable security systems on this planet, so it can be actually the speed of your hardware that slows you down. With Eset Smart Security in the system, you don't need any other guards and safe searches.

    As for tweaks like Tune Up, I don't use them because I tweak manually,

    Control Panel > Administrative > Services
    Start > msconfig
     
  13. Nocturnal77

    Nocturnal77 New Member

    Joined:
    Feb 12, 2011
    Messages:
    38
    Likes Received:
    0
    Re: BSOD/Driver Update issues :*

    Hey Cybercore,

    I hope I can reach you by posting here. Quick question; I am trying to run SFC /scannow (from a command prompt) but getting a 'admin' error stating that only the admin can run this scan. How do I tell this little program that I am the admin?

    Much love!

    Brie
     
  14. Trouble

    Trouble Noob Whisperer

    Joined:
    Nov 30, 2009
    Messages:
    13,845
    Likes Received:
    833
    Re: BSOD/Driver Update issues :*

    Hey Brie;
    Click the start orb then all programs then accessories then right click "command prompt" and choose run as adminstrator then when it launches type sfc /scannow and you should be fine. If prompted at all just answer in the affirmative, yes, ok, continue, etc.
    Cybercore has been on and off the forum today and will probably be back later for sure, I hope. I'm sure he won't mind me taking one of these easy ones for him. And if he does, he can yell at me later in a PM.
    Hope this helps.
    Randy
     
    2 people like this.
  15. Nocturnal77

    Nocturnal77 New Member

    Joined:
    Feb 12, 2011
    Messages:
    38
    Likes Received:
    0
    Re: BSOD/Driver Update issues :*

    Trouble,

    That worked. Thanks so much.

    I am sure Cybercore will be fine with you helping out. I know I would. :)

    Cheers!

    Brie
     
  16. Nocturnal77

    Nocturnal77 New Member

    Joined:
    Feb 12, 2011
    Messages:
    38
    Likes Received:
    0
    Re: BSOD/Driver Update issues :*

    Cybercore (or anyone who would love to help me)

    So I crashed again this evening. I was running a few programs so I don't know if this is the issue but I digress. My problem now is that my minidump folder is empty. I am not sure why this is since I thought I fixed this issue already.

    Where would this dmp file be now? Yes, I have CCleaner but I unchecked the box that removes that file.

    Poop.

    Please Advise and Much Thanks-

    Sab

    ***Edit*** I went to my sysdm.cpl and under the *kernel* it listed *MEMORY.DMP* instead of the minidmp folder. I have since changed this to locate the mini dmp folder. I will assume at this point I can not or do not have a file to locate for this last crash?
     
    #16 Nocturnal77, Mar 3, 2011
    Last edited: Mar 3, 2011
  17. cybercore

    cybercore New Member

    Joined:
    Jul 7, 2009
    Messages:
    15,823
    Likes Received:
    321
  18. Nocturnal77

    Nocturnal77 New Member

    Joined:
    Feb 12, 2011
    Messages:
    38
    Likes Received:
    0
    Re: BSOD/Driver Update issues :*

    Cybercore!!

    Yes, I was not getting the BSOD's much so I had hoped this had solved the problem. But, like ex's, they're back. :(

    I have no idea why I am not getting the reports. I have system set up to record such things:

    "Windows 7:
    Go to Start and type in "sysdm.cpl" (without the quotes) and press Enter
    Click on the Advanced tab
    Click on the Startup and Recovery Settings button
    Ensure that "Automatically restart" is unchecked
    Under the Write Debugging Information header select "Small memory dump (64 kB)" in the dropdown box
    Ensure that the Small Dump Directory is listed as "%systemroot%\Minidump" (without the quotes)
    Click OK twice to exit the dialogs, then reboot for the changes to take effect."

    This is all correct in my system but the minidump folder is empty. :(

    Attached you will find all the BSOD info I think you have requested.

    Please help...Again. Thanks Sweetness. :p
     

    Attached Files:

    #18 Nocturnal77, Mar 14, 2011
    Last edited: Mar 14, 2011
  19. cybercore

    cybercore New Member

    Joined:
    Jul 7, 2009
    Messages:
    15,823
    Likes Received:
    321
    Re: BSOD/Driver Update issues :*

    Howdy Bri. :)

    RAM + old drivers



    1. RAM is set well according to its rates 667 5-5-5-15 1.8v. However, the sticks are slightly mismatching (marked red):

    Module #1

    DDR-667
    Micron Technology 2048
    16HTF25664HY-667E1
    SSTL 1.8V
    5-5-5-15
    Minimum Auto-Refresh 127.500
    Data Access Time 0.450/0.500
    Partial Array Self Refresh No



    Module #2

    DDR-667
    Samsung 1024
    M4 70T2953EZ3-CE6
    SSTL 1.8V
    5-5-5-15
    Minimum Auto-Refresh 105.000
    Data Access Time 0.450/0.600
    Partial Array Self Refresh Yes





    2. Drivers - some are old needing updates:

    Touchpad

    Driver Name : SynTP.sys
    Address : 0x9292e000
    File Type : Driver
    Description : Synaptics Touchpad Driver
    Version : 9.2.1 12Apr07
    Company : Synaptics, Inc.
    Product Name : Synaptics Pointing Device Driver
    Modified Date : 4/12/2007 7:50:06 PM
    Created Date : 4/12/2007 7:50:06 PM
    Filename : C:\Windows\system32\DRIVERS\SynTP.sys
    File Attributes : A




    Toshiba ODD Writing Driver

    Driver Name : tdcmdpst.sys
    Address : 0x92969000
    File Type : System Driver
    Description : Toshiba ODD Writing Driver For x86.
    Version : 2, 0, 0, 0
    Company : TOSHIBA Corporation.
    Product Name :
    Modified Date : 10/18/2006 2:50:04 PM
    Created Date : 10/18/2006 2:50:04 PM
    Filename : C:\Windows\system32\DRIVERS\tdcmdpst.sys
    File Attributes : A





    Texas Instruments

    Driver Name : tifm21.sys
    Address : 0x928a0000
    File Type : Application
    Description : tifm21.sys
    Version : 2.0.0.7
    Company : Texas Instruments
    Product Name : Texas Instruments PCIxx21/PCIxx12 Integrated FlashMedia Controller
    Modified Date : 1/24/2007 5:44:06 PM
    Created Date : 1/24/2007 5:44:06 PM
    Filename : C:\Windows\system32\drivers\tifm21.sys
    File Attributes : A
     
  20. cybercore

    cybercore New Member

    Joined:
    Jul 7, 2009
    Messages:
    15,823
    Likes Received:
    321
    Re: BSOD/Driver Update issues :*

    Update those 3 old drivers and if blue screens don't go away, remove module #2 (Samsung) from the system.
     

Share This Page

Loading...