Unknown_Module -windbg
windows debugging dbg Windows 2003 standard sp2 (32bit )crashed (BSOD) I took the memory.dmp file from the server And installed windbg 32 bit in windows 2008 r2 64 bit And downloaded WindowsServer2003-KB933548-v1-x86-symbols-UPD-ENU and extracted to c:\websymbols set symbol path SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols Loading Dump File [C:\Users\test\Desktop\MEMORY.DMP] Kernel Summary Dump File: Only kernel address space is available Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols Executable search path is: Page 1000000 too large to be in the dump file. ************************************************************************** THIS DUMP FILE IS PARTIALLY CORRUPT. KdDebuggerDataBlock is not present or unreadable. ************************************************************************** Page 1000000 too large to be in the dump file. Unable to read PsLoadedModuleList Page 1000000 too large to be in the dump file. ************************************************************************** THIS DUMP FILE IS PARTIALLY CORRUPT. KdDebuggerDataBlock is not present or unreadable. ************************************************************************** KdDebuggerData.KernBase < SystemRangeStart Windows Server 2003 Kernel Version 3790 MP (4 procs) Free x86 compatible Product: Server, suite: TerminalServer SingleUserTS Machine Name: Kernel base = 0x00000000 PsLoadedModuleList = 0x808a6ea8 Debug session time: Sun Nov 27 08:13:37.484 2011 (UTC + 3:00) System Uptime: 158 days 19:39:40.134 Page 1000000 too large to be in the dump file. ************************************************************************** THIS DUMP FILE IS PARTIALLY CORRUPT. KdDebuggerDataBlock is not present or unreadable. ************************************************************************** Page 1000000 too large to be in the dump file. Unable to read PsLoadedModuleList Page 1000000 too large to be in the dump file. ************************************************************************** THIS DUMP FILE IS PARTIALLY CORRUPT. KdDebuggerDataBlock is not present or unreadable. ************************************************************************** KdDebuggerData.KernBase < SystemRangeStart Loading Kernel Symbols Page 1000000 too large to be in the dump file. Unable to read PsLoadedModuleList GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 CS descriptor lookup failed GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 Page 1000000 too large to be in the dump file. GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 Unable to get program counter GetContextState failed, 0x80004002 Unable to get current machine context, HRESULT 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck D1, {2a, d0000002, 0, f755ed35} ***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057. GetContextState failed, 0x80004002 Unable to get current machine context, HRESULT 0x80004002 GetContextState failed, 0x80004002 Unable to read selector for PCR for processor 0 GetContextState failed, 0x80004002 Unable to read selector for PCR for processor 0 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 Unable to get current machine context, HRESULT 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 Unable to get current machine context, HRESULT 0x80004002 GetContextState failed, 0x80004002 Unable to get current machine context, HRESULT 0x80004002 GetContextState failed, 0x80004002 Unable to get current machine context, HRESULT 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 Unable to get current machine context, HRESULT 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 Unable to get current machine context, HRESULT 0x80004002 GetContextState failed, 0x80004002 Unable to get current machine context, HRESULT 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 Unable to get current machine context, HRESULT 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 Unable to get current machine context, HRESULT 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 Unable to get current machine context, HRESULT 0x80004002 GetContextState failed, 0x80004002 Unable to get current machine context, HRESULT 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 Unable to get current machine context, HRESULT 0x80004002 GetContextState failed, 0x80004002 Unable to get current machine context, HRESULT 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 Unable to get current machine context, HRESULT 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 Unable to get current machine context, HRESULT 0x80004002 GetContextState failed, 0x80004002 Unable to get current machine context, HRESULT 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 Unable to get current machine context, HRESULT 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 Unable to get current machine context, HRESULT 0x80004002 GetContextState failed, 0x80004002 Unable to get current machine context, HRESULT 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 Unable to read selector for PCR for processor 0 GetContextState failed, 0x80004002 Unable to read selector for PCR for processor 1 GetContextState failed, 0x80004002 Unable to read selector for PCR for processor 2 GetContextState failed, 0x80004002 Unable to read selector for PCR for processor 3 GetContextState failed, 0x80004002 Unable to read selector for PCR for processor 0 Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE ) Followup: MachineOwner --------- GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 ?: kd> !analyze -v GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 Unable to get program counter GetContextState failed, 0x80004002 Unable to get current machine context, HRESULT 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1) An attempt was made to access a pageable (or completely invalid) address at an interrupt request level (IRQL) that is too high. This is usually caused by drivers using improper addresses. If kernel debugger is available get stack backtrace. Arguments: Arg1: 0000002a, memory referenced Arg2: d0000002, IRQL Arg3: 00000000, value 0 = read operation, 1 = write operation Arg4: f755ed35, address which referenced memory Debugging Details: ------------------ ***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057. GetContextState failed, 0x80004002 Unable to get current machine context, HRESULT 0x80004002 GetContextState failed, 0x80004002 Unable to read selector for PCR for processor 0 GetContextState failed, 0x80004002 Unable to read selector for PCR for processor 0 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 Unable to get current machine context, HRESULT 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 Unable to get current machine context, HRESULT 0x80004002 GetContextState failed, 0x80004002 Unable to get current machine context, HRESULT 0x80004002 GetContextState failed, 0x80004002 Unable to get current machine context, HRESULT 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 Unable to get current machine context, HRESULT 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 Unable to get current machine context, HRESULT 0x80004002 GetContextState failed, 0x80004002 Unable to get current machine context, HRESULT 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 Unable to get current machine context, HRESULT 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 Unable to get current machine context, HRESULT 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 Unable to get current machine context, HRESULT 0x80004002 GetContextState failed, 0x80004002 Unable to get current machine context, HRESULT 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 Unable to get current machine context, HRESULT 0x80004002 GetContextState failed, 0x80004002 Unable to get current machine context, HRESULT 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 Unable to get current machine context, HRESULT 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 Unable to get current machine context, HRESULT 0x80004002 GetContextState failed, 0x80004002 Unable to get current machine context, HRESULT 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 Unable to get current machine context, HRESULT 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 Unable to get current machine context, HRESULT 0x80004002 GetContextState failed, 0x80004002 Unable to get current machine context, HRESULT 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 Unable to read selector for PCR for processor 0 GetContextState failed, 0x80004002 Unable to read selector for PCR for processor 1 GetContextState failed, 0x80004002 Unable to read selector for PCR for processor 2 GetContextState failed, 0x80004002 Unable to read selector for PCR for processor 3 GetContextState failed, 0x80004002 Unable to read selector for PCR for processor 0 READ_ADDRESS: unable to get nt!MmSpecialPoolStart unable to get nt!MmSpecialPoolEnd unable to get MmPageSize (0x0) - probably bad symbols 0000002a CURRENT_IRQL: d0000002 FAULTING_IP: +6ca52faf0388dd34 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 Page 1000000 too large to be in the dump file. Page 1000000 too large to be in the dump file. f755ed35 ?? ??? DEFAULT_BUCKET_ID: DRIVER_FAULT BUGCHECK_STR: 0xD1 STACK_TEXT: GetContextState failed, 0x80004002 Unable to get current machine context, HRESULT 0x80004002 STACK_COMMAND: kb SYMBOL_NAME: ANALYSIS_INCONCLUSIVE FOLLOWUP_NAME: MachineOwner MODULE_NAME: Unknown_Module IMAGE_NAME: Unknown_Image DEBUG_FLR_IMAGE_TIMESTAMP: 0 BUCKET_ID: CORRUPT_MODULELIST Followup: MachineOwner --------- GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002
November 28th, 2011 7:32am

