RANDOM FREEZE after installing ssd, bios update, clean win7 install

[orochi07]

Hi,

I had this computer since 2011. Recently, i got my new INTEL SSD harddrive. Did a clean windows 7 installation and ran all the windows updates and updated the drivers. I also updated the bios to the latest version 3602. Since then, windows has been giving me random freeze from time to time. It just happened again as I was typing this.

I thought maybe the latest bios might be the cause of the random freeze. So i downgraded the bios back to what i had been using for the past 3 years which was 1502. But the random freeze still occurs. There is no BSOD. Just hard freeze. Keyboard has got no lights. Caplocks and num locks doesn't response. My razer mouse blue led is still on though. Audio will go into indefinite loop.

Windows event viewer gave the Kernel-Power event ID 41. I don't think a dump file is created when it freeze. I tried leaving my computer on throughout the night without touching it and it froze and restarted twice last night. I can't find the root cause to the problem. No overclock. I had also tried cleaning the contact points for the ram and graphic card. Is it because the new SSD is not compatible with motherboard or is the PSU not sufficient to support 5 hdds in total or is there any other underlying reason which can be found in the attached files.

Please help. Thanks in advance

 

[Arc]

There is one crash dump in the zip that is manually initialized by WhoCrashed.

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

Use !analyze -v to get detailed debugging information.

BugCheck DEADDEAD, {0, 0, 18d4f449, 3c2a58ed}

Probably caused by : rspCrash64.sys ( rspCrash64+108b )

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

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

MANUALLY_INITIATED_CRASH1 (deaddead)
The user manually initiated this crash dump.
Arguments:
Arg1: 0000000000000000
Arg2: 0000000000000000
Arg3: 0000000018d4f449
Arg4: 000000003c2a58ed

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


CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0xDEADDEAD

PROCESS_NAME:  WhoCrashedEx.e

CURRENT_IRQL:  0

ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre

LAST_CONTROL_TRANSFER:  from fffff88008d8508b to fffff80002ebfbc0

STACK_TEXT:  
fffff880`086ab6f8 fffff880`08d8508b : 00000000`deaddead 00000000`00000000 00000000`00000000 00000000`18d4f449 : nt!KeBugCheckEx
fffff880`086ab700 00000000`deaddead : 00000000`00000000 00000000`00000000 00000000`18d4f449 00000000`3c2a58ed : rspCrash64+0x108b
fffff880`086ab708 00000000`00000000 : 00000000`00000000 00000000`18d4f449 00000000`3c2a58ed fffff800`02ff330d : 0xdeaddead


STACK_COMMAND:  kb

FOLLOWUP_IP: 
rspCrash64+108b
fffff880`08d8508b ??              ???

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  rspCrash64+108b

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: rspCrash64

IMAGE_NAME:  rspCrash64.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  50976856

FAILURE_BUCKET_ID:  X64_0xDEADDEAD_rspCrash64+108b

BUCKET_ID:  X64_0xDEADDEAD_rspCrash64+108b

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0xdeaddead_rspcrash64+108b

FAILURE_ID_HASH:  {2930a2c1-4049-a66a-c4d8-6d0266b14f39}

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

0: kd> lmvm rspCrash64
start             end                 module name
fffff880`08d84000 fffff880`08d8c000   rspCrash64 T (no symbols)           
    Loaded symbol image file: rspCrash64.sys
    Image path: \SystemRoot\system32\DRIVERS\rspCrash64.sys
    Image name: rspCrash64.sys
    Timestamp:        Mon Nov 05 12:48:46 2012 (50976856)
    CheckSum:         000044D9
    ImageSize:        00008000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

If you think that the issue is causing after installing the SSD, make it sure that it is running with the latest firmware. https://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&DwnldID=18363

Uninstall Marvell Sata driver. Update JMicron drivers form ftp://driver.jmicron.com.tw/SATA_Controller/Windows/

Uninstall avipbb.sys, Avira Security Enhancer. 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.

Observe if there is any change in the situation or not.

 

[orochi07]

Thanks for the reply. Yes, the crash dump was manually initialised by whoCrashed. I was trying to see if it was some settings had prevented the crash dump from being created. However, my crash dump settings were set to create and despite the multiple random freeze that happened, it totally "killed" the machine and no crash dump were created at all.

My ssd was running at the latest firmware. I'll try to uninstall the Marvell sata drivers and update the JMicron Drivers and uninstall Avira (although i have been using avira for quite some time but maybe the latest version have compatibility issue...who knows...)

I'll observe to see if it fixes the problem.

 

[orochi07]

I've tried the things Arc suggested but the random freeze is still occuring. I've since update the bios to the latest version 3602 and also updated the firmware of the ssd. Attached is the latest grab from the diagnostic tools. Please help. Thanks.