dai

do you have a link to your ram

__________________

Proprius

http://www.ocztechnology.com/product...666_reaper_hpc
or
http://www.newegg.com/Product/Produc...82E16820227293

dai

the newegg does not work and there is more than on variant listed
http://www.ocztechnology.com/product...per_hpc_series

__________________

Proprius

http://www.newegg.com/Product/ Product.aspx?Item=N82E16820227293

I put a space to circumvent the shortening. ><

dai

access denied
in the bios lift the ram voltage to 1.8v it's within the manufacturers specs for the lower grade version of the ram
the better quality has a 1.9v upper end
see if that makes a difference

__________________

Proprius

Listed specifications on the site are 1.75V , with timing 6 - 6 - 6 - 18 .
BIOS was defaulted at 1.5V with timings 6 - 6 - 6 - 20.

I tried 1.8V and Vista wouldn't boot. Ditto for 1.75V. Then I changed timing in BIOS to 6-6-6-18, and tried 1.75V, still crashed Vista. I lowered voltage in increments of .5V until it worked, at 1.65V.

This is taken from a review on newegg: "
Cons: This memory will not work without manually tweaking your BIOS. I spend a couple days tinkering with settings before getting to stay stable for about 5 hours at a stretch. Finally I called OCZ about the issues I was having. They gave me this advice which solved the problems and the system has been totally stable since (3 weeks of testing before writing this review) Try 6-6-6-18 with memory voltage at 1.8V. Make sure CMD is at 2T. Also increase the nForce SPP voltage to 1.4V. If you're not overclocking the CPU, run the memory linked and synched to the FSB."

Proprius

Followed the instructions in that newegg review and system booted. Changed the following additional settings in BIOS:

CMD from 1T to 2T
Voltage back up to 1.8V
nForce SPP up to 1.4V
Linked and Synced Memory to FSB

Will inform if I still crash.

Proprius

Problem reoccured, though not during a game - I was installing a program at the time, as well as browsing the internet.

dai

anything in the event viewer this time

__________________

Proprius

Volume Shadow Copy Service error: Unexpected error querying for the IVssWriterCallback interface. hr = 0x80070005. This is often caused by incorrect security settings in either the writer or requestor process.

Operation:
Gathering Writer Data

Context:
Writer Class Id: {e8132975-6f93-4464-a53e-1050253ae220}
Writer Name: System Writer
Writer Instance ID: {9b1a28d8-fab9-4f4b-969f-a934a87fef01}

and

Failed to create restore point on volume (Process = C:\Users\John\AppData\Local\Temp\6406d0375d524ca08837a28f799c0c2e\00000000_TEMP\dxsetup.exe /silent; Descripton = ôÜu; Hr = 0x80070057).

Both within a minute prior to the crash

jcgriff2

0x80070005 is an access-denied error. Do you have any 3rd party backup software installed?

jcgriff2

.

__________________

SysInternals Suite • BSOD Bugchecks • Media Fire • Belarc Advisor • MS TechNet • MS NTDE/CPR
MSDN Err Cds • Everest Home v2.20 • CCleaner • Memtest86+ • MS Help & Support
Live SysInternals AutoRuns • Auslogics Defrag • McAfee RT • Norton RT • Kaspersky RT • MS One Care RT

Proprius

I don't think so, but I'm also not entirely sure what would be 3rd party backup software either.

jcgriff2

A third-party backup product would be non-Microsoft software that you are using to completely back up your system onto another hard drive - be it internal or external.

Also, are you maybe using the Windows Backup and Restore facility - here is a screen shot:



Please note that this is NOT the Windows System Restore system.

Regards. . .

jcgriff2

__________________

SysInternals Suite • BSOD Bugchecks • Media Fire • Belarc Advisor • MS TechNet • MS NTDE/CPR
MSDN Err Cds • Everest Home v2.20 • CCleaner • Memtest86+ • MS Help & Support
Live SysInternals AutoRuns • Auslogics Defrag • McAfee RT • Norton RT • Kaspersky RT • MS One Care RT

Proprius

Nope, nothing like that is installed as far as I know. And I've never opened the Windows Backup and Restore facility before, but I still went through and looked for any setting that may have been enabled somehow, and found nothing.
Perhaps the installation program was trying to make a small restore point or something?

jcgriff2

I don't know what that setup program is - Apologies if already suggested, but have you looked at the Event Viewer for any clues?

If you would like, you can zip up the Event Viewer logs and attach to your next post - you may have to split them up attaching several zip files (max 5 per post) as there are 57 of them in my system right now (fresh Vista install only 2 weeks ago) and their aggregate size is over 50mb - and zipped over 4mb. Each attachment has a 1.96mb max.

They are located in C:\Windows\System32\winevt\Logs - but you my have to copy them out to another folder before zipping them as they are "in use" and usually cannot be accessed by Windows Explorer in the above name folder. It will take me a little bit to go through all of them nd of course there is also the possibility that nothing will be readily apparent in them either.

Regards. . .

jcgriff2

.

__________________

SysInternals Suite • BSOD Bugchecks • Media Fire • Belarc Advisor • MS TechNet • MS NTDE/CPR
MSDN Err Cds • Everest Home v2.20 • CCleaner • Memtest86+ • MS Help & Support
Live SysInternals AutoRuns • Auslogics Defrag • McAfee RT • Norton RT • Kaspersky RT • MS One Care RT

Proprius

I wouldn't mind doing all that if I thought it would help, but other than the two events I posted above there have been no events coresponding with the crash thus far, for now four different crashes since I've started checking the event viewer.

The pattern of things makes me think it must be temperature related - at first the occurence was relatively infrequent, then when I installed the new cooler I also created a bad airflow situation, which caused them to become more frequent. After I fixed the airflow, the crashes have become less frequent.. at least as rare as they were prior to the new cooler, if not rarer.

Do any of the temperatures I've listed seem high? Will the recomended safe ranges for the hardware be listed anywhere? Or have you more knowledgeable folks ruled out overheating for some other reason?

jcgriff2

Have you looked through all 50+ of the event logs? Some like hardware and IE are blocked by Vista and do not get written to. And I have found items in some logs that are unexpected - as in I would not think an event would be in certain log. re you simply looking at the admin log? I cn tell you from experience with BSODs that a hardware error can bring a system down so fast that there is no entry recorded in the Event Logs.

I honestly don't know about the temps and again will defer to the hardware experts on this.

Regards. . .

jcgriff2

.

__________________