Is my SSD failing? Please help!

[ArcticWonder]

So I haven't used my PC in a while, it's been sitting off. I just bought Portal 2 on black friday because it was cheap, and I loved the 1st portal. I downloaded it on my PC and began playing, 1 hour or so in I got the blue screen. It continued to happen, and even happens outside of game which lets me know it's not game drivers or anything. I did a full pc test and everything passed except for the SSD, it said it couldn't test it because there wasn't enough free space. My SSD has 20gb of free space still! I don't know what to do, is it definitely my SSD because of that?

By the way, I noticed some things were randomly disappearing from my PC for a while now. I know thats a sign of my drive failing. But here's the thing: the files that have gone missing are files on my secondary drive, a 1 TB HDD. So maybe the 1TB is going out and causing the BSOD? Or is my luck horrible and are BOTH going out? Please help me I am in a serious pickle!!!

 

[inzone]

As a general rule you shouldn't fill our SSD past 80% capacity because it does affect it. Things do happen and there is no way to know or controlit so it both drives happen to go at the same time then that's your bad luck to have that happen. You should make sure that what you think is happening is actually that and not something else. So run some more tests on the hard drives and try to free up some space on the SSD.

 

[nukemaster]

You may want to use CrystalDiskInfo to check out the SMART attributes for the SSD as well see if anything stands out.

See what the following says

Read Error
Reallocated Sectors
Failing Block Count
Erase Fail
Wear Level
Life Time Used

http://crystalmark.info/download/index-e.html#CrystalDiskInfo

You can also see SMART on the hard drive too. I do not recommend normal tests on SSD's as it takes lots of write cycles to do a test that the controller may be remapping(to other locations even if you have bad sectors) anyway. SSD's are not like hard drives and do not test the same way.

 

[ArcticWonder]

You may want to use CrystalDiskInfo to check out the SMART attributes for the SSD as well see if anything stands out.

See what the following says

Read Error
Reallocated Sectors
Failing Block Count
Erase Fail
Wear Level
Life Time Used

http://crystalmark.info/download/index-e.html#CrystalDiskInfo

You can also see SMART on the hard drive too. I do not recommend normal tests on SSD's as it takes lots of write cycles to do a test that the controller may be remapping(to other locations even if you have bad sectors) anyway. SSD's are not like hard drives and do not test the same way.

