Search
Forum Home | Login
engli5h
engli5h
Join Date 01/2006
0

Win XP Hangs and Blue Screens While using WB5

January 19, 2006 12:32:19 PM from Stardock ForumsStardock Forums
Windowblinds 4.6 works fine, although I have recently purchased Version 5 (latest version as of today) and my PC totally hangs and blue screens on random occasions.

System config =========

Win XP Home SP2 (32 bit)
1 Gig Ram
Athlon XP 3000
Nvidia Geoforce 6600 (Latest Nvidia drivers 81.98)

=======================

WindowBlinds 5.0 System Information Report:

STATUS : WB+ SRV+ HLP+ UI+ TRAY+

WindowBlinds is installed correctly on this PC.

WindowBlinds appears to be activated on this PC

Your machine supports per pixel borders on WindowBlinds skins.

You have one monitor in total.

etc etc

===========

Any ideas? I'd really appreciate it as WB5 is excellent otherwise.
windowblinds
Locked Post
Search this post
Advanced Search
Subscription Options
Reason for Karma (Optional)
Successfully updated karma reason!
engli5h
BX
Join Date 10/2001
+21
Reply #1 January 19, 2006 1:00:44 PM
from WinCustomize ForumsWinCustomize Forums
Had you uninstalled WB4.6 BEFORE installing WB 5???
Reason for Karma (Optional)
Successfully updated karma reason!
engli5h
engli5h
Join Date 01/2006
0
Reply #2 January 19, 2006 1:10:08 PM
from Stardock ForumsStardock Forums
I did an installation over the top of 4.6 at first, then I tried it by uninstalling everything and re-installing WB5 as a fresh copy.

Thanks for the rapid reply.
Reason for Karma (Optional)
Successfully updated karma reason!
engli5h
Neil Banfield
Join Date 04/2001
+1104 sdemployee
Reply #3 January 19, 2006 1:14:03 PM
from WinCustomize ForumsWinCustomize Forums
What does the blue screen say?
Reason for Karma (Optional)
Successfully updated karma reason!

Sign Up or Login and this ad disappears!
There are many great features available to you once you register. Sign Up for a free account and browse the forums without ads.

engli5h
engli5h
Join Date 01/2006
0
Reply #4 January 19, 2006 1:30:25 PM
from Stardock ForumsStardock Forums
Not sure now, something about a kernel fault as far as I remember. I uninstalled WB5 due to the instability. It seemed to hang more than blue screen, i.e no mouse movement etc and the red HD LED on (although the whole system was frozen).
Reason for Karma (Optional)
Successfully updated karma reason!
engli5h
Neil Banfield
Join Date 04/2001
+1104 sdemployee
Reply #5 January 19, 2006 1:50:26 PM
from WinCustomize ForumsWinCustomize Forums
It sounds like a driver problem.  Probably video driver instability as WB 5 pushes your hardware more than WB 4.
Reason for Karma (Optional)
Successfully updated karma reason!
engli5h
engli5h
Join Date 01/2006
0
Reply #6 January 19, 2006 2:04:11 PM
from Stardock ForumsStardock Forums
Is there anything that can be done? i.e with a future update of WB 5, or is it just a case of hoping for Graphics card driver updates?
Reason for Karma (Optional)
Successfully updated karma reason!
engli5h
BX
Join Date 10/2001
+21
Reply #7 January 19, 2006 2:27:14 PM
from WinCustomize ForumsWinCustomize Forums
What is your Graphic Card -- !!!
Reason for Karma (Optional)
Successfully updated karma reason!
engli5h
engli5h
Join Date 01/2006
0
Reply #8 January 19, 2006 2:48:15 PM
from Stardock ForumsStardock Forums
Nvidia Geoforce 6600 (Latest Nvidia drivers 81.98)
Reason for Karma (Optional)
Successfully updated karma reason!
engli5h
Adamness
Join Date 08/2005
0
Reply #9 January 19, 2006 2:57:05 PM
from WinCustomize ForumsWinCustomize Forums
Just read somewhere on this forum that you have to roll back 6600 drivers to 77.77. I think it was in the 'Read this if your UI is black and painting slowly' thread.
Reason for Karma (Optional)
Successfully updated karma reason!
engli5h
engli5h
Join Date 01/2006
0
Reply #10 January 20, 2006 6:30:37 AM
from Stardock ForumsStardock Forums
I read that too, although I didn't really want to roll back to those drivers. The 6600 should be capable of what WB5 throws at it, surely?

