forced to use mac due to windows issue

dipzy

New member
hey peeps,

i remember making a thread a few months back about me having problems with win 7 service pack 1. A few days ago, i decided to install it again since i thought the problems wold have gone away but they haven't and its worse than before.

A few months ago when i had it installed, i got the occasional BSOD about twice a week but now its happening twice everyday.

When the pc loads in to windows after the welcome screen, its very slow, takes along time and then BAMN!!! i get a BSOD which the message " System service exception" and pc restarts. When it loads windows again, BAMN!!! i get the same BSOD.

At times i have had it 3 times in a row before i can finally use my pc and its so annoying that ive been put off my my, i don't feel like using it.

All drivers are up-to-date as well?

Any ideas?
 
Anything more in event viewer?

How did you install SP1? Through Windows Update or did you download the whole redist package?
 
Anything more in event viewer?

How did you install SP1? Through Windows Update or did you download the whole redist package?

How do i check the event viewer?

I installed SP1 through windows update. Could it be my hard drive as it does make whining noises now and again or is that normal?
 
system restore, and wait for issues with sp1 to be fixed.

i guess i might have to do that since its works perfectly fine without SP1 but doesn't having SP1 improve windows in terms of fixing bugs, patches etc?
 
How do i check the event viewer?

I installed SP1 through windows update. Could it be my hard drive as it does make whining noises now and again or is that normal?

Control Panel -> Admin Tools -> Event Viewer

I always install SP1 using the redist file. When it was first released, there were issues with BSOD on server 2008 R2 when using Windows Update to install the package. I saw this myself once so from there on out I've always used the redist.

Some noise is normal, it's usually a clicking noise you need to be worried about. Has it just started doing the whining noise? You may want to go to the manufacturer's website and download their diag tool just to be safe.
 
Control Panel -> Admin Tools -> Event Viewer

I always install SP1 using the redist file. When it was first released, there were issues with BSOD on server 2008 R2 when using Windows Update to install the package. I saw this myself once so from there on out I've always used the redist.

Some noise is normal, it's usually a clicking noise you need to be worried about. Has it just started doing the whining noise? You may want to go to the manufacturer's website and download their diag tool just to be safe.

in event viewer i see alot of this: The driver detected a controller error on \Device\Ide\IdePort2.

and also this: \SystemRoot\SysWow64\Drivers\ULCDRHlp.sys has been blocked from loading due to incompatibility with this system. Please contact your software vendor for a compatible version of the driver.

The hard drive noise has been happening for a week or so now
 
Nope i only got poweriso installed

ULCDRHlp.sys is the Ulead burning engine, that why I asked. The "The driver detected a controller error on \Device\Ide\IdePort2" error you are seeing could be caused from the other warning, or it may be an issue with your drive.

Did that error start showing up in event viewer about the same time your drive starting making noises?
 
ULCDRHlp.sys is the Ulead burning engine, that why I asked. The "The driver detected a controller error on \Device\Ide\IdePort2" error you are seeing could be caused from the other warning, or it may be an issue with your drive.

Did that error start showing up in event viewer about the same time your drive starting making noises?

Yep, at first it was slight humming noises, i thought that was normal but its gone louder and at times it makes this clunk type of sound as if the read head is parking itself. The error did start showing up around the time rhe nouse started.

ULCDRHIp, should i remove it or will it make things worse if i do?
 
Yep, at first it was slight humming noises, i thought that was normal but its gone louder and at times it makes this clunk type of sound as if the read head is parking itself. The error did start showing up around the time rhe nouse started.

ULCDRHIp, should i remove it or will it make things worse if i do?

Make sure your data is backed up and I would scan that drive immediately.

I'd try to find out what is using that .sys file and remove the program itself.
 
It could just be the driver Windows is using.

When SP 1 came out I also installed it (well I would, I have it set to install all important updates).

All of a sudden I start getting internet problems. Connected, disconnected, ETC ETC.

I am using a wireless G non branded dongle in this PC and a Dlink G in the other (both USB due to no slots left on motherboard that aren't used or covered). Any way, I start having issues with the Dlink too. I took it out, bashed it, tapped it (all those problem solving methods
laugh.gif
) and yet still it just steadily got worse.

Then, all of a sudden, it rejects my wireless password (WPA2 so I set it myself). So I immediately crap my pants thinking some one has hacked my router, so go downstairs and change the passwords ETC ETC (plugged in with a NIC cable).

Come upstairs, still won't accept the WPA2, on either of my wireless dongles.

In the end I realised that if I took the little mini CD that came with my non branded dongle and force on the driver (even though Windows tells me not to as it's not verified) it works perfectly. Go to Dlink's FTP and get the driver for that, quelle surprise both are back fully working.

What's really frigging annoying is if I ever unplug them (USB) and put them back in Windows immediately starts using the broken bloody drivers again
sad.gif
 
Im thinking its a driver issue sum where but i keep thinking that sp1 is to blame as i never had any issues what so ever. I think I'll un-install SP1 and see if the problem is still there, if its not I'll leave win 7 without SP1, if its still there then, i will back up data, reinstall windows, then straight away install SP1 and all lastest driver before i install any of my other programs so i know if it was due to a software i was using before
 
I would back up any important data first, then start tweaking just in case your HD dies, it is a lot easier than trying to recover it.
 
I would back up any important data first, then start tweaking just in case your HD dies, it is a lot easier than trying to recover it.

All backed up just in case HDD dies, also looking at SSD's as a replacement if it does
smile.gif
 
One thing i have noticed is i know when i will get BSOD. Its when windows loads into desktop, if its very slow and desktop icons are still loading after a minute, then i will 100% get the BSOD, if all the icons load under a minute then im ok
 
Back
Top