I have a Gateway E series Desktop computer with a gateway 21" DFCD monitor.It has been working perfectly for years .The monitor kept nagging me that I could use a higher resolution.Thinking back it probably meant on TV input as it is a HD monitor as well.
Anyway i increased the resolution on the compute to sometihing like 1900 x 1200 (using the computers numbers) but did not change the resolution ,which was at 60 or 75 can't remember now.
It went to black screen and a message "Out of frequency"
I couldn't reboot into safe mode or anything ,just in an endless loop of XP screen ,blue windows is starting and then crash back to start up sequence
I looked up the problem on the Gateway site which recomended changing setting in current control set to 640 x 480 x 60.I took my HD out and hooked it up as a USB drive to another computer.I tried to use various registry programs but finally imported the system hive into regedit ,worked on it and unloaded back to the problem drive.No luck and three weeks later ,after many more "solutions" no working system.
I beleive I damaged a video driver when it crashed as in safe mode I have seen it hang at AGP440 and even after turning that service off it hangs at mup.sys .Which tells me that whatever comes after AGP440 is where the problem is .
Tried once again last nigh and got into MINIDUMP.These are the resullts
Microsoft (R) Windows Debugger Version 6.7.0005.1
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [G:\WINNT\Minidump\Mini061
207-01.dmp
]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: *** Invalid ***
**************************
**********
**********
**********
**********
**********
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
**************************
**********
**********
**********
**********
**********
Executable search path is:
**************************
**********
**********
**********
**********
***
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
**************************
**********
**********
**********
**********
***
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805624a0
Debug session time: Tue Jun 12 15:12:57.187 2007 (GMT-4)
System Uptime: 0 days 0:01:32.859
**************************
**********
**********
**********
**********
***
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
**************************
**********
**********
**********
**********
***
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
..........................
..........
..........
..........
..........
..........
..........
..........
..........
..........
..........
..........
..........
..........
......
Loading User Symbols
Loading unloaded module list
........
**************************
**********
**********
**********
**********
**********
***
* *
* Bugcheck Analysis *
* *
**************************
**********
**********
**********
**********
**********
***
Use !analyze -v to get detailed debugging information.
BugCheck 51, {4, 1, e1035488, 80}
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
**************************
**********
**********
**********
**********
*******
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
**************************
**********
**********
**********
**********
*******
**************************
**********
**********
**********
**********
*******
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
**************************
**********
**********
**********
**********
*******
**************************
**********
**********
**********
**********
*******
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
**************************
**********
**********
**********
**********
*******
**************************
**********
**********
**********
**********
*******
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
**************************
**********
**********
**********
**********
*******
**************************
**********
**********
**********
**********
*******
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
**************************
**********
**********
**********
**********
*******
Probably caused by : ntoskrnl.exe ( nt+6038a )
Followup: MachineOwner
---------
1: kd> !analyze -v
**************************
**********
**********
**********
**********
**********
***
* *
* Bugcheck Analysis *
* *
**************************
**********
**********
**********
**********
**********
***
REGISTRY_ERROR (51)
Something has gone badly wrong with the registry. If a kernel debugger
is available, get a stack trace. It can also indicate that the registry got
an I/O error while trying to read one of its files, so it can be caused by
hardware problems or filesystem corruption.
It may occur due to a failure in a refresh operation, which is used only
in by the security system, and then only when resource limits are encountered.
Arguments:
Arg1: 00000004, (reserved)
Arg2: 00000001, (reserved)
Arg3: e1035488, depends on where Windows bugchecked, may be pointer to hive
Arg4: 00000080, depends on where Windows bugchecked, may be return code of
HvCheckHive if the hive is corrupt.
Debugging Details:
------------------
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
**************************
**********
**********
**********
**********
*******
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
**************************
**********
**********
**********
**********
*******
**************************
**********
**********
**********
**********
*******
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
**************************
**********
**********
**********
**********
*******
**************************
**********
**********
**********
**********
*******
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
**************************
**********
**********
**********
**********
*******
**************************
**********
**********
**********
**********
*******
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
**************************
**********
**********
**********
**********
*******
**************************
**********
**********
**********
**********
*******
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
**************************
**********
**********
**********
**********
*******
MODULE_NAME: nt
FAULTING_MODULE: 804d7000 nt
DEBUG_FLR_IMAGE_TIMESTAMP:
45e54690
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WRONG_SYMBOLS
BUGCHECK_STR: 0x51
LAST_CONTROL_TRANSFER: from 806169a7 to 8053738a
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
a7bdc91c 806169a7 00000051 00000004 00000001 nt+0x6038a
a7bdc940 805930b0 00000002 00000080 cfb38e84 nt+0x13f9a7
a7bdc968 80592926 e1a36b60 02577e80 cfb38e84 nt+0xbc0b0
a7bdc9b8 805719e6 e1a36b60 02577e80 cfb38e84 nt+0xbb926
a7bdcbb0 80571ef1 02577e80 02577e80 897981a8 nt+0x9a9e6
a7bdcc28 8056f2a8 00000010 a7bdcc68 00000040 nt+0x9aef1
a7bdcc7c 80571dbe 00000000 8a39e128 00000101 nt+0x982a8
a7bdcd50 804dd99f 012bf9a0 00020019 012bf8e8 nt+0x9adbe
a7bdcd64 7c90eb94 badb0d00 012bf8d0 00000000 nt+0x699f
a7bdcd68 badb0d00 012bf8d0 00000000 00000000 0x7c90eb94
a7bdcd6c 012bf8d0 00000000 00000000 00000000 0xbadb0d00
a7bdcd70 00000000 00000000 00000000 00000000 0x12bf8d0
STACK_COMMAND: kb
FOLLOWUP_IP:
nt+6038a
8053738a 5d pop ebp
SYMBOL_STACK_INDEX: 0
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: ntoskrnl.exe
SYMBOL_NAME: nt+6038a
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner
---------
Can somebody tell me what this means and how to fix it. gateway said that I could not reinstall the vdeo chip drivers outside of windows.I dowloaded that last update and extracted it ,copied the files to wherever i found their equivalents in WINNT.
I have probably done more damage with all my "fixing" but just want to get my computer back from what appears to me to be a simple crash.
Thanks
Start Free Trial
