[FAQ] PC auto restart/Blue Screen (BSOD)

Lowyat.NET forums

Lowyat.NET Kopitiam Garage Sales

Lowyat.NET Rules and Regulations FAQ Help Search Members

Welcome Guest ( Log In | Register )

Lowyat.NET -> Technical Support

Bump Topic Add Reply RSS Feed

Outline · [ Standard ] · Linear+

[FAQ] PC auto restart/Blue Screen (BSOD), All questions go here please.

views

yanouchi	Mar 10 2009, 11:22 AM Return to original view \| Post #1
Getting Started Junior Member 89 posts Joined: Aug 2005 From: Kota Bharu	Elop there, i'm having BSOD from sysdata.xml. Here is my dump file, hope anyone will help me... Keep restart pc everytime i want to click like recyle bin, my computer n etc.... Heres my win debuggers result..kinda newbie in this thing, thanks... » Click to show Spoiler - click again to hide... « Microsoft ® Windows Debugger Version 6.11.0001.404 X86 Copyright © Microsoft Corporation. All rights reserved. Loading Dump File [C:\WINDOWS\Minidump\Mini031009-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRVc:\websymbolshttp://msdl.microsoft.com/download/symbols Executable search path is: 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 Machine Name: Kernel base = 0x804d7000 PsLoadedModuleList = 0x805624a0 Debug session time: Tue Mar 10 06:38:54.625 2009 (GMT+8) System Uptime: 0 days 0:03:28.359 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 1000008E, {c0000005, 80550ae2, b6054944, 0} * Kernel symbols are WRONG. Please fix symbols to do analysis. * WARNING: Unable to verify timestamp for nv4_mini.sys * ERROR: Module load completed but symbols could not be loaded for nv4_mini.sys ********************************************************************* * * * * * 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 * * * ********************************************************************* ********************************************************************* * * * * * 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 : nv4_mini.sys ( nv4_mini+50fd00 ) Followup: MachineOwner --------- 1: kd> !analyze -v ***************************************************************************** * * * Bugcheck Analysis * * * ***************************************************************************** KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e) This is a very common bugcheck. Usually the exception address pinpoints the driver/function that caused the problem. Always note this address as well as the link date of the driver/image that contains this address. Some common problems are exception code 0x80000003. This means a hard coded breakpoint or assertion was hit, but this system was booted /NODEBUG. This is not supposed to happen as developers should never have hardcoded breakpoints in retail code, but ... If this happens, make sure a debugger gets connected, and the system is booted /DEBUG. This will let us see why this breakpoint is happening. Arguments: Arg1: c0000005, The exception code that was not handled Arg2: 80550ae2, The address that the exception occurred at Arg3: b6054944, Trap Frame Arg4: 00000000 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 * * * ********************************************************************* ********************************************************************* * * * * * 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 * * * ********************************************************************* ADDITIONAL_DEBUG_TEXT: Use '!findthebuild' command to search for the target build information. If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols. FAULTING_MODULE: 804d7000 nt DEBUG_FLR_IMAGE_TIMESTAMP: 45eef5eb EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s". FAULTING_IP: nt+79ae2 80550ae2 893b mov dword ptr [ebx],edi TRAP_FRAME: b6054944 -- (.trap 0xffffffffb6054944) ErrCode = 00000002 eax=e114d6e8 ebx=00000000 ecx=000001ff edx=e114d6e8 esi=8ad5e0a0 edi=00000010 eip=80550ae2 esp=b60549b8 ebp=b60549f8 iopl=0 nv up ei ng nz ac pe cy cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010297 nt+0x79ae2: 80550ae2 893b mov dword ptr [ebx],edi ds:0023:00000000=???????? Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: DRIVER_FAULT BUGCHECK_STR: 0x8E LAST_CONTROL_TRANSFER: from 80550ac7 to 80550ae2 STACK_TEXT: WARNING: Stack unwind information not available. Following frames may be wrong. b60549f8 80550ac7 00000001 b6054b1c 8000000b nt+0x79ae2 b6054a38 805731be e1162008 00000000 00000000 nt+0x79ac7 b6054a5c 80572d55 00000000 00000000 00000000 nt+0x9c1be b6054b38 80573070 00000000 e1fbf190 b6054b90 nt+0x9bd55 b6054b64 805733f4 00000000 e112d520 b6054b90 nt+0x9c070 b6054b94 80573590 b6054bb8 00000000 e1160840 nt+0x9c3f4 b6054c7c 80582402 e1160840 b6054bb8 00000000 nt+0x9c590 b6054d30 80574f22 fffffffe 0000000c 00000001 nt+0xab402 b6054d4c 804dd98f fffffffe 0000000c 00000001 nt+0x9df22 b6054d64 7c90eb94 badb0d00 0420fe58 00000000 nt+0x698f b6054d68 badb0d00 0420fe58 00000000 00000000 0x7c90eb94 b6054d6c 0420fe58 00000000 00000000 00000000 nv4_mini+0x50fd00 b6054d70 00000000 00000000 00000000 00000000 0x420fe58 STACK_COMMAND: kb FOLLOWUP_IP: nv4_mini+50fd00 badb0d00 ?? ??? SYMBOL_STACK_INDEX: b SYMBOL_NAME: nv4_mini+50fd00 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nv4_mini IMAGE_NAME: nv4_mini.sys BUCKET_ID: WRONG_SYMBOLS Followup: MachineOwner --------- This post has been edited by yanouchi: Mar 10 2009, 11:23 AM Attached File(s)** Minidump.zip ( 18.68k ) Number of downloads: 8
Card PM	Report Top Like Quote Reply

