RE: Windows host process (Rundll32) has stopped working

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

**Warning** if you do not have a solution, or are not smart enough to
understand, do not answer this post**

Update: When I click on 'Check online for a solution and close the program'
( I do not have any programs opened ) the window reappears multiple times in
a frenzy until the recycle bin is closed. 'View problem details' reveals:
Problem signature:

Problem Event Name: APPCRASH
Application Name: RunDLL32.exe
Application Version: 6.0.6000.16386
Application Timestamp: 4549b0e1
Fault Module Name: StackHash_1703
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 00000000
Exception Code: c0000005
Exception Offset: 02b0b5ed
OS Version: 6.0.6000.2.0.0.256.1
Locale ID: 1033
Additional Information 1: 1703
Additional Information 2: 2264db07e74365624c50317d7b856ae9
Additional Information 3: 1344
Additional Information 4: 875fa2ef9d2bdca96466e8af55d1ae6e

This is extremely annoying. Its disturbing that Microsoft has released this
OS in this shape. I have found other bugs as well, but up until now I have
found solutions in this forum.
 
**Warning** if you do not have a solution, or are not smart enough to
understand, do not answer this post**
Click to expand...


Well that's a very friendly approach. It totally precludes anyone from
making constructive suggestions.

Good luck.


Jim
 
I don't understand. I don't have a solution but couldn't the OP just
reboot? or restart the stopped rundll? or buy Ubuntu?

Dale
 
Hi Jon,

The exception code (c0000005) indicates a driver problem. Which one is
another issue. Have you installed any third party software, including
antivirus software? Also, did this problem start immediately after finishing
setup? The first time you did this? Or did it start after some use of the
system? As this probelm does not occur with every Vista user, it is
something about your setup (could be hardware or software) that is the
problem.

--
Best of Luck,

Rick Rogers, aka "Nutcase" - Microsoft MVP

Windows help - www.rickrogers.org
 
Look, all I am trying to do is raise awareness here that Vista Ultimate has
a serious error. I posted the complete error here for anyone qualified that
might offer some insight. I wanted to eliminate garbage responses, no
offense intended
 
Jim: Thans for a worthless response. I am ignoring you. Please do not
respond to my reply.
 
I take it, from the fact that you didn't specifically forbid me from
responding, that only Jim has been grounded?

Dale
 
Hi Jon,

So you have mentioned two compatibility problems.

1) One Care is a beta that may cause all sorts of issues. That's why it's
still a beta product.

2) Nero software contains many drivers and services that run, even if the
software itself is not in use. It may be that it is Vista compatible, but
not compatible with something else on the system (like the above mentioned
One Care beta software).

Could be one of these, could be something else that you've installed.
Resolving driver errors is not easy, does anything show in the event viewer
to indicate a module in use at the time of the error? Have you tried running
the driver verifier?

--
Best of Luck,

Rick Rogers, aka "Nutcase" - Microsoft MVP

Windows help - www.rickrogers.org
 
Update: I am not directly emptying the recycle bin, to be exact. What I did
was create a folder for nero called 'Nero Temp Files'. The program then
outputs temp files when burning a disk to the said folder. The error appears
when I select all items in the temp folder and attempt to send it to the
recycle bin. No matter how many times you try and remove the error it
reappears until the folder is empty. It actually does not reappear. I can
empy the actual recycle bin with no errors, just to clarify the issue. I
assigned this temp file I created within the program defaults. Its apparent
this has to do with windows and the APP colliding.
 
That, Jon, tells me that some function of the program is still active as the
program has a claim on those files. It may be that the application isn't
terminating fully, going into a "standby" mode, or a service that supports
it is active. In any case, there is probably some handle on those files that
hasn't released, and is the cause of the error.

--
Best of Luck,

Rick Rogers, aka "Nutcase" - Microsoft MVP

Windows help - www.rickrogers.org
 
I haven't decided how to deal with it., as I must dump the contents of the
Temp folder periodically.
 
Ah... perhaps, next time, be more exact when describing your issue. That may
facilitate finding an answer to same issue and avoid silly back-and-forths
based on misinformation. And you might throttle back some on the
"**Warning** if you do not have a solution, or are not smart enough to
understand, do not answer this post**" stuff... Kinda hard to "understand"
an issue if it's not presented exactly.

Lang
 
Back
Top