BSOD Problem

6 memory dumps dated from 17 May 2010 to 04 Jun 2010 (3 weeks)
6 different STOP errors, and 6 different causes blamed.
This looks to me like a hardware/compatibility problem - especially due to the STOP 0x124 error.
So, the question is "What did you do to the system in the days preceding the first BSOD?"

So, I'd suggest starting with these hard drive and file system diagnostics.

H/W Diagnostics:
Please start by running these bootable hardware diagnostics:
Memory Diagnostics (read the details at the link)
HD Diagnostic (read the details at the link)

Also, please run one of these free, independent online malware scans to ensure that your current protection hasn't been compromised: Malware (read the details at the link)

Then do this to ensure the file system is OK:

CHKDSK /R /F:
Run CHKDSK /R /F from an elevated (Run as adminstrator) Command Prompt. Please do this for each hard drive on your system.
When it tells you it can't do it right now - and asks you if you'd like to do it at the next reboot - answer Y (for Yes) and press Enter. Then reboot and let the test run. It may take a while for it to run, but keep an occasional eye on it to see if it generates any errors. See "CHKDSK LogFile" below in order to check the results of the test.

Elevated Command Prompt:
Go to Start and type in "cmd.exe" (without the quotes)
At the top of the Search Box, right click on Cmd.exe and select "Run as administrator"

CHKDSK LogFile:
Go to Start and type in "eventvwr.msc" (without the quotes) and press Enter
Expand the Windows logs heading, then select the Application log file entry.
Double click on the Source column header.
Scroll down the list until you find the Chkdsk entry (wininit for Win7) (winlogon for XP).
Copy/paste the results into your next post.

Once that's done, please have a look at this topic for some troubleshooting steps for the STOP 0x124 error: https://www.sevenforums.com/crash-loc...-what-try.html

Summary of the BSOD's:

Code:

Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Fri Jun  4 06:25:14.317 2010 (GMT-4)
System Uptime: 0 days 22:17:56.327
BugCheck 24, {1904fb, fffff8800895c6e8, fffff8800895bf50, fffff80003298c25}
Probably caused by : Ntfs.sys ( Ntfs!NtfsFullDeleteLcb+45 )
PROCESS_NAME:  System
BUGCHECK_STR:  0x24
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sat May 29 09:36:12.614 2010 (GMT-4)
System Uptime: 3 days 4:04:51.108
BugCheck 50, {fffffffffff70000, 0, fffff80003314c30, 0}
Probably caused by : memory_corruption ( nt!MiCaptureProtectionFromProto+1c )
BUGCHECK_STR:  0x50
PROCESS_NAME:  YahooMessenger
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Mon May 24 07:04:58.780 2010 (GMT-4)
System Uptime: 0 days 4:26:06.082
BugCheck 1E, {ffffffffc0000005, fffff88003c758e6, 1, 211}
Probably caused by : rdbss.sys ( rdbss!RxTrackerUpdateHistory+66 )
BUGCHECK_STR:  0x1E
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Mon May 24 02:37:35.566 2010 (GMT-4)
System Uptime: 0 days 20:32:51.985
BugCheck A, {fffffa80871c5550, 2, 0, fffff800032bd989}
Probably caused by : NETIO.SYS ( NETIO!NetiopIoWorkItemRoutine+3b )
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sun May 23 06:02:23.196 2010 (GMT-4)
System Uptime: 0 days 23:40:59.235
BugCheck 1, {60408bcd, 0, ffff, fffff8800e1c5c60}
Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceExit+245 )
BUGCHECK_STR:  0x1
PROCESS_NAME:  svchost.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sun May 16 19:35:16.841 2010 (GMT-4)
System Uptime: 0 days 5:55:30.904
BugCheck 124, {0, fffffa8007598028, b2000040, 800}
Probably caused by : hardware
BUGCHECK_STR:  0x124_GenuineIntel
PROCESS_NAME:  svchost.exe

Try disabling sleep/hibernation for a while to see if that makes a difference. FWIW - I just changed motherboards and that fixed my sleep/hibernate issues (BSOD's) that I've had since Win7 was in beta. What's the make and model of your motherboard?

I had issues with an Asus P6T Deluxe (and replaced it with an Asus P6T Deluxe v2).

The P5 series of boards have issues with Win7 and RAM settings. Research the proper settings for your RAM at the RAM manufacturer's website and the Asus website - then set the RAM to those settings/timings/voltages. (NOT to Auto).

Also, check for a driver named ASACPI.sys - it's the Asus ATK0110 ACPI Utility Driver. Win7 installs the 2005 version from Microsoft's servers - and it's a known cause of BSOD's. The latest version is a 2009/2010 file.

Remove the following drivers and then install freshly downloaded copies of the latest versions:
- video
- chipset
- storage

Only install Win7 drivers. If you can't locate them, post back and we'll see what we can find.

DO NOT USE THE ONE FROM WINDOWS UPDATE!!!
It will probably cause BSOD's

Visit the Asus download site and get it from there. ASUSTeK Computer Inc.-Support- download_item_mkt (Under the Utilities section - use the AISuite or PCProbe to install it)

If that doesn't work, then try this one (attached) that I downloaded for my board

The key here is the date of the driver - if it's 2004 or 2005 it's trouble!
Those from 2009/2010 are not a problem.