BSOD/Windows see new device

Thanks for the reply John John. I was able to open the pci.txt list but it
was empty.So when I boot up i just go into device manager and uninstall the
device and it seems to be fairly stable until I play a game then I get random
BSOD concerning device drivers

"John John" wrote:

> Go here: http://support.microsoft.com/kb/311272/ and download the right
> devcon utility for your computer (most likely you are on 32-bit
> Windows). Place the Devcon utility in your System32 folder. Open a
> command prompt and issue the following commands, pressing <Enter> after
> each line:
>
> cd\
> devcon find pci\* >pci.txt
>
> After the command runs look in the root folder (most likely C:\) for the
> file pci.txt and see if you can't root out the list to find out what the
> device is. If you are having difficulty identifying the device clean up
> the list from known entries and post the unknowns here and someone may
> be able to tell you what the device is. If, after posting the entries
> here, you really can't find the what the problem device is you can
> always disable the device and see if the symptoms go away.
>
> John
>
>
> CentralCal wrote:
>
> > Hello, I have a fairly new pc that has been working fine until just last week
> > or so. I have a been getting a BSOD that is device driver related AND every
> > time I boot up i get a windows message it has found a NEW PCI device. I have
> > a PCI-E vid card that is working fine and a SoundBlaster audio card that
> > works fine as my only devices. I have went through every single folder on my
> > mobo installation disk to try and install the correct file with no luck. I
> > have updated my BIOS sucessfully but still have this silly error. I took a
> > screenshot:
> > http://i74.photobucket.com/albums/i249/CentralCal/PCIproblem.jpg
> > Any ideas?
>

The list was empty??? Are you sure the command ran properly? Did you
download the correct devcon version? Did you enter the command correctly:

devcon find pci\* >pci.txt

If you didn't put the \* switch in there the list will be empty.

John

CentralCal wrote:

> Thanks for the reply John John. I was able to open the pci.txt list but it
> was empty.So when I boot up i just go into device manager and uninstall the
> device and it seems to be fairly stable until I play a game then I get random
> BSOD concerning device drivers
>
> "John John" wrote:
>
>
>>Go here: http://support.microsoft.com/kb/311272/ and download the right
>>devcon utility for your computer (most likely you are on 32-bit
>>Windows). Place the Devcon utility in your System32 folder. Open a
>>command prompt and issue the following commands, pressing <Enter> after
>>each line:
>>
>>cd\
>>devcon find pci\* >pci.txt
>>
>>After the command runs look in the root folder (most likely C:\) for the
>>file pci.txt and see if you can't root out the list to find out what the
>>device is. If you are having difficulty identifying the device clean up
>>the list from known entries and post the unknowns here and someone may
>>be able to tell you what the device is. If, after posting the entries
>>here, you really can't find the what the problem device is you can
>>always disable the device and see if the symptoms go away.
>>
>>John
>>
>>
>>CentralCal wrote:
>>
>>
>>>Hello, I have a fairly new pc that has been working fine until just last week
>>>or so. I have a been getting a BSOD that is device driver related AND every
>>>time I boot up i get a windows message it has found a NEW PCI device. I have
>>>a PCI-E vid card that is working fine and a SoundBlaster audio card that
>>>works fine as my only devices. I have went through every single folder on my
>>>mobo installation disk to try and install the correct file with no luck. I
>>>have updated my BIOS sucessfully but still have this silly error. I took a
>>>screenshot:
>>>http://i74.photobucket.com/albums/i249/CentralCal/PCIproblem.jpg
>>>Any ideas?
>>

Ok, I unzipped the Devcon file into the C:\windows\system32 folder and when I
type "devcon find pci\* >pci.txt " at the command prompt I am asked if i want
to unzip the file I just unzipped into the Win/system32 folder again....?

"John John" wrote:

