I have problem with BSOD. My computer offten restart and I losse my data.
I read in BSOD that I have problem with APC info Mismatch.
Here is output from Winddbg:
Code:Microsoft (R) Windows Debugger Version 6.11.0001.404 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\Minidump\Mini032911-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 \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2 *** WARNING: Unable to verify timestamp for ntkrnlpa.exe *** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe Windows Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (2 procs) Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Personal Machine Name: Kernel base = 0x83a01000 PsLoadedModuleList = 0x83b18c70 Debug session time: Tue Mar 29 22:20:59.171 2011 (GMT+2) System Uptime: 1 days 23:19:30.475 ********************************************************************* * 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 \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2 *** WARNING: Unable to verify timestamp for ntkrnlpa.exe *** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe Loading Kernel Symbols ............................................................... ................................................................ ............................................................... Loading User Symbols Loading unloaded module list ............. Unable to load image \SystemRoot\System32\Drivers\Ntfs.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for Ntfs.sys *** ERROR: Module load completed but symbols could not be loaded for Ntfs.sys ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 24, {1904aa, d8b698bc, d8b695b8, 83abe3d7} *** WARNING: Unable to verify timestamp for fltmgr.sys *** ERROR: Module load completed but symbols could not be loaded for fltmgr.sys *** WARNING: Unable to verify timestamp for AsDsm.sys *** ERROR: Module load completed but symbols could not be loaded for AsDsm.sys *** WARNING: Unable to verify timestamp for eamon.sys *** ERROR: Module load completed but symbols could not be loaded for eamon.sys ***** 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 *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** 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 *** *** *** ************************************************************************* ********************************************************************* * 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+ * ********************************************************************* ********************************************************************* * 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+ * ********************************************************************* Probably caused by : Ntfs.sys ( Ntfs+1122f ) Followup: MachineOwner ---------
BSOD - APC info Mismatch,Mini032911-01
- 03 Apr 2011 #1My System Specs
BSOD - APC info Mismatch,Mini032911-01
- 03 Apr 2011 #2
Senior Member
My System SpecsRe: BSOD - APC info Mismatch,Mini032911-01
Hello and welcome to the forum.
This will get you started...
BSOD - Debugging a BSOD in Vista
This is the instructions on how to upload your BSOD files.
Blue Screen of Death (BSOD) Posting Instructions
- 03 Apr 2011 #3
Senior Member
My System SpecsRe: BSOD - APC info Mismatch,Mini032911-01
Hello I have forwared your Post to one of the forums experts on BSOD, they will be getting back to you.
- 03 Apr 2011 #4My System Specs
Re: BSOD - APC info Mismatch,Mini032911-01
All I can tell from that report is that ESET 2009 was blamed; update to the latest version: Best Free Antivirus Software Trial: Free Home, Business and Gaming Download from ESET
Also provide the BSOD report previously asked for: Blue Screen of Death (BSOD) Posting Instructions
Reply With Quote
BSOD - APC info Mismatch,Mini032911-01
| Similar Threads | ||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| BSOD problem on hp laptop. info included | zipt | Crashes and Debugging | 8 | 28 Dec 2010 |
| BSOD - INFO 34bit | stephinaki | Crashes and Debugging | 9 | 12 Dec 2010 |
| Is there a log file with BSOD information, and what does that info mean? | Anthony | Vista performance & maintenance | 1 | 19 Sep 2008 |
| Inbox mismatch. | Don Pellegrino | Vista mail | 8 | 05 Dec 2007 |
| MD5 Mismatch Error | Biscuit2k | Vista installation & setup | 4 | 14 Jun 2006 |
