USB to Serial for Digital Multimeter - Windows 7 x64 BSOD

Mutant Platypus · Dec 30, 2012

[SOLVED] USB to Serial for Digital Multimeter - Windows 7 x64 BSOD

Hello! I'm trying to run some digital multimeter display software. (The name in the Add/Remove Programs list is "72-9380 Interface Program ver 3.00", the executable is named "TENMA72_9380.exe") It seems to be a USB-to-serial device. It works in safe mode, but not in a normal boot. It always causes a BSOD - whether or not the multimeter is connected - and the most recent BSOD should be from the multimeter display program(SYSTEM_SERVICE_EXCEPTION or something like it). There may be other BSOD reports that are unrelated, sporadic, and predate the installation of the multimeter software. If you would like to address those, I would appreciate it, but I'll make another thread if they become a problem and I can figure out how to get them to occur on demand.

If you're curious, the DMM display software can be had here (downloaded from the product page).

· Current OS - Windows 7 Professional x64
· full retail version (YOU purchased it from retailer)
· Pre-installed OS: Windows 7 Home x64
· Hardware age: 2 years
· OS age: 1 year

· Intel Core i7-2820QM @2.3GHz
· Radeon HD 6850M

· HP Envy 17 2100-cto

As an aside: I have the option to automatically reboot from a system failure (System Properties > Startup and Recover > Settings) turned on, but my system doesn't. It just stays on the BSOD indefinitely. I'd like to get that working so I can use remote desktop software after a crash. If this a complicated issue then don't answer it here, I'll post it in another thread.

Thanks!

usasma · Dec 30, 2012

The WER section of MSINFO32 shows a number of errors blamed on vsserv.exe - This is a core component of the Bull Guard Internet Security suite, as well as the BitDefender AntiVirus package. There are also a lot of STOP 0x117 errors - but these seem to have been going on for longer than the one's with vsserv.exe.

Daemon Tools (and Alcohol % software) are known to cause BSOD's on some Win7 systems (mostly due to the sptd.sys driver, although I have seen dtsoftbus01.sys blamed on several occasions). I strongly suspect that this hold true for Win8 systems also.

