Scottamc, I am going to ask you to do a few things, please. It is important for us to know what hardware you have in as much detail as possible. We very often need to look up a component to help you. To do that we need the Manufacturer and model for every component in your computer, including the PSU and the CPU cooler. These are the instructions I usually give that will give you some guidance and help in finding out what they are, in case you don't already know. Please read it carefully. We always like it in the location in the instructions.
Please fill out your System Specs
Information
Your System Specs will help us to help you, and doing it in this manner will make them available to all helpers in every post and keep us from hunting for them. We ask that you fill them out in as much detail as possible including Desktop or Laptop, Model number if it is an OEM computer and all components with the Manufacturer and Model number if possible.
If you will go to your last post and click the 'My System Specs' in the bottom left of the post, you will find a link to update your system specs. Please fill those out in as much detail as possible, making sure to click save at the bottom of the page. If you would like to know what we would like, you can click 'My System Specs' at the bottom left of this post to see mine. If you do not know what your components are, this will help you accomplish this task.
http://www.sevenforums.com/tutorials/180324-system-info-see-your-system-specs.html
The files you provided gave us some information that we need. However, for some reason all the files were not there. Please re run the BSOD Posting instructions (
http://www.sevenforums.com/bsod-help-support/96879-blue-screen-death-bsod-posting-instructions.html) again. This time try option 2 and click the 'Grab All' button and give it time to complete it's collection. Please upload the unedited file with your next post.
You have quite a few dump files. The only thing common in them is almost every one is a different reason and different stop code.
Code:
L1E62x64
start end module name
fffff880`045d2000 fffff880`045e4000 L1E62x64 T (no symbols)
Loaded symbol image file: L1E62x64.sys
Image path: \SystemRoot\system32\DRIVERS\L1E62x64.sys
Image name: L1E62x64.sys
Timestamp: [COLOR=red]Thu Jun 11 01:45:22 2009[/COLOR] (4A30A802)
CheckSum: 00011259
ImageSize: 00012000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
That is your Atheros AR8121/AR8113/AR8114 PCI-E Ethernet Controller (NDIS6.20). You will notice the date of the driver is quite old and needs updating. You should be able to update it from your Motherboard's web site, if it is a part of your motherboard, which is the case most of the time. Please do that first.
Next, please open a elevated command prompt ( click start, type
cmd in the search box,
right click on the cmd entry and select run as administrator) in the black box that opens, copy/paste
sfc /scannow. If you decide to type it, notice the space between the sfc and the /. It is a system file checker which will scan your system files and attempt to correct any missing or corrupt files. What we want are the results to say windows found no integrity violations. If it says files were found but could not be repaired, close the box, reboot and run it again, after opening the administrative command prompt. You may have to reboot and run it three times for it to repair all system files. If it can't repair them after 3 reboots, let us know.
What is common when we get different stop codes and each is a different reason is this is the case.
Code:
Use !analyze -v to get detailed debugging information.
BugCheck 27, {baad0073, fffff88003a79368, fffff88003a78bc0, fffff88001241dd1}
Probably caused by : [COLOR=red]hardware[/COLOR] ( csc!CscStorepLowIoSetInformationFile+b6 )
Followup: MachineOwner
And this is the most important to me.
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {0, 2, 1, fffff80002b0527c}
Probably caused by : [COLOR=red]memory_corruption[/COLOR] ( nt!MiInitializePfnForOtherProcess+0 )
Followup: MachineOwner
If this is the cause, then almost everything in the dump files is not reliable. That's why it is the most important to me, and why, even though it is one of the longest tests to run, it is one of the most important to find out right away. so, next,
Information
Please 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.zip
Extract 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.
If at any time you have questions or do not understand the instructions, please ask. I don't mind a bit explaining why I am asking for a certain test or further explain any instructions I have given.
