Solved BSOD often since moving from IDE to ACHI

[mart4494]

Had numerous BSOD's since updating from IDE to ACHI using the upgrade tool from the MSoft website. Enabled verifier.exe earlier and rebooted - immediately a BSOD with a message about a rogue driver - please update your driver but did not state which one. Managed to reboot to disable the verifer function.

My specs

Windows 7 64 bit - retail
Reinstalled once when fitting a SSD recently.
Asus P5Q Pro - 4gb ram
ATI HD3870
1 x Kingston SSD 128gb HD
1 x Samsung 500gb HD
1 x Samsung 1tb HD

Attached Windows_NT6_BSOD zip file with HTML enclosed.

As usual with these things it seems to be random so any help appreciated.

 

[FredeGail]

Hello & Welcome to Sevenforums!

May I ask why you want to go to ACHI? I'm running 64-bit Windows, and having my SSD on IDE with no problems.
Secondly, read your manual for your SSD, and look how to set it up etc. Maybe it's not ACHI supporting. I don't know if there's SSDs like this, but who knows.

About your dumb file, I'm not on the BSOD Squad and I can hardly regonize what's wrong.

Best Regards,
FredeGail

 

[mgorman87]

Crash was caused by your Storage Craft software. Please uninstall and then re-enable driver verifier.

BSOD BUGCHECK SUMMARY

[font=lucida console]
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Sat Jun 18 08:34:03.977 2011 (UTC - 4:00)
System Uptime: 0 days 3:19:41.413
*** WARNING: Unable to verify timestamp for stcvsm.sys
*** ERROR: Module load completed but symbols could not be loaded for stcvsm.sys
Probably caused by : stcvsm.sys ( stcvsm+120e9 )
DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
BUGCHECK_STR:  0xc4_3c
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xc4_3c_VRF_stcvsm+120e9
BiosReleaseDate = 02/23/2009
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
CPUID:        "Intel(R) Core(TM)2 Duo CPU     E8400  @ 3.00GHz"
MaxSpeed:     3000
CurrentSpeed: 3005
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
[/font]

 

[mart4494]

Hi FredeGail - I'm beginning to wonder that myself. Read somewhere that there was an overall speed improvement using ACHI over IDE. Not the case if all you're getting is the BSOD.

Thanks for the input

 

[mart4494]

Crash was caused by your Storage Craft software. Please uninstall and then re-enable driver verifier.

BSOD BUGCHECK SUMMARY

[FONT=lucida console]
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Sat Jun 18 08:34:03.977 2011 (UTC - 4:00)
System Uptime: 0 days 3:19:41.413
*** WARNING: Unable to verify timestamp for stcvsm.sys
*** ERROR: Module load completed but symbols could not be loaded for stcvsm.sys
Probably caused by : stcvsm.sys ( stcvsm+120e9 )
DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
BUGCHECK_STR:  0xc4_3c
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xc4_3c_VRF_stcvsm+120e9
BiosReleaseDate = 02/23/2009
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
CPUID:        "Intel(R) Core(TM)2 Duo CPU     E8400  @ 3.00GHz"
MaxSpeed:     3000
CurrentSpeed: 3005
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
[/FONT]

Thanks for the feedback. Ran verifier.exe on each non-Microsoft driver as detailed elsewhere. Did it on an individual by individual file basis and each time the PC booted just fine. Checked stcvsm.sys and that did not cause a BSOD on boot up. Will delete Storage Craft software and reinstall as suggested.

Have also run sfc /scannow a couple of times but it was unable to complete. Ran sfc /verifyonly which completed and came back with integrity errors which has been written to the cbs.log. Copy attached.

Guess it's going to be a file by file restore from the DVD.

Regards

 

[mgorman87]

Do not re-install software, re-enable driver verifier.

 

[mart4494]

An update - Final I hope

Did everything as suggested and the PC settled down. Opened the case and found one of the CPU cooler clips had come loose so the thing was just holding on with 3 clips - maybe it was an overheating CPU causing the problem(s) after all. Decided to change it with a Zalman which screws down. Since then zero BSOD's.

Maybe that was the cause of the BSOD's - we will see. Anyway, just wanted to thank you guys for being here.

Regards