bsod on bootup

[CheesePoofs]

For the second day in a row, my computer has given me a bsod right after I log in and while its still loading programs. the error report thing says

You are receiving this message because a device driver installed on your computer caused a stop error message. This error message required a restart of your computer. After the restart your computer should continue to operate normally, however the error may re-occur until the problem is corrected."

I believe the error in the event viewer that corresponds to the bsod is this one

Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7000
Date: 11/22/2005
Time: 4:13:21 PM
User: N/A
Computer: Computer
Description:
The OrangeWare USB Enhanced Host Controller Service service failed to start due to the following error:
The service cannot be started, either because it is disabled or because it has no enabled devices associated with it.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

there's also this right next to it

Event Type: Information
Event Source: Save Dump
Event Category: None
Event ID: 1001
Date: 11/22/2005
Time: 4:13:18 PM
User: N/A
Computer: Computer
Description:
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009c (0x00000002, 0x80545ff0, 0xb6000000, 0x00020136). A dump was saved in: C:\WINDOWS\MEMORY.DMP.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

I've been getting a few bsods lately because I now have 4 sticks of ram in my system (in sig) and its taken some fiddling to get it stable, but I dont' think this is related because the error report identified it as a driver and not hardware problem. I dont' know what the orangeware service is related to or why it suddenly started to appear, or, more importantly, what I can do to fix it.

 

[LiLithTecH]

Have you tried not OC'ing?

 

[CheesePoofs]

I've had my rig OC'd for months with complete stability. It started doing this yesterday. If it keeps happening I'll set everything back to stock to see if it happens again. Unfortunately I'll be going away for turkey day, so I wont' be at my comptuer to test.

 

[CheesePoofs]

Ugh, it just happened twice more. Same error each time. What is the orangeware USB thing that seems to be causing this?

 

[CheesePoofs]

I got back from thanksgiving yesterday, and was BSOD-free all day.

Today, it gave me a BSOD after a few hours of running. I rebooted, cleaned out all the usb drivers, and went back into windows. I got another bsod . DOes anyone know hwo to fix the issue, which seems to be with the OrangeWare USB Enhanced Host Controller Service?

EDIT: I ran MPSReports after the crash, in case anyone knows how to figure out what happened through that.

 

[CheesePoofs]

bump

 

[montag451]

Put it back to stock, then we can run through some problems if it is still there

 

[CheesePoofs]

Its at stock now after it did it again today. The problem is it seems to do it only within the first hour or two of booting up, so chances are I'll have to wait until tomorrow to see if it happens again.

 

[montag451]

run memtest overnite - see if errors come up.
If so, run one stick at a time overnite to weed out the lame one.

 

[CheesePoofs]

I've run memtest overnight and all through the day at my overclocked setting with no errors, but I'll do it again tonight just to make sure.

Would you recomend running the complete set of tests or just a specific one looped?

 

[kitkat22]

It sounds like a program is causing the problem. Disable all your startup programs and see what happens.

 

[CheesePoofs]

I just finished running memtest for 16.5 hours at stock speeds (but the ram is at ddr333 because I have 4 sticks) with no errors. So far so good in Windows ...

 

[CheesePoofs]

Strangely, it looks like this was related to a bad hard drive I had. The HD was giving me about 3 errors in event viewer every minute and, although it showed up under my computer, it wasn't accessable. It was a clone of my main drive, so something could have gone wrong there.

Anyways, I pulled the drive, and I've been overclocked once more for at least 4 days, BSOD free.