Einstein on SSD's

Ver Greeneyes
Ver Greeneyes
Joined: 26 Mar 09
Posts: 140
Credit: 9,562,235
RAC: 0

RE: im going by memory from

Message 97391 in response to message 97390

Quote:
im going by memory from an old smart computing magazine, but my understanding is it "requires" atleast a small one on the system drive incase of a crash, something to do with the memory dump at BSOD.. i may be completely wrong here though.


Aah, that may be true - I usually turn that stuff off <.< so maybe that stops it complaining for me.

Jord
Joined: 26 Jan 05
Posts: 2,952
Credit: 5,752,225
RAC: 238

Ever since Windows 2000, I

Ever since Windows 2000, I use a separate partition on another drive for the swap (or page) file. I had a nice 4.5GB drive for that at first, but that one died a long time ago. There's no swap file in use on the system partition. I just set it to zero on the system drive.

The trick though is to set the swap page to a different partition/drive first, before turning the swap file on the system drive off, or else Windows will complain that you cannot turn the swap file off!

On one of my systems the swap file is on C:, while the Windows partition lives on D: on another drive (!!). I still don't know how I managed that. :-D

Ver Greeneyes
Ver Greeneyes
Joined: 26 Mar 09
Posts: 140
Credit: 9,562,235
RAC: 0

RE: The trick though is to

Message 97393 in response to message 97392

Quote:
The trick though is to set the swap page to a different partition/drive first, before turning the swap file on the system drive off, or else Windows will complain that you cannot turn the swap file off!


So since he already has that 6GiB swap file on his RAID0 setup, he should be able to turn the one on the system drive off without it complaining now?

Jord
Joined: 26 Jan 05
Posts: 2,952
Credit: 5,752,225
RAC: 238

If all is well, yes. Just set

Message 97394 in response to message 97393

If all is well, yes. Just set both values (minimum and maximum) on C: (or whatever the system drive is) to zero and click Set.

hotze33
hotze33
Joined: 10 Nov 04
Posts: 100
Credit: 366,882,045
RAC: 8,270

With Windows 7 there is no

With Windows 7 there is no point in moving the swap space away from the SSD (imho). Windows usually feels slow, when it uses the swap file. So why loose the SSD speed by changing to a mechanical drive?
The OS and the corresponding swap file should be on the fastest drive to really feel he difference.
Only on extreme usage you can kill a SSD. For normal work it should last quite some time.
For the intel drive there is the Intel SSD Toolbox. There you can look at the smart attributes with one being the host writes. For my drives I have 900GB in 2500h, so roughly 8.5GB a day and far off the 20 GB Intel uses in its calculations.

Mike Hewson
Mike Hewson
Moderator
Joined: 1 Dec 05
Posts: 6,196
Credit: 133,093,632
RAC: 60,023

RE: im going by memory from

Message 97397 in response to message 97390

Quote:
im going by memory from an old smart computing magazine, but my understanding is it "requires" atleast a small one on the system drive incase of a crash, something to do with the memory dump at BSOD.. i may be completely wrong here though.


The message on Windows 7 ( Home Premium ), when attempting to move the swap file off system/C-drive, warns you along the lines that full error reporting may not be available in certain circumstances. But you can click through that dialog box and shift the swap file location anyway. As I've never found M$ error messages overly helpful/understandable, that doesn't worry me. I disable all this dump business - what am I going to do with a memory dump? Decode it myself? Give it to M$, assuming they care?

Cheers, Mike.

I have made this letter longer than usual because I lack the time to make it shorter. Blaise Pascal

Ver Greeneyes
Ver Greeneyes
Joined: 26 Mar 09
Posts: 140
Credit: 9,562,235
RAC: 0

RE: I disable all this dump

Message 97398 in response to message 97397

Quote:
I disable all this dump business - what am I going to do with a memory dump? Decode it myself? Give it to M$, assuming they care?


There are people who can actually decode those things - I've seen at least one instance on a support forum where an expert was able to help out by looking through the memory dump. It's very rare that you actually have a problem that's -that- hard to fix though - so I turn it off too.

Mike Hewson
Mike Hewson
Moderator
Joined: 1 Dec 05
Posts: 6,196
Credit: 133,093,632
RAC: 60,023

RE: There are people who

Message 97399 in response to message 97398

Quote:
There are people who can actually decode those things - I've seen at least one instance on a support forum where an expert was able to help out by looking through the memory dump. It's very rare that you actually have a problem that's -that- hard to fix though - so I turn it off too.


Fair enough. I stay simple - just rollback the new driver or system restore etc. Now that's a great feature that we never had earlier on, being able to backtrack systemic change(s). I've yet to find a BSOD or similiar that hasn't responded to that.

Cheers, Mike.

I have made this letter longer than usual because I lack the time to make it shorter. Blaise Pascal

DanNeely
DanNeely
Joined: 4 Sep 05
Posts: 1,343
Credit: 2,024,078,225
RAC: 1,567,210

There's at least one

There's at least one automated crash dump analysis tool available as well. Who crashed will look to see where the crash came from. If it's an error in a 3rd party driver (eg your GP, sound, chipset) that triggered the exception you'll know what's to blame. The culprit could either be the driver itself, or less likely, that the hardware is failing. It's not foolproof, and if your CPU itself is borderline overloaded/starting to fail, you'll see WHEA_UNCORRECTABLE_ERROR or IRQL_NOT_LESS_OR_EQUAL attributed to 'hardware'. This could be more or less anything but an overheating CPU is the most likely offender.

PS if you're running Vista/Win7 it needs to be run as an administrator in order to work.

Mike Hewson
Mike Hewson
Moderator
Joined: 1 Dec 05
Posts: 6,196
Credit: 133,093,632
RAC: 60,023

RE: There's at least one

Message 97401 in response to message 97400

Quote:

There's at least one automated crash dump analysis tool available as well. Who crashed will look to see where the crash came from. If it's an error in a 3rd party driver (eg your GP, sound, chipset) that triggered the exception you'll know what's to blame. The culprit could either be the driver itself, or less likely, that the hardware is failing. It's not foolproof, and if your CPU itself is borderline overloaded/starting to fail, you'll see WHEA_UNCORRECTABLE_ERROR or IRQL_NOT_LESS_OR_EQUAL attributed to 'hardware'. This could be more or less anything but an overheating CPU is the most likely offender.

PS if you're running Vista/Win7 it needs to be run as an administrator in order to work.


Well, there you go! Learn something new each day. Thanks, I really reckon I'll give that a whiz, particularly at my place of business where we actually have to know on such occasions.

I suppose much of this would come back to having M$ labs certification/validation of the driver(s), and the STOP notification on unverified driver installs that one sees occasionally. Does M$ charge the vendors for submission of drivers to that process ?

Cheers, Mike.

I have made this letter longer than usual because I lack the time to make it shorter. Blaise Pascal

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.