BIOS update. (Code 35) on Windows 7 64bit

NTDEV
1

I am working on a WDF driver which works with several PCI cards. I have been testing it on an XP system with two PCI cards installed, and things seem to be working okay. I then put another disk in the computer and installed Windows 7 64 bit so that I could test that OS. What I am finding is that one of the PCI cards works fine, the other gives an error in device manager “Your computer’s system firmware does not include enough information
to properly configure and use this device. To use this device, contact
your computer manufacturer to obtain a firmware or BIOS update. (Code 35)” From the driver standpoint, the EvtDiviceAdd routine is called, however the EvtPrepareHardware is not called. What is going on here? Is Windows 7 requiring something different from Windows XP?

2

That means your device was enumerated but the id could not find enough resources for it or the device is misreporting something

d

Bent from my phone

From: xxxxx@verizon.netmailto:xxxxx
Sent: ?2/?19/?2013 3:29 PM
To: Windows System Software Devs Interest Listmailto:xxxxx
Subject: [ntdev] BIOS update. (Code 35) on Windows 7 64bit

I am working on a WDF driver which works with several PCI cards. I have been testing it on an XP system with two PCI cards installed, and things seem to be working okay. I then put another disk in the computer and installed Windows 7 64 bit so that I could test that OS. What I am finding is that one of the PCI cards works fine, the other gives an error in device manager “Your computer’s system firmware does not include enough information
to properly configure and use this device. To use this device, contact
your computer manufacturer to obtain a firmware or BIOS update. (Code 35)” From the driver standpoint, the EvtDiviceAdd routine is called, however the EvtPrepareHardware is not called. What is going on here? Is Windows 7 requiring something different from Windows XP?

—
NTDEV is sponsored by OSR

OSR is HIRING!! See http://www.osr.com/careers

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</mailto:xxxxx></mailto:xxxxx>

3

Doron, As this is the same hardware, only the OS is different, it seems to imply that Windows 7 64 bit is looking for something different than XP. Does this make sense? Is there a way to see what the OS is not happy about? Do 32 bit and 64 bit windows require different things from a PCI card?

4

It might if they’re PCIe cards. I know you said “PCI” but many folks (including me) use that term to mean “PCI family, including PCI, PCI-X, and PCIe.”

Well, you can check to see what the devices are reporting.

In WinDbg do “!PCI 2 f” to see a list of all the devices on the system… get the bus and slot number, than do “!PCI 101 ” to see the device config space and capabilities.

If your device isn’t listed, you can force a dump of invalid headers/config/capabilities… see the !PCI debugger extension for more info.

Peter
OSR

5

Try win7 32 bit to rule out 32 vs 64 bit issues as well

d

Bent from my phone

From: xxxxx@verizon.netmailto:xxxxx
Sent: ?2/?20/?2013 5:26 AM
To: Windows System Software Devs Interest Listmailto:xxxxx
Subject: RE:[ntdev] BIOS update. (Code 35) on Windows 7 64bit

Doron, As this is the same hardware, only the OS is different, it seems to imply that Windows 7 64 bit is looking for something different than XP. Does this make sense? Is there a way to see what the OS is not happy about? Do 32 bit and 64 bit windows require different things from a PCI card?

—
NTDEV is sponsored by OSR

OSR is HIRING!! See http://www.osr.com/careers

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</mailto:xxxxx></mailto:xxxxx>

6

I managed to get some information from windbg. unfortunately it does not mean much to me. I am pasting it below. Following it, it the same dumps from running XP. I can see differences, but it still does not indicate to me the exact problem. I plan to get another test machine, but it may take a week or two until I can make that happen.

0: kd> !PCI 101 5 1

