M6800 Owners' Thread

I don't suppose disabling "automatic restart" so you can write down whatever error codes / culprits displayed, has been tried yet, has it?
I would think that'd at least offer a (clearer) starting point (clearer than shooting in the dark with stuff like memtest86, anyway).

 

memtest86 is cheap (free except for the USB stick) and easy to try. And memory is easy and (relatively) cheap to replace.

If memory is bad -- and my experience is that that's a particularly common failure point, in part since most other things are soldered in place and the CPU is clamped much more tightly in place (or soldered down, on Skylake+ systems, which doesn't apply here) -- it can masquerade as just about anything. If you're lucky, it will cause OS panics as is happening here; if you're unlucky, you might get silent data corruption. If it is causing panics, they may or may not be reproducible and may or may not be consistently the same failure point, depending upon whether particular memory cells are bad or if there's some other problem. Unless you have ECC memory, you won't get an explicit memory failure error.

memtest86 is quite effective, if you allow it to run one or two full passes. It tries really, really hard to stress memory.

My rule of thumb is that with any flaky errors the very first thing I try is memtest86.

 

I'm not saying memtest86 isn't a useful tool, but if there's, say, one particular wonky driver that's the root-cause of those BSoD's, you can stress / test the memory until the cows come home, to no avail

 

That's true enough, but by the same token, a memory error could mimic a driver failure, if the error happens to be somewhere that the driver's always loaded. Running a full pass of memtest86 gives you a pretty good assurance of whether the problem's there or elsewhere.

 

There is a tool called "Bluescreenview" which will let you see this information after-the-fact. It will show a log of the BSODs and highlight files with active code running when the BSOD occurred. If there is a similarity between them, you can track down what driver the file belongs to and you have your culprit.

http://www.nirsoft.net/utils/blue_screen_view.html

 

Hallo.
i just got another project in order to upgrade an M6800 with a gtx 980m.
The gtx980m has several damaged pci pins.Is there anyway To find out if the card is damaged?.
If so....is it possible to repair it?.
Any help would be great.
Thanks

 

http://forum.notebookreview.com/attachments/mxm-3-0b-7970m-pinouts-jpg.117904/

Going by that (look towards the lower-right area), the pins that are damaged seem to be part of the "DPA" or "DPB" outputs (DisplayPort A or B). Odds are good those will be used either for the internal display, or one of the external ones.

Depending on which it is, there could be a chance the card could still work with those contacts removed altogether, with the above-mentioned caveat.

How did that happen, anyway? And is the slot it used to be in, still in one piece?

 

Thanks for the quick info.
The motherboard slot is intact,I got the card from another source that did not handle it with care.
Besides that,if it does not work do you think I can send it for repair/exchange to any outlet to fix it?
Thanks

 

Unless you got it "as faulty", and/or for almost-free (aka free-99), i'd rather send it back to the seller and get a refund. "Reapplying" those sort of edge-contacts is... VERY tricky, to say the least, and even if it is feasible (and let's not even bring up the cost), there's no guarantee they won't be "shaved off" the next time you insert it into an MXM slot. They're quite on the "snug" side, if memory serves...

 

Well,was neither the case.But I will try it and see the outcome.
Thanks a lot for your quick answer
Regards.