« previous next »
Pages: [1] 2 3   Go Down

Author Topic: Crash-Reports from DebugDLL: Who gets them?  (Read 995 times)

0 Members and 1 Guest are viewing this topic.

Offline Stahlseele

  • Living Legend
  • *******
  • Posts: 4114
  • Karma: 43
  • 2nd Level TechSupport Agent(BOFH)
Crash-Reports from DebugDLL: Who gets them?
« on: July 09, 2011, 09:10:10 PM »
I have a prety frustrating Problem with my brand new shiney gaming laptop, that i get CTD immediately after spawning . . maximum time was 10 seconds in game before it deposited me on my desktop again in less than one second . .
No error message from windumb either, just like switching between two windows in explorer . .
I have sent several CrashReportings by now, i have completely reinstalled Crysis Wars, patched, and installed MWLL . .
I can connect just fine, as long as i spectate nothing is wrong either . .
I would like to know if somebody who gets the crash reports could take a look at them and tell me what's causing it . .
Or maybe even, how to stop this from happening <.<
I have put the Laptop System-Specs and my Nickname Stahlseele into the comment box . .
Logged
'any kind of discussion of randomness ALWAYS WILL EQUATE to being able to critically hit a mech's reactor by firing a micro beam laser while facing 80 degrees to the side, shooting the ground, which would cause a random explosion which would randomly crit his entire team's reactors which would randomly cause the server itself to explode which would randomly generate a strange quark which would randomly hit the earth and randomly randomness randomfapp the shit fapp random!'
------------------------------
CPU: Intel Core 2 Quad Q9650 @4x3GHz
Memory: GSkill 2x4Gb DDR3 1333Mhz
Video: MSI N580GTX Lightning Xtreme Edition 3072MB
HDD: 2xWD Velociraptor74Gig10k RPM SATA  RAID0; 1x WD Caviar Black 1TB, 1x WD Caviar Green 2TB
Monitor: 2x24" Widescreen 16:9 1920x1080 native resolution
Windows Vista

Offline ShdNx

  • Lead Developer
  • Lance Sergeant
  • *
  • Posts: 356
  • Karma: 26
  • 0x2B || !0x2B
Re: Crash-Reports from DebugDLL: Who gets them?
« Reply #1 on: July 09, 2011, 11:01:11 PM »
We have received 3 crash reports from you recently. Our programmers will look into them once they have time.

I'm afraid we can't tell you much else at this point. I'm sorry for your inconvenience.
Logged
External tools lead developer

Klingon Programmer:
Quote
What is this talk of release? Klingons do not release software. Our software escapes leaving a bloody trail of designers and quality assurance people in its wake.
(Stackoverflow.com)

Offline Stahlseele

  • Living Legend
  • *******
  • Posts: 4114
  • Karma: 43
  • 2nd Level TechSupport Agent(BOFH)
Re: Crash-Reports from DebugDLL: Who gets them?
« Reply #2 on: July 10, 2011, 12:28:39 AM »
Quote from: (TLL)ShdNx on July 09, 2011, 11:01:11 PM
We have received 3 crash reports from you recently. Our programmers will look into them once they have time.

I'm afraid we can't tell you much else at this point. I'm sorry for your inconvenience.
i ain't asking for more, i can't code or do other modding stuff worth shit, else i would have chipped in . .
Logged
'any kind of discussion of randomness ALWAYS WILL EQUATE to being able to critically hit a mech's reactor by firing a micro beam laser while facing 80 degrees to the side, shooting the ground, which would cause a random explosion which would randomly crit his entire team's reactors which would randomly cause the server itself to explode which would randomly generate a strange quark which would randomly hit the earth and randomly randomness randomfapp the shit fapp random!'
------------------------------
CPU: Intel Core 2 Quad Q9650 @4x3GHz
Memory: GSkill 2x4Gb DDR3 1333Mhz
Video: MSI N580GTX Lightning Xtreme Edition 3072MB
HDD: 2xWD Velociraptor74Gig10k RPM SATA  RAID0; 1x WD Caviar Black 1TB, 1x WD Caviar Green 2TB
Monitor: 2x24" Widescreen 16:9 1920x1080 native resolution
Windows Vista

Offline Ingrater

  • MWLL Lead Coder
  • Project Director
  • Star Captain
  • *
  • Posts: 1116
  • Karma: 103
Re: Crash-Reports from DebugDLL: Who gets them?
« Reply #3 on: July 10, 2011, 07:43:03 PM »
Your first crash was due to your graphics driver crashing: nvwgfx2umx.dll
Your second crash was due to a bug in our game code that is already fixed in the alpha version. This fix will be included in 0.5.2
Your third crash is the same as the second one. (This only happens if you use mech jump jets)
Logged
There comes a point where the talking must stop, and people have to do actual work.

Offline Stahlseele

  • Living Legend
  • *******
  • Posts: 4114
  • Karma: 43
  • 2nd Level TechSupport Agent(BOFH)
Re: Crash-Reports from DebugDLL: Who gets them?
« Reply #4 on: July 10, 2011, 08:03:38 PM »
I don't use mechs, that can't be it, if BA jumpjets don't count too . .
Logged
'any kind of discussion of randomness ALWAYS WILL EQUATE to being able to critically hit a mech's reactor by firing a micro beam laser while facing 80 degrees to the side, shooting the ground, which would cause a random explosion which would randomly crit his entire team's reactors which would randomly cause the server itself to explode which would randomly generate a strange quark which would randomly hit the earth and randomly randomness randomfapp the shit fapp random!'
------------------------------
CPU: Intel Core 2 Quad Q9650 @4x3GHz
Memory: GSkill 2x4Gb DDR3 1333Mhz
Video: MSI N580GTX Lightning Xtreme Edition 3072MB
HDD: 2xWD Velociraptor74Gig10k RPM SATA  RAID0; 1x WD Caviar Black 1TB, 1x WD Caviar Green 2TB
Monitor: 2x24" Widescreen 16:9 1920x1080 native resolution
Windows Vista

Offline Ingrater

  • MWLL Lead Coder
  • Project Director
  • Star Captain
  • *
  • Posts: 1116
  • Karma: 103
Re: Crash-Reports from DebugDLL: Who gets them?
« Reply #5 on: July 10, 2011, 08:20:43 PM »
They count too, as a workaround just stop using jumpjets  ;D
Logged
There comes a point where the talking must stop, and people have to do actual work.

Offline Stahlseele

  • Living Legend
  • *******
  • Posts: 4114
  • Karma: 43
  • 2nd Level TechSupport Agent(BOFH)
Re: Crash-Reports from DebugDLL: Who gets them?
« Reply #6 on: July 10, 2011, 10:58:50 PM »
Quote from: Ingrater on July 10, 2011, 08:20:43 PM
They count too, as a workaround just stop using jumpjets  ;D
boooh! ;_;
just out of curiosity, if it can be explained so that someone as dumb as me can understand it:
why does this happen on the laptop, but not on the big rig? O.o
Logged
'any kind of discussion of randomness ALWAYS WILL EQUATE to being able to critically hit a mech's reactor by firing a micro beam laser while facing 80 degrees to the side, shooting the ground, which would cause a random explosion which would randomly crit his entire team's reactors which would randomly cause the server itself to explode which would randomly generate a strange quark which would randomly hit the earth and randomly randomness randomfapp the shit fapp random!'
------------------------------
CPU: Intel Core 2 Quad Q9650 @4x3GHz
Memory: GSkill 2x4Gb DDR3 1333Mhz
Video: MSI N580GTX Lightning Xtreme Edition 3072MB
HDD: 2xWD Velociraptor74Gig10k RPM SATA  RAID0; 1x WD Caviar Black 1TB, 1x WD Caviar Green 2TB
Monitor: 2x24" Widescreen 16:9 1920x1080 native resolution
Windows Vista

Offline Ingrater

  • MWLL Lead Coder
  • Project Director
  • Star Captain
  • *
  • Posts: 1116
  • Karma: 103
Re: Crash-Reports from DebugDLL: Who gets them?
« Reply #7 on: July 11, 2011, 11:23:56 AM »
Most likely because your laptop sound card can not handle as much sounds as your pc can. This results in the crash.
Logged
There comes a point where the talking must stop, and people have to do actual work.

Offline thEClaw

  • Star Captain
  • ***
  • Posts: 818
  • Karma: 52
  • Retreating...
Re: Crash-Reports from DebugDLL: Who gets them?
« Reply #8 on: July 11, 2011, 11:58:36 AM »
There is one thing i would like to ask: What is the user supposed to write in the comments-section of the bug-report? Without any kind of clue or hint, i am always sitting there frowning, not knowing what to fill into that box. How about a little explanation what kind of information you would like to see and what could be considered useful? (in the report-window itself, i mean)
Logged
Read out weapons/vehicle stats (by Hiruma Kai)
Drop Calculator (by Snyp3r)
Edit your weapon-groups outside of MWLL (by me and Az)
Create random drop-lists (by me and, involuntarily, Az)

Offline Stahlseele

  • Living Legend
  • *******
  • Posts: 4114
  • Karma: 43
  • 2nd Level TechSupport Agent(BOFH)
Re: Crash-Reports from DebugDLL: Who gets them?
« Reply #9 on: July 11, 2011, 12:32:45 PM »
what you were doing when the crash occured.
what kind of asset you were using when the crash occured.
where you were when the crash occured.
what kind of OS you are using the mod on.
what kind of hardware you are using.
Logged
'any kind of discussion of randomness ALWAYS WILL EQUATE to being able to critically hit a mech's reactor by firing a micro beam laser while facing 80 degrees to the side, shooting the ground, which would cause a random explosion which would randomly crit his entire team's reactors which would randomly cause the server itself to explode which would randomly generate a strange quark which would randomly hit the earth and randomly randomness randomfapp the shit fapp random!'
------------------------------
CPU: Intel Core 2 Quad Q9650 @4x3GHz
Memory: GSkill 2x4Gb DDR3 1333Mhz
Video: MSI N580GTX Lightning Xtreme Edition 3072MB
HDD: 2xWD Velociraptor74Gig10k RPM SATA  RAID0; 1x WD Caviar Black 1TB, 1x WD Caviar Green 2TB
Monitor: 2x24" Widescreen 16:9 1920x1080 native resolution
Windows Vista

