Meaning of debugger output?

geoffcox

Posts: 23   +0
Hello

I have had my Windows 7 Home Premium turning itself off a few times now. The debugging output is attached - does it give anyone a clue?!

How do I carry out a stack trace?

'appreciate any help on this!

Thanks

Geoff
 

Attachments

  • debuglog.txt
    16.7 KB · Views: 2
This is the important information: "Probably caused by : memory_corruption" Therefore, you need to run memtest on your RAM.


See the link below and follow the instructions. There is a newer version than what is listed; use the newer. If you need to see what the Memtest screen looks like go to reply #21. The third screen is the Memtest screen.

Step1 - Let it run for a LONG time. The rule is a minimum of 7 Passes; the more Passes after 7 so much the better. The only exception is if you start getting errors before 7 Passes then you can skip to Step 2.

There are 8 individual tests per Pass. Many people will start this test before going to bed and check it the next day.

If you have errors you have corrupted memory and it needs to be replaced.

Step 2 – Because of errors you need to run this test per stick of RAM. Take out one and run the test. Then take that one out and put the other in and run the test. If you start getting errors before 7 Passes you know that stick is corrupted and you don’t need to run the test any further on that stick.


Link: https://www.techspot.com/vb/topic62524.html


* Get back to us with the results.
 
I used Mem Test and it came up with 2 errors - I have re-seated the 4 RAM chips and will run Mem Test again tonight.

Cheers

Geoff
 
Any errors with memtest and you have corrupted memory that needs to be replaced, though we have seen on the rare occassion where memory was not seated properly causing this issue.

* Keep us updated.
 
Back