The Corsair User Forums  

Go Back   The Corsair User Forums > Corsair Product Discussion > Solid State Drives (SSD)

Reply
 
Thread Tools Search this Thread Rating: Thread Rating: 44 votes, 5.00 average. Display Modes
  #31  
Old 07-22-2011, 10:27 AM
MariaH79's Avatar
MariaH79 MariaH79 is offline
Maria
MariaH79's PC Specs
 
Join Date: Jul 2011
Location: Norway
Posts: 17
POST ID # = 514680
MariaH79 Reputation: 10
Thumbs up Cheers to Toasted

Been struggling with BSOD´s after i added couple ForceGT in Raid 0.
Setting Ram voltage seems to have solved it, had it on auto before.
Just checked for a couple days now thou, will tell if it does same again.

Was considering doin this until i saw this post, maybe it can help some others.
This should turn off hibernation:
Open command line "run as admin" - type "powercfg -h off" and hit enter and just exit window.
Turning it back on:
Open command line "run as admin" - type "powercfg -h on" and hit enter and just exit window.
Prbly some other way doin the same...
Reply With Quote


  #32  
Old 07-22-2011, 07:19 PM
Toasted Toasted is offline
Registered User
 
Join Date: Apr 2011
Posts: 19,344
POST ID # = 514796
Toasted Toasted Reputation: 108
Default

Quote:
Originally Posted by MariaH79 View Post
Been struggling with BSOD´s after i added couple ForceGT in Raid 0.
Setting Ram voltage seems to have solved it, had it on auto before.
Just checked for a couple days now thou, will tell if it does same again.

Was considering doin this until i saw this post, maybe it can help some others.
This should turn off hibernation:
Open command line "run as admin" - type "powercfg -h off" and hit enter and just exit window.
Turning it back on:
Open command line "run as admin" - type "powercfg -h on" and hit enter and just exit window.
Prbly some other way doin the same...
Glad it worked for you.

Also you have a very nice system 980x
Reply With Quote


  #33  
Old 07-25-2011, 09:22 AM
charithjperera charithjperera is offline
Registered User
 
Join Date: Jul 2011
Posts: 4
POST ID # = 515102
charithjperera Reputation: 10
Default

Here are 3 minidumps after crashing on resume from S3 sleep.
It's all from an F90 drive, v2 firmware.
Attached Files
File Type: txt 072511-14062-01.txt (207.6 KB, 326 views)
File Type: txt 072511-14078-01.txt (207.0 KB, 238 views)
File Type: txt 072511-14140-01.txt (206.9 KB, 252 views)
Reply With Quote


  #34  
Old 07-25-2011, 03:28 PM
Darkwicca Darkwicca is offline
Registered User
Darkwicca's PC Specs
 
Join Date: Jul 2011
Posts: 3
POST ID # = 515190
Darkwicca Reputation: 10
Default

Tested your registry fix toasted. Didn't work. Same BSOD.
Reply With Quote


  #35  
Old 07-25-2011, 03:54 PM
Darkwicca Darkwicca is offline
Registered User
Darkwicca's PC Specs
 
Join Date: Jul 2011
Posts: 3
POST ID # = 515198
Darkwicca Reputation: 10
Default

Changing the ram voltage from auto to manual seems to have stopped the BSOD, but I still get one processor out of four that uses max resources after sleep mode.

In the resource monitor the CPU usage comes from System Interrupts.

When using LatencyMon after sleep mode I see that the DPC count is about 100x larger on mvs91xx.sys than on any other driver. Also the ISR count is over 100x larger in storport.sys than on any other driver. Mvs91xx.sys is for the Marvel 91xx SATA 6G Controller. These results are comparable to other drivers before sleep mode. Any clues how to fix this? As it is now, sleepmode is useless when it resumes using over 20% of total CPU.
Reply With Quote


  #36  
Old 07-26-2011, 12:34 AM
whenamanlies whenamanlies is offline
Registered User
 
Join Date: Jul 2011
Posts: 2
POST ID # = 515268
whenamanlies Reputation: 10
Default

I had several freezes that were followed by BSOD while playing video games but wasn't really connecting that to SSD since it's a brand new system
Just now verified that I can't indeed wake up from sleep and it took multiple hard restarts to get Windows to load again.

Win7 x64 on P8Z68-V Pro (Z68 chipset). Drive connected to Intel's controller (other 2 are disabled in BIOS). Memory voltage is set to 1.5.
Reply With Quote


  #37  
Old 07-26-2011, 02:46 AM
Toasted Toasted is offline
Registered User
 
Join Date: Apr 2011
Posts: 19,344
POST ID # = 515283
Toasted Toasted Reputation: 108
Default

Quote:
Originally Posted by Darkwicca View Post
Tested your registry fix toasted. Didn't work. Same BSOD.
What registry fix?

Quote:
Originally Posted by charithjperera View Post
Here are 3 minidumps after crashing on resume from S3 sleep.
It's all from an F90 drive, v2 firmware.
I can't read your memory dumps. there in .txt i need them in .dump
i also need your system specs.

Quote:
Originally Posted by Darkwicca View Post
Changing the ram voltage from auto to manual seems to have stopped the BSOD, but I still get one processor out of four that uses max resources after sleep mode.

In the resource monitor the CPU usage comes from System Interrupts.

