Freezing followed by BSOD when writing to a file

I recently purchased an SSD for my computer, an ADATA 120GB S511. The SSD had been previously used and apparently was in working condition. I installed Windows 7 Professional x64 on my SSD to use it as a boot drive, rather than my standard HDD which I formatted as NTFS. Since then, I have been experiencing troubles while writing to files.

I try and save a file on my HDD (not the SSD) and a lot of the time it works. In some occasions, however, the following events take place:

• I attempt to save a file
• The cursor is replaced with the pending symbol (spinning circle)
• Any programs open cease to function
• I cannot open directories or files, and icons go blank
• The entire computer freezes up
• A blue screen flashes for a split second and disappears (I do not get the chance to read any information).
• The computer restarts to show a flashing underscore.
• I restart the computer which returns back to normal.

I have looked through the event log and do not see any critical record aside from Kernel-Power which I believe regards the sudden crash but has no information about it.
I researched for anybody having the same problem online, but the ambiguity of this meant that I found few search results. One of the results said to run the chkdsk command in an elevated command prompt to make it run at boot-time. I did so and the problem still occurred. I also ran the "sfc /scannow" command in an elevated command prompt, but the problem still occurred.

I am now stuck for ideas on how to fix this, and am starting to think that it may be a hardware-related problem rather than a software-related one. Any input to how to fix this would be greatly appreciated!

[EDIT] Additional information: the file that I was trying to save became filled with nothing (shows as NUL in Programmer's Notepad 2). [EDIT2] A hex editor shows the file filled with 0s.

[EDIT3] More info: when the BSOD causes a restart, the computer stays at the motherboard loading screen with "press 4 to activate Asus core unlocker" (which isn't usually there)

Post it following the Blue Screen of Death (BSOD) Posting Instructions.

Have you updated the firmware on your SSD? Here are the firmware and guides. Also, when you installed, did you do a clean install? If you are overclocking anything, set everything back to default levels and be sure you set the SSD as 2ND boot option abd DVD as 1st boot option.
Also, please download and install AS SSD, if you don't already have it. Open it , select the SSD from the dropdown list at the top and post a screenshot, you don't have to run the benchmark unless you want to. Also, as always, be careful to not download the junk they always want to download with it. It is an SSD benchmark program, but it shows some good info on the screen. ( Screenshots and Files - Upload and Post in Seven Forums) Also, pleas post a screenshot of Disk Management. Disk Management - Post a Screen Capture Image

OK, you seem to have a system reserved (K) installed on your Drive D and E disk rather than on your SSD. You are also installed in IDE mode.
You need to change to ahci mode. but follow these instructions exactly. AHCI : Enable in Windows 7 / Vista

To check, disconnect your D/E drive and try to boot your SSD. If it boots, what is on the K drive?
If it will not boot, follow these instructions. Be sure to read the warning and info boxes also.
System Reserved Partition - Delete

If you have another OS installed, please let us know before you do anything. And sorry about the wrong link on the SSD. I assume you found the correct one, and did you update it ?

Nice increase in scores. Maybe that will help your freezing problem ( let's hope anyway). Let us know if you continue to have the freezes.

Thank you lots for all the help, Steve

daviga 404, Your BSOD is APC_INDEX_MISMATCH, BugCheck 1. In most of the cases I have seen it, it is caused by any antivirus/firewall software. Let us see what it shows in your crash dump.

A deeper search reveals that it is caused by COMODO Firewall Pro Sandbox Driver.

Code:

fffff880`09a5e468  fffff880`01221e24Unable to load image \SystemRoot\System32\DRIVERS\cmdguard.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for cmdguard.sys
*** ERROR: Module load completed but symbols could not be loaded for cmdguard.sys
 cmdguard+0x6e24

Description here: Driver Reference Table - cmdguard.sys

If you want to get rid of the BSODs, I'd suggest you to uninstall Comodo. Use Microsoft Security Essentials as your antivirus with windows inbuilt firewall, and free MBAM as the on demand scanner.
Download, install and update those, and then run full system scans with both of them, one by one.

Also make it sure that your ADATA S511 SSD is having the latest firmware.

Free up the startup. Windows does not need any other program to auto start with it, but the auto start programs often conflicts and causes various problems including BSODs.

1. Click on the Start button
2. Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
3. Select the “Startup” tab.
4. Deselect all items other than the antivirus.
5. Apply > OK
6. Accept then restart.

Let us know the results.
________________________________________________________________________________
BSOD ANALYSIS:

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1, {76d5040a, 0, ffff, fffff88009a5eca0}

Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceExit+245 )

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

APC_INDEX_MISMATCH (1)
This is a kernel internal error. The most common reason to see this
bugcheck is when a filesystem or a driver has a mismatched number of
calls to disable and re-enable APCs. The key data item is the
Thread->CombinedApcDisable field. This consists of two separate 16-bit
fields, the SpecialApcDisable and the KernelApcDisable. A negative value
of either indicates that a driver has disabled special or normal APCs
(respectively) without re-enabling them; a positive value indicates that
a driver has enabled special or normal APCs (respectively) too many times.
Arguments:
Arg1: 0000000076d5040a, Address of system call function or worker routine
Arg2: 0000000000000000, Thread->ApcStateIndex
Arg3: 000000000000ffff, (Thread->SpecialApcDisable << 16) | Thread->KernelApcDisable
Arg4: fffff88009a5eca0, Call type (0 - system call, 1 - worker routine)

Debugging Details:
------------------


FAULTING_IP: 
+0
00000000`76d5040a ??              ???

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x1

PROCESS_NAME:  svchost.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002ad4469 to fffff80002ad4f00

STACK_TEXT:  
fffff880`09a5ea68 fffff800`02ad4469 : 00000000`00000001 00000000`76d5040a 00000000`00000000 00000000`0000ffff : nt!KeBugCheckEx
fffff880`09a5ea70 fffff800`02ad43a0 : ffffffff`ffffffff 00000000`00000001 00000000`009d9b20 fffff800`0000007a : nt!KiBugCheckDispatch+0x69
fffff880`09a5ebb0 00000000`76d5040a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x245
00000000`016fd1c8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76d5040a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiSystemServiceExit+245
fffff800`02ad43a0 4883ec50        sub     rsp,50h

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  nt!KiSystemServiceExit+245

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc600

FAILURE_BUCKET_ID:  X64_0x1_SysCallNum_52_nt!KiSystemServiceExit+245

BUCKET_ID:  X64_0x1_SysCallNum_52_nt!KiSystemServiceExit+245

Followup: MachineOwner
---------

Should the system reserved partition be assigned a drive letter ??
Normally i would say no but have no knowledge/experience of paragon part manager so dont know if this is something that it has changed especially with it being over 200MB, dual boot ?