Try to download WinDbg (64 bit) and check. Thanks
Free Windows Admin Tool Kit Click here and download it now
November 28th, 2011 3:56pm

Try to download WinDbg (64 bit) and check. Thanks
November 28th, 2011 11:42pm

i did the same problem
Free Windows Admin Tool Kit Click here and download it now
November 29th, 2011 2:53am

Hello, ************************************************************************** THIS DUMP FILE IS PARTIALLY CORRUPT. KdDebuggerDataBlock is not present or unreadable. ************************************************************************** As you can see, the dump file partially corrupt. For that reason, the errors you see are perfectly normal. Please try analyzing another dump file. Bug Check Code 0xD1: http://msdn.microsoft.com/en-us/library/ff560244(v=VS.85).aspx Please proceed like that and check results: Run msconfig and disable all startup items / services except Microsoft ones Uninstall all unused programs Update all possible drivers Disable all security softwares that you have Once done, check results. You can also contact Microsoft CSS. This posting is provided "AS IS" with no warranties or guarantees , and confers no rights. Microsoft Student Partner 2010 / 2011 Microsoft Certified Professional Microsoft Certified Systems Administrator: Security Microsoft Certified Systems Engineer: Security Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration Microsoft Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration Microsoft Certified Technology Specialist: Windows 7, Configuring Microsoft Certified Technology Specialist: Designing and Providing Volume Licensing Solutions to Large Organizations Microsoft Certified IT Professional: Enterprise Administrator Microsoft Certified IT Professional: Server Administrator Microsoft Certified Trainer
November 29th, 2011 4:52pm

Hi, If no clue can be found, you may contact Microsoft Customer Service and Support (CSS) via telephone so that a dedicated Support Professional can assist with your request. To troubleshoot this kind of kernel crash issue, we need to debug the crashed system dump. Unfortunately, debugging is beyond what we can do in the forum. Please be advised that contacting phone support will be a charged call. To obtain the phone numbers for specific technology request please take a look at the web site listed below: http://support.microsoft.com/default.aspx?scid=fh;EN-US;OfferProPhone#faq607 Regards, Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
Free Windows Admin Tool Kit Click here and download it now
November 30th, 2011 1:35am

Hi, If no clue can be found, you may contact Microsoft Customer Service and Support (CSS) via telephone so that a dedicated Support Professional can assist with your request. To troubleshoot this kind of kernel crash issue, we need to debug the crashed system dump. Unfortunately, debugging is beyond what we can do in the forum. Please be advised that contacting phone support will be a charged call. To obtain the phone numbers for specific technology request please take a look at the web site listed below: http://support.microsoft.com/default.aspx?scid=fh;EN-US;OfferProPhone#faq607 Regards, Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
November 30th, 2011 9:32am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics