Clevo p650RS-G hard crashing

Not this school, no. I might consider it when I’m done with school and more financially prepared to drop a chunk of money on it. I’m just really frustrated with this entire situation. I don’t understand how a brand new computer can have this many issues from the get go.

 

See Louis Rossman's videos on popcorn CPUs to make you cry.

 

You should setup full memory dumps and disable auto-reboot so that you have time to read the BSOD or even better, get a photo of it. BSODs usually tell you exactly what is faulting and without that there's not much that can be done.

You can do that in Control Panel -> System -> Advanced System Settings -> Start-up and Recovery.
Under "Write debugging information" change the drop-down to "complete memory dump" and uncheck the automatic restart option. Depending on your RAM size, this should buy you at least 30 seconds if it's a hard fault or should sit on the BSOD until you manually reboot.

 

I’ll look in to that. Thanks

 

So it was an easier fix that I thought. I replaced the ram. Runs like a champ now.

When I had it built I selected the fastest ram they had available thinking all the ram they would offer for my build would be compatible. Turns out that wasn’t the case. The specs for the i7-6820hk show that 2133mhz is the fastest compatible ram and the ram that was in there was 2666mhz. So I purchased the exact same brand and type but in 2133mhz and now I have no issues at all.

The funny thing is that I sent my laptop back and they said they couldn’t replicate the issue. Knowing now that it was a hardware malfunction and not a software issue I don’t think they did anything at all when I sent it in. Way to go tech support. Glad I got to pay for new ram out of pocket.

 

Ok that's new, would you mind sharing where did you find such information? Also did it completely solve your problem?

Thanks

 

Of course. Most of my BSOD’s in bluescreenviewer had the ntoskrnl.exe but not much more in common. Sometimes IRQL..., sometimes nvdlkkm or whatever that one is or syntp or hardware etc. but the ntoskrnl was always around. I did some searching and found that these are often related to memory issues.

So I went and googled my motherboard. An Intel I7-6820HK and got to this website.

https://ark.intel.com/products/88969/Intel-Core-i7-6820HK-Processor-8M-Cache-up-to-3_60-GHz

I cross checked it with a couple others and they were all consistent in the fact that ddr4 2133mhz was the highest speed ram it would allow. I ordered my laptop from HIDevolution and when I purchased it 2666mhz ram was available and I assumed that if they offered it for my build it was compatible; it was not.

I ran memtest86 multiple times on each stick in each port and the computer ran fine on just one of the sticks of ram. However memtest would never pass if I had both ram sticks in and that’s when I would get the BSOD’s.

HIDevolution had my computer for almost two months and even sent it back to the manufacturer for diagnosis. They claim they tested all kinds of things but for something as simple as ram problems, that happened ALL THE TIME, I found it hard to believe anything was done at all.

Long story short, I guess check the compatibility of all of your associated hardware to make sure it’s all compatible. I’ve had headaches the last year and a half over this and never thought to check that.

 

Also as far as I can tell I have no problems. I’ve slowly been reinstalling other software that was buggy. My next two are the newest nvidia graphics driver because I rolled it back to the newest 38x.xx because usually the one closest to the next ten series is the most stable. Basically whatever is in the 380’s would be more stable than the 390.xx. If that makes sense.

And the clevo control center. I got rid of that because it’s buggy. I do miss being able to change my backlight color but if everything is more stable it’s something I can live with.

 

I am glad you found a solution that works for you.

While it may well have been faulty RAM, it was not due to incompatibility. There are hundreds, if not thousands, of laptops in the field with the Intel Core i7-6820HK that successfully support DDR4/2666MHz memory.

ark.intel.com is well known for publishing specs at the release of a CPU, and never updating them. For example, when 16GB memory pieces became available, Intel refused to change their specs at ark.intel to show that the chipset/CPU would support the larger memory capacity. The same is true of the Intel Core i7-6820HK, which also supports DDR4/2400MHz and DDR4/2666MHz memory. You ran Memtest and it showed no errors.

Both HIDevolution and Clevo ran games for hours and days trying to replicate the issue, without a single BSOD. However, upon viewing the log of your last BSOD before sending it in, it indicated it was a driver issue, not RAM.

The bottom line is, after working with you for weeks, continually testing in an attempt to get it to BSOD, it never would. So we sent it back to you. You reported upon its receipt that you were still getting BSODs. We worked with you then, and will continue to work with you for a proper resolution.

Please email be directly at [email protected] and I will offer you what I believe will be a satisfactory solution.