Closed Access Violation at 0x0000000 (all zeros is the point ok?)

Posting this for a friend, because they don't like human interaction

Windows XP SP3
2gb am
Intel Core Duo 2
Mobile Intel 965 Express Chipset

Code:

Start logging at: 2015-10-31 16:36:42.296
[16:36:42.296] Info: Star::Root using bootstrap file 'C:\Program Files\Steam\steamapps\common\Starbound\win32\sbboot.config'
[16:36:42.296] Info: Star::Root using storage directory 'C:\Program Files\Steam\steamapps\common\Starbound\giraffe_storage\'
[16:36:42.297] Info: Preparing Star::Root...
[16:36:42.298] Info: Loading Configuration with config file: 'starbound.config'
[16:36:42.298] Info: Loading Star::Configuration from 'Just (.\..\giraffe_storage\starbound.config)'
[16:36:42.301] Info: Writing Star::Configuration to '.\..\giraffe_storage\starbound.config'
[16:36:42.315] Info: Initializing Star::Root with 2 assets sources
[16:36:42.315] Info: Done preparing Star::Root.
[16:36:42.316] Info: Client Version 'Beta v. Pleased Giraffe - Update 5' Revision: 27433035cd2a72d3c7782aa3182119f87637614a Protocol: 692
[16:36:42.316] Info: Initialized SDL
[16:36:42.325] Info: Initialized SDL Video
[16:36:42.336] Info: Initialized SDL Joystick
[16:36:42.337] Info: Initialized SDL Sound
[16:36:42.339] Error: Fatal Error: Access violation detected at 00000000 (Read of address 00000000)
[0] 95edaa
[1] 95c31e
[2] 9d5302
[3] 150606d
[4] 76b46ac5 waveOutMessage
[5] 76b4366d SendDriverMessage
[6] 76b4853a waveOutGetDevCapsW
[7] 76b480e4 waveOutGetDevCapsW
[8] 76b482b6 waveOutGetDevCapsW
[9] 76b4643f waveOutMessage
[10] 76b46487 waveOutMessage
[11] 76b4611a waveOutMessage
[12] 73f15afe
[13] 73f15a9b
[14] 73f162db
[15] 73f141e3
[16] 73f1479d
[17] f65ba3 SDL_LoadWAV_RW
[18] f61c9a SDL_OpenAudio
[19] 94de75
[20] 409688
[21] 41eda1
[22] a2ba49
[23] a2b846
[24] 9fc0e9
[25] 7c816037 RegisterWaitForInputIdle

Digging around, I assume this is a memory access error of some sort. I notice it's conspicuous that it terminates at all 0's at the sound step, otherwise I have nothing else to contribute. Off the top of my head, we've done the obvious....

rebooted
verify game
reinstall game
delete and reinstall game
delete x file and launch starbound (the config files, the player files)
Administrator mode does not exist on XP
Dropped that SDL.DLL that's been floating around into the game folder
> I also verified my drivers were current, I tried messing with the hardware compression with my sound cards......

stumped, not sure where to go from here with this error

 

bump before bed

 

Have you tried launching the game through the files and not through Steam?

Note that I don't really know what the cause of this is, but I believe Access Violations are caused by other programs fiddling with Starbound (correctly of I'm wrong anyone).

 

Yes, we have tried that

 

Alright, I don't think I can really help from here then.
Perhaps @xxswatelitexx can help, I believe he's experienced with these kinds of things.

 

Actually, access violations are caused when a program tries to access memory that it is not allowed to.

Wherever you got that SDL.DLL from, put it back where you found it - if it was merely an issue with it not finding it, the program would not start at all.

That error is most likely caused when Starbound tried to initialize SDL Sound and failed - according to my logs, the error occured before any assets were loaded.

What OS are you using, and how did you launch it (32 or 64 bit)?

What do Starbound/win32/stderr.txt and Starbound/win32/stdout.txt (stdout is the same as starbound.log) say?

 

It's completely blank, apparently.

 

Do you have a 64-bit OS? If so, does the problem persist when you launch the 64-bit version?

 

I think I saw a 64-bit XP version listed on those Steam surveys...

 

I did a bit of looking around and, although I could not find a RegisterWaitForInputIdle, I did find a WaitForInputIdle, although I could not find a way to cause it to cause an access violation. The next one, SDL_OpenAudio, returns NULL if it fails, meaning that if something tried to access it it would cause an access violation reading 0x00000000, which is our most likely candidate. The only problem now is that I don't know WHY it would fail - I did find a few people saying that they got it to fail with "No available audio device", but those people were on Ubuntu.

Really, this type of thing should never have happened in the first place.

 

32 bit. Also yes, Xp has a 64-bit, but it's actual version name is Windows Xp 64 bit, because g4 bit came out inside its life cycle. Normal XP should be assumed to be 32 bit(though it is good to ask regardless)

No other details to report

 

bump

 

If I am right and SDL cannot find a sound device, do you have a sound card, with the correct drivers downloaded from the manufacturers website?