BSOD when trying to refresh Windows Experience Index.

Hey all,

So I my computer after I upgraded my processor from a Q6600 to a E5450 and I try to update my windows experience I get a BSOD. Now running AV tests and also testing my ram for 3 cycles nothing comes up. I have stress tested the CPU and it can run for hours no problems.

Now Im not sure what could be the problem but any assistance would be greatly appreciated.

~PsyCl0ne

essenbe said:

Hello, PsyCl0ne and welcome to the forums. You had 1 dump file and this is what it said

Code:

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041284, A PTE or the working set list is corrupt.
Arg2: 000000002722b001
Arg3: 000000000000005d
Arg4: fffff70001080000
Debugging Details:

My biggest question is did you research the Motherboard and the CPU? You were not specific on which motherboard you have, only the chipset. Most 680i Motherboards I am aware of are socket 775 made for Core 2 Duo/Core 2 Quad/ Core 2 Extreme CPUs which are 65nm Processors (ARK | Intel® Coreâ„¢2 Quad Processor Q6600 (8M Cache, 2.40 GHz, 1066 MHz FSB)) The E 5450 is a socket 771 Xeon CPU on a 45nm process. (ARK | Intel® Xeon® Processor E5450 (12M Cache, 3.00 GHz, 1333 MHz FSB))

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

Thank you for your reply. You are correct about the 680i sli being a 775 socket but following Mod-lga775-support-for-lga771-xeon-cpus and everything seems to be stable.

Just a side note I have ran mem test for 3 and a bit cycles with no errors and I have ran a couple of cpu stress tests for a minimum of 2 hours and it seems to be stable.

But no worries I will run this test and post back. Thank you for the response I honestly really appreciate it!

Hey so I'm sorry for taking so long to reply. Basically I Raj the test once and at 18 hours the 7th cycle just started and there were no errors so I went and took a nap but when I got up my computer was booted into windows. And there were no logs saved to the 5.1 USB. So I ended up getting my hands on the 5.1 pro version and when I ran it since I have older hardware it loaded a 4.3.7 version.

Any way after 2 days I finally have 10 complete cycles with default settings. There were no errors, please see attached PIC.

~PsyCl0ne

Im just wondering if anyone else can help me with my BSOD.

Ive attached another more recently generated zip with more logs.

essenbe said:

Hello, PsyCl0ne. Sorry, I must have missed your post. In the instructions for memtest86+, you must have missed the part about download from Memtest86+ - Advanced Memory Diagnostic Tool only. However, we will leave that for now, but which test you run can make a big difference. Your last memory dump was from 06/30.

Code:

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041284, A PTE or the working set list is corrupt.
Arg2: 0000000023ce6001
Arg3: 000000000000d48d
Arg4: fffff70001080000

Are you running Raid? Please run Seatools for DOS to check your hard drives. If you are running raid, you will probably not be able to run it. SeaTools for DOS and Windows - How to Use

Also, you are getting a lot of errors from Firefox Plug-In Container. Could you, just as a test, uninstall Firefox? Also, what brand is your motherboard? Manufacturer and model?

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.

Thank you for your reply. My apologies on the memtest. I did initially get the proper one and that ran to 7 complete cycles and I went to sleep before it made it to the 8th and when I woke my computer booted into windows. There were no errors from when I last saw it but I can't give you a PIC for proof.

I used to run raid but it was a separate card that I have since removed. I have also disabled raid in the BIOS.

My motherboard is a 680i sli made by xfx BUT its a mirror clone of the EVGA board.

Also for the command I have ran it previously (also elevated) and there were no errors found.

Also yes Firefox has been puking all over the place when I get home I'm going to be opening a ticket with them. The members in the support forums were unable to help just because the compiler was the one crushing even though there was nothing to compile...