PCI Configuration Space (Segment:0000 Bus:05 Device:01 Function:00)
Common Header:
00: VendorID 1093 National Instruments
02: DeviceID 1340
04: Command ffff IOSpaceEn MemSpaceEn BusInitiate SpecialCycle MemWriteEn VGASnoop PERREn WaitCycle SERREn FB2BEn InterruptDis
06: Status ffff INTPending CapList 66MHzCapable UDFSupported FB2BCapable DataPERR TargetDevAbort TargetAbort InitiatorAbort SERR PERR DEVSELTiming:3
08: RevisionID ff
09: ProgIF ff Unknown
0a: SubClass ff Unknown
0b: BaseClass ff Unknown
0c: CacheLineSize 0008 Burst4DW
0d: LatencyTimer 08
0e: HeaderType 00
0f: BIST 00
10: BAR0 7f9ff000
14: BAR1 7f9fe000
18: BAR2 00000000
1c: BAR3 00000000
20: BAR4 00000000
24: BAR5 00000000
28: CBCISPtr 00000000
2c: SubSysVenID 0000
2e: SubSysID 0000
30: ROMBAR 00000000
34: CapPtr 00
3c: IntLine 03
3d: IntPin 01
3e: MinGnt 00
3f: MaxLat 00
Device Private:
40: 0000acac 00000000 ffffffff 00000000
50: 00000000 00000000 00000000 00000000
60: 00000000 00000000 00000000 00000000
70: 00000000 00000000 00000000 00000000
80: 00000000 00000000 00000000 00000000
90: 00000000 00000000 00000000 00000000
a0: 00000000 00000000 00000000 00000000
b0: 00000000 00000000 00000000 00000000
c0: 00000000 00000000 00000000 00000000
d0: 00000000 00000000 00000000 00000000
e0: 00000000 00000000 00000000 00000000
f0: 00000000 00000000 00000000 00000000
0: kd> !drvobj sgrwdf
Driver object (fffffa80038df670) is for:
\Driver\SGRWDF
Driver Extension List: (id , addr)
(fffff88000efb8bc fffffa800388a800)
Device Object list:
fffffa8003900c70 fffffa80038fde20

0: kd> !devnode 0xfffffa8002da86e0 6
DevNode 0xfffffa8002da86e0 for PDO 0xfffffa8002db1060
Parent 0xfffffa8002d8ab10 Sibling 0xfffffa8002daa6e0 Child 0000000000
InstancePath is “PCI\VEN_1093&DEV_1340&SUBSYS_00000000&REV_00\4&e6d76c4&0&08F0”
ServiceName is “SGRWDF”
State = DeviceNodeDriversAdded (0x303)
Previous State = DeviceNodeInitialized (0x302)
StateHistory[01] = DeviceNodeInitialized (0x302)
StateHistory[00] = DeviceNodeUninitialized (0x301)
StateHistory[19] = Unknown State (0x0)
StateHistory[18] = Unknown State (0x0)
StateHistory[17] = Unknown State (0x0)
StateHistory[16] = Unknown State (0x0)
StateHistory[15] = Unknown State (0x0)
StateHistory[14] = Unknown State (0x0)
StateHistory[13] = Unknown State (0x0)
StateHistory[12] = Unknown State (0x0)
StateHistory[11] = Unknown State (0x0)
StateHistory[10] = Unknown State (0x0)
StateHistory[09] = Unknown State (0x0)
StateHistory[08] = Unknown State (0x0)
StateHistory[07] = Unknown State (0x0)
StateHistory[06] = Unknown State (0x0)
StateHistory[05] = Unknown State (0x0)
StateHistory[04] = Unknown State (0x0)
StateHistory[03] = Unknown State (0x0)
StateHistory[02] = Unknown State (0x0)
Flags (0x6c0020f0) DNF_ENUMERATED, DNF_IDS_QUERIED,
DNF_HAS_BOOT_CONFIG, DNF_BOOT_CONFIG_RESERVED,
DNF_HAS_PROBLEM, DNF_NO_LOWER_DEVICE_FILTERS,
DNF_NO_LOWER_CLASS_FILTERS, DNF_NO_UPPER_DEVICE_FILTERS,
DNF_NO_UPPER_CLASS_FILTERS
Problem = CM_PROB_BIOS_TABLE

BootResourcesList at 0xfffff8a000262010 Version 1.1 Interface 0x5 Bus #0x5
Entry 0 - Memory (0x3) Device Exclusive (0x1)
Flags (0x80) -
Range starts at 0x000000007f9ff000 for 0x1000 bytes
Entry 1 - Memory (0x3) Device Exclusive (0x1)
Flags (0x80) -
Range starts at 0x000000007f9fe000 for 0x1000 bytes
Entry 2 - Interrupt (0x2) Shared (0x3)
Flags (0000) - LEVEL_SENSITIVE
Level 0x3, Vector 0x3, Group 38, Affinity 0xffffffff