Please un-install the program, then use the following free tool to ensure that the troublesome sptd.sys driver is removed from your system (pick the 32 or 64 bit system depending on your system's configuration): ~~DuplexSecure - FAQ~~ Link broken as of 21 Jul 2012
New link (15 Aug 2012): DuplexSecure - Downloads (pick the appropriate version for your system and select "Un-install" when you run it).
Alternate link: Disc-Tools.com
Manual procedure here: Registry and SPTD problems | DAEMON Pro Help

Your TeamViewer drivers date from 2007 - please remove that program immediately
Your Western Digital drivers date from 2008 and are known to cause BSOD's - please remove the Western Digital software also
Your USB 3.0 drivers date from 2010 and are known to cause BSOD's - please update to the 2011/2012 version.

The memory dumps are suggestive of either the vsserv.exe error or issues with your IVT Corporation BlueSolei Bluetooth software. Please uninstall the Bluetooth software. If needed, then download and install a fresh copy of the latest, Win7 compatible version available from the BlueSolei website.

Other suggestions:
- remove BitDefender and install a fresh copy
- scan for virus' Free scans listed here: Free Online AntiMalware Resources

Please update these older drivers. Links are included to assist in looking up the source of the drivers. If unable to find an update, please remove (un-install) the program responsible for that driver. DO NOT manually delete/rename the driver as it may make the system unbootable! :

teamviewervpn.sys Thu Dec 13 04:22:09 2007 (4760F9C1)
TeamViewerVPN Network Adapter
http://www.carrona.org/drivers/driver.php?id=teamviewervpn.sys

wdcsam64.sys Wed Apr 16 04:39:08 2008 (4805BB2C)
Western Digital SCSI Arcitecture Model (SAM) WDM driver
2008 driver version has known BSOD issues in Win7
http://www.carrona.org/drivers/driver.php?id=wdcsam64.sys

nusb3xhc.sys Thu Dec 9 23:50:35 2010 (4D01B19B)
NEC Electronics USB 3.0 Host Controller Driver (previous BSOD issues with 2010 version)
http://www.carrona.org/drivers/driver.php?id=nusb3xhc.sys

nusb3hub.sys Thu Dec 9 23:50:35 2010 (4D01B19B)
NEC Electronics USB 3.0 Host Controller Driver (previous BSOD issues with 2010 version)
http://www.carrona.org/drivers/driver.php?id=nusb3hub.sys

dtsoftbus01.sys Fri Jan 13 08:45:46 2012 (4F10358A)
Daemon Tools driver
Possible BSOD issues in Win7
http://www.carrona.org/drivers/driver.php?id=dtsoftbus01.sys

Analysis:
The following is for informational purposes only.

Code:

**************************Sun Dec 30 15:10:26.914 2012 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\123012-18096-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime:0 days 0:05:50.272
*** WARNING: Unable to verify timestamp for VHIDMini.sys
*** ERROR: Module load completed but symbols could not be loaded for VHIDMini.sys
Probably caused by :VHIDMini.sys ( VHIDMini+f35 )
BugCheck 3B, {c0000005, fffff800032b9221, fffff8800d47ac50, 0}
BugCheck Info: SYSTEM_SERVICE_EXCEPTION (3b)
Arguments: 
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff800032b9221, Address of the instruction which caused the bugcheck
Arg3: fffff8800d47ac50, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
BUGCHECK_STR:  0x3B
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME: BlueSoleilCS.e
FAILURE_BUCKET_ID: X64_0x3B_VHIDMini+f35
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Wed Dec 26 23:49:18.972 2012 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\122712-15568-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime:0 days 1:06:19.846
Probably caused by :ntkrnlmp.exe ( nt!KiSystemServiceExit+245 )
BugCheck 4A, {7732138a, 2, 0, fffff8800ddd4b60}
BugCheck Info: IRQL_GT_ZERO_AT_SYSTEM_SERVICE (4a)
Arguments: 
Arg1: 000000007732138a, Address of system function (system call routine)
Arg2: 0000000000000002, Current IRQL
Arg3: 0000000000000000, 0
Arg4: fffff8800ddd4b60, 0
PROCESS_NAME: vsserv.exe
BUGCHECK_STR:  RAISED_IRQL_FAULT
FAILURE_BUCKET_ID: X64_RAISED_IRQL_FAULT_vsserv.exe_nt!KiSystemServiceExit+245
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Wed Dec 26 20:34:11.832 2012 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\122612-16036-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime:0 days 2:26:47.190
Probably caused by :ntkrnlmp.exe ( nt!KiSystemServiceExit+245 )
BugCheck 4A, {77b4138a, 2, 0, fffff8800d74ab60}
BugCheck Info: IRQL_GT_ZERO_AT_SYSTEM_SERVICE (4a)
Arguments: 
Arg1: 0000000077b4138a, Address of system function (system call routine)
Arg2: 0000000000000002, Current IRQL
Arg3: 0000000000000000, 0
Arg4: fffff8800d74ab60, 0
PROCESS_NAME: vsserv.exe
BUGCHECK_STR:  RAISED_IRQL_FAULT
FAILURE_BUCKET_ID: X64_RAISED_IRQL_FAULT_vsserv.exe_nt!KiSystemServiceExit+245
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Wed Dec 26 18:06:02.265 2012 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\122612-18548-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime:0 days 22:04:37.139
Probably caused by :memory_corruption ( nt!MmUnlockPages+11 )
BugCheck 3B, {c0000005, fffff80003304221, fffff88005dc1c50, 0}
BugCheck Info: SYSTEM_SERVICE_EXCEPTION (3b)
Arguments: 
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff80003304221, Address of the instruction which caused the bugcheck
Arg3: fffff88005dc1c50, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
BUGCHECK_STR:  0x3B
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME: BlueSoleilCS.e
FAILURE_BUCKET_ID: X64_0x3B_nt!MmUnlockPages+11
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Tue Dec 25 19:31:59.570 2012 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\122512-16239-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime:0 days 0:04:24.444
Probably caused by :memory_corruption ( nt!MmUnlockPages+11 )
BugCheck 3B, {c0000005, fffff800032fc221, fffff8800d618c50, 0}
BugCheck Info: SYSTEM_SERVICE_EXCEPTION (3b)
Arguments: 
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff800032fc221, Address of the instruction which caused the bugcheck
Arg3: fffff8800d618c50, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
BUGCHECK_STR:  0x3B
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME: BlueSoleilCS.e
FAILURE_BUCKET_ID: X64_0x3B_nt!MmUnlockPages+11
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Tue Dec 25 19:19:04.592 2012 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\122512-17284-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime:0 days 0:23:19.950
Probably caused by :memory_corruption ( nt!MmUnlockPages+11 )
BugCheck 3B, {c0000005, fffff800032a3221, fffff8800caa7c50, 0}
BugCheck Info: SYSTEM_SERVICE_EXCEPTION (3b)
Arguments: 
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff800032a3221, Address of the instruction which caused the bugcheck
Arg3: fffff8800caa7c50, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
BUGCHECK_STR:  0x3B
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME: BlueSoleilCS.e
FAILURE_BUCKET_ID: X64_0x3B_nt!MmUnlockPages+11
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Tue Dec 25 18:54:10.191 2012 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\122512-16395-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime:0 days 0:08:34.549
Probably caused by :memory_corruption ( nt!MmUnlockPages+11 )
BugCheck 3B, {c0000005, fffff800032b1221, fffff8800d71ec50, 0}
BugCheck Info: SYSTEM_SERVICE_EXCEPTION (3b)
Arguments: 
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff800032b1221, Address of the instruction which caused the bugcheck
Arg3: fffff8800d71ec50, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
BUGCHECK_STR:  0x3B
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME: BlueSoleilCS.e
FAILURE_BUCKET_ID: X64_0x3B_nt!MmUnlockPages+11
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Tue Dec 25 18:44:08.874 2012 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\122512-26161-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime:0 days 0:12:21.232
Probably caused by :memory_corruption ( nt!MmUnlockPages+11 )
BugCheck 3B, {c0000005, fffff800032e5221, fffff8800e21fc50, 0}
BugCheck Info: SYSTEM_SERVICE_EXCEPTION (3b)
Arguments: 
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff800032e5221, Address of the instruction which caused the bugcheck
Arg3: fffff8800e21fc50, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
BUGCHECK_STR:  0x3B
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME: BlueSoleilCS.e
FAILURE_BUCKET_ID: X64_0x3B_nt!MmUnlockPages+11
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Tue Dec 25 18:15:58.164 2012 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\122512-22776-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime:1 days 20:28:32.038
Probably caused by :ntkrnlmp.exe ( nt!KiSystemServiceExit+245 )
BugCheck 4A, {772e138a, 2, 0, fffff88021313b60}
BugCheck Info: IRQL_GT_ZERO_AT_SYSTEM_SERVICE (4a)
Arguments: 
Arg1: 00000000772e138a, Address of system function (system call routine)
Arg2: 0000000000000002, Current IRQL
Arg3: 0000000000000000, 0
Arg4: fffff88021313b60, 0
PROCESS_NAME: vsserv.exe
BUGCHECK_STR:  RAISED_IRQL_FAULT
FAILURE_BUCKET_ID: X64_RAISED_IRQL_FAULT_vsserv.exe_nt!KiSystemServiceExit+245
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

3rd Party Drivers:
The following is for information purposes only.
Any drivers in red should be updated or removed from your system. And should have been discussed in the body of my post.

Code:

**************************Sun Dec 30 15:10:26.914 2012 (UTC - 5:00)**************************
teamviewervpn.sys           Thu Dec 13 04:22:09 2007 (4760F9C1)
intelppm.sys                Mon Jul 13 19:19:25 2009 (4A5BC0FD)
amdxata.sys                 Fri Mar 19 12:18:18 2010 (4BA3A3CA)
IvtBtBus.sys                Tue Apr  6 06:31:35 2010 (4BBB0D87)
AtiHdmi.sys                 Thu May  6 05:20:39 2010 (4BE289E7)
iaStorV.sys                 Thu Jun 10 20:46:19 2010 (4C11875B)
IntcDAud.sys                Fri Oct 15 04:28:17 2010 (4CB810A1)
HECIx64.sys                 Tue Oct 19 19:33:43 2010 (4CBE2AD7)
rikvm_38F51D56.sys          Fri Oct 29 06:52:09 2010 (4CCAA759)
nusb3hub.sys                Thu Dec  9 23:50:35 2010 (4D01B19B)
nusb3xhc.sys                Thu Dec  9 23:50:35 2010 (4D01B19B)
NETwNs64.sys                Tue Jan  4 14:29:41 2011 (4D237525)
igdpmd64.sys                Thu Jan 27 11:57:05 2011 (4D41A3E1)
stwrt64.sys                 Fri Mar  4 05:11:30 2011 (4D70BAD2)
atikmpag.sys                Thu Mar 31 04:50:49 2011 (4D944069)
atikmdag.sys                Thu Mar 31 05:17:25 2011 (4D9446A5)
Accelerometer.sys           Fri May 13 14:47:02 2011 (4DCD7CA6)
hpdskflt.sys                Fri May 13 14:47:02 2011 (4DCD7CA6)
btcomport.sys               Tue Jul 26 22:23:37 2011 (4E2F76A9)
btcombus.sys                Tue Jul 26 22:23:41 2011 (4E2F76AD)
VHIDMini.sys                Tue Jul 26 22:23:59 2011 (4E2F76BF)
LHidFilt.Sys                Fri Sep  2 02:23:09 2011 (4E60764D)
LMouFilt.Sys                Fri Sep  2 02:23:15 2011 (4E607653)
SynTP.sys                   Thu Oct 13 22:34:52 2011 (4E979FCC)
iaStor.sys                  Mon Oct 17 18:54:08 2011 (4E9CB210)
bdfwfpf.sys                 Mon Nov 14 12:16:17 2011 (4EC14CE1)
BtHidBus.sys                Wed Dec 21 01:45:23 2011 (4EF18083)
btnetdrv.sys                Wed Dec 21 01:45:48 2011 (4EF1809C)
btnetBus.sys                Wed Dec 21 01:45:52 2011 (4EF180A0)
btcusb.sys                  Mon Dec 26 21:16:58 2011 (4EF92A9A)
dtsoftbus01.sys             Fri Jan 13 08:45:46 2012 (4F10358A)
DKDFM.sys                   Thu Apr  5 05:32:02 2012 (4F7D6692)
Rt64win7.sys                Wed Apr 11 12:29:16 2012 (4F85B15C)
bdfndisf6.sys               Mon Jun 18 07:55:01 2012 (4FDF1715)
DKRtWrt.sys                 Mon Jun 18 22:13:42 2012 (4FDFE056)
DKTLFSMF.sys                Mon Jul  9 17:54:13 2012 (4FFB5305)
clwvd.sys                   Fri Aug  3 06:49:15 2012 (501BACAB)
gzflt.sys                   Wed Aug 29 10:52:43 2012 (503E2CBB)
trufos.sys                  Fri Sep  7 10:08:07 2012 (5049FFC7)
avc3.sys                    Thu Oct  4 11:23:55 2012 (506DAA0B)
avckf.sys                   Thu Oct  4 11:28:03 2012 (506DAB03)
avchv.sys                   Wed Oct 31 13:05:22 2012 (50915A52)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Wed Dec 26 23:49:18.972 2012 (UTC - 5:00)**************************
wdcsam64.sys                Wed Apr 16 04:39:08 2008 (4805BB2C)

Mutant Platypus · Dec 31, 2012

That fixed it! I bet it was BlueSoleil, as that was the only thing using serial ports.

The only thing I would add here is that the Renesas USB 3.0 Host Controller drivers are the most recent offered by my vendor and I couldn't find them on the Renesas web site (like your note on the driver page says, it may take a lot of research. Renesas specifically says they don't offer end-user support for USB controllers. My vendor (HP) dates the most recent installer for their USB 3.0 drivers as being from 2011, but I wouldn't be surprised if they haven't kept up.

As a side note, I was having trouble getting my network adapters to use IPv6 even though other computers on my network were doing fine. That TeamViewer VPN adapter must have been the culprit.

I've posted a new report here. If you like, could you offer alerts about old/known-issue drivers? I think I updated or uninstalled all of them, but I'm not sure. It looks like the reports are procedurally generated and compared against your database of drivers; is there a site where I can just submit the reports without taking your time?

jcgriff2 · Dec 31, 2012

Hi -

The next best tool to usasma's ability to spot drivers is Driver Verifier.

Run - https://www.sysnative.com/forums/bs...river-verifier-blue-screen-death-related.html

Regards. . .

jcgriff2

`

Mutant Platypus · Dec 31, 2012

jcgriff2 said:
Hi -

The next best tool to usasma's ability to spot drivers is Driver Verifier.

Run - https://www.sysnative.com/forums/bs...river-verifier-blue-screen-death-related.html

Regards. . .

jcgriff2

`

Really? He just keeps them all in his head? Or he just "Ctrl-F"s them on his DRT? Amazing. Then I wouldn't ask for his help in just making sure my drivers are up to date, as I haven't had any BSODs since uninstalling or updating the drivers he mentioned. I'll give the Verifier a try, though.

I submitted the Diskeeper drivers to your DRT, too. I didn't see that "Hex Date Conversion" link in your sig, but can you just get that info from the reports I submitted?

jcgriff2 · Dec 31, 2012

Hex date is no longer used as it's based on time zone.

I still suggest running Driver - https://www.sysnative.com/forums/bs...river-verifier-blue-screen-death-related.html

usasma and I are good with drivers, but Driver Verifier "stress tests" 3rd part driver and will force a BSOD if a driver is flagged.

Regards. . .

jcgriff2

`

Search

Search

USB to Serial for Digital Multimeter - Windows 7 x64 BSOD

Mutant Platypus

New member

usasma

Retired Admin

Mutant Platypus

New member

jcgriff2

Co-Founder / Admin
BSOD Instructor/Expert
Microsoft MVP (Ret.)

Mutant Platypus

New member

jcgriff2

Co-Founder / Admin
BSOD Instructor/Expert
Microsoft MVP (Ret.)

USB to Serial for Digital Multimeter - Windows 7 x64 BSOD

Mutant Platypus

New member

usasma

Retired Admin

Mutant Platypus

New member

jcgriff2

Co-Founder / AdminBSOD Instructor/ExpertMicrosoft MVP (Ret.)

Mutant Platypus

New member

jcgriff2

Co-Founder / AdminBSOD Instructor/ExpertMicrosoft MVP (Ret.)

Co-Founder / Admin
BSOD Instructor/Expert
Microsoft MVP (Ret.)

Co-Founder / Admin
BSOD Instructor/Expert
Microsoft MVP (Ret.)