BSOD i think prolific usb to serial

[vadim7ti]

Hello
Some time ago I started to get BSOD.
I am almost sure part of them related to Prolific USB to serial i start to use.
But i am afraid latest 2 are of some other origin.

I tried different Prolific drivers, some of them do not start to work at all.

SF_vadim7ti.zip (840.4 KB)

Any help would be greatly appreciated!

 

[Northernsoul55]

Hi,

From your crash dumps:

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 10D, {4, 0, fffff880024316a0, fffffa80094f2500}
Unable to load image \SystemRoot\system32\DRIVERS\ser2pl64.sys, Win32 error 0n2
*** 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+86a0 )
Followup: MachineOwner
---------

Your lastest crashes confirm your Prolific Serial Port Driver (ser2pl64.sys) is probably
contributing to your BSOD's
Relates to: USB-to-Serial Cable Driver/GembirdUAS112
I suggest uninstalling from your system and reboot, see if issue remains?

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {ffffffffffffffe8, 2, 0, fffff88000e5a899}
Probably caused by : Wdf01000.sys ( Wdf01000!FxIoQueue:rocessPowerEvents+169 )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.

STOP 0x0000010D: WDF_VIOLATION
Usual causes: Device driver, ?Memory

Driver: Wdf01000.sys Probably not the real cause.

Relates to: WDF Dynamic - Kernel Mode Driver Framework Runtime

All I can suggest for that is to ensure you have all the latest Windows updates installed.

Driver causing issues:

fffff880`009f1828 fffff880`059bab70Unable to load image akshasp.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for akshasp.sys
*** ERROR: Module load completed but symbols could not be loaded for akshasp.sys
akshasp akshasp.sys Mon Feb 02 15:47:42 2009

Refers to: AksFridge driver (Aladdin security products)
Update your drivers here:

:ar: http://www.safenet-inc.com/technical-support/

I would also suggest you remove Spybot-Search and Destroy from your system and then run:
Run SFC to check the integrity of all Windows 7 system files:

Click on the Start > Type in search cmd
Right click cmd at top and Run as Administrator
Type SFC /scannow at the prompt
(Note: there is a space between SFC and /scannow)

:ar: http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

Take memtest. Run for 8 passes and test each stick in a know good slot for an additional 6 passes.
:ar: http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

   Tip

Run these tests overnight

Post back any results/observations.
Cheers
Dave