BSOD when trying to shut down the computer

Diagnostic Report (1.9.0027.0):
-----------------------------------------
Windows Validation Data-->

Validation Code: 0x8004FE21
Cached Online Validation Code: 0x0
Windows Product Key: *****-*****-RFQ2F-7YJCB-HHRYW
Windows Product Key Hash: l2Hnpsdpm/vUa81R/r2UfqQGSFo=
Windows Product ID: 00426-437-6038173-85209
Windows Product ID Type: 5
Windows License Type: Retail
Windows OS version: 6.1.7601.2.00010100.1.0.001
ID: {8B30073F-C51C-4194-AC9C-75174F912D37}(1)
Is Admin: Yes
TestCab: 0x0
LegitcheckControl ActiveX: N/A, hr = 0x80070002
Signed By: N/A, hr = 0x80070002
Product Name: Windows 7 Ultimate
Architecture: 0x00000009
Build lab: 7601.win7sp1_gdr.120330-1504
TTS Error:
Validation Diagnostic:
Resolution Status: N/A

Vista WgaER Data-->
ThreatID(s): N/A, hr = 0x80070002
Version: N/A, hr = 0x80070002

Windows XP Notifications Data-->
Cached Result: N/A, hr = 0x80070002
File Exists: No
Version: N/A, hr = 0x80070002
WgaTray.exe Signed By: N/A, hr = 0x80070002
WgaLogon.dll Signed By: N/A, hr = 0x80070002

OGA Notifications Data-->
Cached Result: N/A, hr = 0x80070002
Version: N/A, hr = 0x80070002
OGAExec.exe Signed By: N/A, hr = 0x80070002
OGAAddin.dll Signed By: N/A, hr = 0x80070002

OGA Data-->
Office Status: 109 N/A
OGA Version: N/A, 0x80070002
Signed By: N/A, hr = 0x80070002
Office Diagnostics: 025D1FF3-364-80041010_025D1FF3-229-80041010_025D1FF3-230-1_025D1FF3-517-80040154_025D1FF3-237-80040154_025D1FF3-238-2_025D1FF3-244-80070002_025D1FF3-258-3

Browser Data-->
Proxy settings: N/A
User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Win32)
Default Browser: C:\Users\Arthur\AppData\Local\Google\Chrome\Application\chrome.exe
Download signed ActiveX controls: Prompt
Download unsigned ActiveX controls: Disabled
Run ActiveX controls and plug-ins: Allowed
Initialize and script ActiveX controls not marked as safe: Disabled
Allow scripting of Internet Explorer Webbrowser control: Disabled
Active scripting: Allowed
Script ActiveX controls marked as safe for scripting: Allowed

File Scan Data-->
File Mismatch: C:\Windows\system32\en-US\sppc.dll.mui[6.1.7600.16385], Hr = 0x800b0100
File Mismatch: C:\Windows\system32\en-US\sppcext.dll.mui[6.1.7600.16385], Hr = 0x800b0100
File Mismatch: C:\Windows\system32\en-US\slc.dll.mui[6.1.7600.16385], Hr = 0x800b0100
File Mismatch: C:\Windows\system32\en-US\slcext.dll.mui[6.1.7600.16385], Hr = 0x800b0100
File Mismatch: C:\Windows\system32\en-US\sppuinotify.dll.mui[6.1.7600.16385], Hr = 0x800b0100
File Mismatch: C:\Windows\system32\en-US\slui.exe.mui[6.1.7600.16385], Hr = 0x800b0100
File Mismatch: C:\Windows\system32\en-US\sppcomapi.dll.mui[6.1.7600.16385], Hr = 0x800b0100
File Mismatch: C:\Windows\system32\en-US\sppcommdlg.dll.mui[6.1.7600.16385], Hr = 0x800b0100
File Mismatch: C:\Windows\system32\en-US\sppsvc.exe.mui[6.1.7600.16385], Hr = 0x800b0100
File Mismatch: C:\Windows\system32\en-US\user32.dll.mui[6.1.7601.17514], Hr = 0x800b0100

Other data-->
Office Details: <GenuineResults><MachineData><UGUID>{8B30073F-C51C-4194-AC9C-75174F912D37}</UGUID><Version>1.9.0027.0</Version><OS>6.1.7601.2.00010100.1.0.001</OS><Architecture>x64</Architecture><PKey>*****-*****-*****-*****-HHRYW</PKey><PID>00426-437-6038173-85209</PID><PIDType>5</PIDType><SID>S-1-5-21-3354008935-3947547926-123196281</SID><SYSTEM><Manufacturer>System manufacturer</Manufacturer><Model>System Product Name</Model></SYSTEM><BIOS><Manufacturer>American Megatrends Inc.</Manufacturer><Version>3203</Version><SMBIOSVersion major="2" minor="6"/><Date>20120221000000.000000+000</Date></BIOS><HWID>A6BC3407018400FE</HWID><UserLCID>0409</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>Central Standard Time(GMT-06:00)</TimeZone><iJoin>0</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><OEM/><GANotification/></MachineData><Software><Office><Result>109</Result><Products/><Applications/></Office></Software></GenuineResults>

Spsys.log Content: 0x80070002

Licensing Data-->
Software licensing service version: 6.1.7601.17514

Name: Windows(R) 7, Ultimate edition
Description: Windows Operating System - Windows(R) 7, RETAIL channel
Activation ID: ac96e1a8-6cc4-4310-a4ff-332ce77fb5b8
Application ID: 55c92734-d682-4d71-983e-d6ec3f16059f
Extended PID: 00426-00170-437-603817-01-1033-7600.0000-1292012
Installation ID: 021363055082349193520841825703054172357466752144633424
Processor Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88338
Machine Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88339
Use License URL: http://go.microsoft.com/fwlink/?LinkID=88341
Product Key Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88340
Partial Product Key: HHRYW
License Status: Licensed
Remaining Windows rearm count: 4
Trusted time: 5/31/2012 1:24:57 PM

Windows Activation Technologies-->
HrOffline: 0x8004FE21
HrOnline: N/A
HealthStatus: 0x0000000000008000
Event Time Stamp: 5:9:2012 19:43
ActiveX: Registered, Version: 7.1.7600.16395
Admin Service: Registered, Version: 7.1.7600.16395
HealthStatus Bitmask Output:
Tampered File: %systemroot%\system32\sppsvc.exe|sppsvc.exe.mui


HWID Data-->
HWID Hash Current: LAAAAAEAAQABAAEAAAACAAAAAQABAAEAln1iyFhsGl2AOq5GvOJ17eaGLnM=

OEM Activation 1.0 Data-->
N/A

OEM Activation 2.0 Data-->
BIOS valid for OA 2.0: yes, but no SLIC table
Windows marker version: N/A
OEMID and OEMTableID Consistent: N/A
BIOS Information:
ACPI Table Name OEMID Value OEMTableID Value
APIC ALASKA A M I
FACP ALASKA A M I
HPET ALASKA A M I
MCFG ALASKA A M I
SSDT SataRe SataTabl
SSDT SataRe SataTabl
SSDT SataRe SataTabl

When running SFC, did you run it by going into the Recovery Environment at disk bootup, or did you enter it by first loading up the Windows CD and entering the Recovery Environment from there? If the former, you most likely have a failed HD or some issue with your drive controller. If the latter, you might have a messed up or illegal DVD of Windows 7.

Try returning to the Recovery Environment on your Windows disc (not from the drive) and enter CHKDSK C: /R in the command prompt just as you did with SFC scan. If you didn't go the way of the Windows disc, you can follow these instructions up to the point where you enter the command prompt, where you can then enter that command.

If CHKDSK runs and you start seeing a good bit of errors, then most likely you have a hardware problem, that being the aforementioned HD/disk controller. This is especially true if you run through it a second time and it still shows up more errors.

You may also run Seatools on all tests (except Advanced) to verify drive integrity. Note that if you are using outdated and/or bugged RAID drivers, disk controller drivers, chipset drivers, BIOS, or drive firmware (if you are using an SSD), then these can reflect in the hardware tests as well as potentially cause all the file corruptions taking place.

I utilized sfc by opening up my command prompt while in windows. I'll try booting it from the disk and running sfc offline.
I've used chkdsk /r many times before and I haven't had any issues.
I've already ran Seatools and I haven't had any issues.
I have no SD.
My BIOS has been flashed.
As for my disk controller drivers and chipset drivers, I don't know how to determine their integrity.

Just update the disk controller/chipset drivers to latest to ensure they're ok.

Only other recommendation given that you're experiencing both BSODs and usermode crashes is to have you run Memtest86+ for at least 7 passes on your RAM.

Alright, I'm currently on vacation, visiting relatives for a week, so I'll meet with you guys in one weeks time. Until then.

Back, i'm going to purchase a new set of ram chips later tonight, but I have a question.

If my ram chips now are set to 1600 9-9-9-24
Can I purchase anything better if possible?
Meaning, I'll switch out my ram chips now with new ones, but once I rma it, I'm wanting to just have 4 ram chips in total once the RMA transacts and sends my new ones through.
So in essence, what if one set of the ram chips are like 2200 9-9-9-24 [Random] instead of 1600 9-9-9-24?
What would I have to set in my bios?
Is this a good idea to mix and match for slots 1-3 and 2-4. Meaning 1-3 will have the same type of ram chips, as for 2-4.

If anyone is reading, i'm still here ^^"

P.S. Thanks for the other two people that have been helping me in this journey.

To my recollection, you can't mix n match speeds, nor can you deviate from the RAM speeds supported by your motherboard. You'll want to refer to your motherboard's manual for that.

I bought a 1.65V 1600MHZ kingston ram set [2chips]
And I ran a sfc and the only issue that I have on multiple accounts has to do with volsnap.inf
How do I fix this?

Also, the ram before the recently purchased one was a 1.5V 1600MHZ Corsair ram.
By stating that I can't mix and match speeds, does that mean I can't RMA the 1.5V 1600MHZ Corsair RAM and use it with the ones I have in my computer right now?

You could try it, but it is not advised. Mixing voltages can have instability problems, as well. It is possible it will work, but as I said, it is better to get the exact same RAM kits at the exact same time to make sure no changes were made between sets.

I have read of people buying the exact same kits at different times and it causing problems (blue screen crashes) because the new kit has a different voltage than the old kit. When I buy multiple kits, I always buy them at the same time from the same seller to avoid such conflicts.


That said: If you do decide to RMA the RAM, make sure to run both sets at 1.65 Volts. Often, 1.5 Volt RAM can be overclocked to 1.65 Volts with no problems. That does not mean the two sets will work together, but it would be the best way to set it up if you wanted to try.


If you swap any memory components, follow these steps for ESD safety:

1. Shut down and turn off your computer.
2. Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
3. Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
4. Make sure you are grounded by using proper grounding techniques, i.e. work on an anti-static workbench, anti-static desk, or an anti-static pad. Hold something metallic while touching it to the anti-static surface, or use an anti-static wristband to attach to the anti-static material while working. If you do not have an anti-static workbench, desk, or pad, you can use your computer tower/case by finding a metal hold in it, such as a drive bay.

Once these steps have been followed, it is safe to remove and replace components within your computer.