Interrupt resource conflict

Hi folks,

Seeing this issue on driver installation ?

This device cannot find enough free resources that it can use. (Code 12)
CM_PROB_NORMAL_CONFLICT.

Any ideas how to figure out what devices/resources would be causing the
conflict?

my windows image does not have the troubleshooting.

Thanks,

Harshada

You’ve connected WinDBg, set breakpoints in your code where you get your resources? Stepped into AddDevice? Stepped in processing of the START IRP? Given it’s your driver, I’d be willing to guess that it’s your driver causing the conflict.

Gary Little
H (952) 223-1349
C (952) 454-4629
xxxxx@comcast.net

On Nov 9, 2011, at 11:12 PM, Harshada wrote:

Hi folks,

Seeing this issue on driver installation ?

This device cannot find enough free resources that it can use. (Code 12) CM_PROB_NORMAL_CONFLICT.

Any ideas how to figure out what devices/resources would be causing the conflict?

my windows image does not have the troubleshooting.

Thanks,

Harshada

— WINDBG is sponsored by OSR For our schedule of WDF, WDM, debugging and other seminars visit: http://www.osr.com/seminars To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer

From the debugger, you can use !arbiter to see conflicting resources (see
the docs for how to interpret the output).

-scott


Scott Noone
Consulting Associate and Chief System Problem Analyst
OSR Open Systems Resources, Inc.
http://www.osronline.com

“Harshada” wrote in message
news:xxxxx@windbg…

Hi folks,

Seeing this issue on driver installation –

This device cannot find enough free resources that it can use. (Code 12)
CM_PROB_NORMAL_CONFLICT.

Any ideas how to figure out what devices/resources would be causing the
conflict?

my windows image does not have the troubleshooting.

Thanks,

Harshada

Windows\inf\setupapi.dev.log can give you some clues.

===============================================

Hi folks,

Seeing this issue on driver installation -

This device cannot find enough free resources that it can use. (Code 12)
CM_PROB_NORMAL_CONFLICT.

Any ideas how to figure out what devices/resources would be causing the
conflict?

my windows image does not have the troubleshooting.

Thanks,

Harshada

— WINDBG is sponsored by OSR For our schedule of WDF, WDM, debugging and
other seminars visit: http://www.osr.com/seminars To unsubscribe, visit the
List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer

where can i find document oh how to use and how to read - !arbiter ?

>where can i find document oh how to use and how to read - !arbiter ?

WinDBG documentation or MSDN:

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

-scott


Scott Noone
Consulting Associate and Chief System Problem Analyst
OSR Open Systems Resources, Inc.
http://www.osronline.com

wrote in message news:xxxxx@windbg…

where can i find document oh how to use and how to read - !arbiter ?

i used !arbiter 4 since i am seeing conflict with interrupt resource. But the list i get doesn’t list the the driver which did not load due to the conflict.

I wouldn’t expect it to show the function driver that didn’t load, that’s
not the purpose. What it should show is the resource in conflict and the
PDOs that are trying to claim it. This will let you see the device that
currently owns the resource you’re trying to claim.

-scott


Scott Noone
Consulting Associate and Chief System Problem Analyst
OSR Open Systems Resources, Inc.
http://www.osronline.com

wrote in message news:xxxxx@windbg…

i used !arbiter 4 since i am seeing conflict with interrupt resource. But
the list i get doesn’t list the the driver which did not load due to the
conflict.