You can change the style the forum displays by selecting your preferred style at the bottom left of the site.
We have made an enhancement so that old threads should now link from search results to the correct thread. This is not yet in place for single post links
409.1 *should* run okay when you are logged in as Admin and running XP SP2 compatibility although it isn't officially supported by RossTech. I've also read reports that the XP compatibilty add-on doesn't fix all known ills from legacy software.
Attach the dump file for this fault and I'll take a quick look.
This is an unhandled exception error which could be caused by any number of reasons. You would need to configure a JIT debug*er to catch the exception and analyse the code in this region to hopefully find the problem or some clues at least.
Other alternatives to achieve compatibility are running a dual boot system with XP or running a VM of an XP install.
Nuvo - the log above is the exception from running in xp sp2 compatability mode as administrator, do you want me to install a JIT de******? Im downloading the windows 7 xp mode thing now to give that ago.
Sonic, VCDS 9081 *won't* run with your cable. VCDS requires the HEX-USB adapter which acts as a dongle. Your cable is a simple USB to serial converter and will only work with VAG-COM 409.1 and below.
Try the XP add-on pack first and see how you go with that. Wow! I didn't realise this "add-on" is a 500MB image file plus you need to install Virtual PC. I smell overkill.
The above unhandled exception details wasn't copied from a .dmp file was it?
Do a file search for this and sort by date and time to find the most recent fault log.
You would need to download and install WinDbg for this task.
Run VAG-COM and WinDbg should break, type !analyze -v into the command line and you will generate the exception analysis. Copy and paste this or attach it as a file if it is a particularly large body of text.
CommandLine: "C:\Ross-Tech\VAG-COM\VagCom.exe"
Symbol search path is: *** Invalid ***
************************************************** **************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the de****** choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
************************************************** **************************
Executable search path is:
ModLoad: 00000000`00400000 00000000`00623000 image00000000`00400000
ModLoad: 00000000`77330000 00000000`774db000 ntdll.dll
ModLoad: 00000000`77510000 00000000`77690000 ntdll32.dll
ModLoad: 00000000`73bc0000 00000000`73bff000 C:\Windows\SYSTEM32\wow64.dll
ModLoad: 00000000`73b60000 00000000`73bbc000 C:\Windows\SYSTEM32\wow64win.dll
ModLoad: 00000000`73b50000 00000000`73b58000 C:\Windows\SYSTEM32\wow64cpu.dll
(de8.175c): Break instruction exception - code 80000003 (first chance)
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntdll.dll -
ntdll!CsrSetPriorityClass+0x40:
00000000`773e1220 cc int 3
0:000> !analyze -v
************************************************** *****************************
* *
* Exception Analysis *
* *
************************************************** *****************************
***** OS symbols are WRONG. Please fix symbols to do analysis.
************************************************** ***********************
*** ***
*** ***
*** Your de****** is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: ntdll!_PEB ***
*** ***
************************************************** ***********************
*** ERROR: Module load completed but symbols could not be loaded for image00000000`00400000
*** ERROR: Symbol file could not be found. Defaulted to export symbols for C:\Windows\SYSTEM32\wow64cpu.dll -
*** ERROR: Symbol file could not be found. Defaulted to export symbols for C:\Windows\SYSTEM32\wow64win.dll -
*** ERROR: Symbol file could not be found. Defaulted to export symbols for C:\Windows\SYSTEM32\wow64.dll -
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntdll32.dll -
************************************************** ***********************
*** ***
*** ***
*** Your de****** is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: IMAGE_NT_HEADERS32 ***
*** ***
************************************************** ***********************
************************************************** *******************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the de******. *
* using .sympath and .sympath+ *
************************************************** *******************
************************************************** *******************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the de******. *
* using .sympath and .sympath+ *
************************************************** *******************
FAULTING_IP:
ntdll!CsrSetPriorityClass+40
00000000`773e1220 cc int 3
ADDITIONAL_DEBUG_TEXT:
Use '!findthebuild' command to search for the target build information.
If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.
MODULE_NAME: ntdll
FAULTING_MODULE: 0000000077330000 ntdll
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5be02b
ERROR_CODE: (NTSTATUS) 0x80000003 - {EXCEPTION} Breakpoint A breakpoint has been reached.
EXCEPTION_CODE: (HRESULT) 0x80000003 (2147483651) - One or more arguments are invalid
EXCEPTION_PARAMETER1: 0000000000000000
PRIMARY_PROBLEM_CLASS: WRONG_SYMBOLS
BUGCHECK_STR: APPLICATION_FAULT_WRONG_SYMBOLS
LAST_CONTROL_TRANSFER: from 000000007739183d to 00000000773e1220
We process personal data about users of our site, through the use of cookies and other technologies, to deliver our services, personalize advertising, and to analyze site activity. We may share certain information about our users with our advertising and analytics partners. For additional details, refer to our Privacy Policy.
By clicking "I AGREE" below, you agree to our Privacy Policy and our personal data processing and cookie practices as described therein. You also acknowledge that this forum may be hosted outside your country and you consent to the collection, storage, and processing of your data in the country where this forum is hosted.
Comment