search

nic1234 / open-sauce

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

Halo:CE exceptions on open with OS #22

Closed GoogleCodeExporter closed 9 years ago

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

gathering exception data

What steps will reproduce the problem?
1.install open sauce
2.open halo ce
3.

What is the expected output? What do you see instead?
it says "gathering exception data"

What version of the product are you using? On what operating system?
open sauce version 3.0 on windows 7 32-bit

Please provide any additional information below.

My halo version is 01.00.09.0620 i have d3d9.dll and d3d9.pdb in my directory. 
i am running windows 7 32-bit. I have version 1.9. Everything seems to be in 
order. But when i go to open Halo:CE it automatically exceptions

Original issue reported on code.google.com by footsmas...@gmail.com on 22 Jan 2012 at 10:50

GoogleCodeExporter commented 9 years ago 
We need the actual exception details, especially the Fault Executable Name and 
Offset.

Original comment by kornma...@gmail.com on 22 Jan 2012 at 11:04

GoogleCodeExporter commented 9 years ago 
Kornman: this is the exception data that comes with the error.

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.0.0
  Fault Module Timestamp: 4f16444a
  Exception Code: c0000005
  Exception Offset: 000126f6
  OS Version: 6.1.7601.2.1.0.256.49
  Locale ID: 1033

I hope this is what you needed :/.

Original comment by footsmas...@gmail.com on 23 Jan 2012 at 4:19

GoogleCodeExporter commented 9 years ago 
This could be occuring due to the device failing to be reset for some reason. 
My current thought is that the resolution the game is trying to reset to isn't 
supported so the device isn't being created.

Could you try loading the game windowed (or vice-versa) and see if it loads 
then?

Original comment by TheFieryScythe@gmail.com on 23 Jan 2012 at 5:54

GoogleCodeExporter commented 9 years ago 
The result is the same in and out of window mode.

Original comment by footsmas...@gmail.com on 23 Jan 2012 at 6:06

GoogleCodeExporter commented 9 years ago 
Could you try running Halo with this DLL please, drop it in your Halo CE root 
directory and post the Game.debug.log that is created after Halo exceptions. 
The log is created in: C:\Users\*your user*\Documents\My Games\Halo 
CE\OpenSauce\Reports

If there is no debug log then the dll doesn't work which wouldn't be entirely 
unexpected.

NOTE: Do NOT distribute this dll, it has been crippled and is intended for 
debugging purposes ONLY.

Original comment by TheFieryScythe@gmail.com on 23 Jan 2012 at 9:43

Attachments:

GoogleCodeExporter commented 9 years ago 
This is what the debug said

Mon Jan 23 21:34:24 2012

21:34:24 process: haloce.exe
21:34:24 process: ntdll.dll
21:34:24 process: kernel32.dll
21:34:24 process: KERNELBASE.dll
21:34:24 process: USER32.dll
21:34:24 process: GDI32.dll
21:34:24 process: LPK.dll
21:34:24 process: USP10.dll
21:34:24 process: msvcrt.dll
21:34:24 process: ADVAPI32.dll
21:34:24 process: sechost.dll
21:34:24 process: RPCRT4.dll
21:34:24 process: ole32.dll
21:34:24 process: OLEAUT32.dll
21:34:24 process: IMM32.DLL
21:34:24 process: MSCTF.dll
21:34:24 process: strings.dll
21:34:24 process: uxtheme.dll
21:34:24 process: DSOUND.dll
21:34:24 process: WINMM.dll
21:34:24 process: POWRPROF.dll
21:34:24 process: SETUPAPI.dll
21:34:24 process: CFGMGR32.dll
21:34:24 process: DEVOBJ.dll
21:34:24 process: CRYPTBASE.dll
21:34:24 process: CLBCatQ.DLL
21:34:24 process: MMDevApi.dll
21:34:24 process: PROPSYS.dll
21:34:24 process: SHLWAPI.dll
21:34:24 process: wdmaud.drv
21:34:24 process: ksuser.dll
21:34:24 process: AVRT.dll
21:34:24 process: AUDIOSES.DLL
21:34:24 process: msacm32.drv
21:34:24 process: MSACM32.dll
21:34:24 process: midimap.dll
21:34:24 process: dwmapi.dll
21:34:24 process: CRYPTSP.dll
21:34:24 process: rsaenh.dll
21:34:24 process: RpcRtRemote.dll
21:34:24 process: winbrand.dll
21:34:24 process: WINTRUST.dll
21:34:24 process: CRYPT32.dll
21:34:24 process: MSASN1.dll
21:34:24 process: d3d9.dll
21:34:24 process: d3dx9_43.dll
21:34:24 process: WS2_32.dll
21:34:24 process: NSI.dll
21:34:24 process: SHELL32.dll
21:34:24 process: MSVCR90.dll
21:34:24 process: PSAPI.DLL
21:34:24 process: d3d9.dll
21:34:24 process: VERSION.dll
21:34:24 process: d3d8thk.dll
21:34:24 process: profapi.dll
21:34:24 function: Yelo_IDirect3D9::CreateDevice; arg[Adapter]: 0; 
arg[DeviceType]: 1; arg[hFocusWindow]: 0x000F04D8; arg[BehaviorFlags]: 64; 
arg[pPresentationParameters]: 0x0075B780; arg[ppReturnedDeviceInterface]: 
0x006B842C;
21:34:24 presentation_parameters: {BackBufferWidth, 800}; {BackBufferHeight, 
600}; {BackBufferFormat, 0x00000016}; {BackBufferCount, 1}; {MultiSampleType, 
0}; {MultiSampleQuality, 0}; {SwapEffect, 1}; {hDeviceWindow, 0x000F04D8}; 
{Windowed, 0}; {EnableAutoDepthStencil, 1}; {AutoDepthStencilFormat, 
0x0000004B}; {Flags, 0}; {FullScreen_RefreshRateInHz, 60}; 
{PresentationInterval, 1};
21:34:24 function: Yelo_IDirect3DDevice9::Initialize; arg[pDevice]: 0x00000000; 
arg[ppDevice]: 0x0012DC5C;
21:34:24 variable[hr]: 0x8876086C;
21:34:24 dx_component_call[Initialize3D] index: 0
21:34:24 dx_component_call[Initialize3D] index: 1

Original comment by footsmas...@gmail.com on 24 Jan 2012 at 3:35

GoogleCodeExporter commented 9 years ago 
Few things:
1. What graphics card to you have?
2. Install the latest DirectX 
http://www.microsoft.com/download/en/details.aspx?id=35, just to be certain you 
have the latest.
3. Does the game definitely run without OS installed (I don't recall you 
saying)? As the render device is failing to be created, but as far as I can 
tell the arguments for creating it all look reasonable and they are passed 
mostly unchanged from Halo itself.

Original comment by TheFieryScythe@gmail.com on 24 Jan 2012 at 5:29

GoogleCodeExporter commented 9 years ago 
In "device manager" under "Display adapters" all i see is "Mobile Intel(R) 945 
Express Chipset Family" i know my graphics card is pretty weak, which i thought 
might have been my problem.

Original comment by footsmas...@gmail.com on 24 Jan 2012 at 6:59

GoogleCodeExporter commented 9 years ago 
Forgot, i already had the latest version of directX and halo does definitely 
run without OS. And if i take out d3d9.dll it runs fine, like normal.

Original comment by footsmas...@gmail.com on 24 Jan 2012 at 7:02

GoogleCodeExporter commented 9 years ago 
Thankyou for your patience on this issue btw, it's confusing the hell out of 
me! I have another dll for you to run, this time all of OS's systems are 
disabled so I can see if it's something OS is doing before the device is 
created that's causing the problem. If this doesn't exception then I may have 
to ask you to run a number of dll's enabling each system to find the culprit if 
you are ok with that.

This one does not output any debug file btw.

NOTE: Do NOT distribute this dll, it has been crippled and is intended for 
debugging purposes ONLY.

Original comment by TheFieryScythe@gmail.com on 24 Jan 2012 at 10:06

Attachments:

GoogleCodeExporter commented 9 years ago 
Hmm. It down't exception, but i get no video feed, i still hear sound but in  
full screen the screen is just black, and in window mode it's see through. :/

Original comment by footsmas...@gmail.com on 24 Jan 2012 at 10:44

GoogleCodeExporter commented 9 years ago 
It even made sapiens screen completely white. :/

Original comment by footsmas...@gmail.com on 24 Jan 2012 at 10:51

GoogleCodeExporter commented 9 years ago 
Great, thats what I was hoping for :). These builds are intentionally crippled 
so that people dont try to use them, hence no rendering takes place.

This one has just the OS settings and debug enabled. Let me know if this one 
exceptions.

NOTE: Do NOT distribute this dll, it has been crippled and is intended for 
debugging purposes ONLY.

Original comment by TheFieryScythe@gmail.com on 24 Jan 2012 at 11:16

Attachments:

GoogleCodeExporter commented 9 years ago 
No exception, all black with big a white box in the middle.

Original comment by footsmas...@gmail.com on 24 Jan 2012 at 11:23

GoogleCodeExporter commented 9 years ago 
FS, what about setting up *one* DLL which displays a message box before each 
system is setup? This way he can see which system crashes without uploading so 
many test DLLs, possibly?

Or maybe (this will be ugly), setting up a test framework (ruh roh!) which runs 
on an xml config? So you can toggle which systems are turned on, etc.

Yes, I know, more code, I wouldn't blame you if you just did multiple DLLs 
still :p

Original comment by kornma...@gmail.com on 24 Jan 2012 at 11:55

GoogleCodeExporter commented 9 years ago 
Thing is it's not an OS component that is crashing. One of the components must 
be doing something that is causing the device creation to fail later on. I 
could try and set up some way to toggle which systems are enabled but it would 
still require multiple runs and changes to the system setup to find the 
offending code. This just seemed like a quicker option :).

