Synaptics causes BSOD on P650SE

I have never touched anything related to under volting or overclocking etc.

I have formatted at least 4 times since getting this laptop last March, from Win8.1 to Win10.
I've tried Clevo drivers, XMG drivers and XMG BIOS and or Drivers directly from the manufacturers including Synaptics and Realtek etc

This has eaten up so much time and energy, and since coming back from the "repair" center the first time there are now
black lines in the screen or the screen goes totally black for 1 second at random times. (also happened on Win8.1)

My brother has the exact same laptop, never had this problem on Win8.1 nor Win10.

I've used a W170ER and W370ET before and never had such issues.

 

Just wanted to say that after installing the Win8.1 driver for synaptics I've seen no more BSODs at all. I've disabled automatic updates, so it does not install the Win10 driver again. I could imagine this is what happens to 9 out of 10 that installs the Win8.1, but not realizing that the Win10 is back and causing more BSODs.

 

Clevo provided Synaptics driver or driver from Synaptics directly?

How long have you been using it?

 

It's the Win 8.1 from the XMG P505 driver site in the main thread of Clevo P65xSx.
Version 19.0.15.2

I've been using it for about a week. This installation had one BSOD while using the auto-installed driver and now with the aforementioned one, I haven't seen any since

On a second thought, shouldn't 8.1 driver be version 18.x.x.x?

 

Yea that's what I thought too, I only used the XMG win10 drivers though, took almost 2 weeks before BSOD so I wouldn't count on it being cured.

Just super random and hard to reproduce.

 

Huh, well I had it happen every day exactly when I went to work. I would wake the laptop from sleep, it would hang on login (no mouse movement) and then mostly BSOD or respond after 15 seconds or so. Sometimes 1 minute later BSOD anyway, because why not

Was happy with 7 and 8.1, but now 10 seems stable for me anyway.

I never had the bbxxkks .sys BSOD though and also never while gaming.

 

That sounds like a different problem then, I've never had any problems with waking from sleep or anything.

 

So what do you have? During gaming?
I think they are somehow all related. It seems weird that from 8.1 to 10 all these BSODs show up.

 

My BSODs always happened during gaming at totally random times, you could be playing all night without problem or you could BSOD after just 5 minutes playing.
I thought it was limited to games only but a few nights ago I was in the middle of work stuff on desktop and it BSOD.

So it can happen anytime, but as far as I remember the BSODs only ever happened while inputting on the keyboard because I was typing when it BSOD a few nights ago,
so maybe it's a faulty batch of keyboards.

I've tried every driver available, no luck.
My brother got the exact same laptop as me (we ordered at same time, came together) and his never had this problem, on Win8.1 or Win10.

So that's why I think it must be hardware, like a bad batch of something.

It went to the repair center and got a mainboard replace no help, but now the screen goes black sometimes (or horizontal black line).

 

Wow you haven't been very lucky! I think you should downgrade to 8.1 if stable or go with 7 even. I know that 7 is rock-solid with this hardware and should be supported till 2020, where this hardware is far obsolete.
If this installation gets weird or BSOD I will settle on Win7 for good and not touch it again.

 

BSODs are often either software related (usually drivers) or memory related. Not always, but most often, in our experience.

Did you contact the repair center about the black screen/line?

 

Yes I was trying to get a new RMA no. but then they were looking for the RMA no. of the first repair, which I have sent, now there's no response, so I'm going to have to send it back to the reseller instead.

 

Ah, yeah the resellers tend to be your best avenue when it comes to support. Hopefully they can help you out.

 

Resellers usually have better channels to the manufacturer where certain things can be assumed which speeds things up.

 

Hey guys, it sounds like a power issue. During heavy use, (gaming), I'm guessing the keyboard and/or trackpad don't get enough power, crashing them. With fans running full blast, the GPU and CPU sucking up everything they can, I'm assuming a AAA game is a real strain on power. I have a P650SG and have the exact same problem. I just realized that I installed regular soDIMM DDR3 RAM, but the laptops are only rated for DDR3L or low voltage. Are we stressing our laptops' power supplies by using the wrong RAM?

 

I guess a better troubleshooting question would be, is anyone currently experiencing these issues with DDR3L, (confirmed) RAM in their system? And if so, how many sticks?

 

