Conversion to 64 bit...
Hi,
Is there should be any limitation using a 32 bit compiled printer
driver, on a windows xp 64 bit?
Also, is there should be any limitation limitation (or that a code
change is required) using 32 bit user mode application that runs on
xp 64 bit, and communicates with a 64 bit compiled driver ? (Besides
exchanging pointers from kernel to user mode and back)
Thanks! Tag: Virtual Audio Device Tag: 95191
Conversion to 64 bit...
Hi,
Is there should be any limitation using a 32 bit compiled printer
driver, on a windows xp 64 bit?
Also, is there should be any limitation limitation (or that a code
change is required) using 32 bit user mode application that runs on
xp 64 bit, and communicates with a 64 bit compiled driver ? (Besides
exchanging pointers from kernel to user mode and back)
Thanks! Tag: Virtual Audio Device Tag: 95190
Failed to load driver on Vista
I have an application that works with two particular drivers, one is
loaded on boot and second is loaded when my application is working. I
use the first driver to load and unload the second driver using ZwLoad/
UnloadDriver. Everything works fine on Win2K and XP but I encounter
some problems in Vista. Sometimes I get error 0xC0000034 upon
ZwLoadDriver of my second driver. I looked for my drivers and devices
in the system, but monitors such as DeviceTree or WinObj do not show
any of them. On the other hand, from a full memory dump I can see my
second driver loaded.
>From some reasons that I can't explain, I see that when I run my
application "as administrator" and immediately close the application
everything suddenly get back to track. When I run my application as
administrator I even do not attemp to load the driver.
Of course, after computer restart the application starts to work fine
as well.
It is important to mention that both drivers are properly signed.
Any help is very appreciated. Tag: Virtual Audio Device Tag: 95189
LNK2019 Error with Win Server 2003 Checked x64
I've written a driver and have successfully built it using WinXP Checked Build.
When I compile the same project with the Windows Server 2003 Checked x64
tools, I get "LNK2019 - unresolved external symbol <blah blah> referenced in
DriverEntry".
I'm linking in .lib files, declaring them as "external" in the driver code.
As I said, the same code and files compile perfectly with the WinXP Checked
Build compiler. I'm getting the LNK2019 unresolved errors with the Windows
Server 2003 Checked x64 Build compiler.
Any help and insight would be appreciated.
Thanks Tag: Virtual Audio Device Tag: 95186
Re: USB camera driver speed limited in vista system?
We send a bulk request using 1600*1200(1920000) bytes size to host driver.
Is this size wrong?
Thank you very much!
Abei
no, it does not. waht size reads are you sending to the bulk endpoint?
--
Please do not send e-mail directly to this alias. this alias is for
newsgroup purposes only.
This posting is provided "AS IS" with no warranties, and confers no rights.
"abei" <aboutwho_1@163.com> wrote in message
news:umQNx%23tnHHA.2452@TK2MSFTNGP02.phx.gbl...
> We have a 2M pixels USB camera to be used in new vista system. We have
> developped a new driver for vista and it works well, but now we have found
> a problem about this driver. Our camera can output about 10fps
> (1600*1200 ) stream when it works in Windows XP system. But our camera can
> only output about 5fps(1600 * 1200) stream when it works in vista.
> Does anyone have meet this problem? Does Vista have a speed limited to USB
> bulk pipe?
>
> thank very much!
>
> abei
> Tag: Virtual Audio Device Tag: 95184
RNDIS interface stops sending traffic after REMOTE_NDIS_RESET_MSG
Hi Guys,
Could somebody tell me why RNDIS interface stops transmitting eth packets
after sending a REMOTE_NDIS_RESET_MSG? Is there any command to know about the
reason of this soft reset?
Also, which command we can use from RNDIS device side to tell the host to
restart the RNDIS initialisation process again? Or Is there any msg from
device side that it can be the initiator?
Thanks a lot for any help..
Regards,
Joji Tag: Virtual Audio Device Tag: 95173
Using QueryPerformanceCounter in NDIS miniport driver
I want to use QueryPerformanceCounter() to get the system's time. But, when I
use it in the DriverEntry(), it will cause the driver crash. So, I'm asking
whether I could use this function in the miniport driver??? Or, I use it
wrongly. Please help me!
Thanks! Tag: Virtual Audio Device Tag: 95171
AVStream PresentationTime
The DDK docs say, for IKsReferenceClock::GetTime, "Do not call this
method when obtaining a timestamp for the PresentationTime member of
KSSTREAM_HEADER. Instead, call IKsReferenceClock::GetCorrelatedTime in
this situation."
However, every one of the samples uses GetTime, and none use
GetCorrelatedTime. Any insight? Or does it just not matter very much?
Cheers,
--mkj
Michael K. Jones
Stone Hill Comsulting
http://www.stonehill.com Tag: Virtual Audio Device Tag: 95169
No UINumber being assigned to PCI attached MPS devices in Vista
I have an MPS driver which relied upon the UINumber to identify which
attached device was being addressed. Past OS's apparently assigned this
attribute the PCI slot location of the MPS board. However, it appears as
though Vista no longer performs this assignment. Is the a different
mechanism that can be used which works in 2000, Server 2003, and XP? Tag: Virtual Audio Device Tag: 95168
Linking issue with DiInstallDriver
Hello,
I am writing a setup application for installing a driver under Vista. I
would like to use DiInstallDriver function, but I meet an error during
linking phase. My code is very simple. I am just checking the API :
#define WINVER 0x0600
#define _WIN32_WINNT 0x0600
#include <windows.h>
#include <newdev.h>
#include <stdio.h>
int wmain()
{
LPCTSTR pInf=L"C:\\Users\\Eric\\dev\\ndistgb.inf";
int ret = DiInstallDriver(NULL,pInf,0,FALSE);
switch(ret)
{
case ERROR_ACCESS_DENIED:
printf("access denied.\n");
default:
printf("installed.\n");
}
return 0;
}
Compilation output is (in french) :
Compilation en cours...
Compilateur d'optimisation Microsoft (R) 32 bits C/C++ version
14.00.50727.762 pour 80x86
Copyright (C) Microsoft Corporation. Tous droits réservés.
cl /Od /I "C:\WinDDK\6000\inc\api" /D "WIN32" /D "_DEBUG" /D "_CONSOLE"
/D "_UNICODE" /D "UNICODE" /Gm /EHsc /RTC1 /MDd /Fo"Debug\\"
/Fd"Debug\vc80.pdb" /W3 /c /Wp64 /ZI /TC /FC .\insdrv.cpp
insdrv.cpp
Édition des liens en cours...
Recherche en cours des bibliothèques
Recherche en cours C:\WinDDK\6000\lib\wlh\i386\newdev.lib :
Recherche en cours C:\WinDDK\6000\lib\wlh\i386\setupapi.lib :
[ removed ]
Recherche en cours C:\WinDDK\6000\lib\wlh\i386\newdev.lib :
Recherche en cours C:\WinDDK\6000\lib\wlh\i386\setupapi.lib :
Fin de la recherche des bibliothèques
insdrv.obj : error LNK2019: symbole externe non résolu _DiInstallDriverW
référencé dans la fonction _wmain
[ or insdrv.obj : error LNK2019: unresolved external symbol
_DiInstallDriverW referenced in function _wmain ]
C:\Users\Eric\Documents\Projets\insdrv\Debug\insdrv.exe : fatal error
LNK1120: 1 externes non résolus
I have also compiled with /TP and I got the same result. newdev.lib is
set in additionnal dependancies. I must have forgotten something but I
have no idea for resolving this issue. Any advice is welcomed. Thanks.
Eric Tag: Virtual Audio Device Tag: 95167
USB camera driver speed limited in vista system?
We have a 2M pixels USB camera to be used in new vista system. We have
developped a new driver for vista and it works well, but now we have found a
problem about this driver. Our camera can output about 10fps (1600*1200 )
stream when it works in Windows XP system. But our camera can only output
about 5fps(1600 * 1200) stream when it works in vista.
Does anyone have meet this problem? Does Vista have a speed limited to USB
bulk pipe?
thank very much!
abei Tag: Virtual Audio Device Tag: 95165
USB Mass Storage and File system
Hi,
I have to implement a USB Mass Storage disk using the flash. This is
to be used with Windows OS.
My question is:-
- Which protocol of Mass Storage shall I use?
- Do I have to implement a File system also for this? I mean how will
windows file manager recognise my disk?
Neeti. Tag: Virtual Audio Device Tag: 95156
Print IRP information
Where can I find data that is trasported by IRP to the levels? I need
to print HEX dump of tis buffer.
Best regards. Tag: Virtual Audio Device Tag: 95155
[KMDF] Hardware for the PLX9x5x sample
Hello,
I'm interested by the PLX9x5x sample but the link in WDK for the product kit
and the hardware specification is dead.
Where can I find these informations and where can I buy the
"PLX9656/9653RDK-LITE board"?
I found this link
(http://www.plxtech.com/pdf/product_briefs/9656rdk-lite.pdf) but I'm not
sure...
Thank you!
Cedric Tag: Virtual Audio Device Tag: 95154
AllocateCommonBuffer failure in Vista
I'm using the the routine "AllocateCommonBuffer" to allocate memory for my
PCI device. The call succeeds in WinXP but in Vista it fails.
Does any one have an idea what it may be? Is DMA different in Vista?
Thanks in advance. Tag: Virtual Audio Device Tag: 95153
Adding adapters to a bridge using a script...
I need to add adapters to a bridge using a script.
I can enable/disable the bridge using devcon, and tweak some settings
using netsh, but how to remove and add an adapter to the bridge?
The problem is that when we add and remove our virtual bridge to the
adapter, the MAC address always goes to the same number (AA-BB-CC-DD-
EE-01), unless we do a strange dance - remove the virtual adapter,
disable the adapter, enable the adapter, add the adapter. Of course
when we reboot, it reverts back to the AA-BB-CC-DD-EE-01 again, and
then we need to do the dance.
So, we just need a script that does the dance for us. Adding and
removing the adapter.
I looked for INetCfg interface and the BINDVIEW sample in the DDK (or
NETCFG in earlier DDKs), but I don't have a DDK.
Help! Tag: Virtual Audio Device Tag: 95146
Question about USB device setup class
Hi!
I have a question about setup classes. My device is a USB device which is
used for software updating inside wireless communication devices. As I
read from WDK documentation, I should not place my device under USB setup
class:
"This class includes USB host controllers and USB hubs, but not USB
peripherals. Drivers for this class are system-supplied."
However I see from WDK 6000 samples, that the "bulkusb" driver is placed
under the USB category. From the WDK documentation I also find the
statements like:
"If your device meets both of the following criteria, you should assign it
to an existing device setup class:
- Your device's installation and configuration requirements match those of
an
existing class.
- Your device's capabilities match those of an existing class."
So is it correct to create a new device setup class in my case or to place
my device under the USB setup class? I ask this to avoid any problems on
WHQL certification...
--
Lauri Ehrenpreis Tag: Virtual Audio Device Tag: 95143
Change communication mode of parallel driver
Hello,
i'd like to change from ECP to CENTRONICS mode on Windows XP.
I tried IOCTL_IEEE1284_GET_MODE/IOCTL_IEEE1284_NEGOTIATE and the
"DefaultModes" entry within RTL_REGISTRY_SERVICES-Parport\Parameters.
Both without success.
IOCTL_IEEE1284_GET_MODE allways return the same ( wrong ) values ( read
protocol = NIBBLE, write protocol = CENTRONICS ).
When using IOCTL_IEEE1284_NEGOTIATE to change the settings, the returned
PARCLASS_NEGOTIATION_MASK structure is always filled with read=0 and write=0.
The "DefaultModes" registry entry seems not to change anything.
Any ideas on how to change the communication mode successfully?
Has anybody ever tried these IOCTLs?
Thank you. Tag: Virtual Audio Device Tag: 95140
Windows CE 5.0. Passing data between an ISR and an IST
HELP:
"
To pass data between an ISR and an IST
1. Reserve physical memory for the ISR in your Config.bib file.
Config.bib contains several examples of reserving physical memory for
the serial and debug drivers.
...
...
"
But my config.bib hasn't the "several examples".
Can anybody give me such example? Please. Tag: Virtual Audio Device Tag: 95139
Serial Number Inplemantaiton in PCIe ExpressCard
Dear Sir,
Can anybody explain the following queries
1) What is the use of Serial Number Implementaion in PCI Express Card/device.
2) How to test this feature in Microsoft Windows Vista and Windows XP.
3) Can we test this feature for a PCI Express device on PCIe single lane
slot (which is on mother board) or do we need to have PCI ExpressCard port
and device to test this feature?
4) Is Serial Number feature in PCI Express card identical to iSerial ( and
String Descriptors) in USB ?
Thanks in advance,
Chiranjeevi Tag: Virtual Audio Device Tag: 95138
USB over IP Virtual Host Controller Interface driver
Hi,
I am imprmenting the project of USB over IP without using any seperate
hardware.
To implement such a system , I read that I have to implement virtual
host controller interface driver.
I have experience in USB driver but not on host controller driver.
I have developed a Vrtual Graphics Driver , in which we were
redirecting all the calls to GDI engine, but I not able to
understand
1) the concept behind Virtual Host Controller Interface driver.
2)its role in the kernel stack.
3)How to implement it ?
I am totally confused as to from where to start or what to read.
Please if you have any suggestion or reference then kindly share it
with me..
Thanking You
Anshul Makkar Tag: Virtual Audio Device Tag: 95129
Re: Standby-Sleep State Problem
Im sorry about that, but when i sent the reply i got an error that my
request cannot be processed now. So i had to resend it.
I suppose this will not be repeated. Sorry once again.
Regards,
James Tag: Virtual Audio Device Tag: 95128
How to Power Down USB Device Programatically?
Hi,
In my generic usb function driver during the IRP_MN_START_DEVICE
device i need to power down and power up a usb Smart Card Reader.
I have tried sending PoRequestPowerIrp to power down and up the
device, it returns successfully.But the power supply to the device is
still continued (It has an LED to indicate that).
I looked in to IOCTL_INTERNAL_USB_CYCLE_PORT Docs say that is
simulates unplug and replug so no power down takes place during this
IOCTL.
Do i need to complete the Start Device and wait for idle notification
then power it down, power it up and configure. Is that a right way to
do it?
Is there any other way i can stop the power supply to the device from
HUB and start it again?
Any help is appreciated..
Thanks
Subodh Tag: Virtual Audio Device Tag: 95126
Filter Driver problem
I'm developping a Filter Driver, but I have a big problem when I inser
a USB Device the 1st time DriverEntry is right called then I have
FilterAddDevice and a undefined number of FilterDispatchPnp calls
with the following code. My device power on but the program can't
comunicate with it!!! Why? What is wrong on my code?
Scuse me for my english.
Best regards for every HELP !!
G.M.
#define _X86_
#include "CORE.h"
#pragma alloc_text (INIT, DriverEntry)
#pragma alloc_text (PAGE, FilterAddDevice)
#pragma alloc_text (PAGE, FilterDispatchPnp)
#pragma alloc_text (PAGE, FilterUnload)
/
**********************************************************************
*
* DriverEntry
*
* This is the default entry point for drivers. The parameters
* are a driver object and the registry path.
*
**********************************************************************/
NTSTATUS DriverEntry(IN PDRIVER_OBJECT DriverObject, IN
PUNICODE_STRING RegistryPath)
{
NTSTATUS status = STATUS_SUCCESS;
UNREFERENCED_PARAMETER (RegistryPath);
DbgPrint ("Entry point DriverEntry\n");
DriverObject->MajorFunction[IRP_MJ_PNP] =
FilterDispatchPnp;
DriverObject->DriverExtension->AddDevice =
FilterAddDevice;
DriverObject->DriverUnload = FilterUnload;
return status;
}
NTSTATUS FilterAddDevice(IN PDRIVER_OBJECT DriverObject, IN
PDEVICE_OBJECT PhysicalDeviceObject)
{
NTSTATUS status = STATUS_SUCCESS;
PDEVICE_OBJECT deviceObject = NULL;
PDEVICE_EXTENSION deviceExtension;
ULONG deviceType = FILE_DEVICE_UNKNOWN;
PAGED_CODE ();
DbgPrint("AddDevice\n");
// Create a filter device object.
status = IoCreateDevice (DriverObject, sizeof (DEVICE_EXTENSION),
NULL, deviceType, FILE_DEVICE_SECURE_OPEN, FALSE, &deviceObject);
deviceExtension = (PDEVICE_EXTENSION) deviceObject-
>DeviceExtension;
deviceExtension->Type = DEVICE_TYPE_FIDO;
deviceExtension->NextLowerDriver = IoAttachDeviceToDeviceStack
(deviceObject, PhysicalDeviceObject);
// Failure for attachment is an indication of a broken plug & play
system.
if(NULL == deviceExtension->NextLowerDriver)
{
IoDeleteDevice(deviceObject);
return STATUS_UNSUCCESSFUL;
}
deviceObject->Flags |= deviceExtension->NextLowerDriver->Flags &
(DO_BUFFERED_IO | DO_DIRECT_IO | DO_POWER_PAGABLE );
deviceObject->DeviceType = deviceExtension->NextLowerDriver-
>DeviceType;
deviceObject->Characteristics = deviceExtension->NextLowerDriver-
>Characteristics;
deviceExtension->Self = deviceObject;
// Let us use remove lock to keep count of IRPs so that we don't
// deteach and delete our deviceobject until all pending I/Os in
our
// devstack are completed. Remlock is required to protect us from
// various race conditions where our driver can get unloaded while
we
// are still running dispatch or completion code.
IoInitializeRemoveLock (&deviceExtension->RemoveLock, POOL_TAG, 1,
100);
deviceExtension->DevicePnPState = NotStarted;
deviceExtension->PreviousPnPState = NotStarted;
deviceObject->Flags &= ~DO_DEVICE_INITIALIZING;
return STATUS_SUCCESS;
}
VOID FilterUnload(IN PDRIVER_OBJECT DriverObject)
{
PAGED_CODE();
ASSERT(DriverObject->DeviceObject == NULL);
DbgPrint ("unload\n");
return;
}
NTSTATUS FilterDispatchPnp (IN PDEVICE_OBJECT DeviceObject, IN PIRP
Irp)
{
NTSTATUS status;
PDEVICE_EXTENSION pdx;
DbgPrint ("FilterDispatchPnp\n");
pdx = (PDEVICE_EXTENSION) DeviceObject->DeviceExtension;
IoSkipCurrentIrpStackLocation(Irp);
status = IoCallDriver(pdx->NextLowerDriver, Irp);
return status;
} Tag: Virtual Audio Device Tag: 95125
filter Driver issue
Can we grab the event of copying or cut of file from a secure location
to an unsecure location through a filter driver like truecrypt code or
something
Any of the help is welcome
regards
vaibhav Tag: Virtual Audio Device Tag: 95122
Re: Standby-Sleep State Problem
Doron,
Thanks for the response. Can you provide me the link to the QFEs where
they are available because i could not find it in Microsoft website.
Also, Can you send me the e-mail address of MSFT PSS.
Thank You.
Regards,
James Tag: Virtual Audio Device Tag: 95121
Re: Standby-Sleep State Problem
Doron,
Thanks for the response. Can you provide me the link to the QFEs where
they are available because i could not find it in Microsoft website.
Also, Can you send me the e-mail address of MSFT PSS.
Thank You.
Regards,
James Tag: Virtual Audio Device Tag: 95120
Re: Standby-Sleep State Problem
Doron,
Thanks for the response. Can you provide me the link to the QFEs where
they are available because i could not find it in Microsoft website.
Also, Can you send me the e-mail address of MSFT PSS.
Thank You.
Regards,
James Tag: Virtual Audio Device Tag: 95117
Re: Standby-Sleep State Problem
Doron,
Thanks for the response. Can you provide me the link to the QFEs where
they are available because i could not find it in Microsoft website.
Also, Can you send me the e-mail address of MSFT PSS.
Thank You.
Regards,
James Tag: Virtual Audio Device Tag: 95116
Re: Standby-Sleep State Problem
Doron,
Thanks for the response. Can you provide me the link to the QFEs where
they are available because i could not find it in Microsoft website.
Also, Can you send me the e-mail address of MSFT PSS.
Thank You.
Regards,
James Tag: Virtual Audio Device Tag: 95115
printer drivers initializing COM
We have recently discovered that during our application's initialization,
certain printer drivers cause COM to be initialized on our thread when we
call CreateIC(). This spoils the thread for our later use, which needs to
initialize COM with a different, incompatible concurrency model.
Shouldn't something like this prevent the printer driver from becoming logo
certified?
Any suggestions how we can program defensively around these rude drivers?
Thanks... Tag: Virtual Audio Device Tag: 95100
MIDI input with AVStream on Windows Vista
I'm having a problem with legacy MIDI input with AVStream on Windows Vista.
The driver works fine on Windows XP. I receive MIDI data from the hardware,
assemble it into a short MIDI message, and then request the leading edge
stream pointer for my pin. KS gives me a 20 byte buffer, which I fill with a
KSMUSICFORMAT structure followed by the MIDI data. Since KSMUSICFORMAT needs
to be DWORD aligned, I set the byte count in the KSMUSICFORMAT to the actual
MIDI message size and the DataUsed member of the leading edge stream pointer
to the total buffer size, rounded up to the next DWORD.
On Windows Vista, the problem is that requesting that the leading edge
stream pointer for my pin fails on occasion, so I have nowhere to store the
incoming data.
I could buffer the data internally until my process handler is called. On
Vista, KS provides 264 byte buffers, so I thought I could use the larger
buffers to store multiple MIDI messages. The problem here is that I have not
been able to put more than one MIDI message into a buffer at a time. I've
tried doing this:
KSMUSICFORMAT
three byte MIDI message
KSMUSICFORMAT
three byte MIDI message
with each of the segments DWORD aligned, for a total of 24 bytes. My test
application only receives the first message.
I tried some other approaches with no success. So I'm a little stumped.
Matt Tag: Virtual Audio Device Tag: 95099
Filter driver question
Hi all
I need to be able to create a PnP filter for a removable usb flash
drive device - which is typically handled by the Usb mass storage
class driver. The filter would need to register an additional
interface for the device PDO in the AddDevice routine
I need to be able to get a handle to the physical drive object ....
(similar to user land \\PhysicalDriveX). If I create an Inf with the
PnP id of the usb drive and set the filter driver to be an Upper
filter then I think this would layer the filter on top of the usbstor
created device .. .and would not be part of the disk object stack ...
right ?
So, how would one go about getting a handle to the physical
drive .. ? Does the filter have to be a disk class upper filter ? Tag: Virtual Audio Device Tag: 95098
Standby-Sleep Problem
Hi All,
Im implementing a USB driver based on usbsamp sample provided in KMDF.
I have implemented D0Entry and D0Exit for handling PnP and Power
Management.
I performed following sequence of steps:
1) Installed the driver.
2) Made the system to enter into Standy / Sleep state.
3) Un-Plugged the device.
4) Pressed the power button to resume back.
After resume i see the crash and here is the log of it. I dont see any
calls from my driver.
I would like to know if this is the expected behaviour.
or
Do i need to handle additional power settings to avoid crash.
All your suggestions are appreciable.
Thank You.
Regards,
James
*** Fatal System Error: 0x0000007e
(0xC0000005,0xF8661371,0xF89489B0,0xF89486AC)
Break instruction exception - code 80000003 (first chance)
A fatal system error has occurred.
Debugger entered on first try; Bugcheck callbacks have not been
invoked.
A fatal system error has occurred.
Connected to Windows XP 2600 x86 compatible target, ptr64 FALSE
Loading Kernel Symbols
.............................................................................................................
Loading User Symbols
Loading unloaded module list
.............
*******************************************************************************
*
*
* Bugcheck
Analysis *
*
*
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 7E, {c0000005, f8661371, f89489b0, f89486ac}
Probably caused by : Wdf01000.sys ( Wdf01000!FxPkgFdo::RaiseDevicePower
+50 )
Followup: MachineOwner
---------
nt!RtlpBreakWithStatusInstruction:
80526da8 cc int 3
kd> !analyze -v
*******************************************************************************
*
*
* Bugcheck
Analysis *
*
*
*******************************************************************************
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e)
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.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: f8661371, The address that the exception occurred at
Arg3: f89489b0, Exception Record Address
Arg4: f89486ac, 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:
usbhub!USBH_SetPowerD0+d3
f8661371 8908 mov dword ptr [eax],ecx
EXCEPTION_RECORD: f89489b0 -- (.exr 0xfffffffff89489b0)
ExceptionAddress: f8661371 (usbhub!USBH_SetPowerD0+0x000000d3)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000001
Parameter[1]: 00000107
Attempt to write to address 00000107
CONTEXT: f89486ac -- (.cxr 0xfffffffff89486ac)
eax=00000107 ebx=82721c7c ecx=825fdbbc edx=825fdbbc esi=825fd948
edi=81e92a28
eip=f8661371 esp=f8948a78 ebp=f8948a90 iopl=0 nv up ei pl nz
ac po cy
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000
efl=00010213
usbhub!USBH_SetPowerD0+0xd3:
f8661371 8908 mov dword ptr [eax],ecx ds:
0023:00000107=????????
Resetting default scope
PROCESS_NAME: System
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx"
referenced memory at "0x%08lx". The memory could not be "%s".
WRITE_ADDRESS: 00000107
BUGCHECK_STR: 0x7E
DEFAULT_BUCKET_ID: NULL_CLASS_PTR_DEREFERENCE
LAST_CONTROL_TRANSFER: from f86614b2 to f8661371
STACK_TEXT:
f8948a90 f86614b2 81e54008 00000100 81e92a28 usbhub!
USBH_SetPowerD0+0xd3
f8948aac f8661727 81e92a28 81e54008 81e54008 usbhub!USBH_PdoSetPower
+0x80
f8948acc f865997b 81e540c0 81e54008 00000002 usbhub!USBH_PdoPower
+0x201
f8948aec f86571d8 81e92a28 81e54008 f8948b20 usbhub!USBH_PdoDispatch
+0x83
f8948afc 804eddf9 81e92970 81e54008 81e540c0 usbhub!USBH_HubDispatch
+0x48
f8948b0c 8052222b 81e540c0 81e54008 00000000 nt!IopfCallDriver+0x31
f8948b20 80522745 81e540c0 81e54008 81e540dc nt!PopPresentIrp+0x57
f8948b40 aa4a069c 81e92970 81e92b58 81e83128 nt!PoCallDriver+0x195
f8948b60 aa4a0763 f8948ba0 aa4b3790 81e540e4 Wdf01000!
FxPkgFdo::RaiseDevicePower+0x50
f8948b74 aa4a0798 81e540e4 f8948ba4 aa4940d6 Wdf01000!
FxPkgFdo::DispatchDeviceSetPower+0xb6
f8948b80 aa4940d6 81e83128 f8948ba0 00000000 Wdf01000!
FxPkgFdo::_DispatchSetPower+0x23
f8948ba4 aa47dd9a 81e54008 f8948bcc aa47df9f Wdf01000!
FxPkgPnp::Dispatch+0x26e
f8948bb0 aa47df9f 81e86420 81e54008 80558ce8 Wdf01000!
FxDevice::Dispatch+0x7f
f8948bcc 804eddf9 81e86420 81e54008 81e540e4 Wdf01000!
FxDevice::DispatchWithLock+0x5d
f8948bdc 8052222b 81e540e4 81e54008 00000000 nt!IopfCallDriver+0x31
f8948bf0 80522745 81e540e4 81e54008 81e54108 nt!PopPresentIrp+0x57
f8948c10 805228b5 81e86420 81e864f0 00000000 nt!PoCallDriver+0x195
f8948c2c aa49f43f 81e86420 00000002 00000001 nt!PoRequestPowerIrp
+0x129
f8948c68 aa49fb06 00000001 00000001 f8948cf0 Wdf01000!
FxPkgPnp::PowerPolicySendDevicePowerRequest+0x4d
f8948c78 aa49e592 81e83128 aa4b49c8 81e83128 Wdf01000!
FxPkgPnp::PowerPolSystemWakeDeviceWakeTriggeredS0+0x11
f8948cf0 aa49f07d 0000052d 81e8329c 81e83128 Wdf01000!
FxPkgPnp::PowerPolicyEnterNewState+0x169
f8948d18 aa49f394 f8948d48 806d06e0 81e83290 Wdf01000!
FxPkgPnp::PowerPolicyProcessEventInner+0x20b
f8948d2c aa49ff34 81e83128 f8948d48 81e85b58 Wdf01000!
FxPkgPnp::_PowerPolicyProcessEventInner+0x26
f8948d58 aa49ffdc f8948d74 8056abd5 81e86420 Wdf01000!
FxEventQueue::EventQueueWorker+0x47
f8948d60 8056abd5 81e86420 81e83290 8055a1fc Wdf01000!
FxThreadedEventQueue::_WorkItemCallback+0xd
f8948d74 80533dd0 81e85b58 00000000 82bc8640 nt!IopProcessWorkItem
+0x13
f8948dac 805c4a28 81e85b58 00000000 00000000 nt!ExpWorkerThread+0x100
f8948ddc 80540fa2 80533cd0 00000001 00000000 nt!PspSystemThreadStartup
+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16
FOLLOWUP_IP:
Wdf01000!FxPkgFdo::RaiseDevicePower+50
aa4a069c 5f pop edi
SYMBOL_STACK_INDEX: 8
SYMBOL_NAME: Wdf01000!FxPkgFdo::RaiseDevicePower+50
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: Wdf01000
IMAGE_NAME: Wdf01000.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4549b23a
STACK_COMMAND: .cxr 0xfffffffff89486ac ; kb
FAILURE_BUCKET_ID: 0x7E_Wdf01000!FxPkgFdo::RaiseDevicePower+50
BUCKET_ID: 0x7E_Wdf01000!FxPkgFdo::RaiseDevicePower+50
Followup: MachineOwner
--------- Tag: Virtual Audio Device Tag: 95093
Standby-Sleep Problem
Hi All,
Im implementing a USB driver based on usbsamp sample provided in KMDF.
I have implemented D0Entry and D0Exit for handling PnP and Power
Management.
I performed following sequence of steps:
1) Installed the driver.
2) Made the system to enter into Standy / Sleep state.
3) Un-Plugged the device.
4) Pressed the power button to resume back.
After resume i see the crash and here is the log of it. I dont see any
calls from my driver.
I would like to know if this is the expected behaviour.
or
Do i need to handle additional power settings to avoid crash.
All your suggestions are appreciable.
Thank You.
Regards,
James
*** Fatal System Error: 0x0000007e
(0xC0000005,0xF8661371,0xF89489B0,0xF89486AC)
Break instruction exception - code 80000003 (first chance)
A fatal system error has occurred.
Debugger entered on first try; Bugcheck callbacks have not been
invoked.
A fatal system error has occurred.
Connected to Windows XP 2600 x86 compatible target, ptr64 FALSE
Loading Kernel Symbols
.............................................................................................................
Loading User Symbols
Loading unloaded module list
.............
*******************************************************************************
*
*
* Bugcheck
Analysis *
*
*
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 7E, {c0000005, f8661371, f89489b0, f89486ac}
Probably caused by : Wdf01000.sys ( Wdf01000!FxPkgFdo::RaiseDevicePower
+50 )
Followup: MachineOwner
---------
nt!RtlpBreakWithStatusInstruction:
80526da8 cc int 3
kd> !analyze -v
*******************************************************************************
*
*
* Bugcheck
Analysis *
*
*
*******************************************************************************
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e)
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.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: f8661371, The address that the exception occurred at
Arg3: f89489b0, Exception Record Address
Arg4: f89486ac, 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:
usbhub!USBH_SetPowerD0+d3
f8661371 8908 mov dword ptr [eax],ecx
EXCEPTION_RECORD: f89489b0 -- (.exr 0xfffffffff89489b0)
ExceptionAddress: f8661371 (usbhub!USBH_SetPowerD0+0x000000d3)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000001
Parameter[1]: 00000107
Attempt to write to address 00000107
CONTEXT: f89486ac -- (.cxr 0xfffffffff89486ac)
eax=00000107 ebx=82721c7c ecx=825fdbbc edx=825fdbbc esi=825fd948
edi=81e92a28
eip=f8661371 esp=f8948a78 ebp=f8948a90 iopl=0 nv up ei pl nz
ac po cy
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000
efl=00010213
usbhub!USBH_SetPowerD0+0xd3:
f8661371 8908 mov dword ptr [eax],ecx ds:
0023:00000107=????????
Resetting default scope
PROCESS_NAME: System
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx"
referenced memory at "0x%08lx". The memory could not be "%s".
WRITE_ADDRESS: 00000107
BUGCHECK_STR: 0x7E
DEFAULT_BUCKET_ID: NULL_CLASS_PTR_DEREFERENCE
LAST_CONTROL_TRANSFER: from f86614b2 to f8661371
STACK_TEXT:
f8948a90 f86614b2 81e54008 00000100 81e92a28 usbhub!
USBH_SetPowerD0+0xd3
f8948aac f8661727 81e92a28 81e54008 81e54008 usbhub!USBH_PdoSetPower
+0x80
f8948acc f865997b 81e540c0 81e54008 00000002 usbhub!USBH_PdoPower
+0x201
f8948aec f86571d8 81e92a28 81e54008 f8948b20 usbhub!USBH_PdoDispatch
+0x83
f8948afc 804eddf9 81e92970 81e54008 81e540c0 usbhub!USBH_HubDispatch
+0x48
f8948b0c 8052222b 81e540c0 81e54008 00000000 nt!IopfCallDriver+0x31
f8948b20 80522745 81e540c0 81e54008 81e540dc nt!PopPresentIrp+0x57
f8948b40 aa4a069c 81e92970 81e92b58 81e83128 nt!PoCallDriver+0x195
f8948b60 aa4a0763 f8948ba0 aa4b3790 81e540e4 Wdf01000!
FxPkgFdo::RaiseDevicePower+0x50
f8948b74 aa4a0798 81e540e4 f8948ba4 aa4940d6 Wdf01000!
FxPkgFdo::DispatchDeviceSetPower+0xb6
f8948b80 aa4940d6 81e83128 f8948ba0 00000000 Wdf01000!
FxPkgFdo::_DispatchSetPower+0x23
f8948ba4 aa47dd9a 81e54008 f8948bcc aa47df9f Wdf01000!
FxPkgPnp::Dispatch+0x26e
f8948bb0 aa47df9f 81e86420 81e54008 80558ce8 Wdf01000!
FxDevice::Dispatch+0x7f
f8948bcc 804eddf9 81e86420 81e54008 81e540e4 Wdf01000!
FxDevice::DispatchWithLock+0x5d
f8948bdc 8052222b 81e540e4 81e54008 00000000 nt!IopfCallDriver+0x31
f8948bf0 80522745 81e540e4 81e54008 81e54108 nt!PopPresentIrp+0x57
f8948c10 805228b5 81e86420 81e864f0 00000000 nt!PoCallDriver+0x195
f8948c2c aa49f43f 81e86420 00000002 00000001 nt!PoRequestPowerIrp
+0x129
f8948c68 aa49fb06 00000001 00000001 f8948cf0 Wdf01000!
FxPkgPnp::PowerPolicySendDevicePowerRequest+0x4d
f8948c78 aa49e592 81e83128 aa4b49c8 81e83128 Wdf01000!
FxPkgPnp::PowerPolSystemWakeDeviceWakeTriggeredS0+0x11
f8948cf0 aa49f07d 0000052d 81e8329c 81e83128 Wdf01000!
FxPkgPnp::PowerPolicyEnterNewState+0x169
f8948d18 aa49f394 f8948d48 806d06e0 81e83290 Wdf01000!
FxPkgPnp::PowerPolicyProcessEventInner+0x20b
f8948d2c aa49ff34 81e83128 f8948d48 81e85b58 Wdf01000!
FxPkgPnp::_PowerPolicyProcessEventInner+0x26
f8948d58 aa49ffdc f8948d74 8056abd5 81e86420 Wdf01000!
FxEventQueue::EventQueueWorker+0x47
f8948d60 8056abd5 81e86420 81e83290 8055a1fc Wdf01000!
FxThreadedEventQueue::_WorkItemCallback+0xd
f8948d74 80533dd0 81e85b58 00000000 82bc8640 nt!IopProcessWorkItem
+0x13
f8948dac 805c4a28 81e85b58 00000000 00000000 nt!ExpWorkerThread+0x100
f8948ddc 80540fa2 80533cd0 00000001 00000000 nt!PspSystemThreadStartup
+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16
FOLLOWUP_IP:
Wdf01000!FxPkgFdo::RaiseDevicePower+50
aa4a069c 5f pop edi
SYMBOL_STACK_INDEX: 8
SYMBOL_NAME: Wdf01000!FxPkgFdo::RaiseDevicePower+50
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: Wdf01000
IMAGE_NAME: Wdf01000.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4549b23a
STACK_COMMAND: .cxr 0xfffffffff89486ac ; kb
FAILURE_BUCKET_ID: 0x7E_Wdf01000!FxPkgFdo::RaiseDevicePower+50
BUCKET_ID: 0x7E_Wdf01000!FxPkgFdo::RaiseDevicePower+50
Followup: MachineOwner
--------- Tag: Virtual Audio Device Tag: 95092
Standby-Sleep State Problem
Hi All,
Im implementing a USB driver based on usbsamp sample provided in KMDF.
I have implemented D0Entry and D0Exit for handling PnP and Power
Management.
I performed following sequence of steps:
1) Installed the driver.
2) Made the system to enter into Standy / Sleep state.
3) Un-Plugged the device.
4) Pressed the power button to resume back.
After resume i see the crash and here is the log of it. I dont see any
calls from my driver.
I would like to know if this is the expected behaviour.
or
Do i need to handle additional power settings to avoid crash.
All your suggestions are appreciable.
Thank You.
Regards,
James
*** Fatal System Error: 0x0000007e
(0xC0000005,0xF8661371,0xF89489B0,0xF89486AC)
Break instruction exception - code 80000003 (first chance)
A fatal system error has occurred.
Debugger entered on first try; Bugcheck callbacks have not been
invoked.
A fatal system error has occurred.
Connected to Windows XP 2600 x86 compatible target, ptr64 FALSE
Loading Kernel Symbols
.............................................................................................................
Loading User Symbols
Loading unloaded module list
.............
*******************************************************************************
*
*
* Bugcheck
Analysis *
*
*
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 7E, {c0000005, f8661371, f89489b0, f89486ac}
Probably caused by : Wdf01000.sys ( Wdf01000!FxPkgFdo::RaiseDevicePower
+50 )
Followup: MachineOwner
---------
nt!RtlpBreakWithStatusInstruction:
80526da8 cc int 3
kd> !analyze -v
*******************************************************************************
*
*
* Bugcheck
Analysis *
*
*
*******************************************************************************
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e)
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.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: f8661371, The address that the exception occurred at
Arg3: f89489b0, Exception Record Address
Arg4: f89486ac, 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:
usbhub!USBH_SetPowerD0+d3
f8661371 8908 mov dword ptr [eax],ecx
EXCEPTION_RECORD: f89489b0 -- (.exr 0xfffffffff89489b0)
ExceptionAddress: f8661371 (usbhub!USBH_SetPowerD0+0x000000d3)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000001
Parameter[1]: 00000107
Attempt to write to address 00000107
CONTEXT: f89486ac -- (.cxr 0xfffffffff89486ac)
eax=00000107 ebx=82721c7c ecx=825fdbbc edx=825fdbbc esi=825fd948
edi=81e92a28
eip=f8661371 esp=f8948a78 ebp=f8948a90 iopl=0 nv up ei pl nz
ac po cy
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000
efl=00010213
usbhub!USBH_SetPowerD0+0xd3:
f8661371 8908 mov dword ptr [eax],ecx ds:
0023:00000107=????????
Resetting default scope
PROCESS_NAME: System
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx"
referenced memory at "0x%08lx". The memory could not be "%s".
WRITE_ADDRESS: 00000107
BUGCHECK_STR: 0x7E
DEFAULT_BUCKET_ID: NULL_CLASS_PTR_DEREFERENCE
LAST_CONTROL_TRANSFER: from f86614b2 to f8661371
STACK_TEXT:
f8948a90 f86614b2 81e54008 00000100 81e92a28 usbhub!
USBH_SetPowerD0+0xd3
f8948aac f8661727 81e92a28 81e54008 81e54008 usbhub!USBH_PdoSetPower
+0x80
f8948acc f865997b 81e540c0 81e54008 00000002 usbhub!USBH_PdoPower
+0x201
f8948aec f86571d8 81e92a28 81e54008 f8948b20 usbhub!USBH_PdoDispatch
+0x83
f8948afc 804eddf9 81e92970 81e54008 81e540c0 usbhub!USBH_HubDispatch
+0x48
f8948b0c 8052222b 81e540c0 81e54008 00000000 nt!IopfCallDriver+0x31
f8948b20 80522745 81e540c0 81e54008 81e540dc nt!PopPresentIrp+0x57
f8948b40 aa4a069c 81e92970 81e92b58 81e83128 nt!PoCallDriver+0x195
f8948b60 aa4a0763 f8948ba0 aa4b3790 81e540e4 Wdf01000!
FxPkgFdo::RaiseDevicePower+0x50
f8948b74 aa4a0798 81e540e4 f8948ba4 aa4940d6 Wdf01000!
FxPkgFdo::DispatchDeviceSetPower+0xb6
f8948b80 aa4940d6 81e83128 f8948ba0 00000000 Wdf01000!
FxPkgFdo::_DispatchSetPower+0x23
f8948ba4 aa47dd9a 81e54008 f8948bcc aa47df9f Wdf01000!
FxPkgPnp::Dispatch+0x26e
f8948bb0 aa47df9f 81e86420 81e54008 80558ce8 Wdf01000!
FxDevice::Dispatch+0x7f
f8948bcc 804eddf9 81e86420 81e54008 81e540e4 Wdf01000!
FxDevice::DispatchWithLock+0x5d
f8948bdc 8052222b 81e540e4 81e54008 00000000 nt!IopfCallDriver+0x31
f8948bf0 80522745 81e540e4 81e54008 81e54108 nt!PopPresentIrp+0x57
f8948c10 805228b5 81e86420 81e864f0 00000000 nt!PoCallDriver+0x195
f8948c2c aa49f43f 81e86420 00000002 00000001 nt!PoRequestPowerIrp
+0x129
f8948c68 aa49fb06 00000001 00000001 f8948cf0 Wdf01000!
FxPkgPnp::PowerPolicySendDevicePowerRequest+0x4d
f8948c78 aa49e592 81e83128 aa4b49c8 81e83128 Wdf01000!
FxPkgPnp::PowerPolSystemWakeDeviceWakeTriggeredS0+0x11
f8948cf0 aa49f07d 0000052d 81e8329c 81e83128 Wdf01000!
FxPkgPnp::PowerPolicyEnterNewState+0x169
f8948d18 aa49f394 f8948d48 806d06e0 81e83290 Wdf01000!
FxPkgPnp::PowerPolicyProcessEventInner+0x20b
f8948d2c aa49ff34 81e83128 f8948d48 81e85b58 Wdf01000!
FxPkgPnp::_PowerPolicyProcessEventInner+0x26
f8948d58 aa49ffdc f8948d74 8056abd5 81e86420 Wdf01000!
FxEventQueue::EventQueueWorker+0x47
f8948d60 8056abd5 81e86420 81e83290 8055a1fc Wdf01000!
FxThreadedEventQueue::_WorkItemCallback+0xd
f8948d74 80533dd0 81e85b58 00000000 82bc8640 nt!IopProcessWorkItem
+0x13
f8948dac 805c4a28 81e85b58 00000000 00000000 nt!ExpWorkerThread+0x100
f8948ddc 80540fa2 80533cd0 00000001 00000000 nt!PspSystemThreadStartup
+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16
FOLLOWUP_IP:
Wdf01000!FxPkgFdo::RaiseDevicePower+50
aa4a069c 5f pop edi
SYMBOL_STACK_INDEX: 8
SYMBOL_NAME: Wdf01000!FxPkgFdo::RaiseDevicePower+50
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: Wdf01000
IMAGE_NAME: Wdf01000.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4549b23a
STACK_COMMAND: .cxr 0xfffffffff89486ac ; kb
FAILURE_BUCKET_ID: 0x7E_Wdf01000!FxPkgFdo::RaiseDevicePower+50
BUCKET_ID: 0x7E_Wdf01000!FxPkgFdo::RaiseDevicePower+50
Followup: MachineOwner
--------- Tag: Virtual Audio Device Tag: 95090
Standby-Sleep Problem
Hi All,
Im implementing a USB driver based on usbsamp sample provided in KMDF.
I have implemented D0Entry and D0Exit for handling PnP and Power
Management.
I performed following sequence of steps:
1) Installed the driver.
2) Made the system to enter into Standy / Sleep state.
3) Un-Plugged the device.
4) Pressed the power button to resume back.
After resume i see the crash and here is the log of it. I dont see any
calls from my driver.
I would like to know if this is the expected behaviour.
or
Do i need to handle additional power settings to avoid crash.
All your suggestions are appreciable.
Thank You.
Regards,
James
*** Fatal System Error: 0x0000007e
(0xC0000005,0xF8661371,0xF89489B0,0xF89486AC)
Break instruction exception - code 80000003 (first chance)
A fatal system error has occurred.
Debugger entered on first try; Bugcheck callbacks have not been
invoked.
A fatal system error has occurred.
Connected to Windows XP 2600 x86 compatible target, ptr64 FALSE
Loading Kernel Symbols
.............................................................................................................
Loading User Symbols
Loading unloaded module list
.............
*******************************************************************************
*
*
* Bugcheck
Analysis *
*
*
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 7E, {c0000005, f8661371, f89489b0, f89486ac}
Probably caused by : Wdf01000.sys ( Wdf01000!FxPkgFdo::RaiseDevicePower
+50 )
Followup: MachineOwner
---------
nt!RtlpBreakWithStatusInstruction:
80526da8 cc int 3
kd> !analyze -v
*******************************************************************************
*
*
* Bugcheck
Analysis *
*
*
*******************************************************************************
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e)
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.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: f8661371, The address that the exception occurred at
Arg3: f89489b0, Exception Record Address
Arg4: f89486ac, 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:
usbhub!USBH_SetPowerD0+d3
f8661371 8908 mov dword ptr [eax],ecx
EXCEPTION_RECORD: f89489b0 -- (.exr 0xfffffffff89489b0)
ExceptionAddress: f8661371 (usbhub!USBH_SetPowerD0+0x000000d3)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000001
Parameter[1]: 00000107
Attempt to write to address 00000107
CONTEXT: f89486ac -- (.cxr 0xfffffffff89486ac)
eax=00000107 ebx=82721c7c ecx=825fdbbc edx=825fdbbc esi=825fd948
edi=81e92a28
eip=f8661371 esp=f8948a78 ebp=f8948a90 iopl=0 nv up ei pl nz
ac po cy
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000
efl=00010213
usbhub!USBH_SetPowerD0+0xd3:
f8661371 8908 mov dword ptr [eax],ecx ds:
0023:00000107=????????
Resetting default scope
PROCESS_NAME: System
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx"
referenced memory at "0x%08lx". The memory could not be "%s".
WRITE_ADDRESS: 00000107
BUGCHECK_STR: 0x7E
DEFAULT_BUCKET_ID: NULL_CLASS_PTR_DEREFERENCE
LAST_CONTROL_TRANSFER: from f86614b2 to f8661371
STACK_TEXT:
f8948a90 f86614b2 81e54008 00000100 81e92a28 usbhub!
USBH_SetPowerD0+0xd3
f8948aac f8661727 81e92a28 81e54008 81e54008 usbhub!USBH_PdoSetPower
+0x80
f8948acc f865997b 81e540c0 81e54008 00000002 usbhub!USBH_PdoPower
+0x201
f8948aec f86571d8 81e92a28 81e54008 f8948b20 usbhub!USBH_PdoDispatch
+0x83
f8948afc 804eddf9 81e92970 81e54008 81e540c0 usbhub!USBH_HubDispatch
+0x48
f8948b0c 8052222b 81e540c0 81e54008 00000000 nt!IopfCallDriver+0x31
f8948b20 80522745 81e540c0 81e54008 81e540dc nt!PopPresentIrp+0x57
f8948b40 aa4a069c 81e92970 81e92b58 81e83128 nt!PoCallDriver+0x195
f8948b60 aa4a0763 f8948ba0 aa4b3790 81e540e4 Wdf01000!
FxPkgFdo::RaiseDevicePower+0x50
f8948b74 aa4a0798 81e540e4 f8948ba4 aa4940d6 Wdf01000!
FxPkgFdo::DispatchDeviceSetPower+0xb6
f8948b80 aa4940d6 81e83128 f8948ba0 00000000 Wdf01000!
FxPkgFdo::_DispatchSetPower+0x23
f8948ba4 aa47dd9a 81e54008 f8948bcc aa47df9f Wdf01000!
FxPkgPnp::Dispatch+0x26e
f8948bb0 aa47df9f 81e86420 81e54008 80558ce8 Wdf01000!
FxDevice::Dispatch+0x7f
f8948bcc 804eddf9 81e86420 81e54008 81e540e4 Wdf01000!
FxDevice::DispatchWithLock+0x5d
f8948bdc 8052222b 81e540e4 81e54008 00000000 nt!IopfCallDriver+0x31
f8948bf0 80522745 81e540e4 81e54008 81e54108 nt!PopPresentIrp+0x57
f8948c10 805228b5 81e86420 81e864f0 00000000 nt!PoCallDriver+0x195
f8948c2c aa49f43f 81e86420 00000002 00000001 nt!PoRequestPowerIrp
+0x129
f8948c68 aa49fb06 00000001 00000001 f8948cf0 Wdf01000!
FxPkgPnp::PowerPolicySendDevicePowerRequest+0x4d
f8948c78 aa49e592 81e83128 aa4b49c8 81e83128 Wdf01000!
FxPkgPnp::PowerPolSystemWakeDeviceWakeTriggeredS0+0x11
f8948cf0 aa49f07d 0000052d 81e8329c 81e83128 Wdf01000!
FxPkgPnp::PowerPolicyEnterNewState+0x169
f8948d18 aa49f394 f8948d48 806d06e0 81e83290 Wdf01000!
FxPkgPnp::PowerPolicyProcessEventInner+0x20b
f8948d2c aa49ff34 81e83128 f8948d48 81e85b58 Wdf01000!
FxPkgPnp::_PowerPolicyProcessEventInner+0x26
f8948d58 aa49ffdc f8948d74 8056abd5 81e86420 Wdf01000!
FxEventQueue::EventQueueWorker+0x47
f8948d60 8056abd5 81e86420 81e83290 8055a1fc Wdf01000!
FxThreadedEventQueue::_WorkItemCallback+0xd
f8948d74 80533dd0 81e85b58 00000000 82bc8640 nt!IopProcessWorkItem
+0x13
f8948dac 805c4a28 81e85b58 00000000 00000000 nt!ExpWorkerThread+0x100
f8948ddc 80540fa2 80533cd0 00000001 00000000 nt!PspSystemThreadStartup
+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16
FOLLOWUP_IP:
Wdf01000!FxPkgFdo::RaiseDevicePower+50
aa4a069c 5f pop edi
SYMBOL_STACK_INDEX: 8
SYMBOL_NAME: Wdf01000!FxPkgFdo::RaiseDevicePower+50
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: Wdf01000
IMAGE_NAME: Wdf01000.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4549b23a
STACK_COMMAND: .cxr 0xfffffffff89486ac ; kb
FAILURE_BUCKET_ID: 0x7E_Wdf01000!FxPkgFdo::RaiseDevicePower+50
BUCKET_ID: 0x7E_Wdf01000!FxPkgFdo::RaiseDevicePower+50
Followup: MachineOwner
--------- Tag: Virtual Audio Device Tag: 95078
Standby-Sleep Problem
Hi All,
Im implementing a USB driver based on usbsamp sample provided in KMDF.
I have implemented D0Entry and D0Exit for handling PnP and Power
Management.
I performed following sequence of steps:
1) Installed the driver.
2) Made the system to enter into Standy / Sleep state.
3) Un-Plugged the device.
4) Pressed the power button to resume back.
After resume i see the crash and here is the log of it. I dont see any
calls from my driver.
I would like to know if this is the expected behaviour.
or
Do i need to handle additional power settings to avoid crash.
All your suggestions are appreciable.
Thank You.
Regards,
James
*** Fatal System Error: 0x0000007e
(0xC0000005,0xF8661371,0xF89489B0,0xF89486AC)
Break instruction exception - code 80000003 (first chance)
A fatal system error has occurred.
Debugger entered on first try; Bugcheck callbacks have not been
invoked.
A fatal system error has occurred.
Connected to Windows XP 2600 x86 compatible target, ptr64 FALSE
Loading Kernel Symbols
.............................................................................................................
Loading User Symbols
Loading unloaded module list
.............
*******************************************************************************
*
*
* Bugcheck
Analysis *
*
*
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 7E, {c0000005, f8661371, f89489b0, f89486ac}
Probably caused by : Wdf01000.sys ( Wdf01000!FxPkgFdo::RaiseDevicePower
+50 )
Followup: MachineOwner
---------
nt!RtlpBreakWithStatusInstruction:
80526da8 cc int 3
kd> !analyze -v
*******************************************************************************
*
*
* Bugcheck
Analysis *
*
*
*******************************************************************************
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e)
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.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: f8661371, The address that the exception occurred at
Arg3: f89489b0, Exception Record Address
Arg4: f89486ac, 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:
usbhub!USBH_SetPowerD0+d3
f8661371 8908 mov dword ptr [eax],ecx
EXCEPTION_RECORD: f89489b0 -- (.exr 0xfffffffff89489b0)
ExceptionAddress: f8661371 (usbhub!USBH_SetPowerD0+0x000000d3)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000001
Parameter[1]: 00000107
Attempt to write to address 00000107
CONTEXT: f89486ac -- (.cxr 0xfffffffff89486ac)
eax=00000107 ebx=82721c7c ecx=825fdbbc edx=825fdbbc esi=825fd948
edi=81e92a28
eip=f8661371 esp=f8948a78 ebp=f8948a90 iopl=0 nv up ei pl nz
ac po cy
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000
efl=00010213
usbhub!USBH_SetPowerD0+0xd3:
f8661371 8908 mov dword ptr [eax],ecx ds:
0023:00000107=????????
Resetting default scope
PROCESS_NAME: System
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx"
referenced memory at "0x%08lx". The memory could not be "%s".
WRITE_ADDRESS: 00000107
BUGCHECK_STR: 0x7E
DEFAULT_BUCKET_ID: NULL_CLASS_PTR_DEREFERENCE
LAST_CONTROL_TRANSFER: from f86614b2 to f8661371
STACK_TEXT:
f8948a90 f86614b2 81e54008 00000100 81e92a28 usbhub!
USBH_SetPowerD0+0xd3
f8948aac f8661727 81e92a28 81e54008 81e54008 usbhub!USBH_PdoSetPower
+0x80
f8948acc f865997b 81e540c0 81e54008 00000002 usbhub!USBH_PdoPower
+0x201
f8948aec f86571d8 81e92a28 81e54008 f8948b20 usbhub!USBH_PdoDispatch
+0x83
f8948afc 804eddf9 81e92970 81e54008 81e540c0 usbhub!USBH_HubDispatch
+0x48
f8948b0c 8052222b 81e540c0 81e54008 00000000 nt!IopfCallDriver+0x31
f8948b20 80522745 81e540c0 81e54008 81e540dc nt!PopPresentIrp+0x57
f8948b40 aa4a069c 81e92970 81e92b58 81e83128 nt!PoCallDriver+0x195
f8948b60 aa4a0763 f8948ba0 aa4b3790 81e540e4 Wdf01000!
FxPkgFdo::RaiseDevicePower+0x50
f8948b74 aa4a0798 81e540e4 f8948ba4 aa4940d6 Wdf01000!
FxPkgFdo::DispatchDeviceSetPower+0xb6
f8948b80 aa4940d6 81e83128 f8948ba0 00000000 Wdf01000!
FxPkgFdo::_DispatchSetPower+0x23
f8948ba4 aa47dd9a 81e54008 f8948bcc aa47df9f Wdf01000!
FxPkgPnp::Dispatch+0x26e
f8948bb0 aa47df9f 81e86420 81e54008 80558ce8 Wdf01000!
FxDevice::Dispatch+0x7f
f8948bcc 804eddf9 81e86420 81e54008 81e540e4 Wdf01000!
FxDevice::DispatchWithLock+0x5d
f8948bdc 8052222b 81e540e4 81e54008 00000000 nt!IopfCallDriver+0x31
f8948bf0 80522745 81e540e4 81e54008 81e54108 nt!PopPresentIrp+0x57
f8948c10 805228b5 81e86420 81e864f0 00000000 nt!PoCallDriver+0x195
f8948c2c aa49f43f 81e86420 00000002 00000001 nt!PoRequestPowerIrp
+0x129
f8948c68 aa49fb06 00000001 00000001 f8948cf0 Wdf01000!
FxPkgPnp::PowerPolicySendDevicePowerRequest+0x4d
f8948c78 aa49e592 81e83128 aa4b49c8 81e83128 Wdf01000!
FxPkgPnp::PowerPolSystemWakeDeviceWakeTriggeredS0+0x11
f8948cf0 aa49f07d 0000052d 81e8329c 81e83128 Wdf01000!
FxPkgPnp::PowerPolicyEnterNewState+0x169
f8948d18 aa49f394 f8948d48 806d06e0 81e83290 Wdf01000!
FxPkgPnp::PowerPolicyProcessEventInner+0x20b
f8948d2c aa49ff34 81e83128 f8948d48 81e85b58 Wdf01000!
FxPkgPnp::_PowerPolicyProcessEventInner+0x26
f8948d58 aa49ffdc f8948d74 8056abd5 81e86420 Wdf01000!
FxEventQueue::EventQueueWorker+0x47
f8948d60 8056abd5 81e86420 81e83290 8055a1fc Wdf01000!
FxThreadedEventQueue::_WorkItemCallback+0xd
f8948d74 80533dd0 81e85b58 00000000 82bc8640 nt!IopProcessWorkItem
+0x13
f8948dac 805c4a28 81e85b58 00000000 00000000 nt!ExpWorkerThread+0x100
f8948ddc 80540fa2 80533cd0 00000001 00000000 nt!PspSystemThreadStartup
+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16
FOLLOWUP_IP:
Wdf01000!FxPkgFdo::RaiseDevicePower+50
aa4a069c 5f pop edi
SYMBOL_STACK_INDEX: 8
SYMBOL_NAME: Wdf01000!FxPkgFdo::RaiseDevicePower+50
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: Wdf01000
IMAGE_NAME: Wdf01000.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4549b23a
STACK_COMMAND: .cxr 0xfffffffff89486ac ; kb
FAILURE_BUCKET_ID: 0x7E_Wdf01000!FxPkgFdo::RaiseDevicePower+50
BUCKET_ID: 0x7E_Wdf01000!FxPkgFdo::RaiseDevicePower+50
Followup: MachineOwner
--------- Tag: Virtual Audio Device Tag: 95077
Standby-Sleep State Problem
Hi All,
Im implementing a USB driver based on usbsamp sample provided in KMDF.
I have implemented D0Entry and D0Exit for handling PnP and Power
Management.
I performed following sequence of steps:
1) Installed the driver.
2) Made the system to enter into Standy / Sleep state.
3) Un-Plugged the device.
4) Pressed the power button to resume back.
After resume i see the crash and here is the log of it. I dont see any
calls from my driver.
I would like to know if this is the expected behaviour.
or
Do i need to handle additional power settings to avoid crash.
All your suggestions are appreciable.
Thank You.
Regards,
James
*** Fatal System Error: 0x0000007e
(0xC0000005,0xF8661371,0xF89489B0,0xF89486AC)
Break instruction exception - code 80000003 (first chance)
A fatal system error has occurred.
Debugger entered on first try; Bugcheck callbacks have not been
invoked.
A fatal system error has occurred.
Connected to Windows XP 2600 x86 compatible target, ptr64 FALSE
Loading Kernel Symbols
.............................................................................................................
Loading User Symbols
Loading unloaded module list
.............
*******************************************************************************
*
*
* Bugcheck
Analysis *
*
*
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 7E, {c0000005, f8661371, f89489b0, f89486ac}
Probably caused by : Wdf01000.sys ( Wdf01000!FxPkgFdo::RaiseDevicePower
+50 )
Followup: MachineOwner
---------
nt!RtlpBreakWithStatusInstruction:
80526da8 cc int 3
kd> !analyze -v
*******************************************************************************
*
*
* Bugcheck
Analysis *
*
*
*******************************************************************************
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e)
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.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: f8661371, The address that the exception occurred at
Arg3: f89489b0, Exception Record Address
Arg4: f89486ac, 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:
usbhub!USBH_SetPowerD0+d3
f8661371 8908 mov dword ptr [eax],ecx
EXCEPTION_RECORD: f89489b0 -- (.exr 0xfffffffff89489b0)
ExceptionAddress: f8661371 (usbhub!USBH_SetPowerD0+0x000000d3)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000001
Parameter[1]: 00000107
Attempt to write to address 00000107
CONTEXT: f89486ac -- (.cxr 0xfffffffff89486ac)
eax=00000107 ebx=82721c7c ecx=825fdbbc edx=825fdbbc esi=825fd948
edi=81e92a28
eip=f8661371 esp=f8948a78 ebp=f8948a90 iopl=0 nv up ei pl nz
ac po cy
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000
efl=00010213
usbhub!USBH_SetPowerD0+0xd3:
f8661371 8908 mov dword ptr [eax],ecx ds:
0023:00000107=????????
Resetting default scope
PROCESS_NAME: System
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx"
referenced memory at "0x%08lx". The memory could not be "%s".
WRITE_ADDRESS: 00000107
BUGCHECK_STR: 0x7E
DEFAULT_BUCKET_ID: NULL_CLASS_PTR_DEREFERENCE
LAST_CONTROL_TRANSFER: from f86614b2 to f8661371
STACK_TEXT:
f8948a90 f86614b2 81e54008 00000100 81e92a28 usbhub!
USBH_SetPowerD0+0xd3
f8948aac f8661727 81e92a28 81e54008 81e54008 usbhub!USBH_PdoSetPower
+0x80
f8948acc f865997b 81e540c0 81e54008 00000002 usbhub!USBH_PdoPower
+0x201
f8948aec f86571d8 81e92a28 81e54008 f8948b20 usbhub!USBH_PdoDispatch
+0x83
f8948afc 804eddf9 81e92970 81e54008 81e540c0 usbhub!USBH_HubDispatch
+0x48
f8948b0c 8052222b 81e540c0 81e54008 00000000 nt!IopfCallDriver+0x31
f8948b20 80522745 81e540c0 81e54008 81e540dc nt!PopPresentIrp+0x57
f8948b40 aa4a069c 81e92970 81e92b58 81e83128 nt!PoCallDriver+0x195
f8948b60 aa4a0763 f8948ba0 aa4b3790 81e540e4 Wdf01000!
FxPkgFdo::RaiseDevicePower+0x50
f8948b74 aa4a0798 81e540e4 f8948ba4 aa4940d6 Wdf01000!
FxPkgFdo::DispatchDeviceSetPower+0xb6
f8948b80 aa4940d6 81e83128 f8948ba0 00000000 Wdf01000!
FxPkgFdo::_DispatchSetPower+0x23
f8948ba4 aa47dd9a 81e54008 f8948bcc aa47df9f Wdf01000!
FxPkgPnp::Dispatch+0x26e
f8948bb0 aa47df9f 81e86420 81e54008 80558ce8 Wdf01000!
FxDevice::Dispatch+0x7f
f8948bcc 804eddf9 81e86420 81e54008 81e540e4 Wdf01000!
FxDevice::DispatchWithLock+0x5d
f8948bdc 8052222b 81e540e4 81e54008 00000000 nt!IopfCallDriver+0x31
f8948bf0 80522745 81e540e4 81e54008 81e54108 nt!PopPresentIrp+0x57
f8948c10 805228b5 81e86420 81e864f0 00000000 nt!PoCallDriver+0x195
f8948c2c aa49f43f 81e86420 00000002 00000001 nt!PoRequestPowerIrp
+0x129
f8948c68 aa49fb06 00000001 00000001 f8948cf0 Wdf01000!
FxPkgPnp::PowerPolicySendDevicePowerRequest+0x4d
f8948c78 aa49e592 81e83128 aa4b49c8 81e83128 Wdf01000!
FxPkgPnp::PowerPolSystemWakeDeviceWakeTriggeredS0+0x11
f8948cf0 aa49f07d 0000052d 81e8329c 81e83128 Wdf01000!
FxPkgPnp::PowerPolicyEnterNewState+0x169
f8948d18 aa49f394 f8948d48 806d06e0 81e83290 Wdf01000!
FxPkgPnp::PowerPolicyProcessEventInner+0x20b
f8948d2c aa49ff34 81e83128 f8948d48 81e85b58 Wdf01000!
FxPkgPnp::_PowerPolicyProcessEventInner+0x26
f8948d58 aa49ffdc f8948d74 8056abd5 81e86420 Wdf01000!
FxEventQueue::EventQueueWorker+0x47
f8948d60 8056abd5 81e86420 81e83290 8055a1fc Wdf01000!
FxThreadedEventQueue::_WorkItemCallback+0xd
f8948d74 80533dd0 81e85b58 00000000 82bc8640 nt!IopProcessWorkItem
+0x13
f8948dac 805c4a28 81e85b58 00000000 00000000 nt!ExpWorkerThread+0x100
f8948ddc 80540fa2 80533cd0 00000001 00000000 nt!PspSystemThreadStartup
+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16
FOLLOWUP_IP:
Wdf01000!FxPkgFdo::RaiseDevicePower+50
aa4a069c 5f pop edi
SYMBOL_STACK_INDEX: 8
SYMBOL_NAME: Wdf01000!FxPkgFdo::RaiseDevicePower+50
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: Wdf01000
IMAGE_NAME: Wdf01000.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4549b23a
STACK_COMMAND: .cxr 0xfffffffff89486ac ; kb
FAILURE_BUCKET_ID: 0x7E_Wdf01000!FxPkgFdo::RaiseDevicePower+50
BUCKET_ID: 0x7E_Wdf01000!FxPkgFdo::RaiseDevicePower+50
Followup: MachineOwner
--------- Tag: Virtual Audio Device Tag: 95076
resource files
Is resource file compulsory for my driver to be built?
Are entries in the resource files are part of the image ie,.sys files.
can I change the entries in reource file after building the driver so that I
can have different entries at different times(basically without building the
driver again).
with the same driver code if I need to build my driver with two product Names:
1.ABC
2.QWE Tag: Virtual Audio Device Tag: 95063
WinDbg Messages
Hello All,
I am using Serial Debugging through WinDbg.
I did the following to set the boot parameters:
1. First i used the command, bcdedit /copy {current} /d "My
DebugEntry". Then rebooted the machine and selected the new boot entry
"My DebugEntry".
2. Then i turned on the debug mode by bcdedit /debug ON.
3. Then used the command, bcdedit /dbgsettings serial debugport:1
baudrate:115200. Then rebooted the machine and used the debugged
enabled boot entry.
After reboot when i login the machine, i get all the below messages in
WinDBG and these messages appear continuously.
How can i eliminate these messages? Do i need to use any other
settings?
Thank You.
Regards,
Sushma
d:\vistartm\base\win32\fusion\sxs\nodefactory.cpp(1615): Entered
CNodeFactory::CreateNode
d:\vistartm\base\win32\fusion\sxs\nodefactory.cpp(1615): [function
CNodeFactory::CreateNode 32bit process csrss.exe tid 0xab4] COM Error
0x00000000 (The operation completed successfully. )
d:\vistartm\base\win32\fusion\sxs\nodefactory.cpp(1276): Entered
CNodeFactory::EndChildren
d:\vistartm\base\win32\fusion\sxs\nodefactory.cpp(1276): [function
CNodeFactory::EndChildren 32bit process csrss.exe tid 0xab4] COM Error
0x00000000 (The operation completed successfully. )
d:\vistartm\base\win32\fusion\sxs\nodefactory.cpp(1615): Entered
CNodeFactory::CreateNode
d:\vistartm\base\win32\fusion\sxs\nodefactory.cpp(1615): [function
CNodeFactory::CreateNode 32bit process csrss.exe tid 0xab4] COM Error
0x00000000 (The operation completed successfully. )
d:\vistartm\base\win32\fusion\sxs\nodefactory.cpp(1615): Entered
CNodeFactory::CreateNode
d:\vistartm\base\win32\fusion\sxs\nodefactory.cpp(1615): [function
CNodeFactory::CreateNode 32bit process csrss.exe tid 0xab4] COM Error
0x00000000 (The operation completed successfully. )
d:\vistartm\base\win32\fusion\sxs\nodefactory.cpp(1615): Entered
CNodeFactory::CreateNode
d:\vistartm\base\win32\fusion\sxs\nodefactory.cpp(1615): [function
CNodeFactory::CreateNode 32bit process csrss.exe tid 0xab4] COM Error
0x00000000 (The operation completed successfully. )
d:\vistartm\base\win32\fusion\sxs\nodefactory.cpp(1615): Entered
CNodeFactory::CreateNode
d:\vistartm\base\win32\fusion\utils\xmlns.cpp(52): Entered
CXMLNamespaceManager::OnCreateNode
d:\vistartm\base\win32\fusion\utils\xmlns.cpp(52): [function
CXMLNamespaceManager::OnCreateNode 32bit process csrss.exe tid 0xab4]
COM Error 0x00000000 (The operation completed successfully. )
d:\vistartm\base\win32\fusion\sxs\nodefactory.cpp(1162): Entered
CNodeFactory::ConvertXMLNodeInfoToSXSNodeInfo
d:\vistartm\base\win32\fusion\utils\xmlns.cpp(197): Entered
CXMLNamespaceManager::Map
d:\vistartm\base\win32\fusion\inc\fusionbuffer.h(202): Entered
CGenericBaseStringBuffer<class CUnicodeCharTraits>::Win32Assign
d:\vistartm\base\win32\fusion\inc\fusionbuffer.h(202): Successfully
exiting CGenericBaseStringBuffer<class
CUnicodeCharTraits>::Win32Assign
d:\vistartm\base\win32\fusion\utils\xmlns.cpp(197): [function
CXMLNamespaceManager::Map 32bit process csrss.exe tid 0xab4] COM Error
0x00000000 (The operation completed successfully. )
d:\vistartm\base\win32\fusion\sxs\nodefactory.cpp(1162): [function
CNodeFactory::ConvertXMLNodeInfoToSXSNodeInfo 32bit process csrss.exe
tid 0xab4] COM Error 0x00000000 (The operation completed
successfully. )
d:\vistartm\base\win32\fusion\sxs\nodefactory.cpp(1162): Entered
CNodeFactory::ConvertXMLNodeInfoToSXSNodeInfo
d:\vistartm\base\win32\fusion\utils\xmlns.cpp(197): Entered
CXMLNamespaceManager::Map
d:\vistartm\base\win32\fusion\utils\xmlns.cpp(197): [function
CXMLNamespaceManager::Map 32bit process csrss.exe tid 0xab4] COM Error
0x00000000 (The operation completed successfully. )
d:\vistartm\base\win32\fusion\sxs\nodefactory.cpp(1162): [function
CNodeFactory::ConvertXMLNodeInfoToSXSNodeInfo 32bit process csrss.exe
tid 0xab4] COM Error 0x00000000 (The operation completed
successfully. )
d:\vistartm\base\win32\fusion\sxs\nodefactory.cpp(1162): Entered
CNodeFactory::ConvertXMLNodeInfoToSXSNodeInfo
d:\vistartm\base\win32\fusion\inc\fusionbuffer.h(566): Entered
CGenericBaseStringBuffer<class CUnicodeCharTraits>::Clear
d:\vistartm\base\win32\fusion\inc\fusionbuffer.h(566): Exited
CGenericBaseStringBuffer<class CUnicodeCharTraits>::Clear
d:\vistartm\base\win32\fusion\sxs\nodefactory.cpp(1162): [function
CNodeFactory::ConvertXMLNodeInfoToSXSNodeInfo 32bit process csrss.exe
tid 0xab4] COM Error 0x00000000 (The operation completed
successfully. )
d:\vistartm\base\win32\fusion\sxs\nodefactory.cpp(1162): Entered
CNodeFactory::ConvertXMLNodeInfoToSXSNodeInfo Tag: Virtual Audio Device Tag: 95060
WinDbg Messages
Hello All,
I am using Serial Debugging through WinDbg.
I did the following to set the boot parameters:
1. First i used the command, bcdedit /copy {current} /d "My
DebugEntry". Then rebooted the machine and selected the new boot entry
"My DebugEntry".
2. Then i turned on the debug mode by bcdedit /debug ON.
3. Then used the command, bcdedit /dbgsettings serial debugport:1
baudrate:115200. Then rebooted the machine and used the debugged
enabled boot entry.
After reboot when i login the machine, i get all the below messages in
WinDBG and these messages appear continuously.
How can i eliminate these messages? Do i need to use any other
settings?
Thank You.
Regards,
Sushma
d:\vistartm\base\win32\fusion\sxs\nodefactory.cpp(1615): Entered
CNodeFactory::CreateNode
d:\vistartm\base\win32\fusion\sxs\nodefactory.cpp(1615): [function
CNodeFactory::CreateNode 32bit process csrss.exe tid 0xab4] COM Error
0x00000000 (The operation completed successfully. )
d:\vistartm\base\win32\fusion\sxs\nodefactory.cpp(1276): Entered
CNodeFactory::EndChildren
d:\vistartm\base\win32\fusion\sxs\nodefactory.cpp(1276): [function
CNodeFactory::EndChildren 32bit process csrss.exe tid 0xab4] COM Error
0x00000000 (The operation completed successfully. )
d:\vistartm\base\win32\fusion\sxs\nodefactory.cpp(1615): Entered
CNodeFactory::CreateNode
d:\vistartm\base\win32\fusion\sxs\nodefactory.cpp(1615): [function
CNodeFactory::CreateNode 32bit process csrss.exe tid 0xab4] COM Error
0x00000000 (The operation completed successfully. )
d:\vistartm\base\win32\fusion\sxs\nodefactory.cpp(1615): Entered
CNodeFactory::CreateNode
d:\vistartm\base\win32\fusion\sxs\nodefactory.cpp(1615): [function
CNodeFactory::CreateNode 32bit process csrss.exe tid 0xab4] COM Error
0x00000000 (The operation completed successfully. )
d:\vistartm\base\win32\fusion\sxs\nodefactory.cpp(1615): Entered
CNodeFactory::CreateNode
d:\vistartm\base\win32\fusion\sxs\nodefactory.cpp(1615): [function
CNodeFactory::CreateNode 32bit process csrss.exe tid 0xab4] COM Error
0x00000000 (The operation completed successfully. )
d:\vistartm\base\win32\fusion\sxs\nodefactory.cpp(1615): Entered
CNodeFactory::CreateNode
d:\vistartm\base\win32\fusion\utils\xmlns.cpp(52): Entered
CXMLNamespaceManager::OnCreateNode
d:\vistartm\base\win32\fusion\utils\xmlns.cpp(52): [function
CXMLNamespaceManager::OnCreateNode 32bit process csrss.exe tid 0xab4]
COM Error 0x00000000 (The operation completed successfully. )
d:\vistartm\base\win32\fusion\sxs\nodefactory.cpp(1162): Entered
CNodeFactory::ConvertXMLNodeInfoToSXSNodeInfo
d:\vistartm\base\win32\fusion\utils\xmlns.cpp(197): Entered
CXMLNamespaceManager::Map
d:\vistartm\base\win32\fusion\inc\fusionbuffer.h(202): Entered
CGenericBaseStringBuffer<class CUnicodeCharTraits>::Win32Assign
d:\vistartm\base\win32\fusion\inc\fusionbuffer.h(202): Successfully
exiting CGenericBaseStringBuffer<class
CUnicodeCharTraits>::Win32Assign
d:\vistartm\base\win32\fusion\utils\xmlns.cpp(197): [function
CXMLNamespaceManager::Map 32bit process csrss.exe tid 0xab4] COM Error
0x00000000 (The operation completed successfully. )
d:\vistartm\base\win32\fusion\sxs\nodefactory.cpp(1162): [function
CNodeFactory::ConvertXMLNodeInfoToSXSNodeInfo 32bit process csrss.exe
tid 0xab4] COM Error 0x00000000 (The operation completed
successfully. )
d:\vistartm\base\win32\fusion\sxs\nodefactory.cpp(1162): Entered
CNodeFactory::ConvertXMLNodeInfoToSXSNodeInfo
d:\vistartm\base\win32\fusion\utils\xmlns.cpp(197): Entered
CXMLNamespaceManager::Map
d:\vistartm\base\win32\fusion\utils\xmlns.cpp(197): [function
CXMLNamespaceManager::Map 32bit process csrss.exe tid 0xab4] COM Error
0x00000000 (The operation completed successfully. )
d:\vistartm\base\win32\fusion\sxs\nodefactory.cpp(1162): [function
CNodeFactory::ConvertXMLNodeInfoToSXSNodeInfo 32bit process csrss.exe
tid 0xab4] COM Error 0x00000000 (The operation completed
successfully. )
d:\vistartm\base\win32\fusion\sxs\nodefactory.cpp(1162): Entered
CNodeFactory::ConvertXMLNodeInfoToSXSNodeInfo
d:\vistartm\base\win32\fusion\inc\fusionbuffer.h(566): Entered
CGenericBaseStringBuffer<class CUnicodeCharTraits>::Clear
d:\vistartm\base\win32\fusion\inc\fusionbuffer.h(566): Exited
CGenericBaseStringBuffer<class CUnicodeCharTraits>::Clear
d:\vistartm\base\win32\fusion\sxs\nodefactory.cpp(1162): [function
CNodeFactory::ConvertXMLNodeInfoToSXSNodeInfo 32bit process csrss.exe
tid 0xab4] COM Error 0x00000000 (The operation completed
successfully. )
d:\vistartm\base\win32\fusion\sxs\nodefactory.cpp(1162): Entered
CNodeFactory::ConvertXMLNodeInfoToSXSNodeInfo Tag: Virtual Audio Device Tag: 95059
Removing a non-present device driver via devcon
Hi, I'm developing an USB device with dual personality, when connected it
will enumerate with a specific VID/PID and will load its firmware via the
specific associated driver then will re-enumerate with the new firmware and
work with another driver. Of course the former driver will now be a
"non-present" device.
During development I want to use devcon to remove and update the first
device driver that holds the firmware, the hwid is found when use findall
command of the devcon utility but no other commands are working when with a
non-resent device, especially removing :(.
Am I missing something obvious or is not possible to manage non-present
devices via the devcon utility aside from listing them, and if so, is there
any other method to remove/update programmatically the device driver of a
non-present device ?
Best regards and thank you for your answers,
Mircea Ciocan Tag: Virtual Audio Device Tag: 95058
DRIVER_UNLOADED_WITHOUT_CANCELLING_PENDING_OPERATIONS
Hi,
I am writing a usb bus driver. When I connect a camera to our board,
our driver will enumerate the camera thus loading the usbscan.sys. I
was able to communicate with the camera properly. But only if I unplug
the camera, I get the BSOD
'DRIVER_UNLOADED_WITHOUT_CANCELLING_PENDING_OPERATIONS'. Our driver
functionality is to get the irp's from usbscan.sys and queue it before
processing. I checked all my internal queues, all our queues are empty
when this happen. Apart from IRP, our driver didnot hold any other
resource of the usbscan.sys.
Our driver is based on WDM and I am installing it in Windows xp sp2.
Any suggestions will be helpful.
Thanks
Ravi
kd> !analyze -v
*******************************************************************************
* Bugcheck
Analysis *
*******************************************************************************
DRIVER_UNLOADED_WITHOUT_CANCELLING_PENDING_OPERATIONS (ce)
A driver unloaded without cancelling timers, DPCs, worker threads,
etc.
The broken driver's name is displayed on the screen.
Arguments:
Arg1: aa1b2318, memory referenced
Arg2: 00000000, value 0 = read operation, 1 = write operation
Arg3: aa1b2318, If non-zero, the instruction address which referenced
the bad memory
address.
Arg4: 00000000, Mm internal code.
Debugging Details:
------------------
READ_ADDRESS: aa1b2318
FAULTING_IP:
usbscan+318
aa1b2318 ?? ???
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0xCE
LAST_CONTROL_TRANSFER: from f89909fc to aa1b2318
TRAP_FRAME: f8990958 -- (.trap fffffffff8990958)
ErrCode = 00000000
eax=00000000 ebx=00000000 ecx=00000000 edx=00000000 esi=f8ca0008
edi=f8ca01e3
eip=aa1b2318 esp=f89909cc ebp=f89909cc iopl=0 nv up ei pl zr
na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000
efl=00010246
<Unloaded_usbscan.sys>+0x318:
aa1b2318 ?? ???
Resetting default scope
STACK_TEXT:
WARNING: Frame IP not in any known module. Following frames may be
wrong.
f89909c8 f89909fc 804e18ff 00000000 f8ca0008 <Unloaded_usbscan.sys>
+0x318
f89909cc 804e18ff 00000000 f8ca0008 f8980ab0 0xf89909fc
f89909fc a9998f02 f8990bb4 a9983219 f8ce90e0 nt!IopfCompleteRequest
+0xa2
f8990a04 a9983219 f8ce90e0 f8ca0008 00000000 usbbus!CompleteIrp+0x32
[c:\usbbus\usbbustr.c @ 750]
f8990bb4 a997b6f6 f8ce90e0 f8990d38 f9a6d3b8 usbbus!HandleTResult
+0x3629 [c:\usbbus\poll.c @ 1869]
f8990d7c 804e23b5 f9a6d3b8 00000000 823c6640 usbbus!
usbbus_NotificationChangeWorker+0x7b6 [c:\usbbus\poll.c @ 848]
f8990dac 80574128 f9a6d3b8 00000000 00000000 nt!ExpWorkerThread+0xef
f8990ddc 804efc81 804e22f1 00000001 00000000 nt!PspSystemThreadStartup
+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16
FAILED_INSTRUCTION_ADDRESS:
usbscan+318
aa1b2318 ?? ???
FOLLOWUP_IP:
usbscan+318
aa1b2318 ?? ???
SYMBOL_STACK_INDEX: 0
FOLLOWUP_NAME: MachineOwner
SYMBOL_NAME: usbscan+318
MODULE_NAME: usbscan
IMAGE_NAME: usbscan.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 0
STACK_COMMAND: .trap fffffffff8990958 ; kb
FAILURE_BUCKET_ID: 0xCE_BAD_IP_usbscan+318
BUCKET_ID: 0xCE_BAD_IP_usbscan+318
Followup: MachineOwner
--------- Tag: Virtual Audio Device Tag: 95047
What status should I return in my dispatch routine when completing an IRP?
What status should I return in my dispatch routine when completing an
IRP (in my LOWEST LAYER DRIVER)?
The documentation is unclear on that but I have 2 choices (let say
ntStat is my completion status):
1. mark the IRP as pending (IoMarkIrpPending), set my completion
status (ntStat) in Irp->IoStatus.Status, complete the IRP
(IoCompleteRequest) and return status PENDING.
2. set my completion status (ntStat) in Irp->IoStatus.Status, complete
the IRP (IoCompleteRequest) and return ntStat.
In both cases the upper layer completion routine will get invoked but
in case #2, the upper driver will get status different than pending
which will indicate that access to the IRP is allowed (the
documentation only states that access is not allowed if pending is
returned so any other status implies that I am allowed to access the
IRP, correct?). wouldn't that cause a crash?
Most of the upper layer drivers check for status pending and than they
wait on the async. event, which is signaled by the IoCompletion
routine, and they do not do that if the status is not pending. This
somehow implies that the IoCompletion routine is not called (the event
is not signaled), correct?
I am currently voting for #1 any other thoughts?
Thanks a lot,
Bobby Marinov Tag: Virtual Audio Device Tag: 95045
Devices power down on IRP_MN_STOP_DEVICE?
According to the The KMDF docs:
"The PnP Manager Redistributes System Resources.
If a user adds a device to a system, and if the device requires system
resources that the PnP manager has already assigned to another device, the
PnP manager attempts to reassign resources.
During this process, the PnP manager stops devices and takes them out of
their working (D0) states. It then delivers new resource lists to the devices
so that they can restart, using the new resources."
I forced STOP_DEVICE on a (non KMDF) driver using the "PNP Driver Test
Tool", and I don't see any power IRPs, or any changes in the power state.
Is this a Docerr? Is it completely wrong, or the framework (but not the PNP
manager) power downs the device automatically on receival of
IRP_MN_STOP_DEVICE? Tag: Virtual Audio Device Tag: 95044
Force update function driver
Hi,
Is it possible to forcefully update the function driver whenever the
bus driver is updated.
--
Vijairaj Tag: Virtual Audio Device Tag: 95028
Hi
When do we need to implement a virtual audio driver, why we just use
specific audio class driver , is there some good sample code included in DDK ?