FIX IS HERE: Sandra Memory bench crashing and or crashing your system?

[pershoot]

If Sandra is crashing your system and or crashing and known tested stable settings, here is your fix:

After installation of latest Sandra (2005 SR1):

start->run->services.msc (hit enter)
double click Sandra Data Service->Log On->Tick 'This account' (under Local system account)->enter in username and password of windows user (who you log in as to use windows)->apply->ok

double click Sandra Service->Log On->Tick 'This account' (under Local system account)->enter in username and password of windows user (who you log in as to use windows)->apply->ok

close Services MMC.

start->run->gpedit.msc (hit enter)->Local Computer Policy->Computer Configuration->Windows Settings->Security Settings->Local Policies->User Rights Assignment->double click 'Lock pages in memory'->Add User or Group->enter in windows user (who you log in as to use windows)->ok->apply->ok->close GPEDIT MMC

now reboot.

To test, run the Sandra memory bench 5-7 times consecutively, manually. You shouldn't crash now. You will also see increased numbers due to your UID locking pages in memory

Hope this helps everyone (as it pulled my hair out, hehe).

Note: This may just be a Win2k3 bug. As i had someone try this on XP (which didnt crash with sandra prior) and sandra crashed. Your mileage may vary...

[bachus_anonym]

After installation of latest Sandra (2005 SR1):
(...)
To test, run the Sandra memory bench 5-7 times consecutively, manually. You shouldn't crash now. You will also see increased numbers due to your UID locking pages in memory
(...)
Note: This may just be a Win2k3 bug. As i had someone try this on XP (which didnt crash with sandra prior) and sandra crashed. Your mileage may vary...

Are you sure that Sandra 2005 SR1 uses Locked Mem Pages? It is checked in the Options but after you run the Mem Benchmark it says it didn't ?

How did you Lock Mem Pages on WinXP? There's no Group Policy Editor on WinXP...? Unless it was maybe XP Professional

[pershoot]

to lock memory pages on sandra 2005 on your operating system, you must not only apply a local policy of granting your UID/GID to memory locked pages, but also to the services that sandra depends on. after locking i gained 100-150mb/s. b4 assigning my GID/UID to said services with just the local 'mem. lock' policy in place, it was not locking (i was -100-150mb/s less then where i am now). i was also crashing with sandra (im on win2k3), but i believe that is just a win2k3 x86-32 bug running on A64, as i have not seen it on xp.

edit: yup sandra would report unlocked pages even with local policy in place. once UID assigned to said services, the warning dissappeared from sandra.

xp home gpedit alternative?: http://www.experts-exchange.com/Operating_Systems/WinXP/Q_21161647.html

xp pro gpedit: http://www.winsupersite.com/showcase/windowsxp_tips_rc1.asp

win2k3 will be similar to xp pro link.

[pershoot]

if you crash while applying UID to both services, only apply to one or the other (you would test this). please reply back and i will add that to the above for xp users. we can merge a win2k3 fix and sandra xp lock in one thread, hehe.

[bachus_anonym]

No, no... I never had Sandra crashed on me on Server2003. I just wondered about Sandra2005 not using LockedMemPages as opposed to Sandra2004.

The ONLY issue I have with Sandra (2004 in particular) on Server2003 is that when pages are locked. When I run Sandra right after OS is loaded then everything is OK. But then, say, I run some apps that fill up memory or SuperPI 32M... When after that I run Mem Bench, it finishes but instead of results I get "Not enough resources" in place where results should be :)

But that's with 2004... There are neither "Sandra Data Service" nor "Sandra Service" when 2004 is instaleld as far as I can see...

EDIT: Sorry for possible OFF-TOPIC :(

[pershoot]

ahh k. yea sandra 2k5 uses a server/client model, thats why those 2 services are there.

im just glad i pinned it for the most part.. heck i thought my memory controller went caput or something, hehe.