[Chris Y]

This message pop-ups

I get that message box a lot now a days. And it's not just that one program. It happens when I close down BitTorrent, and randomly pop-ups when running games.

I'm bad at translating stuff but here we go:

The instruction on "0x00d6d51" refered to memory on "0x00bffffc". The memory task couldn't be executed. Following error was returned: The memory could not be "read".

Click on OK if you want to quit the program.
Click on Cancel if you want to search for errors.
"

(when I click "Cancel" nothing happens, except for my program dying that is)

I ran around 40 tests with MemTest, (around 9 hours test-time) without a single error. I also did get help in the malware section. Crustyoldbloke came to the conclusion that it is not a malware causing my problems and that I should post here instead.

Please help me!

I'll say this in advance too: For some reason when I update Windows XP my computer will refuse to start and I'm forced to remove the newly installed updates. Re-installing Windows XP didn't help either...

[Advertisements]

Memtest seems to miss some bad sticks of RAM. It is not that reliable in my opinion. Try this one instead:

Download Stress Prime

After you download it, double-click on it (which opens the CAB that it is in) and drag the program to your desktop. Now you can run it. Click on the drop-down box at the top and select Large, in-place FFTs - stress RAM and click Start

If it detects a fatal error, it will stop automatically and then report it. Or it may even cause your computer to restart or show an error. Let me know if either of those happen.

Otherwise, stop the scan after about 30 minutes, and then in the window at the bottom, it may say if any errors/warnings were detected. Let me know what it says.

[computerwiz12890]

Memtest seems to miss some bad sticks of RAM. It is not that reliable in my opinion. Try this one instead:

Download Stress Prime

After you download it, double-click on it (which opens the CAB that it is in) and drag the program to your desktop. Now you can run it. Click on the drop-down box at the top and select Large, in-place FFTs - stress RAM and click Start

If it detects a fatal error, it will stop automatically and then report it. Or it may even cause your computer to restart or show an error. Let me know if either of those happen.

Otherwise, stop the scan after about 30 minutes, and then in the window at the bottom, it may say if any errors/warnings were detected. Let me know what it says.

[Chris Y]

No errors detected but here's the log:

More than one CPU detected.
You should run two copies of SP2004 simultaneously.
Type: Large, in-place FFTs - stress some RAM Min: 128 Max: 1024 InPlace: Yes Mem: 8 Time: 15
CPU: 2992MHz FSB: 200MHz [213MHz x 14.0 est.]
CPU: 2992MHz FSB: 200MHz [213MHz x 14.0 est.]
2007-01-15 18:48 Beginning a continuous self-test to check your computer.
Press Stop to end this test.
Test 1, 4000 Lucas-Lehmer iterations of M19922945 using 1024K FFT length.
Test 2, 4000 Lucas-Lehmer iterations of M19922943 using 1024K FFT length.
Test 3, 4000 Lucas-Lehmer iterations of M19374367 using 1024K FFT length.
Test 4, 4000 Lucas-Lehmer iterations of M19174369 using 1024K FFT length.
Test 5, 4000 Lucas-Lehmer iterations of M18874369 using 1024K FFT length.
Self-test 1024K passed!
Test 1, 4500 Lucas-Lehmer iterations of M17432577 using 896K FFT length.
Test 2, 4500 Lucas-Lehmer iterations of M17432575 using 896K FFT length.
Torture Test ran 32 minutes 38 seconds - 0 errors, 0 warnings.
Execution halted.

[computerwiz12890]

Run Stress Prime again, this time select Small FFTs - stress CPU as the test to perform. Let this one run 1 hour before stopping it.

Let me know how it goes.


In addition to that, do this:

Click Start, then Run, type cmd in the Open box and click "Ok". At the prompt in the Command window, type fsutil dirty query c: (This queries the drive and will tell you if it is dirty or clean)

Let me know what it reports.

[Chris Y]

No errors this time around either, here's the log

