Synaptics causes BSOD on P650SE

I bought my P650SE last year and have been playing BF4 for a while. Everything works fine except for one thing. For 4 months, 4 BSODs happened during playing BF4 and windows debug tool claims that it is the SynTp.sys that causes the problem. As far as I know it's the driver for the touch pad. So I updated the driver after the second BSOD, but guess what, it does not solve the problem at all. Has anyone encountered this problem? Also one thing worth highlighted is that BSOD only happens while playing BF4.

 

Have you tried removing the driver just to test?

 

It did not crash every time, just like once per month on average.
Anyway I'll uninstall the driver just in case.

 

Yes I have this similar issue. Occasionally a game will crash or the OS just while idling due to the synaptics driver.

 

You mentioned you purchased it last year, there have been new drivers posted on Jan 8, you may want to try those http://www.sagernotebook.com/drivers.php?cat=601

 

LOL the fail.. First time I've seen touchpad drivers cause BSOD's.. I always used to get BSOD's due to OCing my CPU too much.. never due to fail touchpad drivers

 

Exact same thing happening to me. Driver version 18.0.7.0 dated 1/9/14.

Looks like the official drivers are the same version. Synaptics site isn't much help.

 

Got the same problem. Had a random BSOD today, and I had no idea what could have caused it. Imagine my surprise when BlueScreenView pinned the blame on the Synaptic drivers, which SEEMED to have been working perfectly fine until today.

I gotta ask OP, or any of you guys in this thread, did the problem get resolved after removing the drivers?

 

I'm getting a driver power failure BSOD I thought it was my undervolt at first but it had nothing to do with it since it also crashed when I was also not undervolting. Any ideas?

 

Exact same problem here on P670SG, tried reformatting and BIOS updates, nothing helps.

If I uninstall the Touch driver it still BSODs and then blames HKKbdFltr.sys instead.

For me it never BSODs on desktop though, only ingame.

 

^ I see. I tried getting rid of the Synaptic drivers, but I couldn't deal with the loss in functionality so I reinstalled after a couple of days. Thanks for sticking with it and seeing if it solved the problem - which it apparently doesn't.

To be honest, I decided to just live with the BSODs. The crashes happen once every 3-4 weeks for me. It's not ideal, but it's not that common either.

 

Hey guys, same issue here. I've been talking to a user about this issue too. Random Syntp.sys bsods, and if i unistall synaptics i get the hkkbdfltr.sys one. Funny how both system files are related to keyboard or mouse. It's really hard to pin down the problem because it only happens like each week or so, really random.

 

Another thing to add, it only happens on CS GO to me (and once happened on GTA V). Weird thing, i played a lot of games for many hours and only CS GO showed that problem more than one time.

 

Anyone have any updates?

I thought it might have been related to static build up and was testing while having the laptop grounded via the USB port of an external sound card / amp, but seems not, I was barely 5 minutes into GTA 5 tonight, and BSOD.

 

What if you disable the touchpad and use a mouse? Does it still do a BSOD and pin the blame on something else?

 

Do you also get it during all games or just specific ones.

 

I always play with the touchpad disabled since my hand rests on it a bit, and use a mouse, it will still BSOD saying SynTP.sys
I then uninstalled the Touchpad driver, it still BSODs but just blames HKKbdFltr.sys instead.

It seems to happen in all games, all I have played are TF2, Far Cry 4, GTA 5 and X3 Albion Prelude, I have had BSODs in all except X3 but I haven't played X3 much.
It never BSODs on desktop.

 

Since it does it while gaming, have you tried updating the video card drivers to the newest ones directly from Nvidia?

 

Yes I'm already on the latest (353.06)

I've gone through everything I can think of, it's not overheating, already formatted Windows etc, but I'm not alone with this problem.
It's probably time for an RMA.

 

I RMA'd the laptop to a Clevo repair center, they replaced the entire mainboard.
No problems so far, will update again after using it for a while.

 

Barely 3 hours into my second night of playing, BSOD. This is really ******* me off now.
Obviously it wasn't the mainboard then and the repair center never bothered to test.

 

I have a P670SG with the exact same issues since the W10 upgrade. It does seem like a bad driver rather than hardware at this point.
Hope the problem gets resolved soon - I really don't want to have to downgrade to 8.1 again.

 

Are you sure it only started after the Windows 10 upgrade?
Did you upgrade only instead of a clean install?
Did you install the new Win10 drivers?

I have just done a clean install of Win10 with the new Win10 drivers, no BSOD......yet but I haven't
installed much except for basic stuff, to see if it makes a difference.

 

I had had literally zero BSODs for the three months while running 8.1, even with heavy gaming. I only saw the SynTP.sys BSOD for the very first time after upgrading to 10. As the OP had said though, it is not a frequent occurrence, and difficult to replicate reliably.

I have decided to try a fresh W10 install today, with new drivers on Sager's website - fingers crossed!

 

This is good news, it means it's probably software, not hardware. If you haven't already installed the drivers, I'd recommend installing chipset first, then synaptics, then the rest.
I haven't yet installed all the stuff I'd usually install, I'm keeping it basic to test for the moment.
Will update again after more gameplay.

 

I've got the same problem; BSODs from synaptics; it happens once every week or so. I have been using windows 8.1, it has BSOD on Witcher 3 and DAI. I have installed the newest drivers from the Sager website. However these drivers seem to be the same. Also I have RMA'd the same laptop after the power completely failed 2 days after a BSOD. Will update later with results. Is everyone here having problems with Win10 and the touchpad? Also has anyone found a solution yet?

 