IoResList at 0xfffff8a000262230 : Interface 0x5 Bus 0x5 Slot 0x1
Alternative 0 (Version 1.1)
Preferred Descriptor 0 - Memory (0x3) Device Exclusive (0x1)
Flags (0x80) -
0x001000 byte range with alignment 0x000001
7f9ff000 - 0x7f9fffff
Alternative Descriptor 1 - Memory (0x3) Device Exclusive (0x1)
Flags (0x80) -
0x001000 byte range with alignment 0x001000
0 - 0x7fffffff
Descriptor 2 - DevicePrivate (0x81) Device Exclusive (0x1)
Flags (0000) -
Data: : 0x1 0x0 0x0
Preferred Descriptor 3 - Memory (0x3) Device Exclusive (0x1)
Flags (0x80) -
0x001000 byte range with alignment 0x000001
7f9fe000 - 0x7f9fefff
Alternative Descriptor 4 - Memory (0x3) Device Exclusive (0x1)
Flags (0x80) -
0x001000 byte range with alignment 0x001000
0 - 0x7fffffff
Descriptor 5 - DevicePrivate (0x81) Device Exclusive (0x1)
Flags (0000) -
Data: : 0x1 0x1 0x0
Descriptor 6 - Interrupt (0x2) Shared (0x3)
Flags (0000) - LEVEL_SENSITIVE
0x0 - 0xffffffff

The same dumps from Windows XP (the above are from Windows 7 64 bit)

0: kd> !pci 101 5 1

PCI Configuration Space (Segment:0000 Bus:05 Device:01 Function:00)
Common Header:
00: VendorID 1093 National Instruments
02: DeviceID 1340
04: Command ffff IOSpaceEn MemSpaceEn BusInitiate SpecialCycle MemWriteEn VGASnoop PERREn WaitCycle SERREn FB2BEn InterruptDis
06: Status ffff INTPending CapList 66MHzCapable UDFSupported FB2BCapable DataPERR TargetDevAbort TargetAbort InitiatorAbort SERR PERR DEVSELTiming:3
08: RevisionID ff
09: ProgIF ff Unknown
0a: SubClass ff Unknown
0b: BaseClass ff Unknown
0c: CacheLineSize 0008 Burst4DW
0d: LatencyTimer 08
0e: HeaderType 00
0f: BIST 00
10: BAR0 000df000
14: BAR1 000de000
18: BAR2 00000000
1c: BAR3 00000000
20: BAR4 00000000
24: BAR5 00000000
28: CBCISPtr 00000000
2c: SubSysVenID 0000
2e: SubSysID 0000
30: ROMBAR 00000000
34: CapPtr 00
3c: IntLine 16
3d: IntPin 01
3e: MinGnt 00
3f: MaxLat 00
Device Private:
40: 0000acac 00000000 ffffffff 00000000
50: 00000000 00000000 00000000 00000000
60: 00000000 00000000 00000000 00000000
70: 00000000 00000000 00000000 00000000
80: 00000000 00000000 00000000 00000000
90: 00000000 00000000 00000000 00000000
a0: 00000000 00000000 00000000 00000000
b0: 00000000 00000000 00000000 00000000
c0: 00000000 00000000 00000000 00000000
d0: 00000000 00000000 00000000 00000000
e0: 00000000 00000000 00000000 00000000
f0: 00000000 00000000 00000000 00000000

