XP Crashing

What OS are you running, home or Pro.

I wonder if this would have any effect. If you try automated system recovery instead of repair...

Just trying to throw some ideas at you. \
If you want, we could have a live chit chat on msn or something and we could do a complete system comparison. That might help, seeing I just reloaded my OS and am having no problems what so ever.
I was thinking it might be a TEMP file to tell you the truth, because right before I had any problems I deleted the temp files out of the %systemroot% directory. Of course my A+ software book said I could, so that might not be the problem. Let me know if you would like to do that comparison thing.
-Jeff

Quote:

---

Originally Posted by Martin009

I tried a repair from the OS disk a few months ago and it ended in disaster. For some reason it would not repair. It crashed and corrupted the whole system so I could no longer boot up or anything. Luckily I had just done a complete disk image so I installed it to it’s pre-repair state.

---

One thing I just noticed. None of my COM+ apps are disabled. If any of yours are change the ones from disabled to automatic.
just an idea

Quote:

---

Originally Posted by Black Ops Lab

What OS are you running, home or Pro.

I wonder if this would have any effect. If you try automated system recovery instead of repair...

Just trying to throw some ideas at you. \
If you want, we could have a live chit chat on msn or something and we could do a complete system comparison. That might help, seeing I just reloaded my OS and am having no problems what so ever.
I was thinking it might be a TEMP file to tell you the truth, because right before I had any problems I deleted the temp files out of the %systemroot% directory. Of course my A+ software book said I could, so that might not be the problem. Let me know if you would like to do that comparison thing.
-Jeff

---

Both:
COM+ Event System
COM+ System Application
are not started!

Both are on "Manual".

I'm using Home edition!

com+ is usually manual

Have a look at that link, it tells you what services do what and what can be done without.

out of all of my services, three of them are disabled.
HID
Routing and Remote
Telnet
The rest are either automatic or manual
Take a look at yours and let us know, Martin009

Quote:

---

Originally Posted by NooNoo

com+ is usually manual

Have a look at that link, it tells you what services do what and what can be done without.

---

I tried to start the two com + services that I have.

They both failed to start producing the following error:
Could not start the COM + Event System service on the Local Computer
Error 126: The specified module could not be found

Look at the dependencies and look at the link I posted so you can see what they do.

Thanks.

While I was scanning through the device manager I came across the show hidden option and found the NEC PCI to USB Enhanced Host Controller with an exclamation next to it.

This device is not present, is not working properly, or does not have all its drivers installed. (Code 24)

Click Troubleshoot to start the troubleshooter for this device.

The service name is ousbehc and doesn't seem to have an option for updating the driver

P.S. System Events Notification depend on that service (whatever that means).

Right, so your motherboard drivers are not properly installed. unless this is a usb card, in which case grab the patch from www.usbman.com

Not that I doubt your expertise... But, how do motherboard drivers just become unstable. Out of nowhere, like in my case. There was no reason for it, I had the same error message to the tee. There is no problem now and I have the exact drivers as I did then.

Just out of curiousity?, because I would really enjoy learning from you.
is it the chip set driver???
I personally think it's something to do with Windows itself...

Quote:

---

Originally Posted by NooNoo

Right, so your motherboard drivers are not properly
installed. unless this is a usb card, in which case grab the patch from www.usbman.com

---

Drivers are software. So, therefore can become corrupt and then unstable. You sound like you are familiar with Windows software and its "issues". Well, drivers are just the same if not worse over the years. Think of all the updated drivers in fact. Why do you thing they had to be updated in the first place? Think then about the need for a place called WinDrivers since 1998. 'Nuff said?https://forums.windrivers.com/images.../2006/04/1.gif

Drivers are software. I agree. I understand that. The problem I had though is how does a driver work one day and not the very next. I understand drivers going out on you, and start to make problems slowly as when different patches, updates and other factors come into play to make certain aspect of a device driver stop functioning as it once did. The problem is when it happens because of no apparent reason. I guess the funny thing for me is microsoft had no answers on the problem, Dell had no answers. Updating all of my drivers to this year or last year had no affect. I still had the same problem. A device driver trying to corrupt the kernel stack. No matter what I did got rid of the problem, until I reloaded the OS. After I reinstalled the OS, I reloaded the OLD drivers from 2001-2002, and I am having no problem. My computer runs perfectly and flawlessly, the way it did before the 'device driver' problem.
Is it possible that there was a virus on my computer that Norton couldn't find?

Quote:

---

Originally Posted by TripleRLtd

Drivers are software. So, therefore can become corrupt and then unstable. You sound like you are familiar with Windows software and its "issues". Well, drivers are just the same if not worse over the years. Think of all the updated drivers in fact. Why do you thing they had to be updated in the first place? Think then about the need for a place called WinDrivers since 1998. 'Nuff said?https://forums.windrivers.com/images.../2006/04/1.gif

---

Did anyone figure this out yet?

Quote:

---

Originally Posted by Black Ops Lab

Did anyone figure this out yet?

---

Which bit ?

So in my confus-ed state, I'll venture :- Its all this patching of patching of patches out of sync business that causes these 'otherwise inexplicable' occurances - when a driver gets WHQL stamped on it, they do the testing with standard kit (you might have something unusual or not normally tested for type device) on whatever level of o/s is 'latest', how you, I or they define all of those is what accounts for it.

Start off with a clean install & add all the patches in one go (just like they test it) & you've improved your chances of it all going 'good' considerably ;)

Hi,

I have been experiencing the same problem with BSOD... with same parameters as Martin009. It actually started when I left my computer on for a period of time with a p2p program running in the background.

When I came back to my computer, the computer was rebooted and was at a login screen. After log in, an error report message popped up. After disabling a few start-up apps and uninstalling unnecessary softwares, it worked fine for a while. And then, these fatal errors started happening. With errors that referred to paging, kernel, and etc.

At first few times, Norton Antivirus files were the culprits, so I uninstalled the app and the problem disappeared. But I couldn't reinstall the norton antivirus because it would crash my computer again after clean installation and required restart.

But then it started showing a consistent BSOD at 0x000000C4 with same parameters.

After doing verifier.exe on all drivers, BSOD reported problems on savrt.sys, an auto-enable file for norton antivirus.

I also have nVidia nforce2 motherboard (ASUS) with nVidia GeForce FX 5200 vid card. I'm not sure if you made any improvements with your system, but I have been trying to resolve this problem to avoid a format... too much data and time involved. Moreover, I wanna fix this problem for future reference.

I've had no luck either.

Like you BSOD reported problems on savrt.sys, an auto-enable file for Norton antivirus and advised me to update my Virus software which was already up-to-date.

I have had to put it to one side for the moment is more pressing. Sometimes I can go for a week or so without the BSOD and just as I almost think that it has mysteriously disappeared it returns with its subtle reminder.

Maybe in a few weeks I’ll rededicate myself to trying to sort this out. Like you I would like to know the cause and not just go for a reformat. What’s to say that if we reformat and install everything on correctly that it won’t reappear anyway???

Hmmm and we all know how stable norton can be...and how its the first on the list of targetted software for every virus and trojan writer out there.

There is a reason norton provide a step by step removal of norton manually.

I have sold 35 of those motherboards to one customer. What A Freakin Nightmare. RAM is most likley your problem. That motherboard is enormously picky on the RAM. Buy some high dollar Kingston or Crucial 333 Memory best bet is 2 sticks of 256. If I remember right that has 3 RAM slots put one chip in the slot close to the CPu and one in the furthest from the CPU. Check you timing setting for the CPU and Ram in the BIOS and contact MSI for the latest Bios fix. www.msicomputer.com and Good Luck. Has something to do with resource and memory sharing on that motherboard.

Thanks. I thought that it might be memory so I went out and bought another 512MB stick of kingston. I now have all three in (512 + 2 at 256) and it doens't seem to BSOD as much.

What timing settings should I set in the BIOS? (At present I have default!)

Quote:

---

Originally Posted by Martin009

..What timing settings should I set in the BIOS? (At present I have default!)

---

(I'll answer this bit, while enquiring about your 'less' BSOD state ? None is the expected situation ! :eek2: )

Default is generally good for stability, but not necessarily for performance, so tell us what you've got to change, its different in different bioses, Tom's Hardware covers the most common features found - note there's also tools which let you reprogram the appropriate bios sections for particular stuff if the bios options aren't there, though its pretty advanced stuff ..