memtest probe & shared graphic memory.
Hi,
Platform : nvidia ION (shared graphic memory) Having random lockups, I decided to run memtest. It ran fine : no errors, just another lockup. So I decided to use the "probe" method of detecting memory. It corrupted my display and eventually led to another lockup. Am I right in thinking that by running probe memtest opened for itself the memory reserved for the graphic chip, and when it started executing tests there, the graphic card didn't know what to do, so it locked up? Thanks, Serafean |
It ran fine : no errors, just another lockup
I don't get that. It either ran fine or it locked up. It can't do both. Since you admit to some issue with lockups then we can assume an issue. When you run memtest more than a few other chips are being tested so we can't tell. We can only say memtest should work on most systems. Like 99% of them should pass. A few have odd issues like usb holes for legacy devices. Go back to basic diags. Swap, test, and such for more clues. Power supply, temps and bios settings need to be looked at. Run other versions of memtest or microsoft's memory diagnostics. I'd throw the board away. |
Quote:
Quote:
Quote:
My main question hasn't been answered though : When I tell memtest to probe for memory, does it ignore any limits put up by the BIOS and is thus able to access memory reserved for the graphic chip? Hence the graphic corruption? I did this on 2 computers with integrated graphics, and both behaved the same way. Thanks, Serafean |
All times are GMT -5. The time now is 10:16 AM. |