BCCode 3b : BSODs within first 5~10 minutes of startup

Hi,

I've been getting BSODs within the first few minutes of my startup and I was hoping some of you could help me with my problem for I have no idea why this is happening.

I've attached the memory dumps and I hope that they are useful.

Thanks in advance for the help!

Hello and welcome to SevenForums ThatPerson,

A quick look at your bugcheck and usual causes:

Code:

STOP 0x00000024: NTFS_FILE_SYSTEM 
Usual causes:  Disk corruption, insufficient physical memory, Device driver, 
Indexing, Resident antivirus, backup, defrag programs, Disk/Drive failing/failure
BugCheck 24, {1904fb, fffff8800a65a078, fffff8800a6598d0, fffff880012c60b7}
Unable to load image \SystemRoot\system32\DRIVERS\eamon.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for eamon.sys
*** ERROR: Module load completed but symbols could not be loaded for eamon.sys
Probably caused by : Ntfs.sys ( Ntfs!NtfsCommonClose+1e7 )
------------------
STOP 0x00000050: PAGE_FAULT_IN_NONPAGED_AREA  
Usual causes:  Defective hardware (particularly memory - but not just RAM), 
Faulty system service, Antivirus,  Device driver, NTFS corruption, BIOS
BugCheck 50, {fffff8800ceb59c0, 0, fffff9600010b7e2, 0}
Could not read faulting driver name
Probably caused by : memory_corruption
------------------
STOP 0x0000001E: KMODE_EXCEPTION_NOT_HANDLED
Usual causes:  Device driver, hardware, System service, compatibility, 
Remote control programs, memory, BIOS
BugCheck 1E, {ffffffffc0000005, fffff80001a8534b, 0, ffffffffffffffff}
Probably caused by : memory_corruption
------------------
STOP 0x0000003B: SYSTEM_SERVICE_EXCEPTION 
Usual causes:  System service, Device driver, graphics driver, ?memory
BugCheck 3B, {c0000005, fffff960002a37e2, fffff88007fa5140, 0}
Probably caused by : memory_corruption
------------------
STOP 0x0000003B: SYSTEM_SERVICE_EXCEPTION 
Usual causes:  System service, Device driver, graphics driver, ?memory
BugCheck 3B, {c0000005, fffff80002598382, fffff880094ad9e0, 0}
Probably caused by : ntkrnlmp.exe ( nt!CmpAllocateKeyControlBlock+72 )

FYI, eamon.sys = ESet NOD32 antivirus system monitor driver.

Suggestions based upon evidence from your crashes:
Please uninstall ESET antivirus as it's contributing in your crashes. Replace with Microsoft Security Essentials, at least to test. You may however install it back if we know it was not the cause of your crashes.

• Uninstallers (removal tools) for common antivirus software - ESET Knowledgebase

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

• Microsoft Security Essentials - Free Antivirus for Windows
• Microsoft Security Essentials Download | Free Spyware Protection
• 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.

Observe and let us know if the system is stable.

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:

• SFC /SCANNOW Command - System File Checker

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

• Disk Check

Free up the start-up, nothing except the antivirus is usually needed.

• Startup Programs - Change
• Troubleshoot Application Conflicts by Performing a Clean Startup

----------
Take memtest to make sure nothing is wrong with your RAM. 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.

Let us know the results and further BSOD-s if any.

Thanks koolkat77,

I've deleted Eset and replaced it with Microsoft security essentials, I've run the Systemfile checker, the disk check as well as the Ram tests.
The systemfile checker reported no problems, nor did the disk check or the ram tests.

Unfortunately, I am still getting BSODs.

I have attached the two new BSOD dumps along with the old ones in order to help find the problem. I noticed that there was no BSOD on startup after the Diskcheck, yet today, I once again got a BSOD.

I attached both drive information using crystal disk. I ran SeaTools on both drives for both short generic and long generic tests and all 4 passed.

I ran 6 passes for the Memtest koolkat without getting any errors.

Thanks for the help.

I have not updated the SSD to it`s latest firmware and I cannot update it at the moment since I am running windows from it.

I just went into safe mode and the BSOD appeared later than a normal boot. This time though, the BCcode was 50 and not 3b. I have attached the new dumps as well to give you more information.