| Forum Home | ||||
| Press F1 | ||||
| Thread ID: 107922 | 2010-03-07 10:24:00 | NDIS.sys and BSOD | johcar (6283) | Press F1 |
| Post ID | Timestamp | Content | User | ||
| 864706 | 2010-03-07 10:24:00 | I have two laptops running XP here (a Tosh and a Vaio) and both have recently started blue-screening at unpredictable intervals I noticed this thread (pressf1.co.nz), but don't think it has anything to do with my issue. The Tosh has a reasonably new Seagate 120GB HDD and I have just done a full reinstall using the original disk that came with the machine, but it is still BSODing. My son is using this machine, pretty much just for Facebook and music/music videos. The Vaio is being used by SWMBO who is technophobic and is using it for games, browsing and email - again it's an older machine (4-5 years?) with a newish Seagate HDD. I have run CHKDSK on the Vaio - it seemed to fix something in the third part of the run, but it just flashed briefly and finished and I didn't get to see what it 'fixed'. It is also still BSODing. Haven't rebuilt this one .... yet. There have been no changes to the Vaio (hardware or software) apart from Windows updates. (I know this because SWMBO ignores anything that looks remotely technical and would not know even how to install Flash Player! She wouldn't even know what Flash is used for.) I cannot guarantee what my son may have installed (!!) however since the machine is still BSODing after a rebuild, it's probably safe to assume that it wasn't anything he did. The Tosh has an nVidia driver that is locked - not possible to update it (from a suggestion in the thread referred to above) The driver that seems to be the probem is NDIS.sys - coupled with the exceedingly unhelpful "DRIVER_IRQL_NOT_LESS_OR_EQUAL". Google does not seem to be much help. It seems more than a coincidence that both XP laptops started playing up around the same time - the home PC (a desktop, also XP) and my Win7 laptop are stable as ever. Does anyone here have any idea of what I could look at? |
johcar (6283) | ||
| 864707 | 2010-03-07 10:27:00 | So a stop error code appeared? If so what? | Sweep (90) | ||
| 864708 | 2010-03-07 10:28:00 | NDIS.sys belongs to the network drivers. Uninstall them then install a later version. If that doesnt work, the NIC could be dead. Is XP up to date? If the desktop is up to date copy ndis.sys from it to both of the laptops. It looks like this file can get infected. Have these laptops been scanned with something? | Speedy Gonzales (78) | ||
| 864709 | 2010-03-07 10:38:00 | So a stop error code appeared? If so what? Is that that string of "0x000000" stuff? If so, not sure. Both users getting so p***** off they are just restarting the machine (against my instructions) and carrying on!!!! Plus, I'm not always around when it happens.... NDIS.sys belongs to the network drivers. Uninstall them then install a later version. If that doesnt work, the NIC could be dead. Is XP up to date? If the desktop is up to date copy ndis.sys from it to the laptop thats crashing If there's been no change to the hardware and a full reinstall reapplies the original build (with the original driver specced for the original hardware), how could it be a driver issue? Again, it looks suspicious that both laptops have a NIC issue at the same time. XP is up to date on both machines (including the newly rebult Tosh). I will locate and copy NDIS.sys from the desktop to the lappies and see if that makes a difference. |
johcar (6283) | ||
| 864710 | 2010-03-07 10:43:00 | The driver maybe corrupt or something or infected. If a BSOD shows a file or driver, thats usually the cause of the crash. What else is on these laptops, as in software. Nothing with the name nortons or symantec in it, I hope | Speedy Gonzales (78) | ||
| 864711 | 2010-03-07 10:53:00 | The driver maybe corrupt or something or infected. If a BSOD shows a file or driver, thats usually the cause of the crash. What else is on these laptops, as in software. Nothing with the name nortons or symantec in it, I hope Hell no!!!! :D The Tosh is still pretty 'bare bones' - didn't want to go to the trouble of multiple program reinstalls if it wasn't going to behave. So it's pretty much just the usual Tosh junk (which has always been there) and FF3 at the moment. I have dropped a copy of the NDIS.sys driver from the desktop onto the Vaio (date/timestamp was exactly the same - but as you say, may have been corrupt) - so will wait to see what happens over the next couple of days - thanks Speedy. Will get back with results as soon as I either have (or do not have) them... :) |
johcar (6283) | ||
| 864712 | 2010-03-07 10:54:00 | Damn. Duplicate post! | johcar (6283) | ||
| 864713 | 2010-03-07 10:56:00 | Sweet no probs :) | Speedy Gonzales (78) | ||
| 864714 | 2010-03-07 11:07:00 | The string is what I was mentioning. Don't need the whole string just the last two characters. |
Sweep (90) | ||
| 864715 | 2010-03-10 10:02:00 | Speedy - we have a semblance of stability on the Vaio (the one I copied the NDIS.sys file onto) - no BSODs since overwriting it. (Hmmm. There's no crossed-fingers emoticon....) So I will now attempt the same fix on the Tosh... |
johcar (6283) | ||
| 1 2 3 | |||||