Solved memory_managment issues

[theboyfold]

Hello all

I've attached some logs for your enjoyment, could you have a look and let me know what my first course of action should be please?

Thanks in advance.

ps: Sorry for the short post, need to run!!

 

[zigzag3143]

Hello all

I've attached some logs for your enjoyment, could you have a look and let me know what my first course of action should be please?

Thanks in advance.

ps: Sorry for the short post, need to run!!

They are indeed caused by memory management first you need to check you ram

Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Boot from the CD, and leave it running for at least 5 or 6 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot. Test the sticks individually, and if you find a good one, test it in all slots.


Let us know with the results


Ken J

 

[theboyfold]

Have just been running memtest, have 164864 errors with all 3 sticks in!!

However, when I ran it earlier it didn't show any errors, that was for about an hour or so.

I'm running it again now and it's not shown anything yet. How long should I run it for?

 

[OldMX]

Run the test for each stick a couple of loops.

 

[theboyfold]

Silly question, but where can I see the number of loops that have been run?

 

[zigzag3143]

Silly question, but where can I see the number of loops that have been run?

They are called passes and are clearly shown. You are running memtest from a booted cd/dvd correct? each stick (and slot) should be run for at least 5 passes


Ken J

 

[theboyfold]

Silly question, but where can I see the number of loops that have been run?

They are called passes and are clearly shown. You are running memtest from a booted cd/dvd correct? each stick (and slot) should be run for at least 5 passes


Ken J

Yes, can see it now.

I'm running it from a bootable USB (Pen Drive Linux) and I had all three sticks in.

 

[theboyfold]

Right, I've run each stick for over 5 passes in Memtest, but only using the first slot. All of them passed.

I'm now doing a run with all 3 in.

If this passes do I need to run all sticks in all slots? Or just one stick in each slot as I've shown that the sticks (should) be ok?

 

[theboyfold]

I've now run all the sticks in the all the slots over night and no errors after 12 passes. I've also run IntelBurnTest on a high setting and it survived.

I think it was being caused by a capture card I had in stalled and / or Kaspersky / Roxio BluRay software.

How can I prove this? What other tests can I run?

 

[Tews]

are you still having BSOD problems???

 

[Jonathan_King]

You can run driver verifier: http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

Though you might as well just wait and use your computer normally, as that is the true test.

 

[theboyfold]

Tews:

Not at the moment, but I've not really done anything other than run those tests.

I'm not sure how if those tests are enough or if I need to do anything else?

 

[Tews]

Do as JK suggests ... Driver verifier will stress the drivers, forcing a BSOD .. upload the new .dmp files for analysis..

 

[theboyfold]

Do as JK suggests ... Driver verifier will stress the drivers, forcing a BSOD .. upload the new .dmp files for analysis..

Will do! Thanks for all the help so far

 

[theboyfold]

Well I've followed the instructions and have rebooted with (seemingly) no ill effects.

It stills seems unstable though, for some reason Firefox keeps crashing as does MS Outlook, no reason why though.

I'm starting to wonder if a new install of Windows 7 is needed...

Is there anything I can investigate to see what could be the cause of the program crashes?

 

[theboyfold]

What's the saying? Pride comes before a fall! I'm now posting from the 'safety' of my Mac!

Just had about 7 BSODs in the last 30 minutes!!

I've attached the reports for you to have a look over, enjoy!

 

[Jonathan_King]

Ah...

Remove Daemon Tools Lite, in Programs and Features.

Then run this tool to remove SPTD: http://www.duplexsecure.com/download/SPTDinst-v174-x64.exe

Now go ahead and disable driver verifier, hopefully the BSODs will stop.

...Summary of the Dumps:

[font=lucida console]
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Wed Oct  6 15:54:46.045 2010 (UTC - 4:00)
System Uptime: 0 days 0:00:11.965
BugCheck A, {0, 2, 0, fffff80002cf4436}
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : dxgkrnl.sys ( dxgkrnl!DpiFdoInitializeFdo+11d )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Wed Oct  6 15:47:14.201 2010 (UTC - 4:00)
System Uptime: 0 days 0:00:12.232
BugCheck A, {fffff80002f74c06, 2, 0, fffff80002cfd7a2}
Probably caused by : ntkrnlmp.exe ( nt!RtlDispatchException+122 )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
[/font]

 

[The Howling Wolves]

How is this test different than memtest?
View attachment 102701

and which is better and why?

 

[Jonathan_King]

I'm not sure about the technical details, Denis.

All I know is the user end of it. Memtest86 does a much better test for some reason. The Windows Memory Diagnostic misses a lot of errors, when there is bad RAM.

It's a good last resort; i.e. the OP cannot find any blank CDs, and has no USB drive.

 

[theboyfold]

For some reason that file you linked to me to wouldn't run. So I'm going to go the whole hog and reinstall the OS. For some reason programmes are crashing left right and centre and I've no idea what it is. So I'm going to strip it back and reinstall 7 with all the hardware I (want) and need connected to see what happens then.

BTW, what's the issue with Daemon Tools? Is it a known bug?