BSOD issues Acer TravelMate 8210

Page 1 of 2 12 LastLast

  1. Posts : 11
    windows seven
       #1

    BSOD issues Acer TravelMate 8210


    Hello,

    I have some problems with my windows 7 OS. When I play any game (Call of Duty or Heroes of Newerth) I usually end with bluescreen of death. For last week I got this issue many times and I don't have idea why. Please someone help me.

    This is my dump files: http://www.stun.cz/minidump.rar

    Thanks
      My Computer


  2. Posts : 231
    Win7
       #2

    Many BSOD's can be traced to video driver issues. Could it be that when the games are running, whatever mode the video driver is running in is unstable. I'm no expert--it's just a suggestion.
      My Computer


  3. Posts : 28,845
    Win 8 Release candidate 8400
       #3

    mirdic said:
    Hello,

    I have some problems with my windows 7 OS. When I play any game (Call of Duty or Heroes of Newerth) I usually end with bluescreen of death. For last week I got this issue many times and I don't have idea why. Please someone help me.

    This is my dump files: http://www.stun.cz/minidump.rar

    Thanks

    Hi and welcome

    I took a quick look at about 5 of the dmps. all of them are network related.
    From the date on the drivers I pretty sure you didn't do a clean install as MS suggested.

    I would update all the critical drivers, bios, network, video, ets
    dl and run memtestx86 for several hours a t least
    run a system file check to verify and repair your system files.
    If you are overclocking stop
    \If you have a raid update its driver as well




    ozscr.sys 0x92287000 0x9229d960 0x00016960 0x4267b18c 4/21/2005 8:58:36 AM
    LVUSBSta.sys 0x95773000 0x95781000 0x0000e000 0x43f3250b 2/15/2006 7:56:43 AM
    lv321av.sys 0x82031000 0x8213ce00 0x0010be00 0x43f325ee 2/15/2006 8:00:30 AM
    secdrv.SYS 0x97316000 0x97320000 0x0000a000 0x45080528 9/13/2006 8:18:32 AM
    atikmdag.sys 0x90407000 0x90b66000 0x0075f000 0x47045a68 10/3/2007 10:13:44 PM
    nscirda.sys 0x922e1000 0x922e8800 0x00007800 0x479190cc 1/19/2008 12:55:24 AM
    AGRSM.sys 0x9560b000 0x95711000 0x00106000 0x49184ba5 11/10/2008 9:56:37 AM
    PnkBstrK.sys 0x884e7000 0x8850b000 0x00024000 0x4928cdf8 11/22/2008 10:28:56 PM





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


    Loading Dump File [C:\Users\K\Desktop\111009-29998-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is: SRV*d:\symbols*Symbol information
    Executable search path is:
    Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7600.16385.x86fre.win7_rtm.090713-1255
    Machine Name:
    Kernel base = 0x8284b000 PsLoadedModuleList = 0x82993810
    Debug session time: Tue Nov 10 17:30:43.812 2009 (GMT-5)
    System Uptime: 0 days 13:07:25.090
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    .......................................
    Loading User Symbols
    Loading unloaded module list
    ................
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck D1, {0, 2, 0, 9450cc55}

    Probably caused by : nwifi.sys ( nwifi!MP6SendNBLInternal+39 )

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

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

    DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
    An attempt was made to access a pageable (or completely invalid) address at an
    interrupt request level (IRQL) that is too high. This is usually
    caused by drivers using improper addresses.
    If kernel debugger is available get stack backtrace.
    Arguments:
    Arg1: 00000000, memory referenced
    Arg2: 00000002, IRQL
    Arg3: 00000000, value 0 = read operation, 1 = write operation
    Arg4: 9450cc55, address which referenced memory

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


    READ_ADDRESS: GetPointerFromAddress: unable to read from 829b3718
    Unable to read MiSystemVaType memory at 82993160
    00000000

    CURRENT_IRQL: 2

    FAULTING_IP:
    nwifi!MP6SendNBLInternal+39
    9450cc55 8b08 mov ecx,dword ptr [eax]

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

    BUGCHECK_STR: 0xD1

    PROCESS_NAME: CoDMP.exe


    TRAP_FRAME: 81f5c160 -- (.trap 0xffffffff81f5c160)
    ErrCode = 00000000
    eax=00000000 ebx=81f5c1bc ecx=945353d7 edx=00000020 esi=00000000 edi=00000103
    eip=9450cc55 esp=81f5c1d4 ebp=81f5c1ec iopl=0 nv up ei pl nz ac pe cy
    cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010217
    nwifi!MP6SendNBLInternal+0x39:
    9450cc55 8b08 mov ecx,dword ptr [eax] ds:0023:00000000=????????
    Resetting default scope

    LAST_CONTROL_TRANSFER: from 9450cc55 to 828917eb

    STACK_TEXT:
    81f5c160 9450cc55 badb0d00 00000020 00000000 nt!KiTrap0E+0x2cf
    81f5c1ec 9450d23b 00000000 85000302 86928a70 nwifi!MP6SendNBLInternal+0x39
    81f5c204 945103df 87b7d008 85eda130 00000000 nwifi!MP6Send+0x67
    81f5c21c 8ae2b59d 87d40c08 85eda130 00000000 nwifi!FilterSendNetBufferLists+0x19
    81f5c23c 8ae2b623 85eda130 85eda130 00000000 ndis!ndisFilterSendNetBufferLists+0x87
    81f5c254 8ef1cc20 86928a70 85eda130 00000000 ndis!NdisFSendNetBufferLists+0x38
    81f5c2d0 8ae2b474 8739b460 85eda130 00000000 pacer!PcFilterSendNetBufferLists+0x256
    81f5c2fc 8ae8fd8c 84fa90e0 85eda130 00000000 ndis!ndisSendNBLToFilter+0xf2
    81f5c32c 8b07403e 87d4caa8 85eda130 00000000 ndis!NdisSendNetBufferLists+0x162
    81f5c378 8b0747c1 87d4b220 00000000 00000000 tcpip!FlSendPackets+0x416
    81f5c3cc 8b0744d3 8b0f4d98 00000000 00000000 tcpip!IppFragmentPackets+0x2e2
    81f5c404 8b07c273 8b0f4d98 85d45d5c 85d45df8 tcpip!IppDispatchSendPacketHelper+0x266
    81f5c4a4 8b08230e 00d45d5c 81f5c584 882696f0 tcpip!IppPacketizeDatagrams+0x8d6
    81f5c524 8b082595 00000000 00000004 8b0f4d98 tcpip!IppSendDatagramsCommon+0x652
    81f5c544 8b06230c 85d4d8a8 81f5c55c 81f5c774 tcpip!IpNlpSendDatagrams+0x4b
    81f5c5d0 8b06229d 85d4d8a8 81f5c774 00000000 tcpip!IppSlowSendDatagram+0x31
    81f5c630 8b07dd3c 85d4d8a8 00000000 81f5c774 tcpip!IpNlpFastSendDatagram+0xefd
    81f5c810 8b07fb31 00000000 00000000 87dad8a8 tcpip!UdpSendMessagesOnPathCreation+0x702
    81f5c914 8b07f37a 85d4d920 00f5ca04 00000000 tcpip!UdpSendMessages+0x595
    81f5c928 828daf8a 81f5c9b8 aa0c5bb2 00000000 tcpip!UdpTlProviderSendMessagesCalloutRoutine+0x13
    81f5c990 8b07f170 8b07f367 81f5c9b8 00000000 nt!KeExpandKernelStackAndCalloutEx+0x132
    81f5c9d0 8ee86783 87dad8a8 81f5ca04 85506800 tcpip!UdpTlProviderSendMessages+0x67
    81f5c9e8 8eea672f 856b5008 81f5ca04 856b5008 afd!AfdTLSendMessages+0x27
    81f5ca40 8eea6398 856b5008 85506800 0f1c998d afd!AfdTLFastDgramSend+0x7d
    81f5cab0 8ee963e1 856b5008 81f5cb6c 0000002b afd!AfdFastDatagramSend+0x5d3
    81f5cc28 82aa58f7 86101301 00000001 02497554 afd!AfdFastIoDeviceControl+0x3dc
    81f5ccd0 82aa84ac 85f87b60 000002f0 00000000 nt!IopXxxControlFile+0x2d0
    81f5cd04 8288e42a 000002f4 000002f0 00000000 nt!NtDeviceIoControlFile+0x2a
    81f5cd04 77da64f4 000002f4 000002f0 00000000 nt!KiFastCallEntry+0x12a
    WARNING: Frame IP not in any known module. Following frames may be wrong.
    02497610 00000000 00000000 00000000 00000000 0x77da64f4


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    nwifi!MP6SendNBLInternal+39
    9450cc55 8b08 mov ecx,dword ptr [eax]

    SYMBOL_STACK_INDEX: 1

    SYMBOL_NAME: nwifi!MP6SendNBLInternal+39

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: nwifi

    IMAGE_NAME: nwifi.sys

    DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc89f

    FAILURE_BUCKET_ID: 0xD1_nwifi!MP6SendNBLInternal+39

    BUCKET_ID: 0xD1_nwifi!MP6SendNBLInternal+39

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

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

    DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)

    hope this helps and of course if you get more upload them


    Kenn J++
      My Computer


  4. Posts : 11
    windows seven
    Thread Starter
       #4

    Thanks zigzag3143 for reply, I am going to do tonigt memtest and than I post result here.
      My Computer


  5. Posts : 28,845
    Win 8 Release candidate 8400
       #5

    mirdic said:
    Thanks zigzag3143 for reply, I am going to do tonigt memtest and than I post result here.
    You are welcomelet us know if you need help


    Ken J+
      My Computer


  6. Posts : 11
    windows seven
    Thread Starter
       #6

    Hello,

    Memtest ran for 8hours without error and my drivers are up to date, but BSOD is constantly #1 issue in my notebook.

    I including my dump file, please someone helps me with this annoying problem.

    dumps: http://www.stun.cz/minidump2.rar

    THX for help.
      My Computer


  7. Posts : 5,747
    7600.20510 x86
       #7

    Check that you're not overclocking anything, intentionally or otherwise. Use CPU-Z to look. Post a screenshot of it if ya want.

    These are still on the system and should be updated or uninstalled, depending on their necessity to the system:

    AGRSM AGRSM.sys Mon Nov 10 09:56:37 2008
    nscirda nscirda.sys Sat Jan 19 00:55:24 2008
    ozscr ozscr.sys Thu Apr 21 09:58:36 2005
    LVUSBSta LVUSBSta.sys Wed Feb 15 07:56:43 2006
    lv321av lv321av.sys Wed Feb 15 08:00:30 2006

    ..what Ken has already told you.

    And update to the latest video card driver from ATI's site!

    atikmdag atikmdag.sys Wed Oct 03 23:13:44 2007
      My Computer


  8. Posts : 5,705
    Win7 x64 + x86
       #8

    Just because the driver is the most recent doesn't mean that it's working correctly.

    Download the most recent copy of the wifi drivers from the manufacturer's website
    Uninstall the current wifi drivers
    Install the freshly downloaded ones.

    Running all 20 memory dump files - Will BRB....
      My Computer


  9. Posts : 5,705
    Win7 x64 + x86
       #9

    I ran the last 20 memory dump files. The most significant (IMO) is the last one - a Verifier enabled minidump blaming ozscr.sys - a component of
    O2Micro PC/SC SmartCard Reader Driver

    Please download a fresh copy of the drivers from the website of the computer manufacturer
    Uninstall the current drivers
    Install the freshly downloaded drivers.

    Please understand that there may be more than one issue here - so if the BSOD's continue, please continue to post them.

    Older drivers that should be updated:
    Code:
    lv321av.sys  Wed Feb 15 08:00:30 2006
    ozscr.sys    Thu Apr 21 09:58:36 2005
    atikmdag.sys Wed Oct 03 23:13:44 2007
    LVUSBSta.sys Wed Feb 15 07:56:43 2006
    The summary of the memory dump analysis':
    Code:
    Built by: 7600.16385.x86fre.win7_rtm.090713-1255
    Debug session time: Tue Nov 10 17:30:43.812 2009 (GMT-5)
    System Uptime: 0 days 13:07:25.090
    BugCheck D1, {0, 2, 0, 9450cc55}
    Probably caused by : nwifi.sys ( nwifi!MP6SendNBLInternal+39 )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  CoDMP.exe
    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
    Built by: 7600.16385.x86fre.win7_rtm.090713-1255
    Debug session time: Tue Nov 17 09:19:04.029 2009 (GMT-5)
    System Uptime: 2 days 15:16:45.711
    *** WARNING: Unable to verify timestamp for sptd.sys
    *** ERROR: Module load completed but symbols could not be loaded for sptd.sys
    *** WARNING: Unable to verify timestamp for amdxata.sys
    *** ERROR: Module load completed but symbols could not be loaded for amdxata.sys
    *** WARNING: Unable to verify timestamp for spldr.sys
    *** ERROR: Module load completed but symbols could not be loaded for spldr.sys
    *** WARNING: Unable to verify timestamp for ehdrv.sys
    *** ERROR: Module load completed but symbols could not be loaded for ehdrv.sys
    *** WARNING: Unable to verify timestamp for lv321av.sys
    *** ERROR: Module load completed but symbols could not be loaded for lv321av.sys
    *** WARNING: Unable to verify timestamp for dxgkrnl.sys
    *** ERROR: Module load completed but symbols could not be loaded for dxgkrnl.sys
    *** WARNING: Unable to verify timestamp for e1e6032.sys
    *** ERROR: Module load completed but symbols could not be loaded for e1e6032.sys
    *** WARNING: Unable to verify timestamp for atikmdag.sys
    *** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
    *** WARNING: Unable to verify timestamp for drmk.sys
    *** ERROR: Module load completed but symbols could not be loaded for drmk.sys
    *** WARNING: Unable to verify timestamp for AGRSM.sys
    *** ERROR: Module load completed but symbols could not be loaded for AGRSM.sys
    *** WARNING: Unable to verify timestamp for LUsbFilt.Sys
    *** ERROR: Module load completed but symbols could not be loaded for LUsbFilt.Sys
    *** WARNING: Unable to verify timestamp for LHidFilt.Sys
    *** ERROR: Module load completed but symbols could not be loaded for LHidFilt.Sys
    *** WARNING: Unable to verify timestamp for LMouFilt.Sys
    *** ERROR: Module load completed but symbols could not be loaded for LMouFilt.Sys
    *** WARNING: Unable to verify timestamp for LVUSBSta.sys
    *** ERROR: Module load completed but symbols could not be loaded for LVUSBSta.sys
    *** WARNING: Unable to verify timestamp for netw5v32.sys
    *** ERROR: Module load completed but symbols could not be loaded for netw5v32.sys
    *** WARNING: Unable to verify timestamp for ozscr.sys
    *** ERROR: Module load completed but symbols could not be loaded for ozscr.sys
    *** WARNING: Unable to verify timestamp for ap8g05sz.SYS
    *** ERROR: Module load completed but symbols could not be loaded for ap8g05sz.SYS
    *** WARNING: Unable to verify timestamp for win32k.sys
    *** ERROR: Module load completed but symbols could not be loaded for win32k.sys
    *** WARNING: Unable to verify timestamp for TSDDD.dll
    *** ERROR: Module load completed but symbols could not be loaded for TSDDD.dll
    *** WARNING: Unable to verify timestamp for cdd.dll
    *** ERROR: Module load completed but symbols could not be loaded for cdd.dll
    *** WARNING: Unable to verify timestamp for eamon.sys
    *** ERROR: Module load completed but symbols could not be loaded for eamon.sys
    *** WARNING: Unable to verify timestamp for epfwwfpr.sys
    *** ERROR: Module load completed but symbols could not be loaded for epfwwfpr.sys
    *** WARNING: Unable to verify timestamp for peauth.sys
    *** ERROR: Module load completed but symbols could not be loaded for peauth.sys
    *** WARNING: Unable to verify timestamp for secdrv.SYS
    *** ERROR: Module load completed but symbols could not be loaded for secdrv.SYS
    *** WARNING: Unable to verify timestamp for spsys.sys
    *** ERROR: Module load completed but symbols could not be loaded for spsys.sys
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  System
    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
    Built by: 7600.16385.x86fre.win7_rtm.090713-1255
    Debug session time: Thu Nov 19 11:03:25.750 2009 (GMT-5)
    System Uptime: 0 days 20:12:27.109
    BugCheck A, {0, 2, 1, 82a6d2af}
    Probably caused by : win32k.sys ( win32k!UserEnterUserCritSec+c )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  firefox.exe
    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
    Built by: 7600.16385.x86fre.win7_rtm.090713-1255
    Debug session time: Thu Nov 19 11:49:28.091 2009 (GMT-5)
    System Uptime: 0 days 0:40:46.369
    *** WARNING: Unable to verify timestamp for netw5v32.sys
    *** ERROR: Module load completed but symbols could not be loaded for netw5v32.sys
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  System
    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
    Built by: 7600.16385.x86fre.win7_rtm.090713-1255
    Debug session time: Thu Nov 19 16:53:11.708 2009 (GMT-5)
    System Uptime: 0 days 5:02:06.986
    BugCheck 1000008E, {c0000005, 96c29137, 8eec3c38, 0}
    Probably caused by : win32k.sys ( win32k!TimersProc+75 )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  csrss.exe
    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
    Built by: 7600.16385.x86fre.win7_rtm.090713-1255
    Debug session time: Sat Nov 21 11:15:33.947 2009 (GMT-5)
    System Uptime: 0 days 2:12:11.225
    BugCheck 1000008E, {c0000005, 93732cbb, 9da4bb88, 0}
    Probably caused by : win32k.sys ( win32k!RFONTOBJ::vMakeInactive+18 )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  firefox.exe
    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
    Built by: 7600.16385.x86fre.win7_rtm.090713-1255
    Debug session time: Sun Nov 22 05:58:11.582 2009 (GMT-5)
    System Uptime: 0 days 18:41:30.007
    BugCheck 1000008E, {c0000005, 93f09137, 8eecbc38, 0}
    Probably caused by : win32k.sys ( win32k!TimersProc+75 )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  csrss.exe
    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
    Built by: 7600.16385.x86fre.win7_rtm.090713-1255
    Debug session time: Sun Nov 22 13:35:24.716 2009 (GMT-5)
    System Uptime: 0 days 3:10:47.995
    BugCheck A, {10, 2, 0, 82ac358b}
    Probably caused by : dxgmms1.sys ( dxgmms1!VidSchiSelectReadyNode+60 )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  System
    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
    Built by: 7600.16385.x86fre.win7_rtm.090713-1255
    Debug session time: Sun Nov 22 09:34:52.598 2009 (GMT-5)
    System Uptime: 0 days 0:50:32.877
    BugCheck A, {6, 2, 1, 82a779c6}
    Probably caused by : ntkrpamp.exe ( nt!KiInsertTimerTable+1e2 )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  System
    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
    Built by: 7600.16385.x86fre.win7_rtm.090713-1255
    Debug session time: Sun Nov 22 10:24:08.183 2009 (GMT-5)
    System Uptime: 0 days 0:48:48.462
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  CoDMP.exe
    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
    Built by: 7600.16385.x86fre.win7_rtm.090713-1255
    Debug session time: Sun Nov 22 17:39:55.420 2009 (GMT-5)
    System Uptime: 0 days 4:04:00.656
    BugCheck A, {8, 2, 1, 82e217ee}
    *** WARNING: Unable to verify timestamp for netw5v32.sys
    *** ERROR: Module load completed but symbols could not be loaded for netw5v32.sys
    Probably caused by : hardware ( netw5v32+1431c )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  System
    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
    Built by: 7600.16385.x86fre.win7_rtm.090713-1255
    Debug session time: Thu Nov 26 12:37:28.486 2009 (GMT-5)
    System Uptime: 0 days 3:35:16.765
    BugCheck D1, {12c61153, 2, 0, 952132ab}
    *** WARNING: Unable to verify timestamp for LUsbFilt.Sys
    *** ERROR: Module load completed but symbols could not be loaded for LUsbFilt.Sys
    *** WARNING: Unable to verify timestamp for sptd.sys
    *** ERROR: Module load completed but symbols could not be loaded for sptd.sys
    Probably caused by : hidusb.sys ( hidusb!HumReadReport+3 )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  CoDMP.exe
    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
    Built by: 7600.16385.x86fre.win7_rtm.090713-1255
    Debug session time: Fri Nov 27 15:19:25.685 2009 (GMT-5)
    System Uptime: 0 days 0:09:55.963
    BugCheck 1000008E, {c000001d, 91d7de87, 8078aa90, 0}
    *** WARNING: Unable to verify timestamp for dxgkrnl.sys
    *** ERROR: Module load completed but symbols could not be loaded for dxgkrnl.sys
    *** WARNING: Unable to verify timestamp for atikmdag.sys
    *** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
    Probably caused by : hardware ( dxgmms1!VidSchiExecuteMmIoFlip+4f )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  CoDMP.exe
    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
    Built by: 7600.16385.x86fre.win7_rtm.090713-1255
    Debug session time: Fri Nov 27 15:09:00.907 2009 (GMT-5)
    System Uptime: 0 days 23:58:03.185
    BugCheck 1000008E, {c0000005, 82ae20e1, af7506b4, 0}
    Probably caused by : ntkrpamp.exe ( nt!IopGetFileObjectExtension+f )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  svchost.exe
    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
    Built by: 7600.16385.x86fre.win7_rtm.090713-1255
    Debug session time: Sat Nov 28 11:16:28.593 2009 (GMT-5)
    System Uptime: 0 days 0:37:03.871
    BugCheck 7F, {d, 0, 0, 0}
    *** WARNING: Unable to verify timestamp for win32k.sys
    *** ERROR: Module load completed but symbols could not be loaded for win32k.sys
    Probably caused by : win32k.sys ( win32k+9dac7 )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  csrss.exe
    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
    Built by: 7600.16385.x86fre.win7_rtm.090713-1255
    Debug session time: Sat Nov 28 10:38:53.210 2009 (GMT-5)
    System Uptime: 0 days 2:49:26.364
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  System
    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
    Built by: 7600.16385.x86fre.win7_rtm.090713-1255
    Debug session time: Sat Nov 28 12:12:08.215 2009 (GMT-5)
    System Uptime: 0 days 0:55:10.493
    BugCheck 1000008E, {c0000005, 82a9ddcc, a9237a58, 0}
    Probably caused by : hardware ( nt!FsFilterPerformCompletionCallbacks+16 )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  svchost.exe
    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
    Built by: 7600.16385.x86fre.win7_rtm.090713-1255
    Debug session time: Sat Nov 28 14:06:12.522 2009 (GMT-5)
    System Uptime: 0 days 1:53:33.800
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  System
    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
    Built by: 7600.16385.x86fre.win7_rtm.090713-1255
    Debug session time: Sat Nov 28 18:19:06.466 2009 (GMT-5)
    System Uptime: 0 days 2:51:44.775
    BugCheck 1000008E, {c0000005, 933e9726, 89a7fbfc, 0}
    Probably caused by : win32k.sys ( win32k!xxxRealInternalGetMessage+152 )
    DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
    PROCESS_NAME:  mumble.exe
    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
    Built by: 7600.16385.x86fre.win7_rtm.090713-1255
    Debug session time: Mon Nov 30 05:33:15.440 2009 (GMT-5)
    System Uptime: 0 days 14:24:33.751
    *** WARNING: Unable to verify timestamp for ozscr.sys
    *** ERROR: Module load completed but symbols could not be loaded for ozscr.sys
    DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
    PROCESS_NAME:  System
      My Computer


  10. Posts : 11
    windows seven
    Thread Starter
       #10

    Hello,

    Thanks for help. I deleted old drivers and instal new. We will see if that helped.

    I don't overclocking so there isn't problem.
      My Computer


 
Page 1 of 2 12 LastLast

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 11:00.
Find Us