Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site. Or read our to learn how to use this site. Resently I was given an old 'Dell Dimension 2400' purchased back in 2003, without the origonal xp disk to reformat or restore.

I didn't care because I have a ' w7 32 bit ' I was planning on putting on it, if it ran well. I cleaned it up, ran all the updates and put more ram in it. It ran great.for two weeks. It has both a cd and dvd drives and has a pentium 4 processor. Now when I boot up it says - windows could not start because the following file is missing or corrupt: system 32 drivers pci.sys - you can attempt to repair this file by starting windows using the original setup cd-rom. Select ' r ' at the first screen to start repair.

Googling I found that this computer has xp partitioned on the hard drive and it came two disks called 'recovery' and 'resource' to be used when you need to repair or want to restore instead of coming with a wxp disk so one could reformat. Does anyone know how I can fix the missing file issue? So far what I have tried is, I bought a ' automatic drivers recovery for dell dimension 2400' disk. It did nothing.

Edited by 82_bleepingirl, 20 August 2013 - 05:07 PM. Restart your computer to run the scan. This has five sections and will take some time. Please don't try to use your computer while this scan is running.

There is a file titled i386 which contains a copy of the pci.sys file that you can overwrite the corrupted one with. You will need to go to Start, then click on Run. Then copy and paste the appropriate command below. If this computer does not have SP3 copy and paste this in the Run box, press Enter copy c: windows system32 dllcache pci.sys c: windows system32 drivers When you are asked if you want to overwrite the existing file respond in the affirmative, you should get the message 1 file(s) was copied. If this computer does have SP3 copy and paste this in the Run box, press Enter copy c: windows ServicePackFiles i386 pci.sys c: windows system32 drivers When you are asked if you want to overwrite the existing file respond in the affirmative, you should get the message 1 file(s) was copied. Edited by dc3, 21 August 2013 - 08:34 AM.

Important: Some malware disguises itself as pci.sys, particularly when not located in the C: Windows System32 drivers folder. Therefore, you should check the pci.sys process on your PC to see if it is a threat. We recommend Security Task Manager for verifying your computer's security. This was one of the Top Download.

Thank you for your reply. I could not get into windows at all.

So this morning I tried installing ubuntu. It went all the way through the process and I thought it had installed. After rebooting, all it would do is use the disk as a live cd. So all it did, as far as I can tell is uninstall xp. But I can use it as I said, as a live cd.any idea how I can get it to actually install ubuntu or another linux? I have several I've burned over time.

Hi, AFAIK you can run the Install program on the desktop of the Live CD to install ubuntu on the HDD.

I recently was having problems with my laptop hard freezing, so I reformatted and reinstalled Windows 7 Home Premium only to have the problem carried over. Now whenever I leave the computer alone to automatically sleep without hitting the power button, the computer will many times black the screen and then lock up and need to have the power button held to shut down (no BSOD or events recorded.) To remedy this I tried to remove the automatic sleep timer and moved to only sleep when I press the power button; it sleeps without lockup about half the time. Whenever the computer DOES sleep, I have it set to hibernate after 2 hours of sleeping. At this point the next time I wake the computer, it tells me that the computer blue screened during that period and now restarts fresh.

I've included a Bluescreenview copy/paste showing some things, but can post a dump if needed. Multiple threads around the web show no obvious solution, has anyone been able to fix this problem before?

Make sure the laptop has newest bios file to see if it a bios bug. Run hdtune read the hard drive smart warnings. With a clean install of the os make sure all off the mb chipset and other drivers were installed and updated. Missing a chipset driver may be the issue. SMART tests are coming back clean. I tried chipset drivers just before I posted this thread, thinking the same thing, but as of today they didn't work.

I also updated the BIOS right after reinstalling Windows. I got the same BSOD warning just as I turned on the computer today. I noticed that Windows Update replaced the chipset driver with a newer one, so I reverted back to the old one and only made small progress. The computer no longer locks up while trying to sleep, however it still will not successfully resume from sleep. Once in sleep mode for longer than 30-60 minutes, when turning on the machine it will just say 'Windows did not shut down properly, start Windows normally?' And will force me to start anew. This however doesn't cause a blue screen with driver error.

