|29 Jan 2012||#1|
| || |
Random BSOD - Locale ID: 4105 BCCOde: 1000007e
I've had this issue over and over again and can't seem to solve it. I've taken my friends' advance and ran memory tests and checked the temperature of the CPU, but everytime I do something, it barely lasts more than 15 minutes and it'll reboot.
Here's the BSOD information:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.48
Locale ID: 4105
Additional information about the problem:
OS Version: 6_1_7600
Service Pack: 0_0
Files that help describe the problem:
Read our privacy statement online:
Windows 7 Privacy Statement - Microsoft Windows
If the online privacy statement is not available, please read our privacy statement offline:
I have a Windows 7 Professional X64 machine. This was built by a friend of mine and has a bit of knowledge in computers.
Running on an OEM version of Windows Professional x64. The hardware was all purchased around October 2010.
|My System Specs|
|29 Jan 2012||#2|
| || |
The pre 2009 version of this driver is a known bsod cause.
Please visit this link: Asus tek computer inc. -support- drivers and download p7p55d le
ASUSTeK Computer Inc. -Support- Drivers and Download P7P55D LE
ASUSTeK Computer Inc. - Motherboards- ASUS P5K-VM
Scroll down to the utilities category, then scroll down to the "atk0110 driver for windowsxp/vista/windows 7 32&64-bit" (it's about the 12th item down).
Download and install it.
Go to c:\windows\system32\drivers to check and make sure that the asacpi.sys file is date stamped from 2009 or 2010 (notbefore).
If the above doesnt stop the crashes run these two below.
These crashes were caused by memory corruption (probably a driver).
Please run these two tests to verify your memory and find which driver is causing the problem.
If you are overclocking anything reset to default before running these tests.
In other words STOP!!!
*Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86+ - Advanced Memory Diagnostic Tool
*Boot from the CD, and leave it running for at least 5 or 6 passes.
Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.
Test the sticks individually, and if you find a good one, test it in all slots.
Any errors are indicative of a memory problem.
If a known good stick fails in a motherboard slot it is probably the slot.
Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.
So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Windows 7 Startup Repair feature).
Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Special Pool", "Force Pending I/O Requests" and "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.
Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).
Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.
If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.
|My System Specs|
|30 Jan 2012||#4|
| || |
My pleasure and good luck
|My System Specs|
|Similar help and support threads for2: Random BSOD - Locale ID: 4105 BCCOde: 1000007e|
|Random BSOD - Locale ID 4105?||BSOD Help and Support|
|Bsod frequently Locale ID 4105||BSOD Help and Support|
|Random BSOD BCCode: 1000007e||BSOD Help and Support|
|BSOD at random times BCCode: 1000007e||BSOD Help and Support|
|Random BSOD, Locale ID: 1050, BCCode: 124. ZIP included||BSOD Help and Support|
|Repeated random BSOD; how would I stop it, Locale ID: 4105 BCCode: 19||BSOD Help and Support|
|BSOD locale ID: 4105 PLEASE HELP||BSOD Help and Support|
|Our Sites ||Site Links ||About Us ||Find Us |
© Designer Media Ltd
All times are GMT -5. The time now is 08:07 PM.