search

CodeAsm / open-sauce

Automatically exported from code.google.com/p/open-sauce
1 stars 1 forks source link

Exception upon launch #45

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
NOTE: PROVIDE AS MANY DETAILS AS HUMANLY POSSIBLE. We can't read your mind
or your computer's.

What did the Exception Report say (if this was on Windows)? Include Fault
Executable Name and Offset.

Problem signature:
  Problem Event Name:   APPCRASH
  Application Name: haloce.exe
  Application Version:  1.0.9.620
  Application Timestamp:    4ac7faf1
  Fault Module Name:    d3d9.dll
  Fault Module Version: 3.0.3.0
  Fault Module Timestamp:   4f46e19c
  Exception Code:   c0000005
  Exception Offset: 00012aa6
  OS Version:   6.1.7601.2.1.0.256.1
  Locale ID:    1033

What steps will reproduce the problem? If this happened in a command line
program, GIVE US THE COMMAND LINE ARGUMENTS YOU USED!
1.
2.
3.

What is the expected output? What do you see instead?
For Halo: Custom Edition to launch.
A window with the text "Gathering exception data..."

What version of the product are you using? On what operating system?
OpenSauce V3.0.3. Windows 7 Ultimate (32-bit).

Please provide any additional information below. E.g. PC specs

This may be identical to issue 40, don't know. Installed Halo: Combat Evolved, 
then installed Halo: Custom Edition, updated both to v1.09 and installed 
OpenSauce v3.0.3. I've uninstalled and reinstalled OpenSauce several times, 
Halo: Custom Edition runs fine without it installed.

Here are my system specifications:
  Processor: Intel Pentium Dual CPU E2180 @ 2.00GHz 
  Total amount of system memory: 3GB (actually 4GB)
  Display adapter type: Intel G33/G31 Express Chipset Family
  Total available graphics memory: 256 MB
  HDD Space: 74GB

Original issue reported on code.google.com by emberbla...@hotmail.com on 15 May 2012 at 8:07

GoogleCodeExporter commented 8 years ago 
Thanks for creating a different issue ticket for this (and actually including 
details!)

FS, this is crashing in c_gbuffer_system::AllocateResources. Somehow pDevice is 
bad. Didn't we encounter a similar bug with pDevice becoming bad before (in an 
older build)? And not figure out why ;x?

Original comment by kornma...@gmail.com on 16 May 2012 at 5:15

GoogleCodeExporter commented 8 years ago 
Yep, looks the same as issue 22. For some mystical reason the device fails to 
be created due to something OS does when initializing, but after trying to 
debug this for a long time I just can't see why.

I don't know how we can debug this one without having access to the hardware 
with the dev tools installed. Saying that, both have occurred when using Intel 
chipsets so we could try finding someone with an oldish laptop that this repros 
on to remote into and mess up.

Original comment by TheFieryScythe@gmail.com on 16 May 2012 at 6:05

GoogleCodeExporter commented 8 years ago 
[deleted comment]
GoogleCodeExporter commented 8 years ago 
[deleted comment]
GoogleCodeExporter commented 8 years ago 
[deleted comment]
GoogleCodeExporter commented 8 years ago 
Fixed by revision 15209e0ef7c4027ae1463321294ea1e661718253 (329).

Original comment by TheFieryScythe@gmail.com on 8 Jul 2012 at 8:25

GoogleCodeExporter commented 8 years ago

Original comment by TheFieryScythe@gmail.com on 8 Jul 2012 at 8:25