0x0000004 BSOD often w7 64bit new install

[j0llyr0ger]

hi folks!

i am experiencing a BSOD many times a day on a HP Pavillion g6 laptop. i have done a new install of win7 pro 64.

i have done all the ms updates, checked the hard drive, memcheck, etc. i cant figure out the culprit, although i suspect a driver.

I am currently running in test mode so i can use unsigned drivers like com0com, but this has nothing to do with it, as that is a recent change, and system has been doing this before that.

if someone could please look at my diagnostic files and let me know what driver is causing the BSOD i would very much appreciate it!

thanks in advance.

 

[Arc]

Hi j0llyr0ger.

The bugcheck codes are different, but the cause is the same, USB-to-Serial Cable Driver.

[COLOR=Red]BugCheck D1[/COLOR], {38, 2, 1, fffff88000e9bd57}

*** WARNING: Unable to verify timestamp for ser2pl64.sys
*** ERROR: Module load completed but symbols could not be loaded for ser2pl64.sys
Probably caused by : [URL="http://www.carrona.org/drivers/driver.php?id=ser2pl64.sys"]ser2pl64.sys [/URL]( ser2pl64+ee1c )

Followup: MachineOwner
---------

[COLOR=Red]BugCheck 44[/COLOR], {fffffa8003d8e010, eae, 0, 0}

*** WARNING: Unable to verify timestamp for ser2pl64.sys
*** ERROR: Module load completed but symbols could not be loaded for ser2pl64.sys
Probably caused by : [URL="http://www.sevenforums.com/BugCheck 44, {fffffa8003d8e010, eae, 0, 0}  *** WARNING: Unable to verify timestamp for ser2pl64.sys *** ERROR: Module load completed but symbols could not be loaded for ser2pl64.sys Probably caused by : ser2pl64.sys ( ser2pl64+ee1c )  Followup: MachineOwner ---------"]ser2pl64.sys[/URL] ( ser2pl64+ee1c )

Followup: MachineOwner
---------

And the driver is not any old at all.

fffff880`07400000 fffff880`07431000   ser2pl64 T (no symbols)           
    Loaded symbol image file: ser2pl64.sys
    Image path: \SystemRoot\system32\DRIVERS\ser2pl64.sys
[COLOR=Red]    Image name: ser2pl64.sys
    Timestamp:        Thu Oct 17 16:32:48 2013[/COLOR] (525FC3D8)
    CheckSum:         00032052
    ImageSize:        00031000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

In this situation, I would suggest you to not use Prolific Serial port WDF driver (c:\windows\system32\drivers\ser2pl64.sys). Uninstall it.

Let us know the results.

 

[j0llyr0ger]

Thanks, Archie. I removed that driver, and found an older one on the Prolific site. Unfortunately the BSOD persists. I would hate to have to scrap the adapter, it's a 4 port serial adapter that I have used successfully on multiple computers. But I think Win 7 has a serious issue with it. (at least the 64 bit version) Any ideas? The original driver I was running was actually provided by WIndows Update during installation, and as you said, it's not old at all. But I can't find a more recent driver, and the 2009 version crashes as well.
I definitely have to blame Microsoft for this one, as it's worked great on multiple computers with many OS (except w764)

Thanks for your help!

 

[Arc]

Sorry mate, I dont have any clear perception about the Prolific drivers.

What is the situation visible in the crash dump, you should remove that driver, at least on a test basis.