BSOD 0x00000d1 about 5 hours apart


  1. Posts : 6
    WINDOWS 7 PRO 64BIT
       #1

    BSOD 0x00000d1 about 5 hours apart


    Okay was having issues with vista freezing up so did a clean install formatted the drive and installed 7 pro 64 bit, then started installing accessories

    I have 2 USB to Serial Adapters same type Gigaware that seem to be causing the problem

    WHO crashed shows
    System Information (local)
    --------------------------------------------------------------------------------
    computer name: BEAUCORNER-PC
    windows version: Windows 7 Service Pack 1, 6.1, build: 7601
    windows dir: C:\Windows
    CPU: GenuineIntel Intel(R) Core(TM) i7 CPU 920 @ 2.67GHz Intel586, level: 6
    8 logical processors, active mask: 255
    RAM: 6433177600 total
    VM: 2147352576, free: 1952710656

    --------------------------------------------------------------------------------
    Crash Dump Analysis
    --------------------------------------------------------------------------------
    Crash dump directory: C:\Windows\Minidump
    Crash dumps are enabled on your computer.

    On Tue 10/25/2011 8:25:43 AM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\102511-27643-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
    Bugcheck code: 0xD1 (0x8, 0x2, 0x0, 0xFFFFF88000EFC946)
    Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

    On Tue 10/25/2011 8:25:43 AM GMT your computer crashed
    crash dump file: C:\Windows\memory.dmp
    This was probably caused by the following module: svk2pl64.sys (Svk2pl64+0x9A93)
    Bugcheck code: 0xD1 (0x8, 0x2, 0x0, 0xFFFFF88000EFC946)
    Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
    file path: C:\Windows\system32\drivers\svk2pl64.sys
    product: Gigaware USB to Serial Cable
    company: Gigaware
    description: Gigaware USB to Serial Cable
    Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: svk2pl64.sys (Gigaware USB to Serial Cable, Gigaware).
    Google query: svk2pl64.sys Gigaware DRIVER_IRQL_NOT_LESS_OR_EQUAL

    It shows this each time over and over

    Thanks Jason
    Last edited by darnalljason; 25 Oct 2011 at 12:29. Reason: Update Attachment
      My Computer


  2. Posts : 8,383
    Windows 10 Pro x64, Arch Linux
       #2
      My Computer


  3. Posts : 240
    Win 8 RP, Win 7, XP
       #3

    Attaching more than one USB to Serial Adapter is maybe the problem.
    If the OS is stable when there are no USB to Serial Adapters attached, try plugging in only one and see if OS is still stable.

    You can search for an update of driver software from the manifacturer.

    Are "USB to Serial" and a separate "Serial" device listed in device manager ? What is the serial device you are attaching to the cable ?
      My Computer


  4. Posts : 6
    WINDOWS 7 PRO 64BIT
    Thread Starter
       #4

    Boyans Update


    Boyans, I am attaching a weather station to each serial cord, in device manager there is just two entries under ports gigaware com 4 and gigaware com 5
      My Computer


  5. Posts : 6
    WINDOWS 7 PRO 64BIT
    Thread Starter
       #5

    yowanvista said:

    I have updated the driver to the newest thing I can find. How can i completely remove it and then try to reinstall it
      My Computer


  6. Posts : 6
    WINDOWS 7 PRO 64BIT
    Thread Starter
       #6

    Added files above per posting insturctions
      My Computer


  7. Posts : 240
    Win 8 RP, Win 7, XP
       #7

    darnalljason said:
    Boyans, I am attaching a weather station to each serial cord, in device manager there is just two entries under ports gigaware com 4 and gigaware com 5
    Do the weather station(s) come with some driver to install ?
    The driver and adapter from Gigaware just transform the USB to a serial port - the device you attach to a serial port usually has a driver !

    To uninstall a driver - in Device Manager select device, right click - select Uninstall.
      My Computer


  8. Posts : 6
    WINDOWS 7 PRO 64BIT
    Thread Starter
       #8

    boyans said:
    darnalljason said:
    Boyans, I am attaching a weather station to each serial cord, in device manager there is just two entries under ports gigaware com 4 and gigaware com 5
    Do the weather station(s) come with some driver to install ?
    The driver and adapter from Gigaware just transform the USB to a serial port - the device you attach to a serial port usually has a driver !

    To uninstall a driver - in Device Manager select device, right click - select Uninstall.

    The weather station doesnt have a driver, I install a 3rd party application called virtual weather station that shows what the weather station is showing on the display on the computer screen in that software you just tell it what serial port and what speed, and then it shows up.
      My Computer


  9. Posts : 8,383
    Windows 10 Pro x64, Arch Linux
       #9

    darnalljason said:
    yowanvista said:

    I have updated the driver to the newest thing I can find. How can i completely remove it and then try to reinstall it
    You'll have to remove the software associated to this driver.
    Dump files still blame Svk2pl64.sys, the Gigaware driver
    The only fix to stop these BSODs would be to completely uninstall it
    Code:
    *******************************************************************************
    *                                                                             *
    *                        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: 0000000000000008, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
    Arg4: fffff88000efc946, address which referenced memory
    
    Debugging Details:
    ------------------
    
    
    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80001d16100
     0000000000000008 
    
    CURRENT_IRQL:  2
    
    FAULTING_IP: 
    Wdf01000!imp_WdfObjectGetTypedContextWorker+1e
    fffff880`00efc946 4c8b5110        mov     r10,qword ptr [rcx+10h]
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    BUGCHECK_STR:  0xD1
    
    PROCESS_NAME:  System
    
    TRAP_FRAME:  fffff880022469b0 -- (.trap 0xfffff880022469b0)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000000000000 rbx=0000000000000000 rcx=fffffffffffffff8
    rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff88000efc946 rsp=fffff88002246b40 rbp=fffff88002246c58
     r8=fffff88005a15190  r9=0000057ff8a30a01 r10=fffffa8008680010
    r11=00000000c0000120 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl zr na po nc
    Wdf01000!imp_WdfObjectGetTypedContextWorker+0x1e:
    fffff880`00efc946 4c8b5110        mov     r10,qword ptr [rcx+10h] ds:d1a0:00000000`00000008=????????????????
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from fffff80001ae31e9 to fffff80001ae3c40
    
    STACK_TEXT:  
    fffff880`02246868 fffff800`01ae31e9 : 00000000`0000000a 00000000`00000008 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
    fffff880`02246870 fffff800`01ae1e60 : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`075cf6f0 : nt!KiBugCheckDispatch+0x69
    fffff880`022469b0 fffff880`00efc946 : 00000000`00000002 0000057f`f8a48458 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x260
    fffff880`02246b40 fffff880`05a09a93 : fffffa80`0772d1a0 0000057f`f8a30a98 00000000`00000001 0000057f`f8a30a01 : Wdf01000!imp_WdfObjectGetTypedContextWorker+0x1e
    fffff880`02246b90 fffffa80`0772d1a0 : 0000057f`f8a30a98 00000000`00000001 0000057f`f8a30a01 fffffa80`0756d710 : Svk2pl64+0x9a93
    fffff880`02246b98 0000057f`f8a30a98 : 00000000`00000001 0000057f`f8a30a01 fffffa80`0756d710 fffff880`05a08005 : 0xfffffa80`0772d1a0
    fffff880`02246ba0 00000000`00000001 : 0000057f`f8a30a01 fffffa80`0756d710 fffff880`05a08005 fffff880`021e1040 : 0x57f`f8a30a98
    fffff880`02246ba8 0000057f`f8a30a01 : fffffa80`0756d710 fffff880`05a08005 fffff880`021e1040 00000000`00000022 : 0x1
    fffff880`02246bb0 fffffa80`0756d710 : fffff880`05a08005 fffff880`021e1040 00000000`00000022 00000000`00000001 : 0x57f`f8a30a01
    fffff880`02246bb8 fffff880`05a08005 : fffff880`021e1040 00000000`00000022 00000000`00000001 00000000`00000000 : 0xfffffa80`0756d710
    fffff880`02246bc0 fffff880`021e1040 : 00000000`00000022 00000000`00000001 00000000`00000000 fffffa80`0756d710 : Svk2pl64+0x8005
    fffff880`02246bc8 00000000`00000022 : 00000000`00000001 00000000`00000000 fffffa80`0756d710 fffff880`05a07e51 : 0xfffff880`021e1040
    fffff880`02246bd0 00000000`00000001 : 00000000`00000000 fffffa80`0756d710 fffff880`05a07e51 fffffa80`075cf6f0 : 0x22
    fffff880`02246bd8 00000000`00000000 : fffffa80`0756d710 fffff880`05a07e51 fffffa80`075cf6f0 00000000`00000000 : 0x1
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    Svk2pl64+9a93
    fffff880`05a09a93 ??              ???
    
    SYMBOL_STACK_INDEX:  4
    
    SYMBOL_NAME:  Svk2pl64+9a93
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: Svk2pl64
    
    IMAGE_NAME:  Svk2pl64.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4bb4512d
    
    FAILURE_BUCKET_ID:  X64_0xD1_Svk2pl64+9a93
    
    BUCKET_ID:  X64_0xD1_Svk2pl64+9a93
    
    Followup: MachineOwner
    ---------
      My Computer


 

  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 01:17.
Find Us