BSOD multiple errors

[Rackers]

I have been getting BSODs the last couple of weeks. I am not sure why there are only two crash dumps but it is what was collected when running the program.

I have tested each memory stick separately using Memtest and then tested them all together with no errors. Does the information in the zip file indicate a culprit?

Thanks all.

EDIT: zip re-attached

 

[essenbe]

Hello, Rackers. Would you please run the bsod Posting Instructions again. I need all the files it produces. Many of them were not there. http://www.sevenforums.com/bsod-help-support/96879-blue-screen-death-bsod-posting-instructions.html

It is also very important we have all of your System Specs in under the 'My System Specs' at the bottom left of your last post. Please include your PSU and CPU cooler. This will help you if you need it.

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 '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​

This is the result of your 2 dump files

Use !analyze -v to get detailed debugging information.

[COLOR="Red"]BugCheck 9F[/COLOR], {3, fffffa8006512a10, fffff80005a8d518, fffffa8005d52d30}

Probably caused by : pci.sys

Followup: MachineOwner

and

Use !analyze -v to get detailed debugging information.

BugCheck A, {10, 2, 1, fffff8000427f833}

[COLOR="Red"]Probably caused by : memory_corruption [/COLOR]( nt!MiClearFilePointer+e3 )

Followup: MachineOwner

I know you said you ran memtest, but which program you used matters a great deal. Please use the program below.

Please Run Memtest86+

   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 consecutive 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 open an 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.

 

[Rackers]

Hi,

Thanks for the quick response. I have re-uploaded zip as requested, it seems larger this time so hopefully its all there.

I ran Memtest86 on each stick individually and together and each time they ran at least 11 passes. I also ran sfc /scannow and no violations were found.

Are there any other indicators in the new file provided?

Thanks again for your help.

 

[essenbe]

One of the 2 dump files specifically stated it was memory corruption. Plus your copy of Windows is an OEM_SLP key for an Asus OEM computer. It cannot be activated without a hackers exploit which alters system Files.

Counterfeit installations such as yours contain heavily modified code that causes the installation to behave it unexpected ways. Analyzing BSOD's and determining their causes on these sorts of installations is very unreliable. For this reason, many analysts won't attempt it.

My recommendation is to install a genuine Windows 7. This will minimize the problems you are experiencing, and make subsequent diagnosis of BSOD's far more reliable. Once you are running a Genuine Windows 7 installation, and are still experiencing BSOD's, we will be happy to help you solve them