Still no BSODs here yet since doing a clean install of Win10 + XMG Win10 drivers.
The XMG drivers are still newer than Sagers btw.

 

Guys what's the update?

For me it just BSOD tonight in the middle of CS:GO, at least a week and a half since I installed Windows 10, thought it was cured, then BSOD.
Same SynTP.sys as usual, there is no escape, no hope, no cure.

 

Does anyone have a BSOD memory dump of the crash? I think it's time to do some debugging instead of just reinstalling and swapping drivers.

 

No it seems CCleaner deleted it. But it's always due to SynTP.sys or hkkbdfltr.sys if you uninstall Syanptics drivers.
I'm gonna test again with the Touchpad totally uninstalled and not visible to Windows.

 

The memory dump will help in pinpointing what part of SynTP.sys or hkkbdflter.sys is crashing the OS. There have been cases where the crash of a kernel driver was caused by something other than the driver itself.

 

IxasCaelum has uploaded 2 dump files in this thread.

 

Since I uninstalled the synaptic touchpad driver, no BSOD has occured. However just tonight, another one was caused by hkkbdfltr.sys. . From my observation, everyone's BSODs are caused by exactly the same thing. It makes me wonder if it's this particular model of laptop or there are conflicting drivers.

 

Yes we are all experiencing the exact same thing.
I don't think the Synaptics drivers are the real cause because as you said it will still BSOD but blame something else (Hotkey)
The most confusing part of the entire situation is that it doesn't BSOD on desktop, never, which makes it look more software related than hardware.

Were you ingame when you got that hkkbdfltr.sys BSOD?

 

All my previous syntp.sys caused BSODs happened during playing BF4, all 6 times of them. The hkkbdfltr.sys one occured when I was playing CoD BO2 earlier tonight.
I'm running the latest Nvidia driver.

 

Same issue. Win 8.1 no BSOD ever. Win10 plenty of syntp.sys BSODs. I have not been gaming, but actually using the touchpad for some action, zoom, swipe etc.
Tried Synaptics 19.0.19.1 (Aug. 2015) and the one Win10 installed 19.0.13 (June 2015) I believe.

Never had the hkkbdfitr.sys BSOD though.

So anyone looked into the dumps?

 

Hi Guys,

Seems like I'm not alone with these stupid SynTP.sys BSODs. Did anyone find a solution for this problem? Did updating to Windows 10 solved the issue? In my case, I'm playing Pillars of Eternity, but also happened when playing Skyrim. So, it's very unlikely to be game related.

Regards,
Amid

 

Windows 10 doesn't cure it but the BSODs seem to be more rare for me on Win10 than Win8.1.
I have never BSOD on desktop, only in a game, I think everyone else is the same?

I have since installed the latest Synaptics drivers directly from the Syanptics site, no BSODs YET....

 

i have radom bsod too but no more since updated realtek sound driver

 

What driver version and from where?
The Realtek site directly?

 

from station driver which point to realtek ftp server

 

Well, I did that on the previous Windows 7 installation but didn't solve my problem. I've tried that because every time Windows Crashes, the "sound" get stuck in the last frequency being played.
Please update us if it really stopped happening (since it's rare, it could just be luck).

Thank you,
Amid

PS: Could you provide the exact link you used so that there is no misalignment with driver versions?

 

Do you have the Clevo P650SE or the P150EM?
My audio driver for Win10 from the XMG website is dated 15/07/2015, everything on the Realtek website is older, from June.

 

"sound" get stuck in the last frequency being played"
exactly the same before audio driver update
after update this happens less frequently and so far none of them cause bsod. just the sound stuck for maybe 0.3 sec and it returns to normal.
currently station driver seems closed for maintainence

 

Are you on the Clevo P170EM?

Anyway here's my current driver (XMG)

 

Yes p170em

 

In my case, I have a P9377SM-A but the problem is exactly the same. I was using the drivers published by Sager for Windows 7 then, due to the sound issue mentioned earlier and suspecting this could be issue, I went to Realtek website and downloaded the drivers from there. However, this didn't solve the problem for me. That's the reason I'd like to know the ones you are trying.
I have both Windows 7 and Windows 10 installed (just finished installing them both as a recommendation from Sager support) and have all the drivers published by them installed. Windows 7 seems a bit outdated but since I don't know if its drivers have some customization for the notebook, I decided to stay with them.
If I remember well, the version of the Realtek driver I installed was version 7 or something.

EDIT: My apologies, the version of drivers listed is not 7 but R2.79. They are located at this address: http://www.realtek.com/downloads/do...=24&Level=4&Conn=3&DownTypeID=3&GetDown=false
However, I can confirm that these, at least for Windows 7, don't solve the problem.

 

I've tried updating to latest Audio from Station Drivers but no help.
I BSOD on desktop for the first time ever a few nights ago while typing, it may be related to keyboard input, maybe a faulty keyboard?

Gonna have to RMA again.

 

I wouldnt RMA for 1 BSOD. It may be impossible to duplicate that and they will not know what needs to be repaired/replaced and they will send it back to you if that is the case. You can download a program called Whocrashed to try to get help with it. Often time BSOD are software/drivers and can be fixed by updating them.

 

So I ssemed to have solve my bsod problem that you guys are also having on windows 10.

Ate you guys undervolting? Reducing my UV to something more reasonable seems to have done the trick. But at the same time I also updated to the latest realtek drivers from the Eurocom website.

So one of those seems to have worked. Its been weeks and no bsods while gaming due to synaptics or hkey drivers.

I also would advise against rma'ing. Its definitely not a hardware low level issue. Its most likely a driver conflict with something in windows 10.