Page 1 of 1

D3 crash in Win 7

Posted: Sat Feb 20, 2010 5:21 am
by Duper
Problem signature:
Problem Event Name: APPCRASH
Application Name: main.exe
Application Version: 0.0.0.0
Application Timestamp: 3919f324
Fault Module Name: main.exe
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 3919f324
Exception Code: c0000005
Exception Offset: 00190b97
OS Version: 6.1.7600.2.0.0.256.48
Locale ID: 1033
Additional Information 1: 0cc3
Additional Information 2: 0cc3fb6c351418b1aad976ac656928db
Additional Information 3: e5ff
Additional Information 4: e5ff1dedebe72114a0d24f0bc4bee3e4
cool little feature.

Anyone else having crash problems yet? I imagine this is a sound issue. Tell ya what though. with the ATI 5770 and 1K fps... D3 looks reeEEEeeeallll good. :twisted:

Posted: Sun Feb 21, 2010 3:42 pm
by Duper
ok, guess not. :lol:

oh, new system Stats.

SYSTEM:
mobo: Intel DH55HC
CPU: Intel i3 540 (3.07GHz)
VID: ATI HD5770
M: 4 Gig OCZ DDR3 1333
Sound: SB X-Fi Gamer Extreme (SB0730)
OS: Win 7 Pro (64 bit)
IE 8 & Opera 10.0
Dx 11



Old Stats:

SYSTEM:
mobo: Asus A8N-E
CPU: Athlon64 3500+
VID: Nvidia 8600GT
M: 2 Gig 2400 Corsair
Sound: SB X-Fi Audio [A400](SB0730)
OS: XP PRO
IE 8 & Opera 10.0
Dx 9.0c

Posted: Sun Feb 21, 2010 5:30 pm
by Krom
If you think it is a sound issue, try disabling sound and checking for sure. Actually I haven't run D3 in Windows 7 yet at all even as a test, don't even have it installed but it worked well enough in Vista and 7 isn't that different.

What makes you think it is a sound issue?

Posted: Sun Feb 21, 2010 9:35 pm
by Duper
oh, just blanket reasoning. It seems that most issues in D3 that cause crashing is a sound issue.

I have a X-fi gamer (not the high end one) and the drivers aren't all that, not to mention there is Dx11.

I dunno honestly. I'll test it out later. right now, I'm busy reinstalling my 300 programs, games and apps. :roll: :P :wink:

Posted: Mon Feb 22, 2010 7:15 am
by BUBBALOU
D3 crashes for numerous reasons.... randomly, usually nothing to do with your pc

Posted: Mon Feb 22, 2010 10:23 am
by Foil
Exactly. That 'appcrash' output is basically telling you it's the same old \"exception in winmain()\" we've all seen a thousand times before.