RUNDLL32 on XP SP2

I installed last release of WB5. After lot of problems installing it, I finally succeeded. But when I try to acces display properties, an error occur : "RUNDLL32.EXE encountered an error and must close...". If I unload WB5, it works again. I'm actually under windows XP SP2, Athlon XP-M 2600+, Geforce 6800 Ultra with nvidia forceware 77.62.


WindowBlinds 5 BETA Troubleshooting Report:


WindowBlinds is installed correctly on this PC.

Your machine supports per pixel borders on WindowBlinds skins.

If you suffer visible corruption (overbright) on the frames and have a NVIDIA board then please be aware this is a NVIDIA bug. It has been seen on GeForce 4 cards and some FX series cards.

Video Information

You have one monitor in total.

(CM1997PF) 1 is attached to NVIDIA GeForce 6800 Ultra by www.TweaksRUs.com

'NetMeeting driver' also exists as device '\\.\DISPLAYV1', but is not attached to the desktop and is a mirror driver.

'RDPDD Chained DD' also exists as device '\\.\DISPLAYV2', but is not attached to the desktop and is a mirror driver.

PLEASE report all this information when submitting a problem report, especially anything related to per-pixel skinning. We don't know what's in that Dell you bought last July or the notebook the office gave you. Per-pixel skinning requires your drivers to at least claim to support the functions needed for it.
7,763 views 11 replies
Reply #1 Top
In fact each item in control panel fails (the same RUNDLL32.EXE error...). More bugs, logon studio don't work anymore and I have no logon screen. If I unload WB and apply a new logon, then I can't log anymore (no login window). After reboot, I have 5 RUNDLL32.EXE error windows. Please what can I do ? In fact, I must say that my OS is Windows XP Pro LSD 3.5 with SP2 (a optimized mod based on 32 bits ed. with a few services disabled)... Do I have to install Windows XP Pro SP2 instead or are there any services I have to enable in order to have WB5 work fine ?
Reply #2 Top
It worked fine on my desktop system. But I get the Rundll error on my laptop. I'm running WinXP SP2 with all updates, GeForce Go 6400. Can't remember the forceware version atm cause I can't access the Display Properties window due to the rundll errors. I think it might be 73 or 74.

I also disabled some services that I figured I didn't need, but it's exactly the same as my desktop system.
Reply #3 Top

We are working on the rundll32 issue.

Thats what beta tests are for, to find the issues that we don't have.

Reply #4 Top
I'm super excited about this beta. It looks awesome, boasts overall higher performance and ran glitch-free... until I found out about that Display Properties rundll32.exe bug. It also applies to any entry in the Control Panel. Nothing works. If I unload WB it all works again.
Please Stardock, fix that little bug. This version 5 looks really promising! So far (save for that rundll32 bug) I'm very impressed!!

Laptop specs: Pentium M 1.8GHZ
1GB RAM
Mobility Radeon 9700 128MB
Windows XP SP2 with all the latest patches applied
Reply #5 Top
Hai all,
i have the same problem with the rundll32 on my notebook.
After starting WIN XP SP2 i get twice a rundll32 error.
Also if i right-click on the desktop and select properties
to change my desktop i get the rundl32 error. Sometimes
my screen hangs ... all this after installing WB 5 Beta.

Thanks for fixing rundll32 - errors.

Best regards.
Reply #7 Top
Hi, ...

I have also that rundll32.exe Error.

The instruction at "0x76b22e94" referenced memory at "0x76b22e94". The memory could not be "read". Click on OK to terminate the program.

This error popup window, seem to be upper my cursor and upper all other(s) window. = I have Stardock Cursor XP, latest registred version. Windows XP Pro. Eng. SP2, some pre-relase of SP3.

----------
WindowBlinds 5 BETA Troubleshooting Report:


WindowBlinds is installed correctly on this PC.

Your machine supports per pixel borders on WindowBlinds skins.

If you suffer visible corruption (overbright) on the frames and have a NVIDIA board then please be aware this is a NVIDIA bug. It has been seen on GeForce 4 cards and some FX series cards.

Video Information

You have one monitor in total.

(SyncMaster 711N/712N/710NZ12,SyncMaster Magic CX712N) 1 is attached to NVIDIA GeForce4 MX 440 with AGP8X

'NetMeeting driver' also exists as device '\\.\DISPLAYV1', but is not attached to the desktop and is a mirror driver.

'RDPDD Chained DD' also exists as device '\\.\DISPLAYV2', but is not attached to the desktop and is a mirror driver.

PLEASE report all this information when submitting a problem report, especially anything related to per-pixel skinning. We don't know what's in that Dell you bought last July or the notebook the office gave you. Per-pixel skinning requires your drivers to at least claim to support the functions needed for it.
----------

Sylvain St-Amand (Korgul).


Posted via WinCustomize Browser/Stardock Central
Reply #8 Top
Would it help you, the developers, to post the error data we get from the rundll errors?
Reply #9 Top
By the way, the windowblinds 5, beta build 2005/10/05 have also the run32dll bug.

Nvidia 81.84

If i terminate the explorer.exe process and open nvidia control panel, and press ok, it dont make the rundll32 bug. If i try to not terminate the explorer.exe process, it make the rundll32 after press ok.

Also, i try to use plug and play driver, instead of my normal driver on my lcd screen.

I hope that it will help ?


WindowBlinds 5 BETA Troubleshooting Report:

STATUS : WB+ SRV+ HLP+ UI+

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.

(Plug and Play Monitor) 1 is attached to NVIDIA GeForce4 MX 440 with AGP8X
'NetMeeting driver' also exists as device '\\.\DISPLAYV1', but is not attached to the desktop and is a mirror driver.
'RDPDD Chained DD' also exists as device '\\.\DISPLAYV2', but is not attached to the desktop and is a mirror driver.



Posted via WinCustomize Browser/Stardock Central
Reply #10 Top
I've updated to WB5 4.90.b[b].003 (after full uninstall of previous version of course), and... each bug I submitted before was solved ! There's another one I forgot to tell about before... When using WindowsFX 2.20c[b].003, there's a minor bug. When I open a new window, it isn't skinned until I activate it by clicking It... Just one more thing... Crongatulation to all of you, stardock developpers ! You did a really good job with WB5 !
Reply #11 Top
I'm super excited about this beta. It looks awesome, boasts overall higher performance and ran glitch-free... until I found out about that Display Properties rundll32.exe bug. It also applies to any entry in the Control Panel. Nothing works. If I unload WB it all works again.
Please Stardock, fix that little bug. This version 5 looks really promising! So far (save for that rundll32 bug) I'm very impressed!!


After updating to version 4.90.b[b].003 (and I didn't uninstall the previous version), my one only problem is solved. hehe! That was F.A.S.T.! You guys are my heroes now!

When using WindowsFX 2.20c[b].003, there's a minor bug. When I open a new window, it isn't skinned until I activate it by clicking It... Just one more thing... Crongatulation to all of you, stardock developpers ! You did a really good job with WB5 !


Stardock recommends that you not use WindowFX 2.2 and WindowBlinds 5 together. Wait for the WindowFX 2.5 beta update coming up later this month if you want to use both programs at the same time.