What is going on here? Post the memory dump file (.dmp) on a cloud server like google docs or maybe skydrive and I will look at it in the debugger and see what windows thinks the problem is. Generally, lots of older machines have hardware that did not implement low power link states correctly in the electronics.

This was not a problem because windows had them turned off by default. As bugs were found, people who wrote the drivers disable the functions. As time passed the driver functions were reenabled on the assumption that the devices were no longer in use.

Then the driver was handed over to microsoft and was gets pushed as a update, but now the function is enabled by default and the machine breaks. Often the 'fix' will be to disable the function in control panel power management for the offending device. This was a very common problem because vendors did not like to hand off updated drivers to microsoft because microsoft would attempt to test the drivers and would reject them if they failed (and charge them for the testing) Microsoft does not charge them anymore but I don't think they test them now either (the vendor certifies that they ran the tests). SystemRoot system32 DRIVERS NETw5s64.sys Wed Jan 13 08: this driver failed to respond to a sleep transition request and windows figured the device was broken and called a bugcheck. The driver is a intel wifi network adapter and should be updated.

- -i would update from the toshiba website or the intel website or you can turn off the wifi adapter from sleeping in power management. Note: there are other updates that could be a factor, your BIOS is very old and there can be bugs that require a update but start by updating the driver for the wireless chip. Machine info: Manufacturer TOSHIBA Product Name Satellite A355 Version PSAL6U-03S01E Chassis Type Notebook Product KTKAA Version 1.00 BIOS Version V2.40 BIOS Starting Address Segment e2cf BIOS Release Date. SystemRoot system32 DRIVERS NETw5s64.sys Wed Jan 13 08: this driver failed to respond to a sleep transition request and windows figured the device was broken and called a bugcheck. The driver is a intel wifi network adapter and should be updated. I've updated what I believed to be the driver for the adapter and although the problem ceased for almost 3 weeks, I got the same BSOD error tonight. Would you be willing to check the.dmp to see if there were any noticeable changes between this and last time?

Looks like the same problem: NETw5s64 SystemRoot system32 DRIVERS NETw5s64.sys Wed Jan 13 08: the driver is out of date, the PCI bus told the device to shutdown and it did not, a timer went off and cause a bugcheck because it thought it was a hardware failure. Looks like you did not update the driver or you still have the old driver selected even though you may have installed a updated one. My guess is you have actually delete the old driver and select the hardware to use the new one.

(you can have many potential drivers on the same system for one type of hardware, you have to enter into control panel, start device manager, find the network adapter then right mouse click, select update driver but do not select search automatically for updated driver select 'browse my computer for driver software' then select 'Let me pick from a list of device drivers on my computer' and it should show a list of drivers. (I think my system had 6 drivers for my one card, 3 from microsoft and 3 from intel) the list did not show the dates so I had to use another utility to determine which was the most current and select it) anyway, your driver did not get updated. SystemRoot system32 DRIVERS NETw5s64.sys Wed Jan 13 08: this driver failed to respond to a sleep transition request and windows figured the device was broken and called a bugcheck. The driver is a intel wifi network adapter and should be updated. I've updated what I believed to be the driver for the adapter and although the problem ceased for almost 3 weeks, I got the same BSOD error tonight.

Would you be willing to check the.dmp to see if there were any noticeable changes between this and last time? Looks like the same problem: NETw5s64 SystemRoot system32 DRIVERS NETw5s64.sys Wed Jan 13 08: the driver is out of date, the PCI bus told the device to shutdown and it did not, a timer went off and cause a bugcheck because it thought it was a hardware failure. Looks like you did not update the driver or you still have the old driver selected even though you may have installed a updated one. My guess is you have actually delete the old driver and select the hardware to use the new one. (you can have many potential drivers on the same system for one type of hardware, you have to enter into control panel, start device manager, find the network adapter then right mouse click, select update driver but do not select search automatically for updated driver select 'browse my computer for driver software' then select 'Let me pick from a list of device drivers on my computer' and it should show a list of drivers.

(I think my system had 6 drivers for my one card, 3 from microsoft and 3 from intel) the list did not show the dates so I had to use another utility to determine which was the most current and select it) anyway, your driver did not get updated. SystemRoot system32 DRIVERS NETw5s64.sys Wed Jan 13 08: this driver failed to respond to a sleep transition request and windows figured the device was broken and called a bugcheck. The driver is a intel wifi network adapter and should be updated.

I've updated what I believed to be the driver for the adapter and although the problem ceased for almost 3 weeks, I got the same BSOD error tonight. Would you be willing to check the.dmp to see if there were any noticeable changes between this and last time? Looks like the same problem: NETw5s64 SystemRoot system32 DRIVERS NETw5s64.sys Wed Jan 13 08: the driver is out of date, the PCI bus told the device to shutdown and it did not, a timer went off and cause a bugcheck because it thought it was a hardware failure. Looks like you did not update the driver or you still have the old driver selected even though you may have installed a updated one. My guess is you have actually delete the old driver and select the hardware to use the new one. (you can have many potential drivers on the same system for one type of hardware, you have to enter into control panel, start device manager, find the network adapter then right mouse click, select update driver but do not select search automatically for updated driver select 'browse my computer for driver software' then select 'Let me pick from a list of device drivers on my computer' and it should show a list of drivers. (I think my system had 6 drivers for my one card, 3 from microsoft and 3 from intel) the list did not show the dates so I had to use another utility to determine which was the most current and select it) anyway, your driver did not get updated.

SystemRoot system32 DRIVERS NETw5s64.sys Wed Jan 13 08: this driver failed to respond to a sleep transition request and windows figured the device was broken and called a bugcheck. The driver is a intel wifi network adapter and should be updated. I've updated what I believed to be the driver for the adapter and although the problem ceased for almost 3 weeks, I got the same BSOD error tonight.

Would you be willing to check the.dmp to see if there were any noticeable changes between this and last time? So I've downloaded 3 different drivers for my model of laptop from: I've tried the Atheros driver, Realtek driver, and Intel driver within and out of safe mode.

I uninstall and check 'delete driver software' from the wireless adapter. I go to scan for hardware changes and it instantly reinstalls the 'Intel Wi-Fi link 5100 AGN #2' without asking me, no browsing for files or anything. Since Windows 7 apparently comes with the latest wifi driver, I can't override it with the (possibly) working driver from an earlier date. At this moment, I've changed (from a list of drivers) from Microsoft to Intel.

The Intel version is earlier than the Microsoft one so I'm going to hope that this one will work. Intel makes the driver for their device, then they strip it down to make it kind of generic and give that copy to microsoft. Most often the best driver with the most fixes will come from Intel.

(they remove code they don't want to share with microsoft) the windows plug and play system will automatically install the driver if it is on your machine. (right after you uninstall it) you have to disable the auto install of the drivers in control panel (search for change device installation settings, device manager) and select the 'no' option and a list should pop up that you can select not to install devices. (i forget what it says) you select that option, then go back to device manager, remove the driver, and install the one you want. Then go back and reenable the auto install of drivers again. Intel makes the driver for their device, then they strip it down to make it kind of generic and give that copy to microsoft. Most often the best driver with the most fixes will come from Intel. (they remove code they don't want to share with microsoft) the windows plug and play system will automatically install the driver if it is on your machine.

(right after you uninstall it) you have to disable the auto install of the drivers in control panel (search for change device installation settings, device manager) and select the 'no' option and a list should pop up that you can select not to install devices. (i forget what it says) you select that option, then go back to device manager, remove the driver, and install the one you want. Then go back and reenable the auto install of drivers again. Guess who's back? I'm still having BSODs but much less than before even. Windows hasn't replaced the driver automatically, luckily, but the problem is still persisting with the Intel drivers I reverted back to.

Does this dump happen to say anything different compared to the previous ones? Thanks for your patience. Bugcheck 0x9f DRIVER_POWER_STATE_FAILURE (9f) A driver has failed to complete a power IRP within a specific time. Arguments: Arg1: 000003, A device object has been blocking an Irp for too long a time Arg2: fffffa8004727a10, Physical Device Object of the stack Arg3: fffff80000ba2748, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack Arg4: fffffa8005e7b440, The blocked IRP the bugcheck was in the PCI.sys driver for the PCI bus. It was caused because of a bug in netw5s64. Ni Wewe Amini Free Download more. sys SystemRoot system32 DRIVERS NETw5s64.sys Wed Jan 13 08: Intel 5100 wifi look here for update Note: if you can not get a update for the driver, go to the windows power management and find the wireless driver and tell windows that it can not put it to sleep to save power.

