BSOD Stop 0x00000124 and freezing several times a day

Welcome to SevenForums.

Code:

0: kd> lmvm mv91xx
start             end                 module name
fffff880`014b3000 fffff880`0153f000   mv91xx   T (no symbols)           
    Loaded symbol image file: mv91xx.sys
    Image path: \SystemRoot\system32\DRIVERS\mv91xx.sys
    Image name: mv91xx.sys
    Timestamp:        Fri Aug 27 15:49:22 2010 (4C778A22)
    CheckSum:         00050BB0
    ImageSize:        0008C000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
0: kd> !sysinfo cpuspeed
sysinfo: could not find necessary interfaces.
sysinfo: note that mssmbios.sys must be loaded (XPSP2+).

Most of the BSOD-s seem to be caused by the Marvell Drivers itself. Were they installed correctly?

Uninstall and reinstall in the following manner: Click on the Start ► Control Panel ► Programs ► Uninstall a program ► Uninstall everything related to; Marvell and restart the system. Delete remnants of its drivers/older drivers using Driver Fusion/Sweeper, restart again if required. Get latest drivers afresh from: Driver Reference Table

Stop overclocking if you are and uninstall this program:

Code:

Start Menu\Programs\ASUS\AI Suite II	Public:Start Menu\Programs\ASUS\AI Suite II	Public

Avast! can contribute in BSOD-s, please uninstall it and keep MSE for now:

• avast! Uninstall Utility | Download aswClear for avast! Removal

Recommended antivirus program for Windows 7 based on stability compared to others:-

• Microsoft Security Essentials - Free Antivirus for Windows
• Malwarebytes - The Free version
• Good and Free system security combination.

Do not start the free trial of Malware Bytes; remember to deselect that option when prompted.

Run a full scan with both (separately) once downloaded, installed and updated.

Update the firmware of your SSD if there is one.

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

• Disk Check

Run the System File Checker that scans the of all protected Windows 7 system files and replaces incorrect corrupted, changed/modified, or damaged versions with the correct versions if possible:

• Click on the
• Type CMD on Search
• Left click and Run as Administrator
• Type SFC /scannow

Full tutorial here:

• SFC /SCANNOW Command - System File Checker

Make sure all ram clock/speeds are the same and run memory test.

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.

In case of the 124 bugcheck, go through this thread: Stop 0x124 - what it means and what to try step by step, see if it helps in any way.

Good luck.

For monitoring the heat/celsius of the system, use Speccy or HWinfo:

• Speccy - System Information - Free Download
• CPUID - System & hardware benchmark, monitoring, reporting

Pedro Cury said:

Halfway there... but having some trouble...
- Update the firmware of your SSD if there is one.
Is is ok to go from control panel, find the SSDs and click in the update driver option or should I manually find the drivers to install ?

Did you check on the manufacturers website?

Pedro Cury said:

Crap! MSE just found I´m infected with Win32/Malagent trojan!!

I removed, run it again against the infected folder and nothing was found. Running MalwareBytes now.

I checked another thread on this Trojan and it seems to be trickier to remove. But the thread was 1 year old. Any advices If I should use the same approach or just trust it was removed ? Sorry for changing subjects!

It's okay, run malware bytes to be sure.

Any BSOD-s so far?