Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

BSOD while running new software


  • Please log in to reply
3 replies to this topic

#1 Albertus

Albertus

  • Members
  • 2 posts
  • OFFLINE
  •  
  • Local time:11:23 PM

Posted 19 August 2011 - 06:25 AM

Hello,

This is my fist post here, and the problem I'm having is the following:

I got a new weather station called Davis Vantage, which runs its own software. I got the version which communicates the console of the weather station with the PC via serial cable, but since i have no free COM ports I'm using a serial-usb conversor, Prolific PL2303. Before running the weather software, I installed the drivers of this conversor and updated some drivers of Windows Vista as well. And then I opened the software of the weather station, called Weatherlink 5.9.3. And here comes the problem, after some minutes since the program is running, the BSOD appears suddenly, and the PC automaticaly reboots. It only happens when the weatherlink software is running, and the messages I got from the BSOD are:

- Multiple_IRP_complete_requests
- Driver_IRQL_not_less_or_equal

I also see something related to wdf01000.sys driver system below the screen.

I debugged the memory minidumps archives automatically created by Windows, and this is what I got:

Minidump 1


Microsoft ® Windows Debugger Version 6.12.0002.633 X86
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\Mini080811-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) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6002.18327.x86fre.vistasp2_gdr.101014-0432
Machine Name:
Kernel base = 0x81e40000 PsLoadedModuleList = 0x81f57c70
Debug session time: Mon Aug 8 12:12:26.726 2011 (UTC + 2:00)
System Uptime: 0 days 0:56:31.317
Loading Kernel Symbols
...............................................................
................................................................
....................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 10D, {4, 805643d2, 0, 8f6c2708}

Unable to load image \SystemRoot\system32\DRIVERS\ser2pl.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ser2pl.sys
*** ERROR: Module load completed but symbols could not be loaded for ser2pl.sys
Probably caused by : ser2pl.sys ( ser2pl+5e96 )

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

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

WDF_VIOLATION (10d)
The Kernel-Mode Driver Framework was notified that Windows detected an error
in a framework-based driver. In general, the dump file will yield additional
information about the driver that caused this bug check.
Arguments:
Arg1: 00000004, A NULL parameter was passed to a function that required a non-
NULL value. Use the "ln" debugger command with the value of
Parameter 3 as its argument to determine the function which
requires a non-NULL parameter.
Arg2: 805643d2, Reserved.
Arg3: 00000000, The caller's address.
Arg4: 8f6c2708, Reserved.

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


BUGCHECK_STR: 0x10D_4

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: WeatherLink 5.9

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from 8056d70c to 81f0db3f

STACK_TEXT:
81a20a04 8056d70c 0000010d 00000004 805643d2 nt!KeBugCheckEx+0x1e
81a20a20 8056df51 8f6c2708 00000004 805643d2 Wdf01000!FxVerifierBugCheck+0x24
81a20a40 805643d2 8f6c2708 8f6e10c8 8f6c31d8 Wdf01000!FxVerifierNullBugCheck+0x51
81a20a58 8d912e96 8d91d014 8f6c3458 8f6e10c8 Wdf01000!imp_WdfObjectGetTypedContextWorker+0x1d
WARNING: Stack unwind information not available. Following frames may be wrong.
81a20a6c 8d912066 00000000 8d911e0a 81a20aec ser2pl+0x5e96
81a20abc 8d9131b8 016c31d8 00000000 8f6c31d8 ser2pl+0x5066
81a20aec 8d9124aa 8f6c31d8 7091efe8 70936450 ser2pl+0x61b8
81a20b2c 80580908 709361e8 00000001 00000001 ser2pl+0x54aa
81a20b48 805836bb 709361e8 7091efe8 00000001 Wdf01000!FxIoQueueIoStop::Invoke+0x2a
81a20b70 80585fb8 7091efe8 8f6e1010 8f6c9e10 Wdf01000!FxIoQueue::DispatchRequestToDriver+0x1dc
81a20b90 80587722 8f6c9e00 805ad188 8f6c9e10 Wdf01000!FxIoQueue::DispatchEvents+0x4e9
81a20bac 8058885d 00000000 81a20c1c 84199b38 Wdf01000!FxIoQueue::QueueRequest+0x237
81a20bd0 80567fbc 84199b38 81a20c1c 8f6c32e8 Wdf01000!FxPkgIo::Dispatch+0x377
81a20be8 8d911b72 8f6c3010 7093cfe8 84199b38 Wdf01000!imp_WdfDeviceWdmDispatchPreprocessedIrp+0xf1
81a20c1c 80576f4b 7093cfe8 84199b38 8f6ca320 ser2pl+0x4b72
81a20c3c 80577618 84199b38 81a20c60 81e84976 Wdf01000!FxDevice::PreprocessIrp+0x7b
81a20c48 81e84976 8f6c39d0 84199b38 84199b38 Wdf01000!FxDevice::Dispatch+0x32
81a20c60 82bcd581 83f3e4e0 8f6ca268 00000000 nt!IofCallDriver+0x63
81a20c74 81e84976 8f6ca268 00199b38 84199b38 serenum!Serenum_DispatchPassThrough+0x65
81a20c8c 82086c33 84199b38 84199c80 83f3e4e0 nt!IofCallDriver+0x63
81a20cac 8204b330 8f6ca268 83f3e4e0 00000001 nt!IopSynchronousServiceTail+0x1d9
81a20d38 81e8ac7a 8f6ca268 84199b38 00000000 nt!NtReadFile+0x646
81a20d38 779e5ca4 8f6ca268 84199b38 00000000 nt!KiFastCallEntry+0x12a
0012f000 00000000 00000000 00000000 00000000 0x779e5ca4