0: kd> !devnode 0x8abf96b0 6
DevNode 0x8abf96b0 for PDO 0x8abf9c88
Parent 0x8ab67d70 Sibling 0x8abf9590 Child 0000000000
InstancePath is “PCI\VEN_1093&DEV_1340&SUBSYS_00000000&REV_FF\4&1faf5ea3&0&08F0”
ServiceName is “SGRWDF”
State = DeviceNodeStarted (0x308)
Previous State = DeviceNodeEnumerateCompletion (0x30d)
StateHistory[07] = DeviceNodeEnumerateCompletion (0x30d)
StateHistory[06] = DeviceNodeStarted (0x308)
StateHistory[05] = DeviceNodeStartPostWork (0x307)
StateHistory[04] = DeviceNodeStartCompletion (0x306)
StateHistory[03] = DeviceNodeResourcesAssigned (0x304)
StateHistory[02] = DeviceNodeDriversAdded (0x303)
StateHistory[01] = DeviceNodeInitialized (0x302)
StateHistory[00] = DeviceNodeUninitialized (0x301)
StateHistory[19] = Unknown State (0x0)
StateHistory[18] = Unknown State (0x0)
StateHistory[17] = Unknown State (0x0)
StateHistory[16] = Unknown State (0x0)
StateHistory[15] = Unknown State (0x0)
StateHistory[14] = Unknown State (0x0)
StateHistory[13] = Unknown State (0x0)
StateHistory[12] = Unknown State (0x0)
StateHistory[11] = Unknown State (0x0)
StateHistory[10] = Unknown State (0x0)
StateHistory[09] = Unknown State (0x0)
StateHistory[08] = Unknown State (0x0)
Flags (0x000000f0) DNF_ENUMERATED, DNF_IDS_QUERIED,
DNF_HAS_BOOT_CONFIG, DNF_BOOT_CONFIG_RESERVED
CmResourceList at 0xe197abc8 Version 0.0 Interface 0x5 Bus #0x5
Entry 0 - Memory (0x3) Device Exclusive (0x1)
Flags (0000) - READ_WRITE
Range starts at 0x00000000000df000 for 0x1000 bytes
Entry 1 - DevicePrivate (0x81) Device Exclusive (0x1)
Flags (0000) -
Data - {0x00000001, 0000000000, 0000000000}
Entry 2 - Memory (0x3) Device Exclusive (0x1)
Flags (0000) - READ_WRITE
Range starts at 0x00000000000de000 for 0x1000 bytes
Entry 3 - DevicePrivate (0x81) Device Exclusive (0x1)
Flags (0000) -
Data - {0x00000001, 0x00000001, 0000000000}
Entry 4 - Interrupt (0x2) Shared (0x3)
Flags (0000) - LEVEL_SENSITIVE
Level 0x16, Vector 0x16, Group 0, Affinity 0xffffffff

BootResourcesList at 0xe17b81d8 Version 1.1 Interface 0x5 Bus #0x5
Entry 0 - Memory (0x3) Undetermined Sharing (0)
Flags (0000) - READ_WRITE
Range starts at 0x000000007f9ff000 for 0x1000 bytes
Entry 1 - Memory (0x3) Undetermined Sharing (0)
Flags (0000) - READ_WRITE
Range starts at 0x000000007f9fe000 for 0x1000 bytes
Entry 2 - Interrupt (0x2) Shared (0x3)
Flags (0000) - LEVEL_SENSITIVE
Level 0x3, Vector 0x3, Group 0, Affinity 0xffffffff

IoResList at 0xe17b9448 : Interface 0x5 Bus 0x5 Slot 0x1
Alternative 0 (Version 1.1)
Preferred Descriptor 0 - Memory (0x3) Device Exclusive (0x1)
Flags (0000) - READ_WRITE
0x001000 byte range with alignment 0x000001
7f9ff000 - 0x7f9fffff
Alternative Descriptor 1 - Memory (0x3) Device Exclusive (0x1)
Flags (0000) - READ_WRITE
0x001000 byte range with alignment 0x001000
0 - 0x7fffffff
Descriptor 2 - DevicePrivate (0x81) Device Exclusive (0x1)
Flags (0000) -
Data: : 0x1 0x0 0x0
Preferred Descriptor 3 - Memory (0x3) Device Exclusive (0x1)
Flags (0000) - READ_WRITE
0x001000 byte range with alignment 0x000001
7f9fe000 - 0x7f9fefff
Alternative Descriptor 4 - Memory (0x3) Device Exclusive (0x1)
Flags (0000) - READ_WRITE
0x001000 byte range with alignment 0x001000
0 - 0x7fffffff
Descriptor 5 - DevicePrivate (0x81) Device Exclusive (0x1)
Flags (0000) -
Data: : 0x1 0x1 0x0
Descriptor 6 - Interrupt (0x2) Shared (0x3)
Flags (0000) - LEVEL_SENSITIVE
0x0 - 0xff

7

xxxxx@verizon.net wrote:

I managed to get some information from windbg. unfortunately it does not mean much to me. I am pasting it below. Following it, it the same dumps from running XP. I can see differences, but it still does not indicate to me the exact problem. I plan to get another test machine, but it may take a week or two until I can make that happen.

How much physical memory is in this box? In both cases, the BIOS
assigned the following physical addresses to your BARs:

10: BAR0 7f9ff000
14: BAR1 7f9fe000

Windows XP has overridden those with addresses in the low megabyte:

10: BAR0 000df000
14: BAR1 000de000

Does your BIOS have a setting for “Plug-and-Play operating system”? Is
it possible you have it set to “false”?

