New machine BSOD when going to sleep

[victorwol]

Hi! I got this new laptop, and 2 days ago started crashing while in sleep mode, like I close the lip, put it on the bag, go home and when I get there, it has crashed.

I would really appreciate is anyone here that knows how to read minidumps can take a look and tell me if have any ideas of what is going on.

Thanks a lot!

Victor

 

[TorrentG]

Hello and welcome to the site!

Yup, you have a driver that is causing inconsistent power states, which is responsible for your issues.

1) Uninstall your old Portrait Displays software to remove this very old, problematic driver:

PdiPorts PdiPorts.sys Thu Nov 16 19:31:16 2006

2) Visit your laptop manufacturer's website for your model to download and install the latest Intel Matrix Storage Manager driver to update this old one:

iaStor iaStor.sys Wed Feb 11 20:24:30 2009

3) Install this Microsoft patch to update this other driver related:

http://support.microsoft.com/hotfix/KBHotfix.aspx?kbnum=982018&kbln=en-us

iaStorV iaStorV.sys Wed Apr 08 12:57:17 2009

---------

Enjoy the laptop!

 

[TorrentG]

While at laptop manufacturer's site, also download and install the latest NEC 3.0 USB driver to update this one, for good measure:

nusb3xhc nusb3xhc.sys Thu Jan 21 22:22:21 2010

 

[victorwol]

wow!!!!!! that was FAST!!!!!! thanks for the suggestions,

just out of curiosity and because I'm a total nerd ))) what are you using to read the minidump files?

And how can I find which program is using that PdiPorts.sys, I have not isntalled such a program on purpose.

Again... thanks!!!

 

[victorwol]

Grrrrr!!!!!! you answer so fast and I forgot the power brick om my machine at the office... can't do it till tomorrow morning..... that beast runs on battery for only 30 minutes.... Sager 7280....

 

[TorrentG]

I posted above It's for Portrait Displays. If you don't know what to uninstall, then simply go to C:\Windows\System32\drivers and delete PdiPorts.sys.

Reboot and run Ccleaner to clean the registry.

---------

I use WinDbg. None of what I said above or related is clearly shown at all. It's all based on experience I have and previous knowledge.

It is only in about 3-5% of bsod that the actual cause is clearly shown in plain view. Yours was not part of this percentage. WinDbg also has a little bit of a learning curve, but if you are interested in this kind of thing, you're welcome to ask any questions you may have about it. You could also review the many threads in the bsod section.

Here are some excellent resources that would be very helpful if you'd like to learn about the bsods and WinDbg usage:

Getting started: http://www.sevenforums.com/crash-lockup-debug-how/26584-configuring-debugging-tools.html

Other related link: http://www.sevenforums.com/crash-lockup-debug-how/


-----

Very welcome. Let us know how it goes after you do the above fixes. Very likely there will be no more crashes, but please post them if there are.

 

[victorwol]

thanks a lot! It is very interesting, always wanted to understand how to do that, will give it a read and let you suggestions fix the problem