Welcome Guest ( Log In | Join )

Discover the best free computer help!
Learn more about Geeks to Go by taking the tour. Spyware, virus, trojan, fake security or privacy alerts? Read the malware cleaning guide. Want to reply to a topic, start a new one, or remove the advertising? Join today (always free).
      
 
Reply to this topicStart new topic
Windows Logon fatal error on Shut - Blue Screen, Winlogon error at startup refs uxtheme.dll
pearl-28
post Oct 9 2008, 04:06 PM
Post #1


New Member
*
Posts: 2
OS: XP Pro



Can anyone advise me on how to fix this? I am running XP Professional, and have kept current with all my updates except for one which won't take...I don't think that's the problem though. Thanks! Also, is the memory referenced disk memory or RAM?

1. On shutdown, I get the following error dialog
Winlogon.exe application error. Instruction at "ox....." memory at "ox..." etc memory could not be read.

Clicking ok or "cancel to debug" causes a blue screen with message:

Stop c000021a (fatal system error}
The windows logon process terminated unexpectedly -- status code f0xc000005. System shutdown.

I then do a hard shutdown.

2. On startup, I get the error,
Winlogon encountered a problem and needs to close.

Here are the logs:

szAppName : winlogon.exe szAppVer : 0.0.0.0 szModName : uxtheme.dll
szModVer : 6.0.2900.5512 offset : 00001375

C:\DOCUME~1\Trudy\LOCALS~1\Temp\WER6655.dir00\winlogon.exe.mdmp
C:\DOCUME~1\Trudy\LOCALS~1\Temp\WER6655.dir00\appcompat.txt
<?xml version="1.0" encoding="UTF-16"?>
<DATABASE>
<EXE NAME="uxtheme.dll" FILTER="GRABMI_FILTER_THISFILEONLY">
<MATCHING_FILE NAME="uxtheme.dll" SIZE="218624" CHECKSUM="0xDE6A5D8B" BIN_FILE_VERSION="6.0.2900.5512" BIN_PRODUCT_VERSION="6.0.2900.5512" PRODUCT_VERSION="6.00.2900.5512" FILE_DESCRIPTION="Microsoft UxTheme Library" COMPANY_NAME="Microsoft Corporation" PRODUCT_NAME="Microsoft® Windows® Operating System" FILE_VERSION="6.00.2900.5512 (xpsp.080413-2105)" ORIGINAL_FILENAME="UxTheme.dll" INTERNAL_NAME="UxTheme.dll" LEGAL_COPYRIGHT="© Microsoft Corporation. All rights reserved." VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x40004" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0x4533D" LINKER_VERSION="0x50001" UPTO_BIN_FILE_VERSION="6.0.2900.5512" UPTO_BIN_PRODUCT_VERSION="6.0.2900.5512" LINK_DATE="04/14/2008 00:11:10" UPTO_LINK_DATE="04/14/2008 00:11:10" VER_LANGUAGE="English (United States) [0x409]" />
</EXE>
<EXE NAME="kernel32.dll" FILTER="GRABMI_FILTER_THISFILEONLY">
<MATCHING_FILE NAME="kernel32.dll" SIZE="989696" CHECKSUM="0x7D737C09" BIN_FILE_VERSION="5.1.2600.5512" BIN_PRODUCT_VERSION="5.1.2600.5512" PRODUCT_VERSION="5.1.2600.5512" FILE_DESCRIPTION="Windows NT BASE API Client DLL" COMPANY_NAME="Microsoft Corporation" PRODUCT_NAME="Microsoft® Windows® Operating System" FILE_VERSION="5.1.2600.5512 (xpsp.080413-2111)" ORIGINAL_FILENAME="kernel32" INTERNAL_NAME="kernel32" LEGAL_COPYRIGHT="© Microsoft Corporation. All rights reserved." VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x40004" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0xF44A2" LINKER_VERSION="0x50001" UPTO_BIN_FILE_VERSION="5.1.2600.5512" UPTO_BIN_PRODUCT_VERSION="5.1.2600.5512" LINK_DATE="04/14/2008 00:11:24" UPTO_LINK_DATE="04/14/2008 00:11:24" VER_LANGUAGE="English (United States) [0x409]" />
</EXE>
</DATABASE>
Go to the top of the page
 
+Quote Post
happyrock
post Oct 17 2008, 06:33 AM
Post #2


Trusted Tech
Group Icon
Posts: 3,512
OS: xp



QUOTE
is the memory referenced disk memory or RAM?

its ram...


you or a program you tried to install has tried to change themes and visual styles ...
if you know what program it was...start in safe mode and uninstall it...
you can also try system restore...go back at least a week before the problem started...

This post has been edited by happyrock: Oct 17 2008, 06:35 AM
Go to the top of the page
 
+Quote Post
sUBtech
post Oct 17 2008, 08:38 AM
Post #3


GeekU Junior
Group Icon
Posts: 236
OS: Vista Ultimate



Hi there,
If you not mind i would like to assist you on your blue screen issue.
Please follow the below instruction in order for me to assist you on your blue screen issue


Hi there
Please upload your minidump folder here and i will help you to debug and let you know the reason for BSOD.

Looking for minidump file

Go to My Computer and locate C:\Windows\Minidump or C:\Minidump. Once you have the minidump folder, please zipped the whole folder and upload it here (using add attachement function) or other web hosting page mentioned below. Please provide the link to download your file.



No minidump file available!!!How??
Do the following if you did not find your minidump file

(Window XP)
  • Right click at My Computer
  • Go to Properties
  • Look at Advanced tab then go for Startup and Recovery
  • Look at Settings and untick Automatic Restart
  • Make sure that write debugging information is Small Memory Dump (64kb)


(Window Vista)
  • Right click at My Computer
  • Go to Properties
  • Look at Advanced System Properties tab then go for Startup and Recovery
  • Look at Settings and untick Automatic Restart
  • Make sure that write debugging information is Small Memory Dump (64kb)





Thanks
Go to the top of the page
 
+Quote Post

Reply to this topicStart new topic
1 User(s) are reading this topic (1 Guests and 0 Anonymous Users)
0 Members:

 

Collapse

> Similar Topics

    Topic Title Replies / Views Topic Information
No New Posts   3 / 278 30th January 2006 - 06:40 PM
BTPH started - last by Keith
No New Posts   2 / 460 23rd June 2006 - 04:07 PM
froggie2424 started - last by froggie2424
No New Posts   2 / 364 23rd June 2006 - 12:38 AM
Tiyok started - last by Tiyok
No new   33 / 12,400 24th January 2008 - 08:01 PM
icikle started - last by Murray S.

RSS Time is now: 2nd December 2008 - 05:25 PM
Advertisements do not imply our endorsement of that product or service. The forum is run by volunteers who donate their time and expertise. We make every attempt to ensure that the help and advice posted is accurate and will not cause harm to your computer. However, we do not guarantee that they are accurate and they are to be used at your own risk.