STACK_COMMAND: kb

FOLLOWUP_IP:
ser2pl+5e96
8d912e96 ?? ???

SYMBOL_STACK_INDEX: 4

SYMBOL_NAME: ser2pl+5e96

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: ser2pl

IMAGE_NAME: ser2pl.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 46af12dd

FAILURE_BUCKET_ID: 0x10D_4_ser2pl+5e96

BUCKET_ID: 0x10D_4_ser2pl+5e96

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


Minidump 2


Microsoft ® Windows Debugger Version 6.12.0002.633 X86
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\Mini080911-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) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6002.18327.x86fre.vistasp2_gdr.101014-0432
Machine Name:
Kernel base = 0x81e36000 PsLoadedModuleList = 0x81f4dc70
Debug session time: Tue Aug 9 11:07:49.704 2011 (UTC + 2:00)
System Uptime: 0 days 16:50:11.295
Loading Kernel Symbols
...............................................................
................................................................
.....................
Loading User Symbols
Loading unloaded module list
.....................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 44, {8b92a2ec, e7a, 0, 0}

Probably caused by : kbdclass.sys ( kbdclass!KeyboardClassServiceCallback+182 )

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

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

MULTIPLE_IRP_COMPLETE_REQUESTS (44)
A driver has requested that an IRP be completed (IoCompleteRequest()), but
the packet has already been completed. This is a tough bug to find because
the easiest case, a driver actually attempted to complete its own packet
twice, is generally not what happened. Rather, two separate drivers each
believe that they own the packet, and each attempts to complete it. The
first actually works, and the second fails. Tracking down which drivers
in the system actually did this is difficult, generally because the trails
of the first driver have been covered by the second. However, the driver
stack for the current request can be found by examining the DeviceObject
fields in each of the stack locations.
Arguments:
Arg1: 8b92a2ec, Address of the IRP
Arg2: 00000e7a
Arg3: 00000000
Arg4: 00000000

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


IRP_ADDRESS: 8b92a2ec

FOLLOWUP_IP:
kbdclass!KeyboardClassServiceCallback+182
807d7e34 6a18 push 18h

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x44

PROCESS_NAME: System

CURRENT_IRQL: 2

LAST_CONTROL_TRANSFER: from 81edd5bb to 81f03b3f

STACK_TEXT:
81f2bc2c 81edd5bb 00000044 8b92a2ec 00000e7a nt!KeBugCheckEx+0x1e
81f2bc68 807d7e34 00000000 85812630 81e7c860 nt!IopfCompleteRequest+0x4b9
81f2bc84 82bed8d7 0000000c 85907be0 8b92a2d0 kbdclass!KeyboardClassServiceCallback+0x182
81f2bce8 81ee06e2 858127dc 01812578 00000000 i8042prt!I8042KeyboardIsrDpc+0xeb
81f2bd50 81ede89d 00000000 0000000e 00000000 nt!KiRetireDpcList+0x147
81f2bd54 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x49


STACK_COMMAND: kb

SYMBOL_STACK_INDEX: 2

SYMBOL_NAME: kbdclass!KeyboardClassServiceCallback+182

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: kbdclass

IMAGE_NAME: kbdclass.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 47918f5a

FAILURE_BUCKET_ID: 0x44_kbdclass!KeyboardClassServiceCallback+182

BUCKET_ID: 0x44_kbdclass!KeyboardClassServiceCallback+182

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

I'd appreciate a lot some help with that issue, since it's driving me mad not being able to use the Weather Station properly and getting these crashes.

Thanks in advance.

BC AdBot (Login to Remove)

 


#2 hamluis

hamluis

    Moderator


  • Moderator
  • 56,381 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:04:23 PM

Posted 19 August 2011 - 10:17 AM

http://msdn.microsoft.com/en-us/library/ff557235(v=vs.85).aspx

<<I'm using a serial-usb conversor, Prolific PL2303.>>

From what I see, that's your problem.

Unable to load image \SystemRoot\system32\DRIVERS\ser2pl.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ser2pl.sys
*** ERROR: Module load completed but symbols could not be loaded for ser2pl.sys
Probably caused by : ser2pl.sys ( ser2pl+5e96 )


Louis

#3 Albertus

Albertus
  • Topic Starter

  • Members
  • 2 posts
  • OFFLINE
  •  
  • Local time:11:23 PM

Posted 20 August 2011 - 02:38 PM

You are right Hamluis, I've uninstalled the drivers of the Prolific conversor and added a new ones, apparently designed for windows 7, but it seems to be working fine now.

Thanks for you help.

#4 hamluis

hamluis

    Moderator


  • Moderator
  • 56,381 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:04:23 PM

Posted 20 August 2011 - 03:35 PM

Glad you got it working properly...happy computing :).

Louis




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users