Solved memory_managment issues

[Jonathan_King]

Nothing is wrong with Daemon Tools. The problem is with a driver it uses, SPTD. Read about it here: DuplexSecure - Downloads

Several program use that driver, including Alcohol.

 

[theboyfold]

Brand new install and have just installed LAN, chipset and audio drivers plus Firefox and had another memory_management BSOD

Files attached

 

[Jonathan_King]

All I can recommend from the software end is installing this updated Realtek networking driver: Realtek

Also install this updated GFX driver: NVIDIA DRIVERS 258.96 WHQL

Now RAM problems don't just disappear. You may have corrected something by reseating the sticks, but more is needed.

Test temps: SpeedFan - Access temperature sensor in your computer

Run a memory test again, with all sticks in: http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

Run this Prime95 test: http://www.sevenforums.com/tutorials/100352-cpu-stress-test-prime95.html

Only difference, select Blend instead of Small FFTs.

...Summary of the Dumps:

[font=lucida console]
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Thu Oct  7 10:23:08.268 2010 (UTC - 4:00)
System Uptime: 0 days 0:05:55.283
BugCheck 1A, {3452, 3e12000, fffff70001088218, f640000048718c66}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+33ab3 )
BUGCHECK_STR:  0x1a_3452
PROCESS_NAME:  firefox.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
[/font]

 

[theboyfold]

What should I be expecting in terms of core temps?
At full load it's running between 87c and 96c across the different cores...

I've now gone back to my 'original' RAM which is the same but has a higher clock speed of 1600.

Interestingly I couldn't even run Prime with the older RAM in, and now with the 'new' RAM in it's stressing the CPU across all 8 cores to 100%.

 

[Jonathan_King]

That seems awfully hot to me.

Open up your computer, and clean out any dust buildup. Blast the CPU heatsink/fan with compressed air, wash out any air filters, and plug in any fans you may have.

When that is done, run Prime95 again, using the Large FFTs, and watch the temps. See if it makes a difference.

 

[theboyfold]

Sooooo, popped out after my last post and went to a local PC store

Spoke to a very knowledgable guy in there and walked out with a new heatsink, which is too big for my case!! Lucky for me the case was on the verge of being replaced.

Anyway, have checked my temps and it's now running at about 35-40c on idle and about 60c when under full load.

I'm going to run Prime on Small FFT overnight to see how it holds up, fingers crossed it will be still here in the morning!

One thing I have noticed is this when I run Prime in Blend mode:

[Thu Oct 07 16:02:10 2010]
FATAL ERROR: Rounding was 0.5, expected less than 0.4
Hardware failure detected, consult stress.txt file.
FATAL ERROR: Rounding was 0.5, expected less than 0.4
Hardware failure detected, consult stress.txt file.
FATAL ERROR: Rounding was 0.5, expected less than 0.4
Hardware failure detected, consult stress.txt file.
FATAL ERROR: Rounding was 0.5, expected less than 0.4
Hardware failure detected, consult stress.txt file.
FATAL ERROR: Rounding was 0.5, expected less than 0.4
Hardware failure detected, consult stress.txt file.
FATAL ERROR: Rounding was 0.5, expected less than 0.4
Hardware failure detected, consult stress.txt file.
FATAL ERROR: Rounding was 0.5, expected less than 0.4
Hardware failure detected, consult stress.txt file.
[Thu Oct 07 21:53:28 2010]
FATAL ERROR: Rounding was 0.5, expected less than 0.4
Hardware failure detected, consult stress.txt file.
FATAL ERROR: Rounding was 0.5, expected less than 0.4
Hardware failure detected, consult stress.txt file.
[Thu Oct 07 22:07:53 2010]
FATAL ERROR: Rounding was 0.5, expected less than 0.4
Hardware failure detected, consult stress.txt file.
FATAL ERROR: Rounding was 0.5, expected less than 0.4
Hardware failure detected, consult stress.txt file.
[Thu Oct 07 22:13:14 2010]
Self-test 1024K passed!

Not sure if it's anything to worry about, have done a little reading on it and it could be down to a number of things, what's the learned opinion on here?

 

[theboyfold]

So we can rule out over heating as a cause of the BSOD, as I've just had one with the cores all nice and cool.

I was running the benchmarking in Prime when it went. Files are attached.

I'm starting to think it's the MoBo that's at fault as everything else that I try does nothing.

There is no perfmon report attached as I got this when I tried to run it:

Error:

An error occured while attempting to generate the report.

The RPC server is unavailable.

 

[theboyfold]

So, after much fiddling and playing last night I've reset all my BIOS settings to the failsafe default, set the CPU multiplier to the correct setting for the i7 920 and ran Prime 64 over night. So far no BSOD and it managed to run IntelBurnTest set to maximum and passed 3 runs of that.

So it may have been just a setting in the BIOS after all...

Fingers crossed!

 

[Tews]

You were overclocking your CPU????? ...

 

[Jonathan_King]

Good to hear that.

Overclocking is a definite cause of BSODs. If you are overclocking, and start getting BSODs, that's one of the first things you should try.

Thanks for the report...hope it stays that way!

 

[theboyfold]

I wasn't actually over clocking the CPU at the start of this, it was set correctly. However when you reset to fail safe it removes the multiplier from the CPU clock speed. So I was saying I reset the clock multiplier and the voltage for the RAM after going back to the fail safe.

Thanks for the help so far, I've certainly learnt a lot! I'll let you know if I find anything else.

 

[theboyfold]

Hello again

Now suffering from a new issue where Windows won't boot at all

I've tried to have a look for new BSOD dump files, but happens at a point where it doesn't write a log. Almost instantly after seeing the 'Windows is Starting' line and the dots start to fly on screen I get a BSOD and it reboots.

I've tried to read what it says and I think it's “Page fault in non-paged area”. The only way I can fix it is by using my bootable USB and running Windows Startup Repair from that, as running Startup Repair on the HDD doesn't seem to work.

I thought I'd fixed this issue, but after a few days of the machine sitting idle it started to happen again.

Any thoughts?

 

[Jonathan_King]

Now that sounds like a hard drive issue. Test your drive: HD Diagnostic

 

[theboyfold]

Thanks, I'll give it a go when I'm home.

I'm also wondering if it's the graphics card as I had to reset it when I changed to the case and I've read that it can cause the same issue.

 

[theboyfold]

Just thought I'd finish this thread off. It was in fact as issue with RAM that didn't work with the mobo! Ended up getting the RAM from Crucial and its working fine now.

Thanks for all the help

 

[Jonathan_King]

Thanks for the final update, glad you're all up and running now!