> The list was empty??? Are you sure the command ran properly? Did you
> download the correct devcon version? Did you enter the command correctly:
>
> devcon find pci\* >pci.txt
>
> If you didn't put the \* switch in there the list will be empty.
>
> John
>
> CentralCal wrote:
>
> > Thanks for the reply John John. I was able to open the pci.txt list but it
> > was empty.So when I boot up i just go into device manager and uninstall the
> > device and it seems to be fairly stable until I play a game then I get random
> > BSOD concerning device drivers
> >
> > "John John" wrote:
> >
> >
> >>Go here: http://support.microsoft.com/kb/311272/ and download the right
> >>devcon utility for your computer (most likely you are on 32-bit
> >>Windows). Place the Devcon utility in your System32 folder. Open a
> >>command prompt and issue the following commands, pressing <Enter> after
> >>each line:
> >>
> >>cd\
> >>devcon find pci\* >pci.txt
> >>
> >>After the command runs look in the root folder (most likely C:\) for the
> >>file pci.txt and see if you can't root out the list to find out what the
> >>device is. If you are having difficulty identifying the device clean up
> >>the list from known entries and post the unknowns here and someone may
> >>be able to tell you what the device is. If, after posting the entries
> >>here, you really can't find the what the problem device is you can
> >>always disable the device and see if the symptoms go away.
> >>
> >>John
> >>
> >>
> >>CentralCal wrote:
> >>
> >>
> >>>Hello, I have a fairly new pc that has been working fine until just last week
> >>>or so. I have a been getting a BSOD that is device driver related AND every
> >>>time I boot up i get a windows message it has found a NEW PCI device. I have
> >>>a PCI-E vid card that is working fine and a SoundBlaster audio card that
> >>>works fine as my only devices. I have went through every single folder on my
> >>>mobo installation disk to try and install the correct file with no luck. I
> >>>have updated my BIOS sucessfully but still have this silly error. I took a
> >>>screenshot:
> >>>http://i74.photobucket.com/albums/i249/CentralCal/PCIproblem.jpg
> >>>Any ideas?
> >>
>

Here is a jpg of what it looks like:
http://i74.photobucket.com/albums/i249/CentralCal/devcon.jpg

"John John" wrote:

> The list was empty??? Are you sure the command ran properly? Did you
> download the correct devcon version? Did you enter the command correctly:
>
> devcon find pci\* >pci.txt
>
> If you didn't put the \* switch in there the list will be empty.
>
> John
>
> CentralCal wrote:
>
> > Thanks for the reply John John. I was able to open the pci.txt list but it
> > was empty.So when I boot up i just go into device manager and uninstall the
> > device and it seems to be fairly stable until I play a game then I get random
> > BSOD concerning device drivers
> >
> > "John John" wrote:
> >
> >
> >>Go here: http://support.microsoft.com/kb/311272/ and download the right
> >>devcon utility for your computer (most likely you are on 32-bit
> >>Windows). Place the Devcon utility in your System32 folder. Open a
> >>command prompt and issue the following commands, pressing <Enter> after
> >>each line:
> >>
> >>cd\
> >>devcon find pci\* >pci.txt
> >>
> >>After the command runs look in the root folder (most likely C:\) for the
> >>file pci.txt and see if you can't root out the list to find out what the
> >>device is. If you are having difficulty identifying the device clean up
> >>the list from known entries and post the unknowns here and someone may
> >>be able to tell you what the device is. If, after posting the entries
> >>here, you really can't find the what the problem device is you can
> >>always disable the device and see if the symptoms go away.
> >>
> >>John
> >>
> >>
> >>CentralCal wrote:
> >>
> >>
> >>>Hello, I have a fairly new pc that has been working fine until just last week
> >>>or so. I have a been getting a BSOD that is device driver related AND every
> >>>time I boot up i get a windows message it has found a NEW PCI device. I have
> >>>a PCI-E vid card that is working fine and a SoundBlaster audio card that
> >>>works fine as my only devices. I have went through every single folder on my
> >>>mobo installation disk to try and install the correct file with no luck. I
> >>>have updated my BIOS sucessfully but still have this silly error. I took a
> >>>screenshot:
> >>>http://i74.photobucket.com/albums/i249/CentralCal/PCIproblem.jpg
> >>>Any ideas?
> >>
>

Close the Winzip program and look for the file C:\pci.txt. Is the
device list still empty?

John

CentralCal wrote:

