|
|
Hi for no apparent reason and at any time I am using the computer with
any program Windows XP Pro 64bit stops and the dreaded blue screen
comes up and refers to a file win32k has caused a problem.
Is there a solution to this problem.
Thanks Tony
|
|
What is the error code that you get on the blue screen?
--
Jane, not plain ;) 64 bit enabled :-)
Batteries not included. Braincell on vacation ;-)
MVP Windows Shell/User
<hamsatuk[ at ]hotmail.com> wrote in message
news:vl3r43t5te3cg8vnjl2kg78dtiddd8qmca[ at ]4ax.com...
[Quoted Text] > Hi for no apparent reason and at any time I am using the computer with
> any program Windows XP Pro 64bit stops and the dreaded blue screen
> comes up and refers to a file win32k has caused a problem.
> Is there a solution to this problem.
> Thanks Tony
|
|
On Fri, 18 May 2007 22:13:54 +1000, "Jane C"
<jellybean[ at ]NOSPAMxjgarage.org> wrote:
[Quoted Text] >What is the error code that you get on the blue screen?
Hi Jane it goes off the screen to quick to see the error code, sorry.
Tony
|
|
|
[Quoted Text] >>What is the error code that you get on the blue screen?
> Hi Jane it goes off the screen to quick to see the error code, sorry.
> Tony
Microsoft in its infinite wisdom has decided that the default should now be
to automatically restart whenever the OS crashes, conveniently preventing
you from seeing that useful information.
Go to Control Panel, System, Advanced, Settings (under Startup and
Recovery), and remove the "Automatically restart" checkbox. Then the next
time you'll see the blue screen, it'll stay there instead of just flash and
go away, so you should be able to write down some of that information before
hitting your reset button.
Incidentally, my own XP x64 machine has taken a liking to just crash on me
as well (also caused by win32k.dll), when I'm inserting blank DVDs in my
drive, *and* Nero happens to be running...so predictably in fact, that I've
taken the habit of shutting down Nero before changing any CD (which is then
never a problem)...
|
|
Hello,
that was customer driven response, bring the machine back to a booting
state.<g>
I'ts a prefence thing, some people want it to reboot automatically and some
people don't.
It was changed because of customer feedback.
But you can hit F8 and choose a Safe Mode Option to not reboot the machine
on that next boot.
It will stop on the Blue Screen so you can capture data>
Thanks,
Darrell Gorter[MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights
--------------------
|>From: "Homer J. Simpson" <root[ at ]127.0.0.1>
|>References: <vl3r43t5te3cg8vnjl2kg78dtiddd8qmca[ at ]4ax.com>
<A4238B78-C956-4DA4-B1CE-2BF6DFFC112F[ at ]microsoft.com>
<818r43l00535sk1g5b7gfrhamcurbudfof[ at ]4ax.com>
|>Subject: Re: Problem with Win32k file
|>Date: Fri, 18 May 2007 09:47:17 -0400
|>Lines: 21
|>X-Priority: 3
|>X-MSMail-Priority: Normal
|>X-Newsreader: Microsoft Outlook Express 6.00.3790.3959
|>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.3959
|>X-RFC2646: Format=Flowed; Original
|>Message-ID: <#BBlSMVmHHA.4872[ at ]TK2MSFTNGP03.phx.gbl>
|>Newsgroups: microsoft.public.windows.64bit.general
|>NNTP-Posting-Host: bas8-ottawa23-1177762399.dsl.bell.ca 70.51.58.95
|>Path: TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP03.phx.gbl
|>Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.windows.64bit.general:6715
|>X-Tomcat-NG: microsoft.public.windows.64bit.general
|>
|>>>What is the error code that you get on the blue screen?
|>> Hi Jane it goes off the screen to quick to see the error code, sorry.
|>> Tony
|>
|>Microsoft in its infinite wisdom has decided that the default should now
be
|>to automatically restart whenever the OS crashes, conveniently preventing
|>you from seeing that useful information.
|>
|>Go to Control Panel, System, Advanced, Settings (under Startup and
|>Recovery), and remove the "Automatically restart" checkbox. Then the
next
|>time you'll see the blue screen, it'll stay there instead of just flash
and
|>go away, so you should be able to write down some of that information
before
|>hitting your reset button.
|>
|>Incidentally, my own XP x64 machine has taken a liking to just crash on
me
|>as well (also caused by win32k.dll), when I'm inserting blank DVDs in my
|>drive, *and* Nero happens to be running...so predictably in fact, that
I've
|>taken the habit of shutting down Nero before changing any CD (which is
then
|>never a problem)...
|>
|>
|>
|
|
|
[Quoted Text] > Hello,
> that was customer driven response, bring the machine back to a booting
> state.<g>
Riiiiiiiiiiight. How was the question asked, "would you like to continue
seeing the Blue Screen of Death in the future"?
History indicates that would be the Microsoft thing to do.
|
|
On Fri, 18 May 2007 12:35:11 +0100, hamsatuk[ at ]hotmail.com wrote:
Hi thanks to all who replied and sorry for the delay in replying have
been very busy, any how here is the error codes I am getting.
The first ting is I managed to get XP Pro 64bit back on the disk and
installed the updated Uli SATA drivers also installed SP2 that is all
I have done. The computer will sometimes run for 3 hours with no
problem then if you turn it on the next day problems, so as requested
here are the error codes I have received.
0x000000D1 ref tcpip.sys 0x0000003B ref win32k.sys both were
followed by a physical memory dump 0x0000007E was the most frequent
error but did not referee to any particular reasons. plus the
following 0x00000024, 0x0000001E. I feel it has to be hardware so the
following have been checked.
1. SATA drive replaced with IDE drive same problems
2. Memory removed, cleaned and swooped and tried in single 512k
strips, same problem.
3. Changed the power supply, no different.
All that is left is the m/board and processor. I have tried various
diagnostic software booted at startup and none have given any negative
results except with regards to the processor (AMD Athlon 64bit) which
was a Segmentation Fault but not sure if this was due to the software
not being suitable. It has also stoped at the welcom screen and the
screen has gone blank with no messages as to why.
The motherboard is a Jetway A210GDMS, a Maxtor SATA drive and the
onboard graphice has been replaced by a Nvidia GeForce 7100GS.
I hope this info will jelp you all to shed some light on my problem
othe wise it will ba a trip the my local computer store
[Quoted Text] >Hi for no apparent reason and at any time I am using the computer with
>any program Windows XP Pro 64bit stops and the dreaded blue screen
>comes up and refers to a file win32k has caused a problem.
>Is there a solution to this problem.
>Thanks Tony
|
|
You can check this:
http://support.microsoft.com/?kbid=330182&sd=RMVP
(just a stab in darkness)
Did you flash your BIOS?
Did you try and download the SATA drivers again, since they are 'Floppy
born', they are wulnerable to all kinds of corruption.
Just changing the PSU wouldn't necessarily uncover any of the issues that
comes with poorer quality, you should make sure that your PSU is First Class
or very nearly that.
Troubleshooting errors like these could keep you occupied for a long time,
depending on the age of your machine and the relative cheapness of MB's
these days, a new one might not be a bad idea at all. On the other hand, you
could lay out the specs for a completely new machine for the OS and see if
the present one is running XP Home in a reliable fashion and let it trickle
down the generation gap.
Tony. . .
"Tony" <hamsatuk[ at ]hotmail.com> wrote in message
news:2nec731pjtbh5nimr7vclpsdh2dddfpsrd[ at ]4ax.com...
[Quoted Text] > On Fri, 18 May 2007 12:35:11 +0100, hamsatuk[ at ]hotmail.com wrote:
>
> Hi thanks to all who replied and sorry for the delay in replying have
> been very busy, any how here is the error codes I am getting.
> The first ting is I managed to get XP Pro 64bit back on the disk and
> installed the updated Uli SATA drivers also installed SP2 that is all
> I have done. The computer will sometimes run for 3 hours with no
> problem then if you turn it on the next day problems, so as requested
> here are the error codes I have received.
> 0x000000D1 ref tcpip.sys 0x0000003B ref win32k.sys both were
> followed by a physical memory dump 0x0000007E was the most frequent
> error but did not referee to any particular reasons. plus the
> following 0x00000024, 0x0000001E. I feel it has to be hardware so the
> following have been checked.
> 1. SATA drive replaced with IDE drive same problems
> 2. Memory removed, cleaned and swooped and tried in single 512k
> strips, same problem.
> 3. Changed the power supply, no different.
> All that is left is the m/board and processor. I have tried various
> diagnostic software booted at startup and none have given any negative
> results except with regards to the processor (AMD Athlon 64bit) which
> was a Segmentation Fault but not sure if this was due to the software
> not being suitable. It has also stoped at the welcom screen and the
> screen has gone blank with no messages as to why.
> The motherboard is a Jetway A210GDMS, a Maxtor SATA drive and the
> onboard graphice has been replaced by a Nvidia GeForce 7100GS.
> I hope this info will jelp you all to shed some light on my problem
> othe wise it will ba a trip the my local computer store
> >Hi for no apparent reason and at any time I am using the computer with
> >any program Windows XP Pro 64bit stops and the dreaded blue screen
> >comes up and refers to a file win32k has caused a problem.
> >Is there a solution to this problem.
> >Thanks Tony
|
|
|