I'll think about a better way to test it, and pick this up again tomorrow.

Original comment by TheFieryScythe@gmail.com on 25 Jan 2012 at 12:03

GoogleCodeExporter commented 9 years ago 
Um, i still don't have open sauce. And i would be willing to run the series of 
.dlls until we find the problem.

Original comment by footsmas...@gmail.com on 26 Jan 2012 at 3:30

GoogleCodeExporter commented 9 years ago 
I have been busy with IRL work lately, I will get back to this soon.

Original comment by TheFieryScythe@gmail.com on 26 Jan 2012 at 5:11

GoogleCodeExporter commented 9 years ago 
Ok, so with this DLL you will get a messagebox when you start Halo with the 
number of components to initialize (starting at 3) . If you click yes the 
number will increase, if you click no the game will go on to initialize that 
many components. What I need to find out is which component is causing the 
crash later on, so what you need to do is run the game multiple times, each 
time increasing the number of components to initialise by 1 and clicking no, 
until the game exceptions. When it does exception, take down the exception 
details and post your game.debug.log and the exception details so that I can 
see if it is the same exception.

An exception WILL occur when you close Halo after it has got to the the main 
menu (hearing monks), which you can ignore.

NOTE: Do NOT distribute this dll, it has been crippled and is intended for 
debugging purposes ONLY.

Original comment by TheFieryScythe@gmail.com on 26 Jan 2012 at 9:18

Attachments:

GoogleCodeExporter commented 9 years ago 
I checked yes to all 12 and no exception, until i close halo, but halo doesn't 
have any visual. :/

Original comment by footsmas...@gmail.com on 27 Jan 2012 at 12:00

GoogleCodeExporter commented 9 years ago 
Huh, I thought it would be one of those...interesting. This one covers all 26, 
starting at 12.

Original comment by TheFieryScythe@gmail.com on 27 Jan 2012 at 12:30

Attachments:

GoogleCodeExporter commented 9 years ago 
There were only 12 optional. so 12+12+24. What about the other 2? and does that 
mean the first 12 were already activated?

Original comment by footsmas...@gmail.com on 27 Jan 2012 at 1:36

GoogleCodeExporter commented 9 years ago 
Sorry for all the questions, i'm just trying to learn. :/

Original comment by footsmas...@gmail.com on 27 Jan 2012 at 1:41

GoogleCodeExporter commented 9 years ago 
I probably mis-counted. Just to check, you are letting the game load after each 
increment? So start the game, set the number to 5, click no, restart, set it to 
6, click no, restart, etc?

Original comment by TheFieryScythe@gmail.com on 27 Jan 2012 at 8:36

GoogleCodeExporter commented 9 years ago 
Yes. I did that all the way up to 12, no exception and i'm in window mode and 
the screen is black with a white box in the middle, but i do get sound.

Original comment by footsmas...@gmail.com on 27 Jan 2012 at 3:11

GoogleCodeExporter commented 9 years ago 
I'm an idiot sometimes. When setting up the debug options I disabled the 
directx components, but we needed those components for the crash to occur!

So would you mind doing the same tests on this dll and let me know how it goes?

NOTE: Do NOT distribute this dll, it has been crippled and is intended for 
debugging purposes ONLY.

Original comment by TheFieryScythe@gmail.com on 28 Jan 2012 at 4:48

Attachments:

GoogleCodeExporter commented 9 years ago 
:( i got the same error too. I hope you guys get this fixed since youve put so 
much hard work into this project allready. ill have a go at trying this. thanks 
:).

Original comment by theninja...@gmail.com on 29 Jan 2012 at 12:08

GoogleCodeExporter commented 9 years ago 
Are you absolutely certain yours is the same exception? If not, make a new 
issue with the exception details and we will look at it seperately. I would 
rather people don't assume they are having the same problem unless they know 
what to compare in the exception details.

Original comment by TheFieryScythe@gmail.com on 29 Jan 2012 at 12:17

GoogleCodeExporter commented 9 years ago 
...Okay. So i put in the new one and tested. i checked yes to 3 and it 
exceptions, and it does the same thing when i check no...Here are the exception 
specs

 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.0.0
  Fault Module Timestamp:   4f2425d0
  Exception Code:   c0000005
  Exception Offset: 00012c96
  OS Version:   6.1.7601.2.1.0.256.49
  Locale ID:    1033

And here is the game.debog

Sun Jan 29 08:47:37 2012

08:47:37 process: C:\Program Files\Microsoft Games\Halo Custom 
Edition\haloce.exe
08:47:37 process: C:\Windows\SYSTEM32\ntdll.dll
08:47:37 process: C:\Windows\system32\kernel32.dll
08:47:37 process: C:\Windows\system32\KERNELBASE.dll
08:47:37 process: C:\Windows\system32\USER32.dll
08:47:37 process: C:\Windows\system32\GDI32.dll
08:47:37 process: C:\Windows\system32\LPK.dll
08:47:37 process: C:\Windows\system32\USP10.dll
08:47:37 process: C:\Windows\system32\msvcrt.dll
08:47:37 process: C:\Windows\system32\ADVAPI32.dll
08:47:37 process: C:\Windows\SYSTEM32\sechost.dll
08:47:37 process: C:\Windows\system32\RPCRT4.dll
08:47:37 process: C:\Windows\system32\ole32.dll
08:47:37 process: C:\Windows\system32\OLEAUT32.dll
08:47:37 process: C:\Windows\system32\IMM32.DLL
08:47:37 process: C:\Windows\system32\MSCTF.dll
08:47:37 process: C:\Program Files\Microsoft Games\Halo Custom 
Edition\strings.dll
08:47:37 process: C:\Windows\system32\uxtheme.dll
08:47:37 process: C:\Windows\system32\DSOUND.dll
08:47:37 process: C:\Windows\system32\WINMM.dll
08:47:37 process: C:\Windows\system32\POWRPROF.dll
08:47:37 process: C:\Windows\system32\SETUPAPI.dll
08:47:37 process: C:\Windows\system32\CFGMGR32.dll
08:47:37 process: C:\Windows\system32\DEVOBJ.dll
08:47:37 process: C:\Windows\system32\CRYPTBASE.dll
08:47:37 process: C:\Windows\system32\CLBCatQ.DLL
08:47:37 process: C:\Windows\System32\MMDevApi.dll
08:47:37 process: C:\Windows\System32\PROPSYS.dll
08:47:37 process: C:\Windows\system32\SHLWAPI.dll
08:47:37 process: C:\Windows\system32\wdmaud.drv
08:47:37 process: C:\Windows\system32\ksuser.dll
08:47:37 process: C:\Windows\system32\AVRT.dll
08:47:37 process: C:\Windows\system32\AUDIOSES.DLL
08:47:37 process: C:\Windows\system32\msacm32.drv
08:47:37 process: C:\Windows\system32\MSACM32.dll
08:47:37 process: C:\Windows\system32\midimap.dll
08:47:37 process: C:\Windows\system32\dwmapi.dll
08:47:37 process: C:\Windows\system32\CRYPTSP.dll
08:47:37 process: C:\Windows\system32\rsaenh.dll
08:47:37 process: C:\Windows\system32\RpcRtRemote.dll
08:47:37 process: C:\Windows\system32\winbrand.dll
08:47:37 process: C:\Windows\system32\WINTRUST.dll
08:47:37 process: C:\Windows\system32\CRYPT32.dll
08:47:37 process: C:\Windows\system32\MSASN1.dll
08:47:37 process: C:\Program Files\Microsoft Games\Halo Custom Edition\d3d9.dll
08:47:37 process: C:\Windows\system32\d3dx9_43.dll
08:47:37 process: C:\Windows\system32\WS2_32.dll
08:47:37 process: C:\Windows\system32\NSI.dll
08:47:37 process: C:\Windows\system32\SHELL32.dll
08:47:37 process: 
C:\Windows\WinSxS\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.4940_none_50
916076bcb9a742\MSVCR90.dll
08:47:37 process: C:\Windows\system32\PSAPI.DLL
08:47:37 process: C:\Windows\system32\d3d9.dll
08:47:37 process: C:\Windows\system32\VERSION.dll
08:47:37 process: C:\Windows\system32\d3d8thk.dll
08:47:37 process: C:\Windows\system32\profapi.dll
08:47:37 function: Yelo_IDirect3D9::CreateDevice; arg[Adapter]: 0; 
arg[DeviceType]: 1; arg[hFocusWindow]: 0x002003B2; arg[BehaviorFlags]: 64; 
arg[pPresentationParameters]: 0x0075B780; arg[ppReturnedDeviceInterface]: 
0x006B842C;
08:47:37 presentation_parameters: {BackBufferWidth, 800}; {BackBufferHeight, 
600}; {BackBufferFormat, 0x00000016}; {BackBufferCount, 1}; {MultiSampleType, 
0}; {MultiSampleQuality, 0}; {SwapEffect, 3}; {hDeviceWindow, 0x002003B2}; 
{Windowed, 1}; {EnableAutoDepthStencil, 1}; {AutoDepthStencilFormat, 
0x0000004B}; {Flags, 0}; {FullScreen_RefreshRateInHz, 0}; 
{PresentationInterval, 1};
08:47:37 function: Yelo_IDirect3DDevice9::Initialize; arg[pDevice]: 0x00000000; 
arg[ppDevice]: 0x0012DC5C;
08:47:37 variable[hr]: 0x8876086C;
08:47:37 dx_component_call[Initialize3D] index: 0
08:47:37 dx_component_call[Initialize3D] index: 1

Sun Jan 29 08:47:50 2012

