Jump to content

Welcome to MSFN Forum
Register now to gain access to all of our features. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more. This message will be removed once you have signed in.
Login to Account Create an Account


Photo

Applications built with Visual Studio 2013 x64 crash!

- - - - - vs 2013 x64 windows vista

  • Please log in to reply
3 replies to this topic

#1
ppgrainbow

ppgrainbow

    Advanced Member

  • Member
  • PipPipPip
  • 436 posts
  • OS:Vista Ultimate x64
  • Country: Country Flag

I have a problem here. When I try to run the 64-bit version of a application such as Stella 4.0 that was built with the 64-bit version of Visual Studio 2013, the application crashes.

The problem details are as follows:

Problem signature:
  Problem Event Name:    APPCRASH
  Application Name:    Stella.exe
  Application Version:    4.0.0.0
  Application Timestamp:    53b2cfba
  Fault Module Name:    MSVCR120.dll
  Fault Module Version:    12.0.21005.1
  Fault Module Timestamp:    524f83ff
  Exception Code:    c000001d
  Exception Offset:    0000000000092bc3
  OS Version:    6.0.6002.2.2.0.256.1
  Locale ID:    1033
  Additional Information 1:    78c1
  Additional Information 2:    0869ef10dc8cd21b7395bb14415118ff
  Additional Information 3:    0c15
  Additional Information 4:    4d720ac05b49834e684ca24d3d806421

 

Other applications built using the 64-bit version of Visual Studio 2013 such as Media Player Classic do work under Vista x64.

Is there a way to fix or debug this issue? I know that this issue might have been resolved under Windows 7 SP1, but what about Windows Vista SP2 users?


AVA Direct FX AM3+ specs: Zalman ZM Z9-U3 Black Mid-Tower case / ASUS M5A97 R2.0 / AMD FX-4300 3.8 GHz quad-core processor / Fractal Design Integra R2 500W PSU/ Hyper 212 EVO CPU cooler / Western Digital BLACK SERIES 1 TB (WD1003FZEX) SATA III 7200 RPM / Lite-On iHas124 Black 24x DVD-RW / Sabrent CRW-UINB internal memory card w/USB 2.0 port (to be replaced soon) / 8 GB Crucual (2 x 4GB) Ballistix Sport PC3-12800 DDR3 RAM / EVGA GeForce 8400 GS 520 MHz 1 GB GDDR3 / Microsoft Windows Vista Ultimate SP2 x64



How to remove advertisement from MSFN

#2
Tripredacus

Tripredacus

    K-Mart-ian Legend

  • Super Moderator
  • 9,672 posts
  • OS:Server 2012
  • Country: Country Flag

Donator

It looks to be that your application is expecting a certain version of (at least) MSVCR120.dll and you don't have that one. I would run Depends on the program to see what it complains about. Also, run Procmon on Stella.exe at launch to see what its search order for MSVCR120.dll is. If the first place to look is the home or working dir, you could put the correct version into that folder and no effect anything using the one in the Windows folder.


MSFN RULES | GimageX HTA for PE 3.x | lol probloms
msfn2_zpsc37c7153.jpg

#3
MagicAndre1981

MagicAndre1981

    after Windows 7 GA still Vista lover :)

  • Patrons
  • 5,918 posts
  • OS:Vista Ultimate x86
  • Country: Country Flag

Donator

Exception Code:    c000001d

error c000001d can be those things:

C:\Users\André>err c000001d
# for hex 0xc000001d / decimal -1073741795
  STATUS_ILLEGAL_INSTRUCTION                                     ntstatus.h
# {EXCEPTION}
# Illegal Instruction An attempt was made to execute an illegal instruction.
# as an HRESULT: Severity: FAILURE (1), FACILITY_NULL (0x0), Code 0x1d
# for hex 0x1d / decimal 29
  ERROR_WRITE_FAULT                                              winerror.h
# The system cannot write to the specified device.
# 2 matches found for "c000001d"

maybe it tries to call an API which is not part of Vista. Does the tool have PDB (debug symbols) files? If yes, you can create a dump and we can look at the dmp with Windbg


Posted Image

#4
ppgrainbow

ppgrainbow

    Advanced Member

  • Member
  • PipPipPip
  • 436 posts
  • OS:Vista Ultimate x64
  • Country: Country Flag
Exception Code:    c000001d

error c000001d can be those things:

C:\Users\André>err c000001d
# for hex 0xc000001d / decimal -1073741795
  STATUS_ILLEGAL_INSTRUCTION                                     ntstatus.h
# {EXCEPTION}
# Illegal Instruction An attempt was made to execute an illegal instruction.
# as an HRESULT: Severity: FAILURE (1), FACILITY_NULL (0x0), Code 0x1d
# for hex 0x1d / decimal 29
  ERROR_WRITE_FAULT                                              winerror.h
# The system cannot write to the specified device.
# 2 matches found for "c000001d"

maybe it tries to call an API which is not part of Vista. Does the tool have PDB (debug symbols) files? If yes, you can create a dump and we can look at the dmp with Windbg

 

 

That's what I've been thinking. The 64-bit version of Stella 4.0 tries to call an API that neither exists on Windows XP x64 nor Windows Vista x64.

 

How can I use the Windbg feature with Stella 4.0 to investigate the issue on Vista? Would I have to download the Windows Debugging Tools from the Windows 7 SDK?


AVA Direct FX AM3+ specs: Zalman ZM Z9-U3 Black Mid-Tower case / ASUS M5A97 R2.0 / AMD FX-4300 3.8 GHz quad-core processor / Fractal Design Integra R2 500W PSU/ Hyper 212 EVO CPU cooler / Western Digital BLACK SERIES 1 TB (WD1003FZEX) SATA III 7200 RPM / Lite-On iHas124 Black 24x DVD-RW / Sabrent CRW-UINB internal memory card w/USB 2.0 port (to be replaced soon) / 8 GB Crucual (2 x 4GB) Ballistix Sport PC3-12800 DDR3 RAM / EVGA GeForce 8400 GS 520 MHz 1 GB GDDR3 / Microsoft Windows Vista Ultimate SP2 x64






Also tagged with one or more of these keywords: vs 2013 x64, windows vista

1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users



How to remove advertisement from MSFN