AAO25.com

Assist => Feedback & Suggestions => Bug Reports => Topic started by: Koden on Thursday, January 12, 2012, 04:50:49 AM

Title: BSOD when launching an Assist server
Post by: Koden on Thursday, January 12, 2012, 04:50:49 AM

I've happened to have a BSOD when launching an Assist server, right after clicking the "launch" button.

It happened only twice in a week or so, i didn't wrote off the error log code the first time but i did on the 2nd time. It never happened before

Looking on the event monitor i could only find a savedump error report with this code:

0x0000008e (0xc0000046, 0x804fc8f5, 0x8a1716b0, 0x00000000)

Right while i am opening this thread, i tried to restart the Assist25 server but it keeps starting, crashing and shutting down in a loop  ??? it restarted and crashed over 50 times i think...in the end it somehow started and stopped behaving like that, anyway.

Here's the whole memory dump anyway (it's truncated). It's corrupted too -.-''''' useless.

Code: [Select]

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\MEMORY.DMP]
Kernel Complete Dump File: Full address space is available

************************************************************
WARNING: Dump file has been truncated.  Data may be missing.
************************************************************
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:
**************************************************************************
THIS DUMP FILE IS PARTIALLY CORRUPT.
KdDebuggerDataBlock is not present or unreadable.
**************************************************************************
*********************************************************************
* 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 read PsLoadedModuleList
**************************************************************************
THIS DUMP FILE IS PARTIALLY CORRUPT.
KdDebuggerDataBlock is not present or unreadable.
**************************************************************************
KdDebuggerData.KernBase < SystemRangeStart
Windows XP Kernel Version 2600 MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0x00000000 PsLoadedModuleList = 0x8055d720
Debug session time: Thu Jan 12 10:32:59.781 2012 (GMT+4)
System Uptime: 5 days 23:16:47.765
**************************************************************************
THIS DUMP FILE IS PARTIALLY CORRUPT.
KdDebuggerDataBlock is not present or unreadable.
**************************************************************************
*********************************************************************
* 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 read PsLoadedModuleList
**************************************************************************
THIS DUMP FILE IS PARTIALLY CORRUPT.
KdDebuggerDataBlock is not present or unreadable.
**************************************************************************
KdDebuggerData.KernBase < SystemRangeStart
Loading Kernel Symbols
Unable to read PsLoadedModuleList
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
CS descriptor lookup failed
GetContextState failed, 0x80004002
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
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 8E, {c0000046, 804fc8f5, 8a1716b0, 0}

***** 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
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
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 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
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002


Title: Re: BSOD when launching an Assist server
Post by: Jonnym on Thursday, January 12, 2012, 05:23:55 AM

Do BSOD still exist? have'nt seen one for years, My humble apps to does not run on a low enough level to cause a bsod, It could possibly a fault in the actual server.exe. Not witin our control.

Title: Re: BSOD when launching an Assist server
Post by: Koden on Thursday, January 12, 2012, 05:39:14 AM

Quote from: Jonnym on Thursday, January 12, 2012, 05:23:55 AM

Do BSOD still exist? have'nt seen one for years, My humble apps to does not run on a low enough level to cause a bsod, It could possibly a fault in the actual server.exe. Not witin our control.

Oh, ok then. Anyway, yep Bsod's still exists lol.

Title: Re: BSOD when launching an Assist server
Post by: Koden on Thursday, January 12, 2012, 07:18:54 AM

Quote from: Major-Skrewup on Thursday, January 12, 2012, 06:12:00 AM

last time I got a bsod, was the last time. did u try the repair? to fix anything that mind be ever so slightly fucked Skrewed? I got mod powers to lock these topics when the issues had been addressed and I'm just dieing to lock one to show spanky I'm adequate at foruming. So just give me the word and it'll be done

lol, sure you can lock. Nothing much else to say according to what Jonny says.

Try to lock and unlock too :P  ;D

Title: Re: BSOD when launching an Assist server
Post by: Spanky on Thursday, January 12, 2012, 13:45:10 PM

Did a quick Google, some people with that BSOD had issues with the AMD graphics drivers. I would say try to update your drivers to the latest versions. FileHippo Update Checker works good for programs and some graphics drivers. Short of that, I would say hardware issues. Run Memtest for 2 passes and Prime95 overnight on blend. If either BSOD's or shows errors, then it's your hardware.

Title: Re: BSOD when launching an Assist server
Post by: Jared on Thursday, January 12, 2012, 13:46:12 PM

Check your ram

Title: Re: BSOD when launching an Assist server
Post by: Koden on Thursday, January 12, 2012, 14:19:15 PM

Quote from: Spanky on Thursday, January 12, 2012, 13:45:10 PM

Did a quick Google, some people with that BSOD had issues with the AMD graphics drivers. I would say try to update your drivers to the latest versions. FileHippo Update Checker works good for programs and some graphics drivers. Short of that, I would say hardware issues. Run Memtest for 2 passes and Prime95 overnight on blend. If either BSOD's or shows errors, then it's your hardware.

I'll try a Memtest run, anyway i never experienced BSODs aside of very specific software (i used to have BSODs and CTD with the very first versions of AA3, but back then it was a truly mess of coding).

I'm running on Nvidia btw (little HD4200 integrated under the bonnet, only if the Nvidia burns into flames).

Title: Re: BSOD when launching an Assist server
Post by: Spanky on Thursday, January 12, 2012, 14:42:44 PM

Quote from: Koden on Thursday, January 12, 2012, 14:19:15 PM

I'm running on Nvidia btw (little HD4200 integrated under the bonnet, only if the Nvidia burns into flames).

Did you disable the onboard ATI in the BIOS?

Title: Re: BSOD when launching an Assist server
Post by: Koden on Thursday, January 12, 2012, 16:17:04 PM

Quote from: Spanky on Thursday, January 12, 2012, 14:42:44 PM

Did you disable the onboard ATI in the BIOS?

Yep, cleaned up the drivers before installing the Nvidia ones too.