08:47:50 process: C:\Program Files\Microsoft Games\Halo Custom 
Edition\haloce.exe
08:47:50 process: C:\Windows\SYSTEM32\ntdll.dll
08:47:50 process: C:\Windows\system32\kernel32.dll
08:47:50 process: C:\Windows\system32\KERNELBASE.dll
08:47:50 process: C:\Windows\system32\USER32.dll
08:47:50 process: C:\Windows\system32\GDI32.dll
08:47:50 process: C:\Windows\system32\LPK.dll
08:47:50 process: C:\Windows\system32\USP10.dll
08:47:50 process: C:\Windows\system32\msvcrt.dll
08:47:50 process: C:\Windows\system32\ADVAPI32.dll
08:47:50 process: C:\Windows\SYSTEM32\sechost.dll
08:47:50 process: C:\Windows\system32\RPCRT4.dll
08:47:50 process: C:\Windows\system32\ole32.dll
08:47:50 process: C:\Windows\system32\OLEAUT32.dll
08:47:50 process: C:\Windows\system32\IMM32.DLL
08:47:50 process: C:\Windows\system32\MSCTF.dll
08:47:50 process: C:\Program Files\Microsoft Games\Halo Custom 
Edition\strings.dll
08:47:50 process: C:\Windows\system32\uxtheme.dll
08:47:50 process: C:\Windows\system32\DSOUND.dll
08:47:50 process: C:\Windows\system32\WINMM.dll
08:47:50 process: C:\Windows\system32\POWRPROF.dll
08:47:50 process: C:\Windows\system32\SETUPAPI.dll
08:47:50 process: C:\Windows\system32\CFGMGR32.dll
08:47:50 process: C:\Windows\system32\DEVOBJ.dll
08:47:50 process: C:\Windows\system32\CRYPTBASE.dll
08:47:50 process: C:\Windows\system32\CLBCatQ.DLL
08:47:50 process: C:\Windows\System32\MMDevApi.dll
08:47:50 process: C:\Windows\System32\PROPSYS.dll
08:47:50 process: C:\Windows\system32\SHLWAPI.dll
08:47:50 process: C:\Windows\system32\wdmaud.drv
08:47:50 process: C:\Windows\system32\ksuser.dll
08:47:50 process: C:\Windows\system32\AVRT.dll
08:47:50 process: C:\Windows\system32\AUDIOSES.DLL
08:47:50 process: C:\Windows\system32\msacm32.drv
08:47:50 process: C:\Windows\system32\MSACM32.dll
08:47:50 process: C:\Windows\system32\midimap.dll
08:47:50 process: C:\Windows\system32\dwmapi.dll
08:47:50 process: C:\Windows\system32\CRYPTSP.dll
08:47:50 process: C:\Windows\system32\rsaenh.dll
08:47:50 process: C:\Windows\system32\RpcRtRemote.dll
08:47:50 process: C:\Windows\system32\winbrand.dll
08:47:50 process: C:\Windows\system32\WINTRUST.dll
08:47:50 process: C:\Windows\system32\CRYPT32.dll
08:47:50 process: C:\Windows\system32\MSASN1.dll
08:47:50 process: C:\Program Files\Microsoft Games\Halo Custom Edition\d3d9.dll
08:47:50 process: C:\Windows\system32\d3dx9_43.dll
08:47:50 process: C:\Windows\system32\WS2_32.dll
08:47:50 process: C:\Windows\system32\NSI.dll
08:47:50 process: C:\Windows\system32\SHELL32.dll
08:47:50 process: 
C:\Windows\WinSxS\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.4940_none_50
916076bcb9a742\MSVCR90.dll
08:47:50 process: C:\Windows\system32\PSAPI.DLL
08:47:50 process: C:\Windows\system32\d3d9.dll
08:47:50 process: C:\Windows\system32\VERSION.dll
08:47:50 process: C:\Windows\system32\d3d8thk.dll
08:47:50 process: C:\Windows\system32\profapi.dll
08:47:52 function: Yelo_IDirect3D9::CreateDevice; arg[Adapter]: 0; 
arg[DeviceType]: 1; arg[hFocusWindow]: 0x003703F0; arg[BehaviorFlags]: 64; 
arg[pPresentationParameters]: 0x0075B780; arg[ppReturnedDeviceInterface]: 
0x006B842C;
08:47:52 presentation_parameters: {BackBufferWidth, 800}; {BackBufferHeight, 
600}; {BackBufferFormat, 0x00000016}; {BackBufferCount, 1}; {MultiSampleType, 
0}; {MultiSampleQuality, 0}; {SwapEffect, 3}; {hDeviceWindow, 0x003703F0}; 
{Windowed, 1}; {EnableAutoDepthStencil, 1}; {AutoDepthStencilFormat, 
0x0000004B}; {Flags, 0}; {FullScreen_RefreshRateInHz, 0}; 
{PresentationInterval, 1};
08:47:52 function: Yelo_IDirect3DDevice9::Initialize; arg[pDevice]: 0x00000000; 
arg[ppDevice]: 0x0012DC5C;
08:47:52 variable[hr]: 0x8876086C;
08:47:52 dx_component_call[Initialize3D] index: 0
08:47:52 dx_component_call[Initialize3D] index: 1