I've got 4 sticks of kingston 99u5428-018.A00LF, which are DDR3L and I've been experiencing some of these SynTP.sys BSODs, but none of the other BSOD which seem to plague people. Mine only happened in Win10 and now back on Win10 it has not happened since a month or so. (new drivers I believe).

My BSODs mostly happened after waking the laptop, where it froze and SynTP would show up. I even use a 110W traveling power supply and that seems to play no role.

Based on this I find it hard to believe that it is power problems.

 

I'm wondering if the BSOD on startup and BSOD in-game-only are separate issues. See, it seems unlikely that these are just driver problems, because if the error just moves to pointing to a different driver when you uninstall the Synaptics one, it can't be synaptics. What happens if you uninstall the hotkey driver but not the touchpad?

 

I doubt it's power because my last BSOD happened on desktop while typing.
Meanwhile I'm waiting on my "repaired" laptop to come back from reseller.

 

Experience my first BSOD due to SynTP.sys today. Windows 10 Pro using default drivers from microsoft. Had the laptop for around 6 weeks. BSOD happened while in game, touchpad was disabled.

 

Dunno how I missed this post.
I didn't get to try uninstalling the Hotkey (control center) but again it always comes back to this:
if an identical machine using the same BIOS and drivers doesn't have the problem, it can't be the BIOS or drivers, and I don't think we have anything weird installed to cause any conflicts.
Hopefully someone else can try uninstalling the Hotkey driver, the reseller has my laptop and is testing it.

Disabled via the Fn + F1 shortcut?

Anytime my laptop BSOD, it was while I was using the keyboard (moving ingame or typing while on desktop)
Can anyone else confirm the same?

 

Yes via the keyboard shortcut. It hasn't happened again. I only use the laptop keyboard so yes it was in use.

 

There's no question then, the underlying cause of the BSOD caused in-game has always been the hotkey driver. Not synaptics. We can only assume that the hotkey crashing causes synaptics to crash afterword. I really wonder if the crash will happen using an external keyboard and mouse. Anyone want to test?

 

I'm interested in follow ups as well regarding this (so far we haven't had any calls about it). What are you guys using to analyze your minidump files, if anything?

 

I've been using Blue Screen View to view crash reports. Points to syntp.sys. I am running the Windows 10 version of the synaptics driver.
All my crashes point to SynTP.sys at +6e9cc

 

To confirm this is what the window looks like

 

Hey guys. I'm running a P750-DM and just got a SynTP.sys BSOD -



Just adding to the pile

 

I certainly hope this isn't a prevalent thing on your model, too! Any rhyme or reason to yours?

 

I've gotten the same thing on my M5 a few times now. I never use the track pad anyways so will disabling it in the control panel lesson how often it happens?

 

Just like to report I have had no BSOD on Win10 for a month now. Install date 19th october and I've been playing, shifting screens on HDMI and DP, sleeping, hibernating and what not. I've got hotkey 3.0.0.35 and Synaptics 19.0.24.1.

I am confident that mine is now stable.

 

It happened twice, but I was potentially dealing with a loose SSD connection at the time. I somewhow managed not to plug the darn thing in hard enough... *facepalm*

Hasn't happened since, but I will certainly report back if it does.

 

Yeah no system likes loosing the host storage ^_^

 

Heh. Yeah, seriously. This very may well have been the source of some of the issues I was having with a W7 installation too. I'm enjoying W10 though, so may not revert back to it. If it ain't broke (or spying on you)....

 

The only systems I have worked on that can survive are the IBM Iseries systems which go into a panic mode when they loose the disks, the system pauses itself and it can try to resume when you re-attach the disks, does not always work though.

 

How do you remove the hotkey driver? I'm absolutely sick of these bsod's while trying to play WOT

 

Uninstall Clevo Control Center, we still don't know if that fixes it or not though so let us know if the BSODs stop.

I'm waiting on my laptop to return.

 

My crashes have always happened with an external Microsoft keyboard and Logitech mouse.

Fun story time: in March, I had the same BSODs that you guys did. In fact, if you look in the first page of this topic, you can see some of my posts. Miraculously, around the end of April, my P650SG stopped crashing. I dunno how I did it. I didn't make any changes to the hardware, but I did swap out various drivers and utilities until something finally worked. At the time, I attributed my victory to the removal of Intel Rapid Storage Technology, but it's very possible (and in hindsight, far more likely) that my success was tied to using a certain version of the Hot Key utility instead.

