New
#41
thanks, writh
I really do appreciate you getting this info to me asap so i can continue working on it over the weekend.
thanks, writh
I really do appreciate you getting this info to me asap so i can continue working on it over the weekend.
No problem. Let us know if you need any help as you proceed.
the imageres file coudln't be extracted over. i took ownership and set full control. i then tried copy /y in elevated cmd :
cannot be performed with user mapped section open
_____________________________
strangely the last file did not exist in either system directory or windows 7 install didk
Last edited by bam12; 19 May 2012 at 16:50. Reason: more info
You may need to replace the files through the recovery environment. Use Advanced Boot Options to select Repair Your Computer and get to the System Recovery Options. Then follow the steps to Copy & Paste - in Windows Recovery Console to replace the files.
I have attached the file you need: I should have noticed you have a 32-bit operating system. Your file structure will be somewhat different. The directory on your system is probably C:\Windows\winsxs\netfx-aspnet_common_sql_b03f5f7f11d50a3a_6.1.7600.16385_none_e30a73284d02ae8d
Also, not that I would give you an infected file, but just to be safe, since it is an unknown source, make sure to scan it with your antivirus prior to extracting it. Always scan unknown files with your antivirus prior to opening them; it is a good habit to get into.
thanks again, i will try this.
what about the start windows sound file? could not replace because mapped section open?
i will try this same approach on it and see if that works.
edit
all files copied. running verifier (all installed drivers) to stress test system today. i will post monday
Last edited by bam12; 20 May 2012 at 10:54. Reason: more info
Replacing in the Recovery Environment should negate the mapped section being open. That was why I suggested that method.
yes that worked. sorry i wasn't clear.
i am running the verifier and sfc again to see if we caught everything. and reducing from four sticks/slots to two to test that
thanks. i will report back
Alright, but be aware that with three changes made, Verifier may cause some false positive crashes, so it may not indicate anything wrong with your drivers. I should be able to tell if it is a likely false positive depending on the crash, though. We'll have to wait and see.
Writhziden
I started to run verifier awhile, knowing the crashes would occur intentionally, then changed my mind about the usefulness of it. After running both diskcheck and sfc with clean results, and using the pc for a day without any problems, i am hopefully calling this project a successful fix! I couldn't have done without your help (your other colleagues at 7forum too). Thank you Very very much.
Now, i am not sure exactly what to do about my memory sticks. despite memtest can't be 100% sure they weren't involved because as suggested i took 2 out to test just as we were completing the fixes. i didn't really establish they were bad. i still now have only 2 in orange (there are two orange slots and two purple & you have to use same-color slots in pairs). Can you advise me on testing and replacing my sticks without undoing this fix?
Test the two modules you currently have for twice as long as it takes (on average) for a crash. If no crashes occur, test the other two slots with the modules currently in the system (again, twice as long as it takes on average for a crash). If no crashes still occur, test the other two modules the same way.
If you get crashes in two slots but not the other two slots with both sets of RAM, one of the slots on the motherboard may be bad. If you get crashes with two modules regardless of what slots, that set of RAM is likely bad.