Offline Ingrater

  • MWLL Lead Coder
  • Project Director
  • Star Captain
  • *
  • Posts: 1116
  • Karma: 103
Re: Crash-Reports from DebugDLL: Who gets them?
« Reply #10 on: July 11, 2011, 12:49:06 PM »
It's really hard to say what to fill in there. Basically what Stahlseele said. Depending on the kind of crash you had other information is interresting. For example when you crash inside a huit, it's interresting if you were shooting or if you just have been driving around. Really depends on the crash, Just give as much additional information as you can.
Logged
There comes a point where the talking must stop, and people have to do actual work.

Offline Stahlseele

  • Living Legend
  • *******
  • Posts: 4114
  • Karma: 43
  • 2nd Level TechSupport Agent(BOFH)
Re: Crash-Reports from DebugDLL: Who gets them?
« Reply #11 on: July 11, 2011, 01:59:55 PM »
Quote from: Ingrater on July 11, 2011, 11:23:56 AM
Most likely because your laptop sound card can not handle as much sounds as your pc can. This results in the crash.
so . . autoexec.cfg with s_maxchannels=96 could maybe fix it?
Logged
'any kind of discussion of randomness ALWAYS WILL EQUATE to being able to critically hit a mech's reactor by firing a micro beam laser while facing 80 degrees to the side, shooting the ground, which would cause a random explosion which would randomly crit his entire team's reactors which would randomly cause the server itself to explode which would randomly generate a strange quark which would randomly hit the earth and randomly randomness randomfapp the shit fapp random!'
------------------------------
CPU: Intel Core 2 Quad Q9650 @4x3GHz
Memory: GSkill 2x4Gb DDR3 1333Mhz
Video: MSI N580GTX Lightning Xtreme Edition 3072MB
HDD: 2xWD Velociraptor74Gig10k RPM SATA  RAID0; 1x WD Caviar Black 1TB, 1x WD Caviar Green 2TB
Monitor: 2x24" Widescreen 16:9 1920x1080 native resolution
Windows Vista

Offline Ingrater

  • MWLL Lead Coder
  • Project Director
  • Star Captain
  • *
  • Posts: 1116
  • Karma: 103
Re: Crash-Reports from DebugDLL: Who gets them?
« Reply #12 on: July 11, 2011, 02:04:02 PM »
Yes maybe, if your soundcard can actually handle 96 channels. If you only put it into the autoexec.cfg and your soundcard can't do it, it won't help.
Logged
There comes a point where the talking must stop, and people have to do actual work.

Offline Stahlseele

  • Living Legend
  • *******
  • Posts: 4114
  • Karma: 43
  • 2nd Level TechSupport Agent(BOFH)
Re: Crash-Reports from DebugDLL: Who gets them?
« Reply #13 on: July 11, 2011, 02:13:12 PM »
Quote from: Ingrater on July 11, 2011, 02:04:02 PM
Yes maybe, if your soundcard can actually handle 96 channels. If you only put it into the autoexec.cfg and your soundcard can't do it, it won't help.
I do Tech-Support, Try and Error is my default modus operandi . .
just wondering why it worked for some days and then suddenly it doesn't anymore <.<
« Last Edit: July 11, 2011, 02:40:36 PM by Stahlseele »
Logged
'any kind of discussion of randomness ALWAYS WILL EQUATE to being able to critically hit a mech's reactor by firing a micro beam laser while facing 80 degrees to the side, shooting the ground, which would cause a random explosion which would randomly crit his entire team's reactors which would randomly cause the server itself to explode which would randomly generate a strange quark which would randomly hit the earth and randomly randomness randomfapp the shit fapp random!'
------------------------------
CPU: Intel Core 2 Quad Q9650 @4x3GHz
Memory: GSkill 2x4Gb DDR3 1333Mhz
Video: MSI N580GTX Lightning Xtreme Edition 3072MB
HDD: 2xWD Velociraptor74Gig10k RPM SATA  RAID0; 1x WD Caviar Black 1TB, 1x WD Caviar Green 2TB
Monitor: 2x24" Widescreen 16:9 1920x1080 native resolution
Windows Vista

Offline thEClaw

  • Star Captain
  • ***
  • Posts: 818
  • Karma: 52
  • Retreating...
Re: Crash-Reports from DebugDLL: Who gets them?
« Reply #14 on: July 11, 2011, 02:32:28 PM »
Quote from: Ingrater on July 11, 2011, 12:49:06 PM
Basically what Stahlseele said. Depending on the kind of crash you had other information is interresting.
Uhm...i thought the crash-report itself would at least contain some kind of information.
...
It does, right? :P
Logged
Read out weapons/vehicle stats (by Hiruma Kai)
Drop Calculator (by Snyp3r)
Edit your weapon-groups outside of MWLL (by me and Az)
Create random drop-lists (by me and, involuntarily, Az)
Pages: [1] 2 3   Go Up
« previous next »