It's hard to work out why it's happening because it's random.
Reason for Karma (Optional)
Successfully updated karma reason!
engli5h
Jafo
Join Date 03/2001
+1845 sdemployee
Reply #11 January 20, 2006 7:01:10 AM
from WinCustomize ForumsWinCustomize Forums

read that too, although I didn't really want to roll back to those drivers. The 6600 should be capable of what WB5 throws at it, surely?

I think the first thing to try IS the roll-back to an earlier driver.  Not all updates are actually steps 'forward'...sometimes drivers are known to be worse than previous vers....they may give some groovy smoke effects in Quake 4 or something...but actually fubar your 2D OS interaction....[just an example]...

Reason for Karma (Optional)
Successfully updated karma reason!
engli5h
engli5h
Join Date 01/2006
0
Reply #12 January 20, 2006 7:10:45 AM
from Stardock ForumsStardock Forums
Ok well I have just found an updated driver (ForceWare 82.65) http://downloads.guru3d.com/download.php?det=1299

I've just upgraded my drivers to the above and re-installed WB5, so I'm gonna give it a run for few hours to see if that helps.

If not, I will give the 77.77 drivers a try.
Reason for Karma (Optional)
Successfully updated karma reason!
engli5h
jumanji
Join Date 10/2001
0
Reply #13 January 20, 2006 7:12:04 AM
from WinCustomize ForumsWinCustomize Forums
I have already reported this bug in wb5 several month ago (win2003 4 Gig of mem).
It happens mostly every time if you are doing changes in wb5 and then these changes are applied.
Bluescreen with code 0x000000 System halted. It has something todo with the logon process.
I don't think that this are driver problems, maybe it is related to mem more then 1 gig?
Reason for Karma (Optional)
Successfully updated karma reason!
engli5h
engli5h
Join Date 01/2006
0
Reply #14 January 20, 2006 11:02:18 AM
from Stardock ForumsStardock Forums
I've not had a problem so far with the Forceware 82.65 drivers, but no doubt I'll jinx myself saying that.
Reason for Karma (Optional)
Successfully updated karma reason!
engli5h
Kevin_C
Join Date 11/2002
+7
Reply #15 January 20, 2006 11:19:06 AM
from WinCustomize ForumsWinCustomize Forums
maybe it is related to mem more then 1 gig?


Nah, I have 2GB of RAM and I've not had any problems with WB. I fully believe that this problem with the 660 could be caused by drivers as I have had a problem with PSP X not running when I installed any of the 8x.xx series drivers from NVidia, and the problem occurred regardless of whether or not I had WB installed or running. Like Jafo said, some drivers are just bad.
Reason for Karma (Optional)
Successfully updated karma reason!
engli5h
engli5h
Join Date 01/2006
0
Reply #16 January 20, 2006 3:12:54 PM
from Stardock ForumsStardock Forums
Still no problem with the Forceware 82.65 drivers, but now I've just changed to the Aura skin with transparent borders and shadows so this will be the real test. Fingers crossed.
Reason for Karma (Optional)
Successfully updated karma reason!
engli5h
silveraxe
Join Date 03/2004
0
Reply #17 January 24, 2006 7:35:32 PM
from WinCustomize ForumsWinCustomize Forums
I have had 1 problem like this so far also. I have a Dell dimension 8400 P4 2gig ddr ram ATI Radeon 300X video card. The frist time I started the program it came up with a blue screen. I rebooted then it was fine. But now I am having a problem with Win XP media. I can not open any of the folders with out getting an error in windows explorer. It then shuts down, then comes back. And every time I try to open a file it will happen again. I unloaded WB5 then there was no problems after that. I have sent in an error report. I hope they can find out what it is.

Posted via WinCustomize Browser/Stardock Central
Reason for Karma (Optional)
Successfully updated karma reason!
engli5h
Neil Banfield
Join Date 04/2001
+1104 sdemployee
Reply #18 January 25, 2006 6:23:20 AM
from WinCustomize ForumsWinCustomize Forums
What is the error?
Reason for Karma (Optional)
Successfully updated karma reason!
View all recent posts
Mark all posts as read Delete cookies created by the forum Return to Top
Stardock Forums v        Server Load Time:   Page Render Time: