BSOD Microsoft Windows Kernel Power 331C3B3A-2005-44C2-AC5E-77220C37D6

Welcome to SevenForums.

All the dumps come with bugcheck F4. (Usually hard drive/storage related)

Is the firmware for your SSD up to date? Recheck. And use Microsoft Security Essentials during troubleshooting. (Remove AVG with its removal tool by searching in google)

Code:

Model	OCZ-VERTEX2
Model	OCZ-VERTEX3

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
BugCheck F4, {3, fffffa80107e6060, fffffa80107e6340, fffff80002f8e460}
----- ETW minidump data unavailable-----
Probably caused by : wininit.exe
................................................................................
BugCheck F4, {3, fffffa800f401060, fffffa800f401340, fffff80002fd7460}

----- ETW minidump data unavailable-----
Probably caused by : csrss.exe
................................................................................
BugCheck F4, {3, fffffa80109bab30, fffffa80109bae10, fffff80002fcd460}

----- ETW minidump data unavailable-----
Probably caused by : csrss.exe
................................................................................
BugCheck F4, {3, fffffa80108e6060, fffffa80108e6340, fffff80002f80460}

----- ETW minidump data unavailable-----
Probably caused by : wininit.exe
................................................................................
BugCheck F4, {3, fffffa80108d8b30, fffffa80108d8e10, fffff80002f80460}

----- ETW minidump data unavailable-----
Probably caused by : wininit.exe
................................................................................
BugCheck F4, {3, fffffa801099cb30, fffffa801099ce10, fffff80002f80460}

----- ETW minidump data unavailable-----
Probably caused by : wininit.exe
................................................................................
BugCheck F4, {3, fffffa80108d67e0, fffffa80108d6ac0, fffff80002f86460}

----- ETW minidump data unavailable-----
Probably caused by : wininit.exe
................................................................................
BugCheck F4, {3, fffffa80109c4b30, fffffa80109c4e10, fffff80002fdc460}

----- ETW minidump data unavailable-----
Probably caused by : wininit.exe

0: kd> !sysinfo cpuspeed
CPUID:        "Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3410

Run Disk Check on your hard disk for file system errors and bad sectors on it:

• Disk Check

Make sure all the ram clock/speeds are the same.If you are overclocking any hardware, STOP. Reset any changed values back to default.

Take memtest. Run for 8 passes and test each stick in a know good slot for an additional 6 passes.

• RAM - Test with Memtest86+
• Guide to using Memtest86+ - Geeks to Go Forums

The goal is to test all the RAM sticks and all the motherboard slots.

Check your motherboard manual to ensure the RAM sticks are in the recommended motherboard slots. Some motherboards have very specific slots required for the number of RAM sticks installed.

If you get errors, stop the test and continue with the next step.

1. Remove all but one stick of RAM from your computer (this will be RAM stick #1), and run Memtest86 again, for 7 passes.
Be sure to note the RAM stick, use a piece of tape with a number, and note the motherboard slot.
If this stick passes the test then go to step #3.

2. If RAM stick #1 has errors, repeat the test with RAM stick #2 in the same motherboard slot.
If RAM stick #2 passes, this indicates that RAM stick #1 may be bad. If you want to be absolutely sure, re-test RAM stick #1 in another known good slot.
If RAM stick #2 has errors, this indicates another possible bad RAM stick, a possible motherboard slot failure or inadequate settings.
3. Test the next stick of RAM (stick #2) in the next motherboard slot.
If this RAM stick has errors repeat step #2 using a known good stick if possible, or another stick.
If this RAM stick has no errors and both sticks failed in slot#1, test RAM stick #1 in this slot.
4. If you find a stick that passes the test, test it in all the other motherboard slots.

If Part 2 testing shows errors, and all tests in Part 3 show errors, you will need to test the RAM sticks in another computer and/or test other RAM in your computer to identify the problem.

In this way, you can identify whether it is a bad stick of RAM, a bad motherboard, or incompatibility between the sticks.

Errors are sometimes found after 8 passes.
Do this test overnight, before going to bed.

Let us know the results.