When using LatencyMon after sleep mode I see that the DPC count is about 100x larger on mvs91xx.sys than on any other driver. Also the ISR count is over 100x larger in storport.sys than on any other driver. Mvs91xx.sys is for the Marvel 91xx SATA 6G Controller. These results are comparable to other drivers before sleep mode. Any clues how to fix this? As it is now, sleepmode is useless when it resumes using over 20% of total CPU.
Try updating your Marvell Drivers. Or plug the drive to the Intel Chipset.

Quote:
Originally Posted by whenamanlies View Post
I had several freezes that were followed by BSOD while playing video games but wasn't really connecting that to SSD since it's a brand new system
Just now verified that I can't indeed wake up from sleep and it took multiple hard restarts to get Windows to load again.

Win7 x64 on P8Z68-V Pro (Z68 chipset). Drive connected to Intel's controller (other 2 are disabled in BIOS). Memory voltage is set to 1.5.
What drive are you using? Force 3?
try to set your PCH voltage to 1.10v
if that doesn't work then manually set the DRAM Timings in the BIOS (Refer to your motherboard manual.
Reply With Quote


  #38  
Old 07-26-2011, 03:42 AM
ozjom672 ozjom672 is offline
Registered User
ozjom672's PC Specs
 
Join Date: Jul 2011
Posts: 5
POST ID # = 515289
ozjom672 Reputation: 10
Default

It is the same but do not have the Asus P8P67.

Corsair Focre 3
Thailand

Last edited by ozjom672; 07-26-2011 at 04:00 AM.
Reply With Quote


  #39  
Old 07-26-2011, 05:24 AM
Toasted Toasted is offline
Registered User
 
Join Date: Apr 2011
Posts: 19,344
POST ID # = 515293
Toasted Toasted Reputation: 108
Default

Quote:
Originally Posted by ozjom672 View Post
It is the same but do not have the Asus P8P67.

Corsair Focre 3
Thailand
Plug it in the Grey port of your motherboard. not navy blue.
Reply With Quote


  #40  
Old 07-26-2011, 05:54 AM
charithjperera charithjperera is offline
Registered User
 
Join Date: Jul 2011
Posts: 4
POST ID # = 515296
charithjperera Reputation: 10
Default

Quote:
Originally Posted by Toasted View Post
I can't read your memory dumps. there in .txt i need them in .dump
i also need your system specs.
Aah sorry for renaming the dumps, the forum doesnt allow .dmp files; just rename them and they'll be right.

My system specs are:
HP Compaq TC4400
945GM, Intel T2400 (1.83GHz), Win 7 Pro x86
Reply With Quote


  #41  
Old 07-26-2011, 05:59 AM
Darkwicca Darkwicca is offline
Registered User
Darkwicca's PC Specs
 
Join Date: Jul 2011
Posts: 3
POST ID # = 515297
Darkwicca Reputation: 10
Default

Quote:
Originally Posted by Toasted View Post
What registry fix?

Try updating your Marvell Drivers. Or plug the drive to the Intel Chipset.
The TreatAsInternalPort registry fix.

I changed the port that the corsair disc was connected to, that cleared up the problem. No blue screen, no excess cpu usage. Turns out that it was connected to the intel chipset after all, but it looked like it was using the marvell driver? When I changed it to the marvell port, it worked fine.
Reply With Quote


  #42  
Old 07-26-2011, 08:15 AM
Toasted Toasted is offline
Registered User
 
Join Date: Apr 2011
Posts: 19,344
POST ID # = 515305
Toasted Toasted Reputation: 108
Default

Quote:
Originally Posted by Darkwicca View Post
The TreatAsInternalPort registry fix.

I changed the port that the corsair disc was connected to, that cleared up the problem. No blue screen, no excess cpu usage. Turns out that it was connected to the intel chipset after all, but it looked like it was using the marvell driver? When I changed it to the marvell port, it worked fine.
If it is working fine on the Marvell controller then leave it as is.
Reply With Quote


  #43  
Old 07-26-2011, 08:18 AM
Toasted Toasted is offline
Registered User
 
Join Date: Apr 2011
Posts: 19,344
POST ID # = 515306
Toasted Toasted Reputation: 108
Default

Quote:
Originally Posted by charithjperera View Post
Aah sorry for renaming the dumps, the forum doesnt allow .dmp files; just rename them and they'll be right.

My system specs are:
HP Compaq TC4400
945GM, Intel T2400 (1.83GHz), Win 7 Pro x86
Still Cannot be read please make a .zip archive.
Reply With Quote


  #44  
Old 07-26-2011, 08:37 PM
ozjom672 ozjom672 is offline
Registered User
ozjom672's PC Specs
 
Join Date: Jul 2011
Posts: 5
POST ID # = 515467
ozjom672 Reputation: 10
Default

Quote:
Originally Posted by Toasted View Post
Plug it in the Grey port of your motherboard. not navy blue.
I plugged in gray, but not cured.
Reply With Quote


  #45  
Old 07-27-2011, 02:28 AM
Toasted Toasted is offline
Registered User
 
Join Date: Apr 2011
Posts: 19,344
POST ID # = 515514
Toasted Toasted Reputation: 108
Default

Quote:
Originally Posted by ozjom672 View Post
I plugged in gray, but not cured.
Is the System OCed?
Reply With Quote


Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT -4. The time now is 09:06 PM.


Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2019, vBulletin Solutions, Inc.