Tag Info

Hot answers tagged


One tool you could use is the Resource Monitor in Windows. Open Task Manager and click the "Resource Monitor" button on the Performance tab. Once in the Resource Monitor, go to the Disk tab, where you can see which processes are accessing your disks, and exactly which disks and which files they're accessing. Another tool is Process Explorer from ...


.Net 3.5 is already part of Windows 8, so the installer doesn't work. You can use DISM to install .Net 3.5: DISM /Online /Enable-Feature /FeatureName:NetFx3 /All /LimitAccess /Source:d:\sources\sxs


It is always a better bet to stick with the drivers from the motherboard manufacturer. These drivers are known to work with your board's exact configuration (since most things that require drivers can be at least mildly customized.) And most BSOD issues are hardware related (thermal/mechanical/electrical.) If a driver were the cause of BSOD issues, the ...


Since the program was dying originally whoever I clicked the Favorites button to open the Favorites\History panel, I was thinking "Maybe I should delete all of my favorites, moving them to my desktop for now, theorizing that perhaps there is some fav shortcut that is corrupt in some way. When I did so, I dialog box appeared indicating that the files were ...


32Bit applications read from the Wow6432Node keys. The directory makes no difference. The 2 folders are predefined so that you can have a 32Bit and 64Bit version of the same tool installed. sure Windows determines that it is a 32Bit version and uses the WoW64 subsystem to run 32Bit application on a 64Bit Windows.


You miss a C++ Runtime. Run the Command prompt (cmd.exe) with admin rights and run this command: SxsTrace Trace -logfile:SxsTrace.etl Now run the script which causes the SideBySide error. Go back to the command prompt press ENTER/RETURN to generate the SxsTrace.etl. Now type this: sxstrace Parse -logfile:SxSTrace.etl -outfile:SxSTrace.txt Now open the ...


Like harrymc said, a couple programs you can use are Resource Monitor, Process Explorer, Process Monitor, and DiskMon. However, the problem here is most likely that there is a wire loose or a faulty/dying optical drive mobo. Basically, it's connecting and disconnecting, causing Windows to keep registering it as a new drive. Additionally, it could be a ...

Only top voted, non community-wiki answers of a minimum length are eligible