I used CrystalDiskInfo and everything looked fine. Here's a screenshot of the SSD's results: [url=https://dl.dropbox.com/u/43798842/Untitled.jpg]https://dl.dropbox.com/u/43798842/Untitled.jpg [/url]

What else could be causing this freezing and the BSOD? My first guess is motherboard... I tested my CPU, GPU, and they both were fine. I also wonder if my power supply is putting out wonky powers causing these problems idk.... BTW thanks for the replies hoping for much more help!

 

[nukemaster]

Your screen looks very good. That drive looks to be in NEW condition.

Do you know if you are running the latest firmware? Please read the notes for firmware updates as some erase the drive. A backup is ALWAYS a good idea(EaseUS has some free software if you do not have anything else, I would recommend you do the backup to another system so you can restore the image if needed. The drive may need to be aligned after this as well. Sorry for all the work. You can always check ALL other options first).

Before upgrading the firmware, be sure to back up important data
to a separate storage medium. Complete data loss may occur as a
result of the firmware update process!

1. After downloading the firmware installation package, extract
the zip file. If you are running Windows OS, browse to the
extracted folder and launch "Mushkin_FieldUpdater.exe" with admin-
istrative privileges. If SF_FieldUpdater is not launched with
administrative privileges, the Chronos SSD(s) will not be dis-
covered by the updater. If running Linux, launch
"SF_FieldUpdater_FC14-32Bit" or "SF_FieldUpdater_FC12-64Bit".

2. Once the updater application is launched, the Chronos SSD(s)
should be discovered in the window. Check the box beside the
drive you want to update. Select the "Update Firmware" button on
the bottom left. A navigation window will appear.

3. Highlight the “MKN_FW_5-0-4.ffp” file from the extracted folder,
then click "Open" at the bottom right of the window. You will then
receive a warning message. Click "Proceed" to continue flashing
the firmware.

4. The system may automatically reboot after the firmware update
is complete. If it does not reboot after 5 minutes, shut the
machine down and restart.

Congratulations, your Chronos SSD is now updated!

http://www.mushkin.com/Digital-Storage/SSDs/MKNSSDCR60GB.aspx

Did you get the blue screen codes by any chance? If not, This can get you the codes and even give you more info on the blue screens.
http://www.nirsoft.net/utils/blue_screen_view.html

Now as for missing files. A scan of the hard drive may help get to the answer of that.

 

[ArcticWonder]

I don't really know what exactly causes your problem, perhaps the virus infection or other things. You should check it clearly.
But for the safety of your files, you have to run a third party recovery tool to restore the files at first. You can try this free one:
http://www.squidoo.com/tested-data-recovery-freeware-recommendations-for-you
I have used it to successfully retrieve my inaccessible data. i hope it will help you, too.

That reminds me everyone, viruses and malware, etc are not a problem I know beyond a shadow of a doubt I have none because I literally never visit anywhere on that pc. All my internet browsing is on this laptop, not my gaming pc.

 

[ArcticWonder]

Your screen looks very good. That drive looks to be in NEW condition.

Do you know if you are running the latest firmware? Please read the notes for firmware updates as some erase the drive. A backup is ALWAYS a good idea(EaseUS has some free software if you do not have anything else, I would recommend you do the backup to another system so you can restore the image if needed. The drive may need to be aligned after this as well. Sorry for all the work. You can always check ALL other options first).

Before upgrading the firmware, be sure to back up important data
to a separate storage medium. Complete data loss may occur as a
result of the firmware update process!

1. After downloading the firmware installation package, extract
the zip file. If you are running Windows OS, browse to the
extracted folder and launch "Mushkin_FieldUpdater.exe" with admin-
istrative privileges. If SF_FieldUpdater is not launched with
administrative privileges, the Chronos SSD(s) will not be dis-
covered by the updater. If running Linux, launch
"SF_FieldUpdater_FC14-32Bit" or "SF_FieldUpdater_FC12-64Bit".

2. Once the updater application is launched, the Chronos SSD(s)
should be discovered in the window. Check the box beside the
drive you want to update. Select the "Update Firmware" button on
the bottom left. A navigation window will appear.

3. Highlight the “MKN_FW_5-0-4.ffp” file from the extracted folder,
then click "Open" at the bottom right of the window. You will then
receive a warning message. Click "Proceed" to continue flashing
the firmware.

4. The system may automatically reboot after the firmware update
is complete. If it does not reboot after 5 minutes, shut the
machine down and restart.

Congratulations, your Chronos SSD is now updated!

http://www.mushkin.com/Digital-Storage/SSDs/MKNSSDCR60GB.aspx

Did you get the blue screen codes by any chance? If not, This can get you the codes and even give you more info on the blue screens.
http://www.nirsoft.net/utils/blue_screen_view.html

Now as for missing files. A scan of the hard drive may help get to the answer of that.

I doubt it's firmware because everything has been fine for a year. I did install firmware for it when I got it, I don't see why a new version being available would screw it up all of a sudden. But thanks for the ideas. I'm still leaning toward MOBO or PSU. I need to do some testing of my mobo.

 

[nukemaster]

Please keep us posted.

You are very right, most of the time if it works, don't update it. Only some bugs have been over time(like the 2000 hour bug one SSD had in the past). at 600 hours your SSD is sooo new.

 

[ArcticWonder]

Please keep us posted.

You are very right, most of the time if it works, don't update it. Only some bugs have been over time(like the 2000 hour bug one SSD had in the past). at 600 hours your SSD is sooo new.

Yeah I only using my gaming PC FOR gaming, I don't leave it on so the drive has had a very easy life. I just tested my voltages and they all seem very good. So now it's down to my Mobo or RAM. I will try to find my BSOD codes.. How do I use that Blue Screen View program to find the codes?

 

[nukemaster]

When you open it, It will look at your mini dump files and show you all the info The Bug Check Code is the big one it will also show any drivers that crashes too(under Crash Address).

Do not always go by what it says crashed. For instance I have good number of 0x0000001e and 0x00000124 from overclocking voltage testing(trying to get as low as I could.). They show ntoskrnl.exe and hal.dll(even listed my network card once) as crashing, but it has nothing to do with Windows it self and all to do with instability caused by too little voltage.

So you if you happen to be overclocking, I would go to stock for testing.

 

[ArcticWonder]

When you open it, It will look at your mini dump files and show you all the info The Bug Check Code is the big one it will also show any drivers that crashes too(under Crash Address).

Do not always go by what it says crashed. For instance I have good number of 0x0000001e and 0x00000124 from overclocking voltage testing(trying to get as low as I could.). They show ntoskrnl.exe and hal.dll(even listed my network card once) as crashing, but it has nothing to do with Windows it self and all to do with instability caused by too little voltage.

So you if you happen to be overclocking, I would go to stock for testing.

I used the program. It showed ntoskrnl.exe like you said, beyond that I' 'm not sure how to determine what it's telling me.

 

[ArcticWonder]

When you open it, It will look at your mini dump files and show you all the info The Bug Check Code is the big one it will also show any drivers that crashes too(under Crash Address).

Do not always go by what it says crashed. For instance I have good number of 0x0000001e and 0x00000124 from overclocking voltage testing(trying to get as low as I could.). They show ntoskrnl.exe and hal.dll(even listed my network card once) as crashing, but it has nothing to do with Windows it self and all to do with instability caused by too little voltage.

So you if you happen to be overclocking, I would go to stock for testing.

Here are the codes, if you care to slog through them. Idk what they mean
ntoskrnl.exe ntoskrnl.exe+329602 fffff800`02014000 fffff800`025ef000 0x005db000 0x4f558ca0 3/5/2012 8:03:44 PM Microsoft® Windows® Operating System NT Kernel & System 6.1.7600.16973 (win7_gdr.120305-1504) Microsoft Corporation C:\Windows\system32\ntoskrnl.exe
hal.dll fffff800`025ef000 fffff800`02638000 0x00049000 0x4a5bdf08 7/13/2009 5:27:36 PM
kdcom.dll fffff800`01fb0000 fffff800`01fba000 0x0000a000 0x4d4d40d9 2/5/2011 4:21:45 AM
mcupdate_AuthenticAMD.dll fffff880`00c95000 fffff880`00ca2000 0x0000d000 0x4a5bdf65 7/13/2009 5:29:09 PM
PSHED.dll fffff880`00ca2000 fffff880`00cb6000 0x00014000 0x4a5be027 7/13/2009 5:32:23 PM Microsoft® Windows® Operating System Platform Specific Hardware Error Driver 6.1.7600.16385 (win7_rtm.090713-1255) Microsoft Corporation C:\Windows\system32\PSHED.dll
CLFS.SYS fffff880`00cb6000 fffff880`00d14000 0x0005e000 0x4a5bc11d 7/13/2009 3:19:57 PM
CI.dll fffff880`00d14000 fffff880`00dd4000 0x000c0000 0x4a5be01d 7/13/2009 5:32:13 PM
Wdf01000.sys fffff880`00e6f000 fffff880`00f13000 0x000a4000 0x4a5bc19f 7/13/2009 3:22:07 PM
WDFLDR.SYS fffff880`00f13000 fffff880`00f22000 0x0000f000 0x4a5bc11a 7/13/2009 3:19:54 PM
ACPI.sys fffff880`00f22000 fffff880`00f79000 0x00057000 0x4a5bc106 7/13/2009 3:19:34 PM
WMILIB.SYS fffff880`00f79000 fffff880`00f82000 0x00009000 0x4a5bc117 7/13/2009 3:19:51 PM
msisadrv.sys fffff880`00f82000 fffff880`00f8c000 0x0000a000 0x4a5bc0fe 7/13/2009 3:19:26 PM
pci.sys fffff880`00f8c000 fffff880`00fbf000 0x00033000 0x4a5bc117 7/13/2009 3:19:51 PM
vdrvroot.sys fffff880`00fbf000 fffff880`00fcc000 0x0000d000 0x4a5bcadb 7/13/2009 4:01:31 PM
partmgr.sys fffff880`00fcc000 fffff880`00fe1000 0x00015000 0x4a5bc11e 7/13/2009 3:19:58 PM
volmgr.sys fffff880`00fe1000 fffff880`00ff6000 0x00015000 0x4a5bc11d 7/13/2009 3:19:57 PM
volmgrx.sys fffff880`00e00000 fffff880`00e5c000 0x0005c000 0x4a5bc141 7/13/2009 3:20:33 PM
pciide.sys fffff880`00e5c000 fffff880`00e63000 0x00007000 0x4a5bc115 7/13/2009 3:19:49 PM
PCIIDEX.SYS fffff880`00dd4000 fffff880`00de4000 0x00010000 0x4a5bc114 7/13/2009 3:19:48 PM
mountmgr.sys fffff880`00de4000 fffff880`00dfe000 0x0001a000 0x4a5bc11a 7/13/2009 3:19:54 PM
atapi.sys fffff880`00e63000 fffff880`00e6c000 0x00009000 0x4a5bc113 7/13/2009 3:19:47 PM
ataport.SYS fffff880`00c00000 fffff880`00c2a000 0x0002a000 0x4a5bc118 7/13/2009 3:19:52 PM
msahci.sys fffff880`00c2a000 fffff880`00c35000 0x0000b000 0x4a5bcabd 7/13/2009 4:01:01 PM
amdxata.sys fffff880`00c35000 fffff880`00c40000 0x0000b000 0x4ba3a3ca 3/19/2010 8:18:18 AM
fltmgr.sys fffff880`00c40000 fffff880`00c8c000 0x0004c000 0x4a5bc11f 7/13/2009 3:19:59 PM
fileinfo.sys fffff880`0102f000 fffff880`01043000 0x00014000 0x4a5bc481 7/13/2009 3:34:25 PM
Ntfs.sys fffff880`01043000 fffff880`011e5000 0x001a2000 0x4d79996d 3/10/2011 7:39:25 PM
msrpc.sys fffff880`01274000 fffff880`012d2000 0x0005e000 0x4a5bc17c 7/13/2009 3:21:32 PM
ksecdd.sys fffff880`012d2000 fffff880`012ec000 0x0001a000 0x4ec48579 11/16/2011 7:54:33 PM
cng.sys fffff880`012ec000 fffff880`0135f000 0x00073000 0x4ec48cfb 11/16/2011 8:26:35 PM
pcw.sys fffff880`0135f000 fffff880`01370000 0x00011000 0x4a5bc0ff 7/13/2009 3:19:27 PM
Fs_Rec.sys fffff880`01370000 fffff880`0137a000 0x0000a000 0x4f4ef2fc 2/29/2012 7:54:36 PM
ndis.sys fffff880`014f1000 fffff880`015e3000 0x000f2000 0x4a5bc184 7/13/2009 3:21:40 PM
NETIO.SYS fffff880`01400000 fffff880`01460000 0x00060000 0x4a5bc18a 7/13/2009 3:21:46 PM
ksecpkg.sys fffff880`01460000 fffff880`0148b000 0x0002b000 0x4ec48d32 11/16/2011 8:27:30 PM
tcpip.sys fffff880`01601000 fffff880`017fe000 0x001fd000 0x4a5bc26e 7/13/2009 3:25:34 PM
fwpkclnt.sys fffff880`0148b000 fffff880`014d5000 0x0004a000 0x4a5bc164 7/13/2009 3:21:08 PM
vmstorfl.sys fffff880`014d5000 fffff880`014e5000 0x00010000 0x4a5bc67e 7/13/2009 3:42:54 PM
volsnap.sys fffff880`0137a000 fffff880`013c6000 0x0004c000 0x4a5bc128 7/13/2009 3:20:08 PM
spldr.sys fffff880`014e5000 fffff880`014ed000 0x00008000 0x4a0858bb 5/11/2009 8:56:27 AM
rdyboost.sys fffff880`013c6000 fffff880`01400000 0x0003a000 0x4a5bc48a 7/13/2009 3:34:34 PM
mup.sys fffff880`015e3000 fffff880`015f5000 0x00012000 0x4a5bc201 7/13/2009 3:23:45 PM
hwpolicy.sys fffff880`015f5000 fffff880`015fe000 0x00009000 0x4a5bc0fa 7/13/2009 3:19:22 PM
fvevol.sys fffff880`01200000 fffff880`0123a000 0x0003a000 0x4abd7db2 9/25/2009 6:34:26 PM
disk.sys fffff880`0123a000 fffff880`01250000 0x00016000 0x4a5bc11d 7/13/2009 3:19:57 PM
CLASSPNP.SYS fffff880`018e9000 fffff880`01919000 0x00030000 0x4a5bc11e 7/13/2009 3:19:58 PM
cdrom.sys fffff880`0194f000 fffff880`01979000 0x0002a000 0x4a5bc11a 7/13/2009 3:19:54 PM
aswSnx.SYS fffff880`02a85000 fffff880`02b75000 0x000f0000 0x50334f74 8/21/2012 1:05:56 AM
cmdguard.sys fffff880`01800000 fffff880`01891000 0x00091000 0x4eef875e 12/19/2011 10:50:06 AM
Null.SYS fffff880`02b75000 fffff880`02b7e000 0x00009000 0x4a5bc109 7/13/2009 3:19:37 PM
Beep.SYS fffff880`02b7e000 fffff880`02b85000 0x00007000 0x4a5bca8d 7/13/2009 4:00:13 PM
vga.sys fffff880`02b85000 fffff880`02b93000 0x0000e000 0x4a5bc587 7/13/2009 3:38:47 PM
VIDEOPRT.SYS fffff880`02b93000 fffff880`02bb8000 0x00025000 0x4a5bc58b 7/13/2009 3:38:51 PM
watchdog.sys fffff880`02bb8000 fffff880`02bc8000 0x00010000 0x4a5bc53f 7/13/2009 3:37:35 PM
RDPCDD.sys fffff880`02bc8000 fffff880`02bd1000 0x00009000 0x4a5bce62 7/13/2009 4:16:34 PM
rdpencdd.sys fffff880`02bd1000 fffff880`02bda000 0x00009000 0x4a5bce62 7/13/2009 4:16:34 PM
rdprefmp.sys fffff880`02bda000 fffff880`02be3000 0x00009000 0x4a5bce63 7/13/2009 4:16:35 PM
Msfs.SYS fffff880`02be3000 fffff880`02bee000 0x0000b000 0x4a5bc113 7/13/2009 3:19:47 PM
Npfs.SYS fffff880`02bee000 fffff880`02bff000 0x00011000 0x4a5bc114 7/13/2009 3:19:48 PM
tdx.sys fffff880`02a00000 fffff880`02a1e000 0x0001e000 0x4a5bc16b 7/13/2009 3:21:15 PM
TDI.SYS fffff880`02a1e000 fffff880`02a2b000 0x0000d000 0x4a5bc16e 7/13/2009 3:21:18 PM
aswTdi.SYS fffff880`02a2b000 fffff880`02a3d000 0x00012000 0x50334f3d 8/21/2012 1:05:01 AM
cmdhlp.sys fffff880`02a3d000 fffff880`02a49000 0x0000c000 0x4eef8719 12/19/2011 10:48:57 AM
afd.sys fffff880`02e41000 fffff880`02eca000 0x00089000 0x4efa940c 12/27/2011 7:59:08 PM
aswrdr2.sys fffff880`02eca000 fffff880`02eda000 0x00010000 0x50334f4c 8/21/2012 1:05:16 AM
netbt.sys fffff880`02eda000 fffff880`02f1f000 0x00045000 0x4a5bc178 7/13/2009 3:21:28 PM
wfplwf.sys fffff880`02f1f000 fffff880`02f28000 0x00009000 0x4a5bccb6 7/13/2009 4:09:26 PM
pacer.sys fffff880`02f28000 fffff880`02f4e000 0x00026000 0x4a5bccc5 7/13/2009 4:09:41 PM
inspect.sys fffff880`02f4e000 fffff880`02f66000 0x00018000 0x4eef8714 12/19/2011 10:48:52 AM
netbios.sys fffff880`02f66000 fffff880`02f75000 0x0000f000 0x4a5bccb6 7/13/2009 4:09:26 PM
serial.sys fffff880`02f75000 fffff880`02f92000 0x0001d000 0x4a5bcaa8 7/13/2009 4:00:40 PM
wanarp.sys fffff880`02f92000 fffff880`02fad000 0x0001b000 0x4a5bcced 7/13/2009 4:10:21 PM
termdd.sys fffff880`02fad000 fffff880`02fc1000 0x00014000 0x4a5bce64 7/13/2009 4:16:36 PM
rdbss.sys fffff880`01891000 fffff880`018e2000 0x00051000 0x4a5bc219 7/13/2009 3:24:09 PM
nsiproxy.sys fffff880`02fc1000 fffff880`02fcd000 0x0000c000 0x4a5bc15e 7/13/2009 3:21:02 PM
mssmbios.sys fffff880`02fcd000 fffff880`02fd8000 0x0000b000 0x4a5bc3be 7/13/2009 3:31:10 PM
discache.sys fffff880`02fd8000 fffff880`02fe7000 0x0000f000 0x4a5bc52e 7/13/2009 3:37:18 PM
csc.sys fffff880`01979000 fffff880`019fc000 0x00083000 0x4a5bc22a 7/13/2009 3:24:26 PM
dfsc.sys fffff880`02e00000 fffff880`02e1e000 0x0001e000 0x4db78623 4/26/2011 6:57:39 PM
blbdrive.sys fffff880`02e1e000 fffff880`02e2f000 0x00011000 0x4a5bc4df 7/13/2009 3:35:59 PM
aswSP.SYS fffff880`07237000 fffff880`07294000 0x0005d000 0x50334f72 8/21/2012 1:05:54 AM
AsIO.sys fffff880`07294000 fffff880`0729a000 0x00006000 0x4a768bb4 8/2/2009 11:03:16 PM C:\Windows\system32\drivers\AsIO.sys
tunnel.sys fffff880`0729a000 fffff880`072c0000 0x00026000 0x4a5bccc1 7/13/2009 4:09:37 PM
amdppm.sys fffff880`072c0000 fffff880`072d5000 0x00015000 0x4a5bc0fd 7/13/2009 3:19:25 PM
nvlddmkm.sys fffff880`07438000 fffff880`0812c000 0x00cf4000 0x506b3099 10/2/2012 10:21:13 AM
dxgkrnl.sys fffff880`072d5000 fffff880`073c9000 0x000f4000 0x4d3fa1a0 1/25/2011 8:22:56 PM
dxgmms1.sys fffff880`0812c000 fffff880`08172000 0x00046000 0x4d3fa174 1/25/2011 8:22:12 PM
HDAudBus.sys fffff880`08172000 fffff880`08196000 0x00024000 0x4a5bcbf5 7/13/2009 4:06:13 PM
Rt64win7.sys fffff880`08196000 fffff880`081c8000 0x00032000 0x49a65b0d 2/26/2009 1:04:13 AM
usbohci.sys fffff880`081c8000 fffff880`081d3000 0x0000b000 0x4d8c0a90 3/24/2011 7:22:56 PM
USBPORT.SYS fffff880`08256000 fffff880`082ac000 0x00056000 0x4d8c0a97 3/24/2011 7:23:03 PM
usbehci.sys fffff880`082ac000 fffff880`082bd000 0x00011000 0x4d8c0a91 3/24/2011 7:22:57 PM
parport.sys fffff880`082bd000 fffff880`082da000 0x0001d000 0x4a5bcaa8 7/13/2009 4:00:40 PM
ASACPI.sys fffff880`082da000 fffff880`082e2000 0x00008000 0x4a5e9f11 7/15/2009 7:31:29 PM
serenum.sys fffff880`082e2000 fffff880`082ee000 0x0000c000 0x4a5bcaa1 7/13/2009 4:00:33 PM
wmiacpi.sys fffff880`082ee000 fffff880`082f7000 0x00009000 0x4a5bc3b6 7/13/2009 3:31:02 PM
CompositeBus.sys fffff880`082f7000 fffff880`08307000 0x00010000 0x4a5bcaa1 7/13/2009 4:00:33 PM
AgileVpn.sys fffff880`08307000 fffff880`0831d000 0x00016000 0x4a5bccf0 7/13/2009 4:10:24 PM
rasl2tp.sys fffff880`0831d000 fffff880`08341000 0x00024000 0x4a5bcce3 7/13/2009 4:10:11 PM
ndistapi.sys fffff880`08341000 fffff880`0834d000 0x0000c000 0x4a5bccd8 7/13/2009 4:10:00 PM
ndiswan.sys fffff880`0834d000 fffff880`0837c000 0x0002f000 0x4a5bcce3 7/13/2009 4:10:11 PM
raspppoe.sys fffff880`0837c000 fffff880`08397000 0x0001b000 0x4a5bcce9 7/13/2009 4:10:17 PM
raspptp.sys fffff880`08397000 fffff880`083b8000 0x00021000 0x4a5bccea 7/13/2009 4:10:18 PM
rassstp.sys fffff880`083b8000 fffff880`083d2000 0x0001a000 0x4a5bccf1 7/13/2009 4:10:25 PM
SaiBus.sys fffff880`083d2000 fffff880`083dc980 0x0000a980 0x4c516361 7/29/2010 3:17:53 AM
rdpbus.sys fffff880`083dd000 fffff880`083e8000 0x0000b000 0x4a5bceaa 7/13/2009 4:17:46 PM
kbdclass.sys fffff880`083e8000 fffff880`083f7000 0x0000f000 0x4a5bc116 7/13/2009 3:19:50 PM
mouclass.sys fffff880`08200000 fffff880`0820f000 0x0000f000 0x4a5bc116 7/13/2009 3:19:50 PM
swenum.sys fffff880`0820f000 fffff880`08210480 0x00001480 0x4a5bca92 7/13/2009 4:00:18 PM
ks.sys fffff880`08211000 fffff880`08254000 0x00043000 0x4b8f37d9 3/3/2010 8:32:25 PM
umbus.sys fffff880`081d3000 fffff880`081e5000 0x00012000 0x4a5bcc20 7/13/2009 4:06:56 PM
usbhub.sys fffff880`0886a000 fffff880`088c4000 0x0005a000 0x4d8c0aaa 3/24/2011 7:23:22 PM
NDProxy.SYS fffff880`088c4000 fffff880`088d9000 0x00015000 0x4a5bccdd 7/13/2009 4:10:05 PM
SaiMini.sys fffff880`088d9000 fffff880`088dcf00 0x00003f00 0x4c516361 7/29/2010 3:17:53 AM
HIDCLASS.SYS fffff880`088dd000 fffff880`088f6000 0x00019000 0x4a5bcbfd 7/13/2009 4:06:21 PM
HIDPARSE.SYS fffff880`088f6000 fffff880`088fe080 0x00008080 0x4a5bcbf9 7/13/2009 4:06:17 PM
nvhda64v.sys fffff880`088ff000 fffff880`08931000 0x00032000 0x4ff30ed0 7/3/2012 7:25:04 AM
portcls.sys fffff880`08931000 fffff880`0896e000 0x0003d000 0x4a5bcc03 7/13/2009 4:06:27 PM
drmk.sys fffff880`0896e000 fffff880`08990000 0x00022000 0x4a5bd8e5 7/13/2009 5:01:25 PM
ksthunk.sys fffff880`08990000 fffff880`08995200 0x00005200 0x4a5bca93 7/13/2009 4:00:19 PM
HdAudio.sys fffff880`08996000 fffff880`089f2000 0x0005c000 0x4a5bcc23 7/13/2009 4:06:59 PM
kbdhid.sys fffff880`089f2000 fffff880`08a00000 0x0000e000 0x4a5bca94 7/13/2009 4:00:20 PM
mouhid.sys fffff880`08800000 fffff880`0880d000 0x0000d000 0x4a5bca94 7/13/2009 4:00:20 PM
crashdmp.sys fffff880`0880d000 fffff880`0881b000 0x0000e000 0x4a5bcabd 7/13/2009 4:01:01 PM
dump_dumpata.sys fffff880`0881b000 fffff880`08827000 0x0000c000 0x4a5bc113 7/13/2009 3:19:47 PM
dump_atapi.sys fffff880`08827000 fffff880`08830000 0x00009000 0x4a5bc113 7/13/2009 3:19:47 PM
dump_dumpfve.sys fffff880`08830000 fffff880`08843000 0x00013000 0x4a5bc18f 7/13/2009 3:21:51 PM
usbccgp.sys fffff880`08843000 fffff880`08860000 0x0001d000 0x4d8c0a97 3/24/2011 7:23:03 PM
USBD.SYS fffff880`08860000 fffff880`08861f00 0x00001f00 0x4d8c0a8b 3/24/2011 7:22:51 PM
hidusb.sys fffff880`081e5000 fffff880`081f3000 0x0000e000 0x4a5bcbfe 7/13/2009 4:06:22 PM
win32k.sys fffff960`00090000 fffff960`003a4000 0x00314000 0x00000000
Dxapi.sys fffff880`081f3000 fffff880`081ff000 0x0000c000 0x4a5bc574 7/13/2009 3:38:28 PM
monitor.sys fffff880`07400000 fffff880`0740e000 0x0000e000 0x4a5bc58c 7/13/2009 3:38:52 PM
TSDDD.dll fffff960`00490000 fffff960`0049a000 0x0000a000 0x00000000
cdd.dll fffff960`00610000 fffff960`00637000 0x00027000 0x00000000
luafv.sys fffff880`0740e000 fffff880`07431000 0x00023000 0x4a5bc295 7/13/2009 3:26:13 PM
aswMonFlt.sys fffff880`073c9000 fffff880`073eb000 0x00022000 0x50334f3c 8/21/2012 1:05:00 AM
aswFsBlk.SYS fffff880`083f7000 fffff880`08400000 0x00009000 0x50334f37 8/21/2012 1:04:55 AM
WudfPf.sys fffff880`07200000 fffff880`07221000 0x00021000 0x4a5bcbd1 7/13/2009 4:05:37 PM
lltdio.sys fffff880`07221000 fffff880`07236000 0x00015000 0x4a5bcc92 7/13/2009 4:08:50 PM
nwifi.sys fffff880`0d0e7000 fffff880`0d13a000 0x00053000 0x4a5bcc3b 7/13/2009 4:07:23 PM
ndisuio.sys fffff880`0d13a000 fffff880`0d14d000 0x00013000 0x4a5bccb5 7/13/2009 4:09:25 PM
rspndr.sys fffff880`0d14d000 fffff880`0d165000 0x00018000 0x4a5bcc92 7/13/2009 4:08:50 PM
HTTP.sys fffff880`0d000000 fffff880`0d0c8000 0x000c8000 0x4a5bc1a8 7/13/2009 3:22:16 PM
bowser.sys fffff880`0d0c8000 fffff880`0d0e6000 0x0001e000 0x4d6497da 2/22/2011 9:15:06 PM
mpsdrv.sys fffff880`0d165000 fffff880`0d17d000 0x00018000 0x4a5bcc79 7/13/2009 4:08:25 PM
mrxsmb.sys fffff880`0d17d000 fffff880`0d1aa000 0x0002d000 0x4dc0bf1a 5/3/2011 6:51:06 PM
mrxsmb10.sys fffff880`0d1aa000 fffff880`0d1f8000 0x0004e000 0x4e17c0a7 7/8/2011 6:44:55 PM
mrxsmb20.sys fffff880`02a49000 fffff880`02a6c000 0x00023000 0x4dc0bf19 5/3/2011 6:51:05 PM
cpuz135_x64.sys fffff880`073eb000 fffff880`073f4000 0x00009000 0x4cd94db0 11/9/2010 5:33:36 AM
peauth.sys fffff880`0d693000 fffff880`0d739000 0x000a6000 0x4a5bd8df 7/13/2009 5:01:19 PM
secdrv.SYS fffff880`0d739000 fffff880`0d744000 0x0000b000 0x4508052e 9/13/2006 5:18:38 AM
srvnet.sys fffff880`0d744000 fffff880`0d771000 0x0002d000 0x4dba2ca3 4/28/2011 7:12:35 PM
tcpipreg.sys fffff880`0d771000 fffff880`0d783000 0x00012000 0x4a5bcccd 7/13/2009 4:09:49 PM
srv2.sys fffff880`0d783000 fffff880`0d7ea000 0x00067000 0x4dba2cb3 4/28/2011 7:12:51 PM
srv.sys fffff880`0da51000 fffff880`0dae6000 0x00095000 0x4dba2cc1 4/28/2011 7:13:05 PM

 

[nukemaster]

Have you by any chance tested your memory lately? memtest86+ is a burnable CD/DVD to do just that for you.
http://www.memtest.org/#downiso

Do you know how to see if you are getting errors in the Event Viewer?

Can you post a screen of the actual BugCheck codes please.
would look something like this.

 

[ArcticWonder]

Have you by any chance tested your memory lately? memtest86+ is a burnable CD/DVD to do just that for you.
http://www.memtest.org/#downiso

Do you know how to see if you are getting errors in the Event Viewer?

Can you post a screen of the actual BugCheck codes please.
would look something like this.
http://imageshack.us/a/img152/5107/bsodsean117.png

I think I may have fixed it. I pulled my RAM out and put it back in and so far so good. I think one of my DIMMS was loose. I'll keep you posted.

 

[nukemaster]

Fingers crossed. I have seen memory cause all kinds of random blue screens(and like you have actually seen memory slightly loose[Damn P5W DH!!!]).

 

[ArcticWonder]

The RAM was the problem guys. Thank you for all your help.

 

[ArcticWonder]

Best answer selected by ArcticWonder.