More than one CPU detected.
You should run two copies of SP2004 simultaneously.
Type: Small FFTs - stress CPU Min: 8 Max: 32 InPlace: Yes Mem: 8 Time: 15
CPU: 2992MHz FSB: 200MHz [213MHz x 14.0 est.]
CPU: 2992MHz FSB: 200MHz [213MHz x 14.0 est.]
2007-01-17 20:56 Beginning a continuous self-test to check your computer.
Press Stop to end this test.
Test 1, 800000 Lucas-Lehmer iterations of M172031 using 8K FFT length.
Test 2, 800000 Lucas-Lehmer iterations of M163839 using 8K FFT length.
Test 3, 800000 Lucas-Lehmer iterations of M159745 using 8K FFT length.
Self-test 8K passed!
Test 1, 560000 Lucas-Lehmer iterations of M212991 using 10K FFT length.
Test 2, 560000 Lucas-Lehmer iterations of M210415 using 10K FFT length.
Test 3, 560000 Lucas-Lehmer iterations of M208897 using 10K FFT length.
Self-test 10K passed!
Test 1, 460000 Lucas-Lehmer iterations of M250519 using 12K FFT length.
Test 2, 460000 Lucas-Lehmer iterations of M245759 using 12K FFT length.
Test 3, 460000 Lucas-Lehmer iterations of M245281 using 12K FFT length.
Self-test 12K passed!
Test 1, 380000 Lucas-Lehmer iterations of M291913 using 14K FFT length.
Test 2, 380000 Lucas-Lehmer iterations of M286719 using 14K FFT length.
Test 3, 380000 Lucas-Lehmer iterations of M282625 using 14K FFT length.
Torture Test ran 1 hours, 16 minutes 14 seconds - 0 errors, 0 warnings.
Execution halted.

The fsutil says the drive is clean.

[computerwiz12890]

ok, let's see if we can get anything useful out of Event Viewer:

Click on Start, Run, type eventvwr in the text box and then press Enter. Click on Application and see if there are any exlamation marks or red X's at the time when your computer had an error or froze. If there is an exlamation mark or X next to an item, double-click on that entry and copy the description of the error. Do the same thing for the System section. Post the description along with the source so I know what the description belongs to.

[Chris Y]

Now that's a huge list... It's a lot of X's and not too few of ! either. Here's one of the latest that I think happend about when I had that kinda memory error:

source: "Application Error"
"Felaktigt program jk2ded.exe, version 0.0.0.0, felaktig modul unknown, version 0.0.0.0, felaktig adress 0x00d6d5f1.

Mer information finns i Hjälp- och supportcenter på sidan [url="http://go.microsoft.com/fwlink/events.asp.""]http://go.microsoft.com/fwlink/events.asp."[/url]

Would be translated to something like:

Bad application jk2ded.exe, version 0.0.0.0, bad module unknown, version 0.0.0.0, bad address 0x00d6d5f1.

More information in the help- and support center on page [url="http://go.microsoft.com/fwlink/events.asp.""]http://go.microsoft.com/fwlink/events.asp."[/url]

In the system tab there seems to be also some errors that keeps coming back and they're always in the same order.

One source named "ati2mtag" gave this error many times on the list:
CPLIB :: Open Session - Failed to load the library

And another one with source "NetBT" which couldn't initiate because it couldn't "create the drivers".

Edited by Chris Y, 18 January 2007 - 12:41 AM.

[computerwiz12890]

One source named "ati2mtag" gave this error many times on the list:
CPLIB :: Open Session - Failed to load the library

Please update the drivers for your video card. If you do not know how to do this, let me know and I will assist.

This may be the answer to your problem.

[Chris Y]

Okay, I'm now updated with the latest drivers from 10th Jan 2007. My memory problem is still around though.

Edited by Chris Y, 20 January 2007 - 07:00 AM.

[hornet_hockey]

OMG, thank you for posting this, I have the same problem. Every time I log off it does that

[Chris Y]

I'm using no special toolbar. Unless it's hidden.

[The Skeptic]

Do you have an onboard video connection? If yes connect your monitor temporarilly to this connection. Run the computer and see if the problem recurs.

[Chris Y]

I don't know what that is. I guess chances are that I don't have one then.

[The Skeptic]

See f you have another point at the back of the computer to whuch you can connect the monitor. If there is one, connect the monitor cable to there and try to run the computer.

What is the make and model of the motherboard? Let us know and we will help you to find out if there is an onboard connection.