New
#31
One more BSOD:
Attachment 29975
One more BSOD:
Attachment 29975
OK, these 4 from today
That is the Application Compatibility CacheCode:Use !analyze -v to get detailed debugging information. BugCheck 3B, {c0000005, fffff8006d683093, ffffd00021152a00, 0} Probably caused by : ahcache.sys ( ahcache!AhcpCacheBuildEnvironmentSafe+2be ) Followup: MachineOwner
The other 2 were thisCode:UNEXPECTED_KERNEL_MODE_TRAP_M (1000007f) This means a trap occurred in kernel mode, and it's a trap of a kind that the kernel isn't allowed to have/catch (bound trap) or that is always instant death (double fault). The first number in the bugcheck params is the number of the trap (8 = double fault, etc) Consult an Intel x86 family manual to learn more about what these traps are. Here is a *portion* of those codes: If kv shows a taskGate use .tss on the part before the colon, then kv. Else if kv shows a trapframe use .trap on that value Else .trap on the appropriate frame will show where the trap was taken (on x86, this will be the ebp that goes with the procedure KiTrap) Endif kb will then show the corrected stack. Arguments: Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT Arg2: fffff801bb4f4e70 Arg3: ffffd00022895e60 Arg4: fffff801b9687c16
Code:Use !analyze -v to get detailed debugging information. BugCheck 1E, {ffffffffc0000005, fffff8011a085f44, 0, ffffffffffffffff} Probably caused by : memory_corruption Followup: memory_corruption
Please Run Memtest86+
InformationPlease download from this site only http://www.memtest.org/ in the middle of the page are the Download links, you can download the ISO.zip or the Auto USB Flash Drive installer.zipExtract the Zip file. If you chose the ISO image, burn it to a CD using Windows Disk Image Burner or any Image burner you may have. If you downloaded the Auto USB installer, extract it, insert your USB 2.0 Flash Drive and take note of the drive letter. Run the installer, select the Flash Drive Letter, check the format box and press next. It will install memtest86+ to a flash drive. You can use either V4.20 or V5.01. Boot from your selected media. If you use V5.01 it will tell you to press certain buttons at the start, please press no buttons. The test will begin on it's own and continue to run until you stop it. It needs to run for 8 complete passes or until you receive an error. If you receive an error, stop the test. Even 1 error is a fail. Each pass tests a different part of the ram and each of the 10 tests in each pass tests something different. It takes a minimum of 8 passes to completely test the ram, more passes are better. It is quite a long test and will take several hours depending on how much ram you have. Due to the time length it is best to run overnight. If you have any questions, please do not hesitate to ask
Also, please run Seatools for DOS http://www.sevenforums.com/tutorials...s-how-use.html
Last edited by essenbe; 15 Aug 2015 at 04:32.
Ok, so, I ran Memtest, it took 8 hours and a half, 8 passes occured with no errors!
Seatools for DOS showed that error as I reported before, I am guessing it is the Hard Drive, as I tested another PSU and the same errors ocurred.
I bought a new HD and it will arrive through the week, in the next weekend I will change the HD and I will be posting here if it solved the problem.
"I will be back."
Please doArnold, Rogeriop I'll look forward to hearing from you. When you say you got the same errors with another PSU, do you mean the power surge error?
Yes, the same errors that I had with my original PSU. The computer tried to initiate but could not. If not HD, I am suspecting the motherboard. As I said, I will make the tests and come back here at the weekend.
Cheers!
Unfortunately, there is no way to test a Motherboard without expensive equipment that the Motherboard Manufacturers have. What is normally done is we test everything we can and if everything passes, it has to be the motherboard. The Manufacturers don't like that approach most times, but they leave us no other options. Does your board have a debug LED on it? If so, read the codes when that happens.
Ok, next weekend I will be continuing the diagnoses.