Hope this is what you needed...:/

Original comment by footsmas...@gmail.com on 29 Jan 2012 at 2:51

GoogleCodeExporter commented 9 years ago 
...so what is happening? It's exceptioning when you yes or click no?

Original comment by TheFieryScythe@gmail.com on 29 Jan 2012 at 4:00

GoogleCodeExporter commented 9 years ago 
Yes, when i first open it and it asks me if i want to enable 3 of the 
plugins(or whatever it says) i clicked yes and no and both times it exceptioned.

Original comment by footsmas...@gmail.com on 29 Jan 2012 at 8:38

GoogleCodeExporter commented 9 years ago 
Going to have to defer to you for thoughts on this Korn, this debugging is 
going no-where (though thanks for the help anyway footsmashingwierdo :)). It's 
got to be one of the components being initialized that is causing the device to 
fail as disabling OS internally stops the exception and the device gets created 
successfully. I can't see anything in the initialization code that messes with 
DirectX since there is no device to mess with at that point, so as a guess, 
since that chipset uses the system memory could there be something OS is doing 
with the memory causing this?

Original comment by TheFieryScythe@gmail.com on 30 Jan 2012 at 8:49

GoogleCodeExporter commented 9 years ago 
I think the easiest way to figure out the problem would be to actually debug a 
32-bit crash dump (which won't be a problem since your OS is 32-bit). In order 
to create a crash dump follow these instructions: 
http://support.microsoft.com/kb/931673. Note that you'll need to keep the 
Exception! message up or else haloce.exe will close. Use 7zip or something to 
compress the .dmp file and then throw it up on some free hosting site (as I 
think google project has file attachment limits)

If you get an access denied error, you'll need to run the task manager 
(C:\Windows\System32\taskmgr.exe) with admin privileges.

FS, do you know what is calling Yelo_IDirect3DDevice9::Initialize with pDevice 
set to NULL? If not, you should dump _ReturnAddress();

Original comment by kornma...@gmail.com on 30 Jan 2012 at 10:00

GoogleCodeExporter commented 9 years ago 
lol yah im getting almost the same

Mon Jan 30 21:23:20 2012

21:23:20 component_initialized: 3
21:23:20 component_initialized: 4
21:23:20 component_initialized: 5
21:23:20 component_initialized: 6
21:23:20 component_initialized: 7
21:23:20 component_initialized: 8
21:23:20 component_initialized: 9
21:23:20 component_initialized: 10
21:23:20 component_initialized: 11
21:23:20 component_initialized: 12
21:23:21 process: C:\Users\Jack\Documents\Halo Custom Edition\haloce.exe
21:23:21 process: C:\Windows\SYSTEM32\ntdll.dll
21:23:21 process: C:\Windows\system32\kernel32.dll
21:23:21 process: C:\Windows\system32\KERNELBASE.dll
21:23:21 process: C:\Windows\system32\USER32.dll
21:23:21 process: C:\Windows\system32\GDI32.dll
21:23:21 process: C:\Windows\system32\LPK.dll
21:23:21 process: C:\Windows\system32\USP10.dll
21:23:21 process: C:\Windows\system32\msvcrt.dll
21:23:21 process: C:\Windows\system32\ADVAPI32.dll
21:23:21 process: C:\Windows\SYSTEM32\sechost.dll
21:23:21 process: C:\Windows\system32\RPCRT4.dll
21:23:21 process: C:\Windows\system32\ole32.dll
21:23:21 process: C:\Windows\system32\OLEAUT32.dll
21:23:21 process: C:\Windows\system32\apphelp.dll
21:23:21 process: C:\Windows\AppPatch\AcLayers.DLL
21:23:21 process: C:\Windows\system32\SspiCli.dll
21:23:21 process: C:\Windows\system32\SHELL32.dll
21:23:21 process: C:\Windows\system32\SHLWAPI.dll
21:23:21 process: C:\Windows\system32\USERENV.dll
21:23:21 process: C:\Windows\system32\profapi.dll
21:23:21 process: C:\Windows\system32\WINSPOOL.DRV
21:23:21 process: C:\Windows\system32\MPR.dll
21:23:21 process: C:\Windows\AppPatch\AcGenral.DLL
21:23:21 process: C:\Windows\system32\UxTheme.dll
21:23:21 process: C:\Windows\system32\WINMM.dll
21:23:21 process: C:\Windows\system32\samcli.dll
21:23:21 process: C:\Windows\system32\MSACM32.dll
21:23:21 process: C:\Windows\system32\VERSION.dll
21:23:21 process: C:\Windows\system32\sfc.dll
21:23:21 process: C:\Windows\system32\sfc_os.DLL
21:23:21 process: C:\Windows\system32\dwmapi.dll
21:23:21 process: C:\Windows\system32\SETUPAPI.dll
21:23:21 process: C:\Windows\system32\CFGMGR32.dll
21:23:21 process: C:\Windows\system32\DEVOBJ.dll
21:23:21 process: C:\Windows\system32\urlmon.dll
21:23:21 process: C:\Windows\system32\iertutil.dll
21:23:21 process: C:\Windows\system32\WININET.dll
21:23:21 process: C:\Windows\system32\Normaliz.dll
21:23:21 process: C:\Windows\AppPatch\AcXtrnal.DLL
21:23:21 process: C:\Windows\system32\SHUNIMPL.DLL
21:23:21 process: C:\Windows\system32\SortWindows6Compat.dll
21:23:21 process: C:\Windows\system32\IMM32.DLL
21:23:21 process: C:\Windows\system32\MSCTF.dll
21:23:21 process: C:\Users\Jack\Documents\Halo Custom Edition\strings.dll
21:23:21 process: C:\Windows\system32\DSOUND.dll
21:23:21 process: C:\Windows\system32\POWRPROF.dll
21:23:21 process: C:\Windows\system32\CRYPTBASE.dll
21:23:21 process: C:\Windows\system32\CLBCatQ.DLL
21:23:21 process: C:\Windows\System32\MMDevApi.dll
21:23:21 process: C:\Windows\System32\PROPSYS.dll
21:23:21 process: C:\Windows\system32\wdmaud.drv
21:23:21 process: C:\Windows\system32\ksuser.dll
21:23:21 process: C:\Windows\system32\AVRT.dll
21:23:21 process: C:\Windows\system32\AUDIOSES.DLL
21:23:21 process: C:\Windows\system32\msacm32.drv
21:23:21 process: C:\Windows\system32\midimap.dll
21:23:21 process: C:\Windows\system32\CRYPTSP.dll
21:23:21 process: C:\Windows\system32\rsaenh.dll
21:23:21 process: C:\Windows\system32\RpcRtRemote.dll
21:23:21 process: C:\Windows\system32\winbrand.dll
21:23:21 process: C:\Windows\system32\WINTRUST.dll
21:23:21 process: C:\Windows\system32\CRYPT32.dll
21:23:21 process: C:\Windows\system32\MSASN1.dll
21:23:21 process: C:\Users\Jack\Documents\Halo Custom Edition\d3d9.dll
21:23:21 process: C:\Windows\system32\d3dx9_43.dll
21:23:21 process: C:\Windows\system32\WS2_32.dll
21:23:21 process: C:\Windows\system32\NSI.dll
21:23:21 process: 
C:\Windows\WinSxS\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.6161_none_50
934f2ebcb7eb57\MSVCR90.dll
21:23:21 process: C:\Windows\system32\PSAPI.DLL
21:23:21 process: C:\Windows\system32\d3d9.dll
21:23:21 process: C:\Windows\system32\d3d8thk.dll
21:23:25 function: Yelo_IDirect3D9::CreateDevice; arg[Adapter]: 0; 
arg[DeviceType]: 1; arg[hFocusWindow]: 0x00200546; arg[BehaviorFlags]: 384; 
arg[pPresentationParameters]: 0x0075B780; arg[ppReturnedDeviceInterface]: 
0x006B842C;
21:23:25 presentation_parameters: {BackBufferWidth, 640}; {BackBufferHeight, 
480}; {BackBufferFormat, 0x00000016}; {BackBufferCount, 1}; {MultiSampleType, 
0}; {MultiSampleQuality, 0}; {SwapEffect, 1}; {hDeviceWindow, 0x00200546}; 
{Windowed, 0}; {EnableAutoDepthStencil, 1}; {AutoDepthStencilFormat, 
0x0000004B}; {Flags, 1}; {FullScreen_RefreshRateInHz, 60}; 
{PresentationInterval, 1};
21:23:25 function: Yelo_IDirect3DDevice9::Initialize; arg[pDevice]: 0x00000000; 
arg[ppDevice]: 0x0012DC5C;
21:23:25 variable[hr]: 0x00000000;
21:23:25 dx_component_call[Initialize3D] index: 0
21:23:25 dx_component_call[Initialize3D] index: 1
21:23:25 dx_component_call[Initialize3D] index: 2
21:23:25 dx_component_call[Initialize3D] index: 3
21:23:25 dx_component_call[Initialize3D] index: 4
21:23:25 dx_component_call[Initialize3D] index: 5
21:23:25 dx_component_call[Initialize3D] index: 6
21:23:25 dx_component_call[Initialize3D] index: 7
21:23:25 dx_component_call[Initialize3D] index: 8
21:23:25 dx_component_call[Initialize3D] index: 9

Original comment by theninja...@gmail.com on 30 Jan 2012 at 10:28

GoogleCodeExporter commented 9 years ago 
theninjadogbuster:
Your issue is different, please reinstall/repair OS using the 3.0.0 installer 
and make a new issue containing the exception details from the send report 
dialog (click View Details) that appears when it exceptions.

Korn:
        IDirect3DDevice9** alias = ppReturnedDeviceInterface;

        if(!g_d3d_device.IsInitialized())
                g_d3d_device.Initialize(*ppReturnedDeviceInterface, &ppReturnedDeviceInterface);

        *alias = &g_d3d_device;

This is done before the device is created, so *ppReturnedDeviceInterface 
(dereferencing the pointer to the device pointer) will be NULL.

Original comment by TheFieryScythe@gmail.com on 30 Jan 2012 at 12:32

GoogleCodeExporter commented 9 years ago 
...iiiii Still don't understand :P lol. I know nothing about coding and wish i 
could be of more help, but i truly don't know how. I can take instruction, but 
besides that i can't do much, I really was hoping to get OS working, or at 
least an answer of why it's not working...I am sorry to bother you constantly, 
but i don't know what else to do...:/

Original comment by footsmas...@gmail.com on 1 Feb 2012 at 2:59

GoogleCodeExporter commented 9 years ago 
When Halo exceptions, do not close the exception window or send report dialog 
and follow these instructions:

1.Start Task Manager. To do this, use one of the following methods:
◦Right-click an empty area of the task bar, and then click Start Task Manager.
◦Press CTRL+SHIFT+ESC.

2.Click the Processes tab.

3.Right-click haloce.exe, and then click Create Dump File.

If you see no option for creating a dump file, close task manager then go to 
C:\Windows\System32\ and run taskmgr.exe with admin priviledges. Then try to 
create a crash dump again.

4.When you receive a message that states that the dump file was successfully 
created, click OK.

5.Go to C:\Users\*UserName*\AppData\Local\Temp and copy the haloce.dmp file to 
your desktop.

6.Compress the dmp file using winzip/winrar/7z then upload it to a file sharing 
website and post us the link.

Original comment by TheFieryScythe@gmail.com on 2 Feb 2012 at 8:31

GoogleCodeExporter commented 9 years ago 
Hi here is the dump file of my Halo CE.
http://www.mediafire.com/download.php?ksib8515j5822ek

Original comment by hunterof...@gmail.com on 20 Feb 2012 at 1:05

GoogleCodeExporter commented 9 years ago 
1. That's a x64 .DMP, not a x86. Follow our instructions from earlier.
2. You're new to this issue thread so we need the exact exception information, 
which we can't get from that .DMP because it's not a x86 .DMP, to rule your 
problem out as being caused by something else

Original comment by kornma...@gmail.com on 20 Feb 2012 at 1:27

GoogleCodeExporter commented 9 years ago 
oh i forgot say something when I remove the d3d9.dll halo startup. is something 
bad or good ?

Original comment by hunterof...@gmail.com on 20 Feb 2012 at 8:39

GoogleCodeExporter commented 9 years ago

Original comment by kornma...@gmail.com on 21 Mar 2012 at 10:10

GoogleCodeExporter commented 9 years ago 
Sorry it took me so long to get back to you guys, and thank you for your 
patients with me. Before i create the dump file, which d3d9.dll am supposed to 
use, the original or one of the ones you guys gave me?

Original comment by footsmas...@gmail.com on 23 Mar 2012 at 1:18

GoogleCodeExporter commented 9 years ago 
Install v3.0.3 and create the 32-bit dump file

Original comment by kornma...@gmail.com on 23 Mar 2012 at 5:49

GoogleCodeExporter commented 9 years ago 
Reinstall OS version 3.0.3 using it's installer, then get a 32bit dump when/if 
it crashes.

Original comment by TheFieryScythe@gmail.com on 23 Mar 2012 at 5:51

GoogleCodeExporter commented 9 years ago 
Okay so. Open halo, get the exception, start task manager, go to create dump 
file, make it a 32bit, compress and post. That sound right?

Original comment by footsmas...@gmail.com on 23 Mar 2012 at 8:37

GoogleCodeExporter commented 9 years ago 
New problem...When i go to C:Users\"username"\ i don't see Appdata... It says 
it's saved there but i don't see it and start bar search isn't turning up 
anything either...Help?

Original comment by footsmas...@gmail.com on 23 Mar 2012 at 8:45

GoogleCodeExporter commented 9 years ago 
You probably don't have your folder options set to show hidden files and 
folders. Just put C:\Users\"username"\AppData manually or turn on hidden files 
and folders:
http://windows.microsoft.com/en-GB/windows-vista/Show-hidden-files

Original comment by TheFieryScythe@gmail.com on 24 Mar 2012 at 4:32

GoogleCodeExporter commented 9 years ago 
Thank you fileshare site is verifying. Stay tuned, kids.

Original comment by footsmas...@gmail.com on 24 Mar 2012 at 8:16

GoogleCodeExporter commented 9 years ago 
Here 'tis http://www.mediafire.com/?iogby0ib3uugby4 Can't wait to hear back :D

Original comment by footsmas...@gmail.com on 24 Mar 2012 at 8:16

GoogleCodeExporter commented 9 years ago 
According to this dump, you're still using OS v3.0.0. Please upgrade first.

Original comment by kornma...@gmail.com on 25 Mar 2012 at 1:12