ppgrainbow
Content Type
Profiles
Forums
Events
Posts posted by ppgrainbow
-
-
Okay, I think that I finally solved the problem.
It's the capacity of larger CompactFlash cards itself and not the SATA-to-CF drive. As far as I know, although the BIOS will recognise larger CF cards in POST, the Windows operating system will NOT boot correctly, if not at all.
I have tested the boot process with the First Champion 1 GB 80x CompactFlash card and well do you know, Windows Vista booted up without problems.
I haven't been able to test a 2 GB or a 8 GB capacity CF cards as they may not work 100% correctly with the SATA to CF drive.
The SATA-to-CF drive treated the Kingston Ultimate 32 GB 266x drive as a floppy drive and since it had trouble booting properly, I ended up ruining the card and tossing it in the trash.
Edit: I tested it with some of the CF cards and found that the First Champion 1 GB CF card worked, but as far as I know, that CF card is not bootable. I also tested it with a Kingston 1 GB CF card and the CF card has issues being recognised when Windows Vista boots up.
I wish that I had the time to test which CF cards work with the Startech SATA to CF drive, but I don't right now.
0 -
Wait a minute.The only way that I can try different CompactFlash card sizes is turning off the computer, ejecting the current CF card and inserting another one. I tried a 2 GB capacity CF card the other day and Windows Vista still stalled after boot. I was hoping for a solution so that I don't have to eject the CF card for at least one minute when Windows Vista restarts all of the devices after it boots up.
If the thingy is SATA connected, it should be "hot swappable", or not?
http://mt-naka.com/hotswap/index_enu.htm
jaclaz
According to the NewEgg review on StarTech's SATA-to-CF card:
This product does not support hot-swapping of flash cards while the PC is powered on. You must turn-off your computer to switch cards.
For some reason, the CF card when inserted into the SATA-to-CF drive would not load correctly when Windows Vista resets the devices after it boots up as one NewEgg reviewer complains that the the drive is either incompatible or poorly made.
I should try the HotSwap! utility to see how things go from here.
0 -
try a different media. Maybe the current one causes the slow start. Or you can insert the media each time after the boot. Or use Hibernation to avoid restarting all devices. Suspend/Resume of devices is much faster.
The only way that I can try different CompactFlash card sizes is turning off the computer, ejecting the current CF card and inserting another one. I tried a 2 GB capacity CF card the other day and Windows Vista still stalled after boot. I was hoping for a solution so that I don't have to eject the CF card for at least one minute when Windows Vista restarts all of the devices after it boots up.
Update: I re-enabled the hibernation feature. This is the case when the power went out about a hour ago.
Anyways, for some reason. The BIOS would detect the CF card inside the SATA-to-CF drive, but when Windows Vista boots up and resets the devices, the CF card inserted into the drive would not load properly.
I'm wondering if there is a way to fix this buggy issue here via a registry hack or a utility?
0 -
Maybe I got some definitions wrong.
Would this be accurate?
The device with media inserted is slow to start, but the device without media is not slow to start.
jaclaz
That's accurate.
0 -
The driver is fine. It is the device which is slow to start.
I knew it.
Do you have any idea what can be done that can make Vista detect the CF card in the drive at boot without having to hang on startup?
0 -
Still, is the delay actually in:
- CLASSPNP.SYS
- PARTMGR.SYS
- DISK.SYS
(as hinted before the two latter ones may have a connection with partitioned/not partitioned/fixed/removable status of the media).
And personally I wouldn't rule out specific brand/model/*whatever* of the actual card, it seems to me like CF cards are one of the pieces of hardware where every make/model behaves slightly differently.
At least some time ago I converted a couple old machines (win2K) to use CF cards (but on IDE/PATA bus, and obviously using el-cheapo no-name adapters) and I remember having quite a few difficulties in finding "decently performing" CF cards (this might be completely unrelated, cannot really remember if the issues I had initially were connected to booting).
jaclaz
Like I said before, the boot delay occurs in the classpnp.sys and it only happens when the CF card is inserted inside the SATA-to-CF adapter.
0 -
the long delay occurs by starting the ULTIMATE CF CARD ATA Device:
- <phase name="bootStart" startTime="53" endTime="625731" duration="625677"> <pnpObject name="IDE\DiskULTIMATE_CF_CARD________________________Ver7.02K\5+2efc85c4+0+3.0.0" type="Device" activity="Start" startTime="5287" endTime="625301" duration="620014" prePendTime="620014" description="Disk drive" friendlyName="ULTIMATE CF CARD ATA Device" />
this delays boot for 626 seconds. Is this the adapter?
In the trace I see the delay in CLASSPNP.SYS!ClassPnpStartDevice, so that's why you see the long classpnp.sys entry.
Yep. It's the adapter itself and not the CF card. This boot delay issue occurs only if the CF card is inserted inside the SATA-to-CF adapter.
0 -
-noPrepReboot is only needed for shutdown or hibernation, but not for boot.
Run this command please, which adds wait analysis:
xbootmgr -trace boot -traceFlags BASE+CSWITCH+DRIVERS+POWER+LATENCY+DISK_IO_INIT+DISPATCHER+FILE_IO+FILE_IO_INIT+FILENAME -stackwalk profile+CSwitch+ReadyThread+DiskReadInit+DiskWriteInit -resultPath C:\Output
compress the generated ETL as 7z/RAR, upload it and send me the link via PM.
I'm gonna be uploading it onto my OneDrive account and privately send you a note.
I've noticed that while Windows Vista was attempting to boot, I've noticed a long wait in the CLASSPNP.SYS and partmgr.sys driver delays of 620.01 seconds! Ouch!
I always though that crcdisk.sys was the issue as it was determined in Safe Mode, but it appears that I was wrong.The datestamps on the classpnp.sys file is 2009-04-11 and for the partmgr.sys, it's 2009-04-11 for one file and 2012-03-20 for the other two files.
0 -
Okay, I would like to post a update to this forum post.
I used this command to perform the boot trace below:
xbootmgr -trace rebootCycle -noPrepRebootAlthough, that it performed a boot cycle trace, it traced the output on the root directory of drive C. Therefore, when the tracing was finished, I decided to move it to the C:\Output\Boot sub-directory.
But when I tried to perform this command:
xbootmgr -trace boot -noPrepReboot -traceFlags BASE+CSWITCH+DRIVERS+POWER -resultPath C:\Output\TraceI ended up getting this error message:
'-noPrepReboot': This option can only be used with shutdown and rebootCycle traces.See 'xbootmgr.exe -help' for more information.
Nevertheless, I viewed the following files in the C:\Output directory:
1. First, looking at the boot_BASE+CSWITCH_1.etl and boot_BASE+CSWITCH_1_km_premerge.etl files.
Between around 10 to 315 seconds elapsed time (ET), no activity was being sampled. Between 315 to 520 seconds ET, activity usage started to spike with almost 2,500 hard faults at 320 seconds.
The shutdown_BASE+CSWITCH_1_km_premerge.etl file stated that it took 44 seconds to reboot the computer. Not bad.
2. And then it comes the C:\Output\Trace\boot_BASE+CSWITCH+DRIVERS+POWER_1.etl file. The analysis stated that it took about 80 seconds longer than boot_BASE+CSWITCH_1.etl/boot_BASE+CSWITCH_1_km_premerge.etl files
If you look in the Driver Delays section of this file, you'll notice that partmgr.sys took 310.78 seconds to load and CLASSPNP.SYS taking 1 ms shorter to load. Numerous delays between the 320 to 600 second ET mark indicate long delays with fltmgr.sys delaying for as much as 8 seconds in the 420 to 470 second ET mark.
Something sounds fishy here and the cause of this issue is difficult to decipher here. If you have the Windows 7.1 SDKs installed should I upload the files from the C:\Output\Trace directory onto my OneDrive account so that the issue can be looked into?
If so, please let me know.0 -
You need the Windows 7 SDK under Vista (the tools from the Windows 8 SDK no longer work under Vista
):During setup, you can select to only get the WPT (you can uncheck all other tools)
Thanks for the help.
I'll look into reinstalling the Windows 7.1 SDK. However, this requires me to uninstall the Visual Studio 2010 runtime first. Installing the Windows 7.1 SDK will reinstall the VS2010 runtine.0 -
My guess is that the "hard drive led" is actually an "activity on SATA bus led", and if this is the case there is no way you can change it's behaviour.
As well if you set in the BIOS SATA/AHCI, that setting affects the way the controller is detected by the booting OS and it's "global" for all devices connected to the SATA bus, so last sidenote seems to me like perfectly "normal".
The "booting issue" sounds strange, it seems like the booting OS "interrogates" the device and cannot have the reply it expects.
Is the behaviour the same with?:
- a CF card inserted (wiped, i.e. all 00's)
- a CF card partitioned/formatted (i.e. with first sector a MBR)
- a CF card only formatted (i.e. as "superfloppy" with first sector a PBR)
Can you make a boot log with the CF card (i.e. "hanging") and one without the CF card (i.e. booting normally)?
Additionally, can you try tracing the boot with xbootmgr/xperf?
http://helpdeskgeek.com/how-to/speed-up-boot-time-in-windows-vista/
I believe you need the WAIK or the SDK to get the tools.
jaclaz
Sorry for not responding earlier, but this behaviour occours only when the CompactFlash card is inserted and it doesn't matter if the card is partitioned/formatted or not.
In a forum post by asicnewbie in early May 2008 complianed that the Addonics SATA to CompactFlash adapter doesn't work with the majority of the cards that the user owns and stated that the user's PC will either sit there for a very long time (and will eventually error out) when the user tries to acces the drive or that it simply hangs the Windows XP operating system: http://arstechnica.com/civis/viewtopic.php?f=11&t=127190
On a side note, I'm wondering if it's possible to obtain xbootmg/xperf without going through the hassle of reinstalling the Windows SDK or not? :\
At one point, I went into Safe Mode and found that the hanging error points to the crcdisk.sys which has a timestamp of 2008-01-19. So, I'm wondering if a outdated crcdisk.sys has to do with this booting issue or not.
I might try a smaller capacity CF card to see if it makes a difference or not soon.
0 -
Hey there!
I had someone install the StarTech 3.5" SATA to CompactFlash SSD adapter in the 3.5" drive bay and so far, the computer is working good.
Windows Vista can detect what CompactFlash card is inside the 3.5" SATA to CF drive bay without any major problems. However, I'm running into issues after I insert the CF card in the 3.5" SATA to CF drive bay and turn the computer on:
1. The BIOS will recognise the CF card that is connected to the 3.5" SATA to CF drive bay as it is connected on SATA Port 4 on the ASUS M5A97 R2.0 motherboard. However, when Windows Vista attempts to boot up with the "© Microsoft Corporation" Segoe UI text and the green progress bar above it, the green light indicator on the SATA to CF drive goes off and the red hard drive LED stays on and the computer hangs indefinitely. In a interval of one minute, the hard drive LED will go off and the green light indicator on the SATA to CF drive goes on for a short period of time.
One temporary work around is that when I try to eject the CF card from the SATA to CF drive, the hard drive LED light would go off. I would leave it ejected for up to one minute and it would let the internal hard drive on SATA Port 1 continue to boot the Windows Vista operating system.
2. When there is data being read or written on the CF card, not only the green light indicator is blinking, but the hard drive LED light is blinking as well and it's not supposed to do that.I have a couple of questions to ask to try to remedy this if possible:
1. Is there a way to fix the issue that will allow Windows Vista to boot successfully even if the CF card is inserted inside the internal SATA to CF drive?
2. In any event there is read and write activity on the CF card, is there a way to stop it from using the hard drive LED light?
The model number on the StarTech SATA to CompactFlash card is 35BAYCF2SAT. The model number can easily be searched on Google. The issues that I mentioned above are minor and do not affect the functionality and performance of my computer.On a sidenote, in order to successfully recognise the CF card inside the the SATA to CF drive, I had to set the SATA ports to use AHCI mode and not IDE mode.
0 -
I went from Windows XP (retail upgrade) to Windows Vista (OEM) and then Windows Vista to Windows 2000 when my laptop died and then back to Windows Vista (retail).
The reason is that I admit that I used the old computer for more than 11 to 13 years, I found that it is just simply too slow and no longer useful to remain on Windows 2000 (which has been unsupported for more than four years). By using Windows Vista on this new computer for a couple of years, I will be able to still use software that is still designed to run on the aging OS. Windows Vista will remain supported until April 2017, btw.
I'm very happy with the OS that I'm using right now.
0 -
As far as I know, I'd avoid the 256 GB capacity flash drives that are worth just $25 and do not work reliably.
I'm getting a lot of negative reviews regarding the flash drive that you mentioned. One person called it a scam...a actual "8 GB flash drive with properties hacked"...aka counterfeit 256 GB flash drives that only show up as 8 GB. Seriously, I think that Amazon needs to ban the seller for selling defective products.
The fixed price for a new 256 GB flash drive right now is at least $150. A product with the highest review score on Google would go for at least $180.
0 -
I got your note and found that the 64-bit version of Stella 4.0 worked on Windows XP x64 and Windows Vista x64 worked when it is compiled with Visual Studio 2012 and without AVX support!
nice to hear this
0 -
I'm wondering why you keep using symfix in this and your other thread. Why not set the _NT_SYMBOL_PATH environment variable and be done with it?
That's what I've been thinking all along. I forgot to set the _NT_SYMBOL_PATH when I used !symfix to try to fix the symbols. :\
0 -
The current official version of Stella is compiled with MSVC2013 and can be compiled using MSVC2012. The source can be found here: http://sourceforge.net/projects/stella/files/stella/4.0/stella-4.0-src.tar.gz/download
check your PM and look if my compile works for you
I got your note and found that the 64-bit version of Stella 4.0 worked on Windows XP x64 and Windows Vista x64 worked when it is compiled with Visual Studio 2012 and without AVX support!
I will take this issue to the AtariAge forums, if possible.
0 -
ok, install the VC++ 2010 Express version and compile the code on your own and make sure nothing related to AVX is selected in the compiler options.
I think that I will head to the AtariAge forums and let them know what could be up with the 64-bit version of Stella 4.0.
In other words, I think that I will have to stick with the 32-bit version of the software built with MSVC 2013 as this will most likely be the latest 32-bit version of the compiler that will work with Windows XP/Vista.
0 -
Naah, it was just curiosity
, IF the 32 bit version works fine on your Vista AND there is NO noticeable differences (in practice, i.e. speed, features, capabilities, etc.) between the 32 bit and the 64 bit version in (say) Windows 7 SP1 it's hard for me to understand the reason why you spent more than (still say) 8 minutes in troubleshooting the issue (that seems in my perverted mind a non-issue).Call me "tough" and "hairy reasoner" as much as you want, as I have no idea (and actually I am not particularly interested in learning) what exactly it is AVX code, but it either provides a noticeable bettering in *something* or it does not.
If the bettering (if any) is not noticeable then I wouldn't pursue this "chase" for AVX code support, while of course if you are doing this for the fun of it
or to boldly go where no man has gone before , I can understand entirely .JFYI:
http://reboot.pro/topic/17568-what-advantage-hold-64-bit-programs-over-their-32-bit-version/
jaclaz
I see what you mean there. I'll take a look at the link that you showed me and discover the advantages of running 64-bit software over the 32-bit version.
0 -
Just out of curiosity, do you find any noticeable difference in running (on a supported OS) the 64 bit version vs. running the 32 bit version?
I mean, is it:
- faster?
- allowing to map more RAM memory?
- something else?
jaclaz
It's hard to tell. AVX code support has been present since Visual Studio 2010 SP1. Although the AMD FX-4300 has AVX support, AVX code is only present in Windows 7 SP1 and later.
Developers are starting to use AVX code for 64-bit apps built with MSVC 2013. This is not a issue in 32-bit apps built with MSVC 2013.
If you think that my comment is confusing and doesn't make sense, let me know.
0 -
Look if you can get the source of the tool and compile it with an older C++ Version (2010, 2012) and make sure no AVX is enabled in the compiler options.
The current official version of Stella is compiled with MSVC2013 and can be compiled using MSVC2012. The source can be found here: http://sourceforge.net/projects/stella/files/stella/4.0/stella-4.0-src.tar.gz/download
0 -
This is a follow-up to my previous post, "Internet Explorer has stopped working..." made a couple of weeks back.
Thanks to the help of MagicAndre1981, I've decided to debug Internet Explorer 9 to determine what dependency could be causing IE9 to crash.
Here's a complete output to determine what has been constantly causing IE9 to crash all of the time here...Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64Copyright (c) Microsoft Corporation. All rights reserved.CommandLine: "C:\Program Files (x86)\Internet Explorer\iexplore.exe"Symbol search path is: *** Invalid ******************************************************************************** Symbol loading may be unreliable without a symbol search path. ** Use .symfix to have the debugger choose a symbol path. ** After setting your symbol path, use .reload to refresh symbol locations. *****************************************************************************Executable search path is:ModLoad: 00000000`00ce0000 00000000`00d98000 iexplore.exeModLoad: 00000000`76ff0000 00000000`77176000 ntdll.dllModLoad: 00000000`771b0000 00000000`77310000 ntdll32.dllModLoad: 00000000`00050000 00000000`00086000 C:\Windows\system32\verifier.dllPage heap: pid 0xC7C: page heap enabled with flags 0x3.AVRF: iexplore.exe: pid 0xC7C: flags 0x48004: application verifier enabledModLoad: 00000000`743c0000 00000000`74405000 C:\Windows\system32\wow64.dllModLoad: 00000000`74370000 00000000`743be000 C:\Windows\system32\wow64win.dllModLoad: 00000000`74ca0000 00000000`74ca9000 C:\Windows\system32\wow64cpu.dll(c7c.6c0): Break instruction exception - code 80000003 (first chance)*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntdll.dll -ntdll!DbgBreakPoint:00000000`770361f0 cc int 3
Hit Debug > Go for the first time around and got this:
0:000> gModLoad: 00000000`76ec0000 00000000`76fed000 WOW64_IMAGE_SECTIONModLoad: 00000000`764e0000 00000000`765f0000 WOW64_IMAGE_SECTIONModLoad: 00000000`76ec0000 00000000`76fed000 NOT_AN_IMAGEModLoad: 00000000`76a90000 00000000`76b5d000 NOT_AN_IMAGEModLoad: 00000000`68e70000 00000000`68ea1000 C:\Windows\syswow64\verifier.dllPage heap: pid 0xC7C: page heap enabled with flags 0x3.AVRF: iexplore.exe: pid 0xC7C: flags 0x48004: application verifier enabledModLoad: 00000000`764e0000 00000000`765f0000 C:\Windows\syswow64\kernel32.dllModLoad: 00000000`74d60000 00000000`74e26000 C:\Windows\syswow64\ADVAPI32.dllModLoad: 00000000`76040000 00000000`76130000 C:\Windows\syswow64\RPCRT4.dllModLoad: 00000000`74cd0000 00000000`74d30000 C:\Windows\syswow64\Secur32.dllModLoad: 00000000`75f70000 00000000`76040000 C:\Windows\syswow64\USER32.dllModLoad: 00000000`75e10000 00000000`75ea0000 C:\Windows\syswow64\GDI32.dllModLoad: 00000000`75ea0000 00000000`75f4a000 C:\Windows\syswow64\msvcrt.dllModLoad: 00000000`75a60000 00000000`75ab9000 C:\Windows\syswow64\SHLWAPI.dllModLoad: 00000000`74ec0000 00000000`759d1000 C:\Windows\syswow64\SHELL32.dllModLoad: 00000000`75c40000 00000000`75d85000 C:\Windows\syswow64\ole32.dllModLoad: 00000000`75ac0000 00000000`75bd2000 C:\Windows\syswow64\urlmon.dllModLoad: 00000000`76810000 00000000`7689d000 C:\Windows\syswow64\OLEAUT32.dllModLoad: 00000000`76130000 00000000`762e9000 C:\Windows\syswow64\iertutil.dllModLoad: 00000000`763c0000 00000000`764db000 C:\Windows\syswow64\WININET.dllModLoad: 00000000`75f50000 00000000`75f53000 C:\Windows\syswow64\Normaliz.dll(c7c.6c0): WOW64 breakpoint - code 4000001f (first chance)First chance exceptions are reported before any exception handling.This exception may be expected and handled.*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntdll32.dll -ntdll32!DbgBreakPoint:771c0004 cc int 3
Hit Debug > Go for a second time around and got this:
0:000:x86> gModLoad: 75be0000 75c40000 C:\Windows\SysWOW64\IMM32.DLLModLoad: 762f0000 763b8000 C:\Windows\syswow64\MSCTF.dll(c7c.6c0): Access violation - code c0000005 (first chance)First chance exceptions are reported before any exception handling.This exception may be expected and handled.ntdll!RtlVirtualUnwind+0x2d9:00000000`77028df9 488b02 mov rax,qword ptr [rdx] ds:fffffa60`1044db70=????????????????
Access violation reported (code C0000005) in modules IMM32.DLL and MSCTF.DLL.
Ran Debug > Go for the third time and got this output:0:000> gModLoad: 00000000`75f60000 00000000`75f69000 C:\Windows\syswow64\LPK.DLL(c7c.6c0): Access violation - code c0000005 (first chance)First chance exceptions are reported before any exception handling.This exception may be expected and handled.ntdll!RtlVirtualUnwind+0x2d9:00000000`77028df9 488b02 mov rax,qword ptr [rdx] ds:fffffa60`1044db70=????????????????
Another access violation reported in module LPK.DLL.
Ran Debug > Go for the last time and got this output:0:000> gModLoad: 00000000`759e0000 00000000`75a5d000 C:\Windows\syswow64\USP10.dll(c7c.6c0): Access violation - code c0000005 (first chance)First chance exceptions are reported before any exception handling.This exception may be expected and handled.ntdll!RtlVirtualUnwind+0x2d9:00000000`77028df9 488b02 mov rax,qword ptr [rdx] ds:fffffa60`1044db70=????????????????
An access violation reported in USP10.DLL which was widely responsible for crashing Internet Explorer 9 while attempting to view Unicode characters on someone's Twitter account. >.<
Now to try to isolate the problem I decided to fix the symbols and analyse the output for these issues involving IE9:0:000> !symfix *C:\Symbols*http://msdl.microsoft.com/download/symbols0:000> !analyze -v
The final result of the output are as follows:
******************************************************************************** ** Exception Analysis ** *********************************************************************************** ERROR: Symbol file could not be found. Defaulted to export symbols for C:\Windows\system32\verifier.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 C:\Windows\system32\wow64cpu.dll -*** ERROR: Symbol file could not be found. Defaulted to export symbols for C:\Windows\system32\wow64win.dll -***** OS symbols are WRONG. Please fix symbols to do analysis.*** ERROR: Symbol file could not be found. Defaulted to export symbols for C:\Windows\syswow64\kernel32.dll -***** OS (WOW64 kernel32) symbols are WRONG. Please fix symbols to do analysis.**************************************************************************** ****** ****** Your debugger 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 ****** ******************************************************************************************************************************************************** ****** ****** Your debugger 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: nt!IMAGE_NT_HEADERS32 ****** ******************************************************************************* ERROR: Module load completed but symbols could not be loaded for iexplore.exe*** ERROR: Symbol file could not be found. Defaulted to export symbols for C:\Windows\syswow64\ole32.dll -GetPageUrlData failed, server returned HTTP status 404URL requested: http://watson.microsoft.com/StageOne/iexplore_exe/9_0_8112_16561/539247f9/ntdll_dll/6_0_6002_18881/51da3d16/c0000005/00038df9.htm?Retriage=1FAULTING_IP:ntdll!RtlVirtualUnwind+2d900000000`77028df9 488b02 mov rax,qword ptr [rdx]EXCEPTION_RECORD: ffffffffffffffff -- (.exr 0xffffffffffffffff)ExceptionAddress: 0000000077028df9 (ntdll!RtlVirtualUnwind+0x00000000000002d9) ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000NumberParameters: 2 Parameter[0]: 0000000000000000 Parameter[1]: fffffa601044db70Attempt to read from address fffffa601044db70FAULTING_THREAD: 00000000000006c0PROCESS_NAME: iexplore.exeADDITIONAL_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.FAULTING_MODULE: 00000000764e0000 kernel32DEBUG_FLR_IMAGE_TIMESTAMP: 51da3d90MODULE_NAME: wow64ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.EXCEPTION_PARAMETER1: 0000000000000000EXCEPTION_PARAMETER2: fffffa601044db70READ_ADDRESS: fffffa601044db70FOLLOWUP_IP:wow64!Wow64EmulateAtlThunk+698200000000`743d1f02 85ed test ebp,ebpMOD_LIST: <ANALYSIS/>BUGCHECK_STR: APPLICATION_FAULT_INVALID_POINTER_READ_WRONG_SYMBOLSPRIMARY_PROBLEM_CLASS: INVALID_POINTER_READDEFAULT_BUCKET_ID: INVALID_POINTER_READLAST_CONTROL_TRANSFER: from 0000000076ff5ef8 to 0000000077028df9STACK_TEXT:00000000`0014d790 00000000`76ff5ef8 : 00000000`00000000 00000000`00000000 fffffa60`1044db10 00000000`00884280 : ntdll!RtlVirtualUnwind+0x2d900000000`0014d7f0 00000000`76ff5dfa : 00000000`00000003 00000000`00000010 00000000`00000000 00000000`759e0000 : ntdll!RtlWalkFrameChain+0x13800000000`0014dd70 00000000`76ff5d7b : 00000000`00000001 00000000`0005d859 00000000`0010000e 00000000`0014de18 : ntdll!RtlWalkFrameChain+0x3a00000000`0014dda0 00000000`000651b4 : 00000000`00880080 00000000`00884280 00000000`000041a0 00000000`00000040 : ntdll!RtlCaptureStackBackTrace+0x4b00000000`0014ddd0 00000000`0005b9a5 : 00000000`00000000 00000000`0014df20 00000000`0014df70 00000000`0005e924 : verifier!VerifierStopMessage+0x67c00000000`0014de10 00000000`743d1f02 : 00000000`7ffeffff 00000000`002ee47c 00000000`0014df70 00000000`7ffeffff : verifier+0xb9a500000000`0014de90 00000000`743ca986 : 00000000`00000000 00000000`002ee328 00000000`002ee374 00000000`7efdd000 : wow64!Wow64EmulateAtlThunk+0x698200000000`0014dfb0 00000000`74ca3688 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`7efdd000 : wow64!Wow64SystemServiceEx+0xca00000000`0014e860 00000000`743cab36 : 00000000`00000000 00000000`0014edf0 fffffa60`005efcc0 fffffa60`1044dc20 : wow64cpu!TurboDispatchJumpAddressEnd+0x2800000000`0014e8f0 00000000`743c621a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : wow64!Wow64SystemServiceEx+0x27a00000000`0014e920 00000000`74390c35 : 00000000`0014eca0 0000002b`0000004c 00000000`00000000 00000000`00000000 : wow64!Wow64KiUserCallbackDispatcher+0x23e00000000`0014ec80 00000000`77036db6 : 00000000`00000000 00000000`00000000 00000000`735b003a 00000000`00000000 : wow64win+0x20c3500000000`0014edf0 00000000`74ca3d09 : 00000000`74ca3cc5 00000023`771f94b2 00000000`00000023 00000000`00000202 : ntdll!KiUserCallbackDispatcher+0x1f00000000`0014ee48 00000000`74ca3cc5 : 00000023`771f94b2 00000000`00000023 00000000`00000202 00000000`002ef540 : wow64cpu!TurboDispatchJumpAddressEnd+0x6a900000000`0014ee50 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : wow64cpu!TurboDispatchJumpAddressEnd+0x665SYMBOL_STACK_INDEX: 6SYMBOL_NAME: wow64!Wow64EmulateAtlThunk+6982FOLLOWUP_NAME: MachineOwnerIMAGE_NAME: wow64.dllSTACK_COMMAND: ~0s ; kbBUCKET_ID: WRONG_SYMBOLSFAILURE_BUCKET_ID: INVALID_POINTER_READ_c0000005_wow64.dll!Wow64EmulateAtlThunkWATSON_STAGEONE_URL: http://watson.microsoft.com/StageOne/iexplore_exe/9_0_8112_16561/539247f9/ntdll_dll/6_0_6002_18881/51da3d16/c0000005/00038df9.htm?Retriage=1Followup: MachineOwner---------
Something is fishy here. Reinstalling Internet Explorer 9 has had no help. The STACK_TEXT shows a list of dependencies that could be the culprint here and for some reason, it points to wow64.dll, but I don't know if it's true or not.
Sorry for the distressful spam here, but can anyone look up the offending dependencies that caused IE9 to stop working properly here?
Thanks for your time.0 -
vpsrlq looks like AVX command which which is only supported in Windows 7 Sp1, but not in Vista.
Thanks for telling me.
It looks like that this might be a bug that broke 64-bit compatibility in Windows 7 RTM and below. As far as I know, the 64-bit version of Stella 4.0 uses Advanced Vector Extensions (AVX) that only exist in Windows 7 SP1 and later. I'm wondering if there is a way to patch the 64-bit version of MSVCRT120.DLL without vpsrlq and AVX support on Windows Vista or not. Otherwise, I will have to use the 32-bit version of Stella 4.0 as it is built using MSVC2013.
As far as I know, the next major release of Stella or the next major version of Visual Studio, will neither support Windows XP nor Windows Vista.
The AMD FX-4300 CPU does have AVX support, but I'm disappointed to hear that the latest 64-bit release of Stella would not work in Windows Vista, even if the OS is still supported until April 2017.
0 -
you need to fix the symbols:
http://support.microsoft.com/kb/311503/en-us
and you should look if there are PDBs for your tool.
Now run !analyze -v in Windbg to see more details.
Okay, what I did was to fix the symbols from the C:\Symbols directory by typing this command:
!symfix *C:\Symbols*http://msdl.microsoft.com/download/symbols
Next when I ran the !analyze -v command, here's the output of what I received:
******************************************************************************** ** Exception Analysis ** ************************************************************************************* OS symbols are WRONG. Please fix symbols to do analysis.**************************************************************************** ****** ****** Your debugger 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 ****** ****************************************************************************FAULTING_IP:MSVCR120!log+2d3000007fe`f2ea2bc3 c5e173d034 vpsrlq xmm3,xmm0,34hEXCEPTION_RECORD: ffffffffffffffff -- (.exr 0xffffffffffffffff)ExceptionAddress: 000007fef2ea2bc3 (MSVCR120!log+0x00000000000002d3) ExceptionCode: c000001d (Illegal instruction) ExceptionFlags: 00000000NumberParameters: 0FAULTING_THREAD: 0000000000001260DEFAULT_BUCKET_ID: WRONG_SYMBOLSPROCESS_NAME: image00000001`40000000ADDITIONAL_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.FAULTING_MODULE: 0000000076ff0000 ntdllDEBUG_FLR_IMAGE_TIMESTAMP: 524f83ffERROR_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION} Illegal Instruction An attempt was made to execute an illegal instruction.EXCEPTION_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION} Illegal Instruction An attempt was made to execute an illegal instruction.MOD_LIST: <ANALYSIS/>PRIMARY_PROBLEM_CLASS: WRONG_SYMBOLSBUGCHECK_STR: APPLICATION_FAULT_WRONG_SYMBOLSLAST_CONTROL_TRANSFER: from 00000001400568cc to 000007fef2ea2bc3STACK_TEXT: 00000000`0012f960 00000001`400568cc : 00000000`0012fa10 00000001`40221da0 00000001`40221da0 00000000`00000000 : MSVCR120!log+0x2d300000000`0012f9c0 00000001`4008c44e : 00000000`002ea730 00000001`40221da0 00000000`0012fcf0 00000000`0012fbb8 : image00000001_40000000+0x568cc00000000`0012fb70 00000001`40154cca : 00000000`00000001 00000000`00000001 00000000`001b0010 00000000`00000000 : image00000001_40000000+0x8c44e00000000`0012fd90 00000001`40001020 : 00000000`001f3474 00000000`0000000a 00000000`001f3474 00000000`0000000a : image00000001_40000000+0x154cca00000000`0012fe90 00000001`400010f2 : 00000000`00000001 00000000`001b0010 00000000`000002f4 000007fe`f2e3276b : image00000001_40000000+0x102000000000`0012fed0 00000001`4015419d : 00000001`40000000 00000000`00000000 00000000`001f3474 01cf9d1f`0000000a : image00000001_40000000+0x10f200000000`0012ff20 00000000`76eda54d : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : image00000001_40000000+0x15419d00000000`0012ff60 00000000`77016861 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : kernel32!BaseThreadInitThunk+0xd00000000`0012ff90 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!RtlUserThreadStart+0x21FAILED_INSTRUCTION_ADDRESS:MSVCR120!log+2d3000007fe`f2ea2bc3 c5e173d034 vpsrlq xmm3,xmm0,34hFOLLOWUP_IP:MSVCR120!log+2d3000007fe`f2ea2bc3 c5e173d034 vpsrlq xmm3,xmm0,34hSYMBOL_STACK_INDEX: 0SYMBOL_NAME: msvcr120!log+2d3FOLLOWUP_NAME: MachineOwnerMODULE_NAME: MSVCR120IMAGE_NAME: MSVCR120.dllSTACK_COMMAND: ~0s ; kbBUCKET_ID: WRONG_SYMBOLSFAILURE_BUCKET_ID: WRONG_SYMBOLS_c000001d_MSVCR120.dll!logFollowup: MachineOwner---------For some reason, the analyst is telling me that I'm *not* using the correct symbols despite the fact that I set the symbol path to the C:\Symbols directory. Is there a way to make the WinDbg use the correct symbols?
Regardless of the fact that I'm not using the correct symbols, it seems that I'm trying to make some progress here and determine what could be causing the 64-bit version of Stella, built with the 64-bit version of VS2013 to crash.
0
I always though that crcdisk.sys was the issue as it was determined in Safe Mode, but it appears that I was wrong.
, I can understand entirely 
.
Issues with the 3.5" SATA to CompactFlash SSD Adapter
in Windows Vista
Posted
I don't understand too. I think it would be best to contact StarTech regarding this issue.