BSOD error 109 nakon instalacije SSD-a (dajem .dmp na uvid)

[Flake]

Zdravo,

nakon sto sam stavio novi SSD (Mushkin Chronos 60GB sata3) u kompjuter poceli su problemi. OS/Win7 sam nanovo instalirao i vec u tjedan dana stavio dva nova firmware-a na SSD sa nadom da se neće javljati nikakvi problemi. Evo copy-paste dmp-a, nisam u tome strucan pa ako netko zna rjesenje, bilo kakvo bio bih mu zahvalan.

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\101311-18064-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*D:\Program Files\Debug\*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02c13000 PsLoadedModuleList = 0xfffff800`02e58670
Debug session time: Thu Oct 13 19:49:27.725 2011 (UTC + 2:00)
System Uptime: 0 days 1:38:11.505
Loading Kernel Symbols
...............................................................
................................................................
..................................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 109, {a3a039d89b9505e1, b3b7465eee11d547, fffff80002c822b0, 1}

*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption

Followup: memory_corruption
---------
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

CRITICAL_STRUCTURE_CORRUPTION (109)
This bugcheck is generated when the kernel detects that critical kernel code or
data have been corrupted. There are generally three causes for a corruption:
1) A driver has inadvertently or deliberately modified critical kernel code
 or data. See http://www.microsoft.com/whdc/driver/kernel/64bitPatching.mspx
2) A developer attempted to set a normal kernel breakpoint using a kernel
 debugger that was not attached when the system was booted. Normal breakpoints,
 "bp", can only be set if the debugger is attached at boot time. Hardware
 breakpoints, "ba", can be set at any time.
3) A hardware corruption occurred, e.g. failing RAM holding kernel code or data.
Arguments:
Arg1: a3a039d89b9505e1, Reserved
Arg2: b3b7465eee11d547, Reserved
Arg3: fffff80002c822b0, Failure type dependent information
Arg4: 0000000000000001, Type of corrupted region, can be
    0 : A generic data region
    1 : Modification of a function or .pdata
    2 : A processor IDT
    3 : A processor GDT
    4 : Type 1 process list corruption
    5 : Type 2 process list corruption
    6 : Debug routine modification
    7 : Critical MSR modification

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


BUGCHECK_STR:  0x109

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

PROCESS_NAME:  System

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff80002c8fc40

STACK_TEXT:  
fffff880`031845d8 00000000`00000000 : 00000000`00000109 a3a039d8`9b9505e1 b3b7465e`ee11d547 fffff800`02c822b0 : nt!KeBugCheckEx


STACK_COMMAND:  kb

CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
    fffff80002c8242f - nt!KiInsertQueueApc+17f
    [ a7:b7 ]
1 error : !nt (fffff80002c8242f)

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  ONE_BIT

FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT

BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT

Followup: memory_corruption

Konfa je ova pod Moj Komp. + gore navedeni SSD. Te naglasavam da mi se nijednom nije rusio Win na obicnom disku prije ovog SSD-a

[nino]

Koliko sam vidio, tvoja mb nema sata2 portove. Ja sam takodjer imao na Gigabyte ploci frku sa ssd-om na sata3 portovima.

Na sata2 radi normalno, u daljnje istrazivanje nisam isao.

[Flake]

nema, samo 6x sata3 portova, mozda da kupim sata3 data kabel? malo ga je teze naci kod nas (hrv+bih)

[nino]

Sumnjam, nisam stigao proucavat ali imas i tu nesto texta o Sandforce kontrolerima.

[Flake]

hvala, budem procitao