Odd that it couldn’t read the command/status or revision/class words.
Is it possible your hardware has some very long initialization sequence?

–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.

8

(nice find, Mr. Roberts)

THAT is freakin’ cool. I’ve NEVER seen that before.

Is the Revision Number allowed to be oxFF?? I didn’t think it was…

Is this one particular device exhibiting this behavior, OP? Perhaps it’s toasted? Have you tried a different physical device?

Peter
OSR

9

The box has 4GB of memory

The Bios does have a setting for “Plug-and-Play Operating system” which was off, however I turned it on before I started this thread. At the time, I thought it would fix the problem but it did not. I guess I should double check that it took.

This card is known to have defects, however it was working well enough for driver testing (at least under XP). I have used other cards under XP but have not had the chance to try another one under Win 7. My company is still using XP and I have to work a bit to get Win 7 boxes for testing.

I did notice the Revision at 0xff, however the hardware id reports REV_00

The box is fairly old. If this looks abnormal to you guys, perhaps I should not get too concerned until I can test on another box and card.

10

Well, I’ll tell you: That looks mighty funky to me. Note it reports 0xFF as the revision number on BOTH systems.

Why not grab another device of the same vid/did and throw it in whatever system you have around (XP, Win7, whatever) and see if IT also reports Rev 0xFF, and messed-up command and status registers.

Something is off…

Peter
OSR

11

xxxxx@osr.com wrote:

(nice find, Mr. Roberts)

THAT is freakin’ cool. I’ve NEVER seen that before.

Is the Revision Number allowed to be oxFF?? I didn’t think it was…

Yes, it’s valid. In USB, revision ID is a BCD value, so the hex digits
must be 0 through 9, but the PCI spec simply says it is a “vendor
defined extension to the Device ID”.

–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.

12

xxxxx@verizon.net wrote:

The box has 4GB of memory

Hmm, then it is unusual that the BARs were assigned just below the 2GB
boundary. In a box with 4GB of RAM, the BIOS will usually create the
PCI hole just below the 4GB boundary, meaning 0xFFxxxxxx, not
0x7Fxxxxxx. Does the BIOS actually acknowledge 4GB RAM?

The box is fairly old. If this looks abnormal to you guys, perhaps I should not get too concerned until I can test on another box and card.

It’s very hard to say. PCI chipsets have certainly improved over time,
but unless this is from the 20th Century, I’d be hard-pressed to blame
the motherboard.

–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.

13

>0x7Fxxxxxx. Does the BIOS actually acknowledge 4GB RAM?
The Bios reports “available” RAM as 3GB XP shows 2.93 GB Win 7 shows 4GB, 3GB “available”
I have looked for bios settings that might change this, but found nothing.

Why not grab another device of the same vid/did and throw it in whatever system you have around >(XP, Win7, whatever) and see if IT also reports Rev 0xFF, and messed-up command and status >registers.

I did this and the results below look much more correct. It is now looking to me like an issue with the card and / or test box. With luck I can get another test box next week and put this to bed.

0: kd> !pci 101 3 d

PCI Configuration Space (Segment:0000 Bus:03 Device:0d Function:00)
Common Header:
00: VendorID 1093 National Instruments
02: DeviceID 1340
04: Command 0010 MemWriteEn
06: Status 0280 FB2BCapable DEVSELTiming:1
08: RevisionID 00
09: ProgIF 00
0a: SubClass 00
0b: BaseClass ff
0c: CacheLineSize 0008 Burst4DW
0d: LatencyTimer 08
0e: HeaderType 00
0f: BIST 00
10: BAR0 febff000
14: BAR1 febfe000
18: BAR2 00000000
1c: BAR3 00000000
20: BAR4 00000000
24: BAR5 00000000
28: CBCISPtr 00000000
2c: SubSysVenID 0000
2e: SubSysID 0000
30: ROMBAR 00000000
34: CapPtr 00
3c: IntLine 13
3d: IntPin 01
3e: MinGnt 00
3f: MaxLat 00
Device Private:
40: 0000acac 00000000 80000000 00000000
50: 00000000 00000000 00000000 00000000
60: 00000000 00000000 00000000 00000000
70: 00000000 00000000 00000000 00000000
80: 00000000 00000000 00000000 00000000
90: 00000000 00000000 00000000 00000000
a0: 00000000 00000000 00000000 00000000
b0: 00000000 00000000 00000000 00000000
c0: 00000000 00000000 00000000 00000000
d0: 00000000 00000000 00000000 00000000
e0: 00000000 00000000 00000000 00000000
f0: 00000000 00000000 00000000 00000000