yanouchi	Mar 10 2009, 12:53 PM Return to original view \| Post #2
Getting Started Junior Member 89 posts Joined: Aug 2005 From: Kota Bharu	QUOTE(francischuahcw @ Mar 10 2009, 11:29 AM) Hi there, You are having conflicts with your Nvidia driver. Please remove the current version of your driver from your system and download the latest version for your system. Please update the information and status after you install a new version of your Nvidia driver. Thanks and regards. already update new driver...try to update information with WinDBG, its not working..status say Debugee not connected. After restart for new driver no more BSOD
Card PM	Report Top Like Quote Reply

yanouchi	Mar 12 2009, 08:53 PM Return to original view \| Post #3
Getting Started Junior Member 89 posts Joined: Aug 2005 From: Kota Bharu	QUOTE(yanouchi @ Mar 10 2009, 12:53 PM) already update new driver...try to update information with WinDBG, its not working..status say Debugee not connected. After restart for new driver no more BSOD today it got worst....BSOD..i try in safe mode, still BSOD... here the error: IRQL_NOT_LESS_OR_EQUAL after that i try in safe mode, it error like this: nv4_disp.dll i think something with updating the new driver... then after that i try to restart again here the error: PAGE_FAULT_IN_NONPAGE_AREA
Card PM	Report Top Like Quote Reply

yanouchi	Mar 12 2009, 10:21 PM Return to original view \| Post #4
Getting Started Junior Member 89 posts Joined: Aug 2005 From: Kota Bharu	Okay heres the attachment minidump. Right now i'm uninstall the nvidia driver, But the problem still there. Please help...thanks Attached File(s) Minidump.zip ( 197.32k ) Number of downloads: 12
Card PM	Report Top Like Quote Reply

yanouchi	Mar 13 2009, 09:59 PM Return to original view \| Post #5
Getting Started Junior Member 89 posts Joined: Aug 2005 From: Kota Bharu	QUOTE(francischuahcw @ Mar 13 2009, 12:09 AM) A few thing to clarified with me here. Please let me know are you using a PC or a laptop. Above stated is the result from some of your minidump file. From what i can observe here you are having problem on your hardware and it is not your graphic card driver. Instead i would have suspect you are having a faulty motherboard or a defect ram. Some of the minidump file show you have a memory corruption and pointed to the INTEL_CPU_MICROCODE_ZERO which is something related to the processor cache memory. Would suggest you to run memtest86+ to check your RAM for stability. Please do a few round of full test and let me know the outcome of your RAM test before we troubleshoot further. Regards. okay already run the memtest86+, each of ram tested and 4 pcs tested together (3GB), passed all the 8 test. no error. I'm using pc. i found some solution for problem like this such as clean the dust on gc card, use eraser to rub at metal parts ram but still have that serious error message This post has been edited by yanouchi: Mar 14 2009, 07:31 AM
Card PM	Report Top Like Quote Reply

yanouchi	Apr 16 2012, 11:35 AM Return to original view \| Post #6
Getting Started Junior Member 89 posts Joined: Aug 2005 From: Kota Bharu	I have BSOD appeared display error disk.sys. have this problem when: 1. when finish loading at the taskbar (icons) 2. when using utilities software advance system care to clean registry etc 3. i have to restart then back to normal heres my minidump: please help thanks.... This post has been edited by yanouchi: Apr 16 2012, 11:54 AM Attached File(s) Minidump.zip ( 37.32k ) Number of downloads: 6
Card PM	Report Top Like Quote Reply

« Next Oldest · Technical Support · Next Newest »

Add Reply Options

Change to:

0.0241sec

0.30

7 queries

GZIP Disabled
Time is now: 8th December 2025 - 10:23 AM

All Rights Reserved © 2002- 2025 Vijandren Ramadass (~unite against racism~)

Removal Request

Powered by Invision Power Board © 2025 IPS, Inc.