Pages: [1] :: one page |
|
Author |
Thread Statistics | Show CCP posts - 0 post(s) |
Etienne Merten
|
Posted - 2006.11.25 15:34:00 -
[1]
KMODE_EXCEPTION_NOT_HANDLED - BLUE SCREEN OF DEATH.
I've filed bug reports on this, and talked to a Bug Hunter about it, and filed a more updated bug report on it.
Warp to a complex or an asteroid belt. Engage the multiple NPC's. As soon as they start targeting, blue screen of death (hard reboot, log server saves nothing). It's an "unknown device driver error" to windows, giving a KMODE_EXCEPTION_NOT_HANDLED message.
I've attached windows dump files, dxdiags, etc.
I know you guys are aware of this one, but wanted to make sure it was still in sight as we approach the rollout on TQ.
I haven't tested missions yet (that's next), but I can't do belt hunting nor complexes at all with this bug and I won't run software that hard reboots my system. Haven't had problems like this in TQ for at least 9-12 months. This one is serious, guys!
Also, I have it happen at other times, harder to pin down. Seems to involve many little session changes overlapping...like trying to engage a cloak before coming out of warp completely, or undocking into a fleet stress test, etc.
PLEASE do NOT launch revelations on TQ before this gets resolved. It's still in build 2.14.27756...will test later builds tomorrow.
Best regards, Eti
|
BBQ
Gallente Suicidal Tendencies Ltd
|
Posted - 2006.11.25 16:26:00 -
[2]
Dont think that its an EvE error.
Blue Screen's are normally caused by driver errors or other kernal mode programs, it is not possible for eve itself to generate a BSOD as it does not have direct access to the parts of windows that can cause a BSOD.
Along with the bluescreen there would have been a reason (long lists of register entries and an address) or file name of the crashing driver, it would be helpfull to put the lower part of the bluescreen here to see what driver generated the crash. ----
God gave us a brain, he also gave us a voice.
Shame some people have yet to connect them.
|
Baleorg
Gallente Guys of Sarcasm
|
Posted - 2006.11.25 16:50:00 -
[3]
Originally by: BBQ it is not possible for eve itself to generate a BSOD as it does not have
sure its possible, add some invalid pointers and there you go ^^ ---
BTW: A GOOD Cache-Cleaner |
Baleorg
Gallente Guys of Sarcasm
|
Posted - 2006.11.25 17:02:00 -
[4]
Originally by: Shigsy My own home made brand of BoB/ASCN sigs \o/
yep.. doesnt work :-> ---
BTW: A GOOD Cache-Cleaner |
Shigsy
Caldari Four Horsemen
|
Posted - 2006.11.25 17:02:00 -
[5]
Try it again but this time with sound turned off.
My own home made brand of BoB/ASCN sigs \o/ |
ChronoLynx
Caldari Federation of Freedom Fighters Executive Outcomes
|
Posted - 2006.11.25 18:56:00 -
[6]
Edited by: ChronoLynx on 25/11/2006 18:56:39 nvm |
Etienne Merten
|
Posted - 2006.11.25 23:19:00 -
[7]
Edited by: Etienne Merten on 25/11/2006 23:23:34 OK, first of all, you tweak network and/or DirectX calls and you sure as heck can cause bluescreens.
Secondly, I did turn sound off, all effects off, turret effects off, minimized all graphics options, full or windowed mode, even went pure new client, default settings.
Third, in the bug report, I added all the windows dump files, including the list of hex register values (always the same, regardless of how I recreated the problem). And if you read above, the device driver is "unknown" because windows can't identify it. I think it might be in the network layer of the new revelations code...but I definitely could be wrong.
Sorry boys, but it IS some invalid call or (more likely) a non-handled exception return (probably assuming some basic dx9 capability on my dx9 card that it doesn't handle right).
BUT, it IS a problem, it IS crashing my system, and I KNOW it's happening to others.
So, if it's NOT happening to you, don't answer (unless you want more details...after reading the second entry on page 10 of the bug thread). If it is, PLEASE answer!
Thanks!
Eti
|
BBQ
Gallente Suicidal Tendencies Ltd
|
Posted - 2006.11.26 00:45:00 -
[8]
Debugged you zip file...
Quote: Microsoft (R) Windows Debugger Version 6.6.0007.5 Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Documents and Settings\Chris\Desktop\me.dmp] Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: C:\WINDOWS\Symbols Executable search path is: Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Kernel base = 0x804d7000 PsLoadedModuleList = 0x805624a0 Debug session time: Mon Nov 6 08:31:58.125 2006 (GMT+0) System Uptime: 0 days 0:18:11.816 Loading Kernel Symbols ............................................................................................................................................ Loading User Symbols Loading unloaded module list .............. Unable to load image ALCXWDM.SYS, Win32 error 2 *** WARNING: Unable to verify timestamp for ALCXWDM.SYS *** ERROR: Module load completed but symbols could not be loaded for ALCXWDM.SYS ******************************************************************************* * * * Bugcheck Analysis * * * *******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007F, {d, 0, 0, 0}
Probably caused by : ALCXWDM.SYS ( ALCXWDM+9e1bc )
Followup: MachineOwner ---------
0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * *******************************************************************************
UNEXPECTED_KERNEL_MODE_TRAP_M (1000007f) This means a trap occurred in kernel mode, and it's a trap of a kind that the kernel isn't allowed to have/catch (bound trap) or that is always instant death (double fault). The first number in the bugcheck params is the number of the trap (8 = double fault, etc) Consult an Intel x86 family manual to learn more about what these traps are. Here is a *portion* of those codes: If kv shows a taskGate use .tss on the part before the colon, then kv. Else if kv shows a trapframe use .trap on that value Else .trap on the appropriate frame will show where the trap was taken (on x86, this will be the ebp that goes with the procedure KiTrap) Endif kb will then show the corrected stack. Arguments: Arg1: 0000000d, EXCEPTION_GP_FAULT Arg2: 00000000 Arg3: 00000000 Arg4: 00000000
Debugging Details: ------------------
BUGCHECK_STR: 0x7f_d
DEFAULT_BUCKET_ID: DRIVER_FAULT
PROCESS_NAME: ExeFile.exe
LAST_CONTROL_TRANSFER: from 891a24a8 to b9fe81bc
STACK_TEXT: WARNING: Stack unwind information not available. Following frames may be wrong. ab9232dc 891a24a8 89185ba0 000801c0 00000001 ALCXWDM+0x9e1bc ab9232e0 89185ba0 000801c0 00000001 00000000 0x891a24a8 ab9232e4 000801c0 00000001 00000000 00000000 0x89185ba0 ab9232e8 00000000 00000000 00000000 00000000 0x801c0
STACK_COMMAND: kb
FOLLOWUP_IP: ALCXWDM+9e1bc b9fe81bc 660f6f27 movdqa xmm4,xmmword ptr [edi]
SYMBOL_STACK_INDEX: 0
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: ALCXWDM
IMAGE_NAME: ALCXWDM.SYS
DEBUG_FLR_IMAGE_TIMESTAMP: 43f59429
SYMBOL_NAME: ALCXWDM+9e1bc
FAILURE_BUCKET_ID: 0x7f_d_ALCXWDM+9e1bc
BUCKET_ID: 0x7f_d_ALCXWDM+9e1bc
Followup: MachineOwner
ALCXWDM.SYS (your sound driver) crashed after being instructed by exefile.exe. I would look for an updated sound driver as that should fix your problem. Your sounddriver is made by Avance Logic. ----
God gave us a brain, he also gave us a voice.
Shame some people have yet to connect them.
|
Hllaxiu
Shiva Morsus Mihi
|
Posted - 2006.11.26 01:01:00 -
[9]
Play without sound like the rest of us. (IIRC a survey was done and over half of eve players have sound turned off) --- Our greatest glory is not in never failing, but in rising up every time we fail. - Emerson |
Baleorg
Gallente Guys of Sarcasm
|
Posted - 2006.11.26 01:12:00 -
[10]
Originally by: Hllaxiu Play without sound like the rest of us. (IIRC a survey was done and over half of eve players have sound turned off)
well iam not the rest.. i play with soudn without probs.. even when running 2 clients ---
BTW: A GOOD Cache-Cleaner |
|
Tutaku
Brutor tribe
|
Posted - 2006.11.26 01:38:00 -
[11]
Originally by: BBQ ALCXWDM.SYS (your sound driver) crashed after being instructed by exefile.exe. I would look for an updated sound driver as that should fix your problem. Your sounddriver is made by Avance Logic.
Same problem I have. While a driver update might work for some, everything about my sytem is shrink-wrap new including its drivers. That plus the fact that running the release build on Tranquility (not to mention everything else in the world) is perfectly fine certainly leaves room for an actual problem with the test build.
|
Gaogan
Gallente Solar Storm Axiom Empire
|
Posted - 2006.11.26 01:46:00 -
[12]
This is very simple. You have a buggy driver and it crashed. Replace it with a new version that isn't buggy. Kernel mode code does not trust user mode code; it must validate every parameter passed to it. Whatever eve is doing to trigger the bug, the bug is in a driver, and CCP isn't going to debug windows crash dumps for you.
|
Etienne Merten
|
Posted - 2006.11.26 02:49:00 -
[13]
Edited by: Etienne Merten on 26/11/2006 02:53:56 Edited by: Etienne Merten on 26/11/2006 02:53:13 Good info...at least now I know which driver it is. The problem is that a) I did play it without the sound enabled and it still happened and b) I have the latest driver (which is 1 year old, but that's the best they have for now) and c) I played online tonight without it happening.
Now, you can blame a buggy driver, or you can test the parameters you're sending to a sound driver against the "standard" soundcards...which I know they do. Obviously someone did...because it seems to be fixed tonight.
I am not going to stop turning in bug reports just because it's an interaction with a driver...buggy driver or not...CCP still needs to know about driver interaction problems and I am willing to bet they want to know.
And yes, I like playing with sound with 2 clients open on my system (which I've been doing for a long time on TQ without this problem).
I do appreciate the debug info and the driver identification. I wish I could afford to upgrade to something newer, but I can't. Will make sure they haven't snuck a new driver for it in the last 2 days...and will send the debug info to them, too! :-)
Cheers BBQ!
(oh and Gaogan, take a chill pill! You sound like Microsoft Support)
|
BBQ
Gallente Suicidal Tendencies Ltd
|
Posted - 2006.11.26 12:09:00 -
[14]
Edited by: BBQ on 26/11/2006 12:12:21 The good thing about AC97 drivers is that all sound is generated by the driver and fed to a control chip that has a common AC97 interface, this means that other peoples drivers may work on your soundchip (but not all as some stop it)
I use a laptop with AC97 sound and it works perfectly using a VIA AC97 driver from windows update, it may well be that you can find another sound driver that works fully with your hardware.
First thing I may suggest is to see if windows update has a driver that works, you need to select it as by default under windows update drivers are not installed if there is an update.
BTW, the crash dump you sent was only the very basic, if the crashes keep happening I would suggest changing the dump mode from Small to Kernal dump as it provides alot more data to analyse. ----
God gave us a brain, he also gave us a voice.
Shame some people have yet to connect them.
|
|
|
|
Pages: [1] :: one page |
First page | Previous page | Next page | Last page |