> Here is a jpg of what it looks like:
> http://i74.photobucket.com/albums/i249/CentralCal/devcon.jpg
>
> "John John" wrote:
>
>
>>The list was empty??? Are you sure the command ran properly? Did you
>>download the correct devcon version? Did you enter the command correctly:
>>
>>devcon find pci\* >pci.txt
>>
>>If you didn't put the \* switch in there the list will be empty.
>>
>>John
>>
>>CentralCal wrote:
>>
>>
>>>Thanks for the reply John John. I was able to open the pci.txt list but it
>>>was empty.So when I boot up i just go into device manager and uninstall the
>>>device and it seems to be fairly stable until I play a game then I get random
>>>BSOD concerning device drivers
>>>
>>>"John John" wrote:
>>>
>>>
>>>
>>>>Go here: http://support.microsoft.com/kb/311272/ and download the right
>>>>devcon utility for your computer (most likely you are on 32-bit
>>>>Windows). Place the Devcon utility in your System32 folder. Open a
>>>>command prompt and issue the following commands, pressing <Enter> after
>>>>each line:
>>>>
>>>>cd\
>>>>devcon find pci\* >pci.txt
>>>>
>>>>After the command runs look in the root folder (most likely C:\) for the
>>>>file pci.txt and see if you can't root out the list to find out what the
>>>>device is. If you are having difficulty identifying the device clean up
>>>>the list from known entries and post the unknowns here and someone may
>>>>be able to tell you what the device is. If, after posting the entries
>>>>here, you really can't find the what the problem device is you can
>>>>always disable the device and see if the symptoms go away.
>>>>
>>>>John
>>>>
>>>>
>>>>CentralCal wrote:
>>>>
>>>>
>>>>
>>>>>Hello, I have a fairly new pc that has been working fine until just last week
>>>>>or so. I have a been getting a BSOD that is device driver related AND every
>>>>>time I boot up i get a windows message it has found a NEW PCI device. I have
>>>>>a PCI-E vid card that is working fine and a SoundBlaster audio card that
>>>>>works fine as my only devices. I have went through every single folder on my
>>>>>mobo installation disk to try and install the correct file with no luck. I
>>>>>have updated my BIOS sucessfully but still have this silly error. I took a
>>>>>screenshot:
>>>>>http://i74.photobucket.com/albums/i249/CentralCal/PCIproblem.jpg
>>>>>Any ideas?
>>>>

The only pci.txt I can find has 0 kb.

"John John" wrote:

> Close the Winzip program and look for the file C:\pci.txt. Is the
> device list still empty?
>
> John
>
> CentralCal wrote:
>
> > Here is a jpg of what it looks like:
> > http://i74.photobucket.com/albums/i249/CentralCal/devcon.jpg
> >
> > "John John" wrote:
> >
> >
> >>The list was empty??? Are you sure the command ran properly? Did you
> >>download the correct devcon version? Did you enter the command correctly:
> >>
> >>devcon find pci\* >pci.txt
> >>
> >>If you didn't put the \* switch in there the list will be empty.
> >>
> >>John
> >>
> >>CentralCal wrote:
> >>
> >>
> >>>Thanks for the reply John John. I was able to open the pci.txt list but it
> >>>was empty.So when I boot up i just go into device manager and uninstall the
> >>>device and it seems to be fairly stable until I play a game then I get random
> >>>BSOD concerning device drivers
> >>>
> >>>"John John" wrote:
> >>>
> >>>
> >>>
> >>>>Go here: http://support.microsoft.com/kb/311272/ and download the right
> >>>>devcon utility for your computer (most likely you are on 32-bit
> >>>>Windows). Place the Devcon utility in your System32 folder. Open a
> >>>>command prompt and issue the following commands, pressing <Enter> after
> >>>>each line:
> >>>>
> >>>>cd\
> >>>>devcon find pci\* >pci.txt
> >>>>
> >>>>After the command runs look in the root folder (most likely C:\) for the
> >>>>file pci.txt and see if you can't root out the list to find out what the
> >>>>device is. If you are having difficulty identifying the device clean up
> >>>>the list from known entries and post the unknowns here and someone may
> >>>>be able to tell you what the device is. If, after posting the entries
> >>>>here, you really can't find the what the problem device is you can
> >>>>always disable the device and see if the symptoms go away.
> >>>>
> >>>>John
> >>>>
> >>>>
> >>>>CentralCal wrote:
> >>>>
> >>>>
> >>>>
> >>>>>Hello, I have a fairly new pc that has been working fine until just last week
> >>>>>or so. I have a been getting a BSOD that is device driver related AND every
> >>>>>time I boot up i get a windows message it has found a NEW PCI device. I have
> >>>>>a PCI-E vid card that is working fine and a SoundBlaster audio card that
> >>>>>works fine as my only devices. I have went through every single folder on my
> >>>>>mobo installation disk to try and install the correct file with no luck. I
> >>>>>have updated my BIOS sucessfully but still have this silly error. I took a
> >>>>>screenshot:
> >>>>>http://i74.photobucket.com/albums/i249/CentralCal/PCIproblem.jpg
> >>>>>Any ideas?
> >>>>
>

I don't know what the heck is going on here but it looks like the
computer has no pci devices, which is most unlikely! Are you logged on
with Administrative credentials, logged on as an Administrator? Is the
Plug and Play service set to Automatic Start and is it running? Make
sure the service is running and let's try this again just to make sure
we are looking at the right file, try this:

cd\
devcon find pci\* >findpci.txt

Is the findpci.txt file still empty? If yes try this:

cd\
devcon find * >foundhdw.txt

Is the foundhdw.txt file empty?

If you can't get a hardware list with Devcon try using the msinfo32 tool:

Click on Start | Run type msinfo32.exe in the Open box, and then click
OK or press <Enter>.

Look in the Components\Problem Devices section. Right click on the
problem device and save as text file, post the contents of the file here.

John


CentralCal wrote:

> The only pci.txt I can find has 0 kb.
>
> "John John" wrote:
>
>
>>Close the Winzip program and look for the file C:\pci.txt. Is the
>>device list still empty?
>>
>>John
>>
>>CentralCal wrote:
>>
>>
>>>Here is a jpg of what it looks like:
>>>http://i74.photobucket.com/albums/i249/CentralCal/devcon.jpg
>>>
>>>"John John" wrote:
>>>
>>>
>>>
>>>>The list was empty??? Are you sure the command ran properly? Did you
>>>>download the correct devcon version? Did you enter the command correctly:
>>>>
>>>>devcon find pci\* >pci.txt
>>>>
>>>>If you didn't put the \* switch in there the list will be empty.
>>>>
>>>>John
>>>>
>>>>CentralCal wrote:
>>>>
>>>>
>>>>
>>>>>Thanks for the reply John John. I was able to open the pci.txt list but it
>>>>>was empty.So when I boot up i just go into device manager and uninstall the
>>>>>device and it seems to be fairly stable until I play a game then I get random
>>>>>BSOD concerning device drivers
>>>>>
>>>>>"John John" wrote:
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>>Go here: http://support.microsoft.com/kb/311272/ and download the right
>>>>>>devcon utility for your computer (most likely you are on 32-bit
>>>>>>Windows). Place the Devcon utility in your System32 folder. Open a
>>>>>>command prompt and issue the following commands, pressing <Enter> after
>>>>>>each line:
>>>>>>
>>>>>>cd\
>>>>>>devcon find pci\* >pci.txt
>>>>>>
>>>>>>After the command runs look in the root folder (most likely C:\) for the
>>>>>>file pci.txt and see if you can't root out the list to find out what the
>>>>>>device is. If you are having difficulty identifying the device clean up
>>>>>>the list from known entries and post the unknowns here and someone may
>>>>>>be able to tell you what the device is. If, after posting the entries
>>>>>>here, you really can't find the what the problem device is you can
>>>>>>always disable the device and see if the symptoms go away.
>>>>>>
>>>>>>John
>>>>>>
>>>>>>
>>>>>>CentralCal wrote:
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>>Hello, I have a fairly new pc that has been working fine until just last week
>>>>>>>or so. I have a been getting a BSOD that is device driver related AND every
>>>>>>>time I boot up i get a windows message it has found a NEW PCI device. I have
>>>>>>>a PCI-E vid card that is working fine and a SoundBlaster audio card that
>>>>>>>works fine as my only devices. I have went through every single folder on my
>>>>>>>mobo installation disk to try and install the correct file with no luck. I
>>>>>>>have updated my BIOS sucessfully but still have this silly error. I took a
>>>>>>>screenshot:
>>>>>>>http://i74.photobucket.com/albums/i249/CentralCal/PCIproblem.jpg
>>>>>>>Any ideas?
>>>>>>

John John, Both pci.txt and foundhdw.txt were empty but the msinfo32 came up
with the culprit. I took a screenshot of it:
http://i74.photobucket.com/albums/i249/CentralCal/PCIproblem-1.jpg.
AS I was typing this I was looking for any other problems and found this in
the Storage folder of system info:
http://i74.photobucket.com/albums/i249/CentralCal/PCI-IDE.jpg.

"John John" wrote:

> I don't know what the heck is going on here but it looks like the
> computer has no pci devices, which is most unlikely! Are you logged on
> with Administrative credentials, logged on as an Administrator? Is the
> Plug and Play service set to Automatic Start and is it running? Make
> sure the service is running and let's try this again just to make sure
> we are looking at the right file, try this:
>
> cd\
> devcon find pci\* >findpci.txt
>
> Is the findpci.txt file still empty? If yes try this:
>
> cd\
> devcon find * >foundhdw.txt
>
> Is the foundhdw.txt file empty?
>
> If you can't get a hardware list with Devcon try using the msinfo32 tool:
>
> Click on Start | Run type msinfo32.exe in the Open box, and then click
> OK or press <Enter>.
>
> Look in the Components\Problem Devices section. Right click on the
> problem device and save as text file, post the contents of the file here.
>
> John
>
>
> CentralCal wrote:
>
> > The only pci.txt I can find has 0 kb.
> >
> > "John John" wrote:
> >
> >
> >>Close the Winzip program and look for the file C:\pci.txt. Is the
> >>device list still empty?
> >>
> >>John
> >>
> >>CentralCal wrote:
> >>
> >>
> >>>Here is a jpg of what it looks like:
> >>>http://i74.photobucket.com/albums/i249/CentralCal/devcon.jpg
> >>>
> >>>"John John" wrote:
> >>>
> >>>
> >>>
> >>>>The list was empty??? Are you sure the command ran properly? Did you
> >>>>download the correct devcon version? Did you enter the command correctly:
> >>>>
> >>>>devcon find pci\* >pci.txt
> >>>>
> >>>>If you didn't put the \* switch in there the list will be empty.
> >>>>
> >>>>John
> >>>>
> >>>>CentralCal wrote:
> >>>>
> >>>>
> >>>>
> >>>>>Thanks for the reply John John. I was able to open the pci.txt list but it
> >>>>>was empty.So when I boot up i just go into device manager and uninstall the
> >>>>>device and it seems to be fairly stable until I play a game then I get random
> >>>>>BSOD concerning device drivers
> >>>>>
> >>>>>"John John" wrote:
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>>Go here: http://support.microsoft.com/kb/311272/ and download the right
> >>>>>>devcon utility for your computer (most likely you are on 32-bit
> >>>>>>Windows). Place the Devcon utility in your System32 folder. Open a
> >>>>>>command prompt and issue the following commands, pressing <Enter> after
> >>>>>>each line:
> >>>>>>
> >>>>>>cd\
> >>>>>>devcon find pci\* >pci.txt
> >>>>>>
> >>>>>>After the command runs look in the root folder (most likely C:\) for the
> >>>>>>file pci.txt and see if you can't root out the list to find out what the
> >>>>>>device is. If you are having difficulty identifying the device clean up
> >>>>>>the list from known entries and post the unknowns here and someone may
> >>>>>>be able to tell you what the device is. If, after posting the entries
> >>>>>>here, you really can't find the what the problem device is you can
> >>>>>>always disable the device and see if the symptoms go away.
> >>>>>>
> >>>>>>John
> >>>>>>
> >>>>>>
> >>>>>>CentralCal wrote:
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>>Hello, I have a fairly new pc that has been working fine until just last week
> >>>>>>>or so. I have a been getting a BSOD that is device driver related AND every
> >>>>>>>time I boot up i get a windows message it has found a NEW PCI device. I have
> >>>>>>>a PCI-E vid card that is working fine and a SoundBlaster audio card that
> >>>>>>>works fine as my only devices. I have went through every single folder on my
> >>>>>>>mobo installation disk to try and install the correct file with no luck. I
> >>>>>>>have updated my BIOS sucessfully but still have this silly error. I took a
> >>>>>>>screenshot:
> >>>>>>>http://i74.photobucket.com/albums/i249/CentralCal/PCIproblem.jpg
> >>>>>>>Any ideas?
> >>>>>>
>

CentralCal wrote:

> http://i74.photobucket.com/albums/i249/CentralCal/PCIproblem-1.jpg.

Right click on the Problem PCI device in the above screenshot and save
the information in a text file then post the contents of the text file
here. We need the PCI\VEN_ ID sting and number if we are to even
attempt to identify the device. I can't read that on a screen shot and
I wont torture eye to even try to read off the posted image. Post the
information from the text file if you want more help.

John

"John John" wrote:

> CentralCal wrote:
Here is the text file you asked for:
> > http://i74.photobucket.com/albums/i249/CentralCal/PCIproblem-1.jpg.
My mobo is a gigabyte 965p-ds3 v3.3 and im using the native mode sata
controller for my 2 sata hard drives and my sata cd/dvd rom. I have the
latest bios and have installed ALL of the latest mobo drivers.
>
> Right click on the Problem PCI device in the above screenshot and save
> the information in a text file then post the contents of the text file
> here. We need the PCI\VEN_ ID sting and number if we are to even
> attempt to identify the device. I can't read that on a screen shot and
> I wont torture eye to even try to read off the posted image. Post the
> information from the text file if you want more help.
>
> John
> http://i74.photobucket.com/albums/i249/CentralCal/Problemdevice.jpg

CentralCal wrote:

>
> "John John" wrote:
>
>
>>CentralCal wrote:
>
> Here is the text file you asked for:
>
>>>http://i74.photobucket.com/albums/i249/CentralCal/PCIproblem-1.jpg.

I can't read what it says on that picture! I need you to copy the
*exact* PCI/VEN number of the problem device! Right click on the
"Highlighted" (blue text) and save the information of the problem device
to a text file. Then open the .txt file and copy and paste the contents
of the file to your reply. The text file will look something like this:


System Information report written at: 17/06/2007 08:44:37 PM
[Problem Devices]

Device PNP Device ID Error Code
3Com 3C920 Integrated Fast Ethernet Controller (3C905C-TX Compatible)
PCI\VEN_10B7&DEV_9200&SUBSYS_00C71028&REV_78\4&BB7B4AE&0&60F0 22


The above is a phony file that I generated, the information in your file
will be in the same type of format but the information will be
different, it will identify the problem device in your computer.

I repeat, I cannot read the information in a fuzzy .jpg file that you
post on a web site, I need the accurate information in text form so that
I may read it and attempt to identify the device, I cannot identify the
device by looking at screenshots!

John

Thanks for you tenacity John John, it is really appreciated. Here is the text:
PNP Device ID PCI\VEN_8086&DEV_2820&SUBSYS_B0021458&REV_02\3&13C0B0C5&0&FA

In the smaller window there is an error code also, Code#39

"John John" wrote:

> CentralCal wrote:
>
> >
> > "John John" wrote:
> >
> >
> >>CentralCal wrote:
> >
> > Here is the text file you asked for:
> >
> >>>http://i74.photobucket.com/albums/i249/CentralCal/PCIproblem-1.jpg.
>
> I can't read what it says on that picture! I need you to copy the
> *exact* PCI/VEN number of the problem device! Right click on the
> "Highlighted" (blue text) and save the information of the problem device
> to a text file. Then open the .txt file and copy and paste the contents
> of the file to your reply. The text file will look something like this:
>
>
> System Information report written at: 17/06/2007 08:44:37 PM
> [Problem Devices]
>
> Device PNP Device ID Error Code
> 3Com 3C920 Integrated Fast Ethernet Controller (3C905C-TX Compatible)
> PCI\VEN_10B7&DEV_9200&SUBSYS_00C71028&REV_78\4&BB7B4AE&0&60F0 22
>
>
> The above is a phony file that I generated, the information in your file
> will be in the same type of format but the information will be
> different, it will identify the problem device in your computer.
>
> I repeat, I cannot read the information in a fuzzy .jpg file that you
> post on a web site, I need the accurate information in text form so that
> I may read it and attempt to identify the device, I cannot identify the
> device by looking at screenshots!
>
> John
>
>

CentralCal wrote:

> Thanks for you tenacity John John, it is really appreciated. Here is the text:
> PNP Device ID PCI\VEN_8086&DEV_2820&SUBSYS_B0021458&REV_02\3&13C0B0C5&0&FA

PCI\VEN_8086 tells us it's an Intel device (8086 is the Vendor ID)

DEV_2820 is the device id number. It isn't well documanted but from
what I can gather it appears to be ICH8 4 port Serial ATA Storage
Controller (0x2820 is the device ID)

You can look them up here: http://www.pcidatabase.com/index.php

If you search through the Intel page you will find the 0x2820 device
entry: http://www.pcidatabase.com/vendor_details.php?id=1302


> In the smaller window there is an error code also, Code#39

Code 39 means that the drivers for it are corrupt or missing.
http://support.microsoft.com/kb/310123

You mentioned in an earlier post that you also found what appeared to be
a problem in the Storage section of the msinfo32 report, this would seem
to corroborate the SATA Controller identification.

I would suggest that you look again on the motherbord driver CD to see
if there are additional drivers or software for the SATA Storage
Controller. Based on the Motherboard information that you supplied in
an earlier post you can also check here for the SATA Controller
software/drivers here: http://tinyurl.com/2xrsb6 Scroll down for the
full GIGABYTE SATA2 RAID Driver package (3.01MB).

John