Page 1 of 1

BSOD issue with T420.

Posted: Sat Jul 16, 2011 10:04 am
by blackomegax
Summary: If system is placed into standby, and then an android phone plugged in to the yellow USB port to charge while the laptop is in standby, and then the laptop is brought up and logged in, the system will very quicky BSOD something about the USB hub.

I figure it's just something to do with windows being surprised by a new device for failing to receive USB init signals (or likewise, the phone forgets to send them, having thought itself already plugged in for long enough)

Systeminfo: win7 enterprise 64bit, T420+nvidia, Intel SSD. Rest is stock.

Re: BSOD issue with T420.

Posted: Sat Jul 16, 2011 11:12 am
by Colonel O'Neill
What's the setting for Always on USB in Power Manager?
Does it help if you choose Android device or generic USB device?

Re: BSOD issue with T420.

Posted: Sun Jul 17, 2011 3:39 pm
by blackomegax
Always on USB is enabled, which is the root of the problem. It only happens when i plug a phone in charge while the system is in standby.
The phone is set to charge only, NOT storage or tether (HTC Evo+stock rooted fw)

Re: BSOD issue with T420.

Posted: Sun Jul 17, 2011 6:19 pm
by smh
It seems that it is a Windows problem. Try the following:
1) Disable the "Always on USB"
2) Restart your computer
3) Enter Standby
4) Plug in your phone, in the same USB port you used when the "Always on USB" was enabled
5) Exit Standby

See what happens. If you get BSOD then it is definitely the communication between Windows and phone that causes the crash, if not then try disabling your phone's USB data transfer (don't know if your phone has this, my blackberry has an option that says "Charge only" when connected to USB data cable) and enable the "Always on USB" and see what happens.

Re: BSOD issue with T420.

Posted: Mon Jul 18, 2011 12:04 pm
by blackomegax
Again: the phone is in charge-only mode, which has as little data communication as possible.
And the entire point is that i need always-on USB for charging things, and it won't do that when it's off. Which WOULD fix the bsod, but defeat the purpose.