My P650SG was crash free for months. It even went through a Windows 8.1 to 10 upgrade with no problems. Sadly, a couple of weeks ago, I had the bright idea of updating all my drivers to their Windows 10 version cause you know, why not. I didn't realize that it would cause these damn BSODs to start happening again. Unfortunately, I don't remember exactly what version of Hot Key I was using before.

Is there anything bad that can happen from deleting Hot Key and just running without it for a while? Cause I might try that and see what happens.

 

Try hotkey 3.0.0.35 and Synaptics 19.0.24.1
That works for me.
You can remove hotkey without any trouble, but I recommend it for reducing fan noise.

 

Another user with the exact same issue here. I first downgraded the synaptics to an older version, still happened, then removed it, still happened except now it says its caused by hkkbdfltr.sys . Diagnosing issue with WhoCrashed. I'm not really getting a BSOD, its more like the screen goes black mid game stuck on whatever sound was last played, the backlight flickers a few times, and then the computer restarts. Temps are about 55c on GPU and 60c on CPU when it happens, and it happens on any game, about once every 2-3 days, whether the game stresses the GPU or not.

xink64, where do you see what version hotkey is? I can only find the control center download for version 5.0000.0.32. I don't even know how to find what version my control center was before, so I don't know how to tell if this one will be any different.

As a side note, if I use any utility to even slightly change the clock speeds of my memory or core of the GPU, i also have an issue where the GPU will randomly lock at 540mhz until I restart....

System specs, Clevo P670RE3 / Sager NP8677, with i7 6820HQ, 970M, 16gb DDR4 ram, Samsung 850 pro SSD, windows 10 Pro x64.

 

Is this still happening to anyone? I just had this like 10 minutes ago. This has also happened in the past to my P650SG. The weird thing is that the BSoD is not blue, it is orange.

https://drive.google.com/file/d/0B3GMqW1ooxOlbWpVemJTSzc5M2s/view

Picture in Google Drive link ^^

 

I just had it happen again, within a couple hours after updating to synaptics 19.0.24.1 and control center 5.0.

syntp.sys (SynTP+0x6E9CC)
Bugcheck code: 0xD1 (0xFFFFE0005A600008, 0x2, 0x0, 0xFFFFF800A2EBE9CC)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL

Im regretfully going to uninstall control center and see if that helps.

Mine could very well be orange too, but im very colorblind.

 

hotkey and control center is not the same I believe. When I check the version I go to the executable file of the program go to settings and then it should say somewhere which version of the program it is.

 

Guys....seriously, who installs touchpad drivers nowadays Not only are most of us using mice, but windows has enough default drivers to run that pad on its own.
I would never bloat my comp with touchpad drivers, even if it didn't work without them

 

Well windows installs a TouchPad driver on its own which is prone to give people bsod, which is one of the reasons why this thread came to be!

 

Ah, damn. I thought it was the official synaptics driver who was at fault. This must be happening on the newer windows versions, as I've never had this on win7. I wonder what exactly is causing this...

 

It's an official synaptics driver. It's just installed automatically by Windows 10. If you use 8.1 or 7 you also need this Synaptics driver for a "functioning" touchpad. However the problem here (with my setup however) is Win10 + a set of synaptics drivers which where autoinstalled and crashed the system constantly. Since version ****.24 of synaptics, it never makes any errors anymore. Guess they fixed it. The broken versions had a very smooth and nice scrolling, which they have removed, I suspect it was causing some of the trouble.

 

It seems MS rolled out a new build of Windows 10 not long ago. Has anyone been experiencing the crashes on this recent update?

 

I am still crashing with the new 19.0.24 synaptics drivers, and the BSOD even said synaptics was the cause of this. And to iterate that the touchpad doesn't even seem to be responsible, many of us on this thread including myself, have completely removed all traces of the touchpad drivers, and the crash still happens due to clevo hotkey.

And as far as needing the touchpad drivers, without them, I cannot disable the touchpad via hotkey anymore, and while i generally use a mouse, it is sometimes convenient to be able to use a touchpad and scroll smoothly, as well as customize its settings to function better. With them gone, I have to go to device manager and completely disable the device permanently, and its not even functional outside of games. I can confirm, windows does indeed force install genuine synaptics drivers, which was an inconvenience to prevent.

 

Yes, I have the newest windows 10 updates, and I am still experiencing this issue. It happened twice yesterday.

 

I've just realized I was still on 10240 with no crashes in a long time.
I will upgrade now just for sports..