14

Whew! That’s a relief… The results look reasonable now. Note the REV field is now 0x00, as might be expected… not 0xFF (which, while evidently legal would be both unusual and unwise in the extreme), and the Command and Status fields now make sense as well.

Yup. You have a toasted card. Or a toasted host machine. Or both.

Peter
OSR

15

Thanks for all your help. This is about the only place I have found to get intelligent answers to questions!

16

I came late to this thread so my contribution might be completely irrelevant to this problem, but I seem to recall the OP talking about this being tested on older hardware so I thought it might apply:

There is a limitation in some older intel architectures that prevents you from seeing more than 3GB of ram even tho the motherboard has slots for 2 2GB sticks and the OS will show you that you have it.

I know this because my late 2006 macbook (core2) only supports 3G of ram. I installed 2 2G sticks because 3G of ram is 50% more than 2G of RAM and you cant buy 1.5 G sticks.

-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of xxxxx@verizon.net
Sent: Friday, February 22, 2013 6:03 AM
To: Windows System Software Devs Interest List
Subject: RE:[ntdev] BIOS update. (Code 35) on Windows 7 64bit

0x7Fxxxxxx. Does the BIOS actually acknowledge 4GB RAM?
The Bios reports “available” RAM as 3GB XP shows 2.93 GB Win 7 shows 4GB, 3GB “available”
I have looked for bios settings that might change this, but found nothing.

Why not grab another device of the same vid/did and throw it in whatever system you have around >(XP, Win7, whatever) and see if IT also reports Rev 0xFF, and messed-up command and status >registers.

I did this and the results below look much more correct. It is now looking to me like an issue with the card and / or test box. With luck I can get another test box next week and put this to bed.

0: kd> !pci 101 3 d

PCI Configuration Space (Segment:0000 Bus:03 Device:0d Function:00) Common Header:
00: VendorID 1093 National Instruments
02: DeviceID 1340
04: Command 0010 MemWriteEn
06: Status 0280 FB2BCapable DEVSELTiming:1
08: RevisionID 00
09: ProgIF 00
0a: SubClass 00
0b: BaseClass ff
0c: CacheLineSize 0008 Burst4DW
0d: LatencyTimer 08
0e: HeaderType 00
0f: BIST 00
10: BAR0 febff000
14: BAR1 febfe000
18: BAR2 00000000
1c: BAR3 00000000
20: BAR4 00000000
24: BAR5 00000000
28: CBCISPtr 00000000
2c: SubSysVenID 0000
2e: SubSysID 0000
30: ROMBAR 00000000
34: CapPtr 00
3c: IntLine 13
3d: IntPin 01
3e: MinGnt 00
3f: MaxLat 00
Device Private:
40: 0000acac 00000000 80000000 00000000
50: 00000000 00000000 00000000 00000000
60: 00000000 00000000 00000000 00000000
70: 00000000 00000000 00000000 00000000
80: 00000000 00000000 00000000 00000000
90: 00000000 00000000 00000000 00000000
a0: 00000000 00000000 00000000 00000000
b0: 00000000 00000000 00000000 00000000
c0: 00000000 00000000 00000000 00000000
d0: 00000000 00000000 00000000 00000000
e0: 00000000 00000000 00000000 00000000
f0: 00000000 00000000 00000000 00000000

NTDEV is sponsored by OSR

OSR is HIRING!! See http://www.osr.com/careers

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

17

xxxxx@verizon.net wrote:

I did this and the results below look much more correct. It is now looking to me like an issue with the card and / or test box. With luck I can get another test box next week and put this to bed.

0: kd> !pci 101 3 d

PCI Configuration Space (Segment:0000 Bus:03 Device:0d Function:00)
Common Header:
…
10: BAR0 febff000
14: BAR1 febfe000

THAT’S what I expect!

–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.

18

Just to finally close this thread out, I was able to put a “working” card in the test box and everything is working fine under Win7 64 so it was definitely a toasted PCI card. As to why it behaved differently under XP I do not know (or care at this point).

19

Thanks for closing the discussion, Mr. Rodkey. Much appreciated.

Glad we could help bring your mystery to a successful conclusion.

Peter
OSR