Bugcheck 0x9f DRIVER_POWER_STATE_FAILURE (9f) A driver has failed to complete a power IRP within a specific time. Arguments: Arg1: 000003, A device object has been blocking an Irp for too long a time Arg2: fffffa8004727a10, Physical Device Object of the stack Arg3: fffff80000ba2748, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack Arg4: fffffa8005e7b440, The blocked IRP the bugcheck was in the PCI.sys driver for the PCI bus. It was caused because of a bug in netw5s64.sys SystemRoot system32 DRIVERS NETw5s64.sys Wed Jan 13 08: Intel 5100 wifi look here for update Note: if you can not get a update for the driver, go to the windows power management and find the wireless driver and tell windows that it can not put it to sleep to save power.

Thank you for all of your help. Everything has been working well for the past month. Bugcheck 0x9f DRIVER_POWER_STATE_FAILURE (9f) A driver has failed to complete a power IRP within a specific time. Arguments: Arg1: 000003, A device object has been blocking an Irp for too long a time Arg2: fffffa8004727a10, Physical Device Object of the stack Arg3: fffff80000ba2748, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack Arg4: fffffa8005e7b440, The blocked IRP the bugcheck was in the PCI.sys driver for the PCI bus.

It was caused because of a bug in netw5s64.sys SystemRoot system32 DRIVERS NETw5s64.sys Wed Jan 13 08: Intel 5100 wifi look here for update Note: if you can not get a update for the driver, go to the windows power management and find the wireless driver and tell windows that it can not put it to sleep to save power. Thank you for all of your help. Everything has been working well for the past month. I am having the same problem. Did you get the correct driver or disable sleep? Bugcheck 0x9f DRIVER_POWER_STATE_FAILURE (9f) A driver has failed to complete a power IRP within a specific time.

Arguments: Arg1: 000003, A device object has been blocking an Irp for too long a time Arg2: fffffa8004727a10, Physical Device Object of the stack Arg3: fffff80000ba2748, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack Arg4: fffffa8005e7b440, The blocked IRP the bugcheck was in the PCI.sys driver for the PCI bus. It was caused because of a bug in netw5s64.sys SystemRoot system32 DRIVERS NETw5s64.sys Wed Jan 13 08: Intel 5100 wifi look here for update Note: if you can not get a update for the driver, go to the windows power management and find the wireless driver and tell windows that it can not put it to sleep to save power. Thank you for all of your help. Everything has been working well for the past month. I am having the same problem. Did you get the correct driver or disable sleep? Microsoft kept wanting to force it's Windows Updated driver on my wireless card, but I had to revert it back to the driver from Toshiba.

Though the driver is 6 years old, it no longer gives me trouble. Bugcheck 0x9f DRIVER_POWER_STATE_FAILURE (9f) A driver has failed to complete a power IRP within a specific time. Arguments: Arg1: 000003, A device object has been blocking an Irp for too long a time Arg2: fffffa8004727a10, Physical Device Object of the stack Arg3: fffff80000ba2748, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack Arg4: fffffa8005e7b440, The blocked IRP the bugcheck was in the PCI.sys driver for the PCI bus. It was caused because of a bug in netw5s64.sys SystemRoot system32 DRIVERS NETw5s64.sys Wed Jan 13 08: Intel 5100 wifi look here for update Note: if you can not get a update for the driver, go to the windows power management and find the wireless driver and tell windows that it can not put it to sleep to save power.

Thank you for all of your help. Everything has been working well for the past month. I am having the same problem. Did you get the correct driver or disable sleep?

Microsoft kept wanting to force it's Windows Updated driver on my wireless card, but I had to revert it back to the driver from Toshiba. Though the driver is 6 years old, it no longer gives me trouble. I entered the name of the Network Adaptor on the site recommended by johnbl Then I downloaded the Intel Driver Update Utility and updated the driver. It DID find a new driver for my network adaptor which the computer maker HP did not.

Since the new driver has been installed I have no more shutdown errors when the computer is put in sleep mode. Thanks johnbl!