Crysis Warhead Crashes (Son's new build)

New build w/ fresh Win7 64 installed. Started out w/ about 12 Event Viewer messages but have reolved most of those. Solved one were related to bad Logitech KB screen drivers (G19) and bundled software that came with the MoBo. The beta nVidia drivers solved the last one I fixed.

last BSOD was 3 days ago but got two in a row last night well pushing the system w/ Crysis Warhead. Core temps were in high 40's. Haven't started any real OC'ing as yet as wanted ton get a clean Event Viewer for few days. resolving all driver issues, before starting that. Uploaded zip file has both dumps.

His system specs are:

ASUS Rampage II Extreme
ASUS Model OC Station
Intel Core i7 920 (OC's using "Level Up Feature tp 965 speeds -3.4 Ghz)
EVGA GeForce GTX 295 FTW Edition 1792MB
Mushkin Redline(3 x 2GB) DDR3-1600 Model 998692 w/ 6-7-6-18 timings
Seagate Barracuda 7200.12 1TB
AFT XM-35U Card Reader
Antec Twelve Hundred ATX Tower Case +(2) optional120mm Fans
Antec Signature SG-850 850W PSU
Plextor Model PX-B320SA w/LS
Logitech G19 Black USB Wired
Logitech G9 Gaming Mouse
EnerMax Magma CPU fansWindows 7 Ultimate
Prolimatech Shadow HS
IC Diamond 7 Carat Thermal Compound
Dell U2410

Hey.

Anytime you get bsod, it's very wise to default clock the machine in all aspects.
When bsod are alleviated, then you can take things from there concerning clock speeds.

You're getting the 0x116 video errors. My standard advice to troubleshoot this specific error is always

1) Do not overclock anything. Ensure adequate cooling of all components, especially video card.
2) Update chipset drivers and bios if possible.
3) Check that the RAM Vdimm (Ram voltage) and timings are correct for the specific memory modules in use. Settings are in bios. Visit RAM maker's site for details.
4) update video card driver from NVIDIA's website.

In addition, there are old drivers on the system causing problems. Update them or uninstall them from the system:

AsInsHelp64 AsInsHelp64.sys Fri Jan 04 00:36:10 2008
adfs adfs.SYS Thu Jun 26 16:52:37 2008
secdrv secdrv.SYS Wed Sep 13 09:18:38 2006
speedfan speedfan.sys Sun Sep 24 09:26:48 2006

Make these changes and let us know how it goes and if the bsod have stopped. Then you can overclock all you want.

Good luck.

1) Do not overclock anything. Ensure adequate cooling of all components, especially video card.

As indicated in original post, temperatures are all well below "normal", case has 8 fans, HS fan has twin fans and core temps were only in high 40's, vid card hovers around 50. Just bumped up CPU speed 2 days ago.....BSOD's come within 10-60 minutes in WoW for two weeks now w/ no OC.

2) Update chipset drivers and bios if possible.

Machine was built the last week in October....all BIOS, drivers are latest and greatest off Asus web site. As per original post, GFX driver is nVidia's latest beta (195) which solved another event viewer error.

3) Check that the RAM Vdimm (Ram voltage) and timings are correct for the specific memory modules in use. Settings are in bios. Visit RAM maker's site for details.

All RAM voltages are "stock", only change is timings which are as per manufacturer spec at 6-7-6-18.. Ran Metest for 16 passes, no errors.

4) update video card driver from NVIDIA's website.

Again, driver is 195, nvidia's latest beta.

AsInsHelp64.sys Driver is latest and greatest
adfs.SYS Haven't figured out yet what the heck this is...perhaps adobe something
secdrv.SYS - Appears to b part of SafeDisk protection scheme - installed w/ game
speedfan.sys - speedfan version installed is their "latest and greatest"

In short no "old" drivers were installed. Box is only 2 weeks old and all drivers were taken from latest list on vendor web sites.

Hrrrm, that safedisk one is on almost every system I saw today with bsod, so that might be something to consider.

How about the RAM voltage? is there a recommendation for that?

What you could also do for testing purposes, is to put a large fan running to point inside the open case. See if bsod happens like that. I know you said temps low but it's still a good troubleshooting method. Also, you can raise the gpu fan with software to highest as well.

Safedisk is copy protection .... it's supposed to screw things up :)

Ram voltage is well below spec (1.55 volts)....1.65 is max

This is an Antec 1200 case with 6 case fans installed at present (took 2 fans out, ordered replacements) and twin HS fans in push-pull config. All temps are very low ....

At idle (Ambient 23C) w/ all fans on low setting:

CPU = 30C
NB = 43C
SB = 41C
MB = 28C

At load (Prime95) w/ all fans on low setting:

CPU = 53C
NB = 45C
SB = 42C
MB = 28C

Max Core temps 65/63/63/61 recorded by Real temp / Core Temp

GPU max temp = 53C

GPU Fan is fine on Auto as not getting hot

JackNaylorPE said:

Ram voltage is well below spec (1.55 volts)....1.65 is max

Does the RAM's page on the manufacturer's site say 1.65v? If so, set it to that.

Edit - yep, it needs 1.65v and 6-7-6-18 timings.

The 1.65 is a maximum according to Mushkin TS folks. They suggest leaving on Auto until BCLK hits 183 and then moving to 1.6. Jives with the table here.

Overclocking Choices And Details - Review Tom's Hardware : Overclocking Core i7: Power Versus Performance

Convinced this is driver not hardware related.

If it was my machine with the crashes, I'd most definitely set it 1.65v and take things from there.

The 0x116 is very related to it.

Often times the only way to get memory stable is to get those voltage settings on the mark., With 6Gb it might take a slight bump in IOH voltage to get stable. For 1600 memory speed the Op will most likely need the 1.65 volts which is perfectly safe.

Not all boards use the same Auto settings for memory so setting up the timings and voltages manually is prefered. The chart the Op posted is a general overclocking guide and had no numbers listed for memory speed versus memory voltage which tend to work in a linear fashion. The chart also made no reference to which board was being used or the brand of memory being used.

The required Vdimm has more to do with the intended memory speed than anything else. For the full 1600MHz the Op will no doubt need 1.6-1.65 for memory voltage.

I can get to BCLK 174 and remain stable at 1.3125 CPU Voltage and like 1.55 DRAM Voltage. Trying 177 BCLK, CPU up to 1.4 and DRAM to 1. does nada.