VirtualHere caught Abort signal

14 posts / 0 new
Last post
pmiller
VirtualHere caught Abort signal

Michael:

My application uses 4 serial ports and a USB sound adapter. Most of the time when I start my application it connects to a couple of the serial ports but then vhusbdpin aborts.
If I restart the PI I can usually connect and everything works fine.
Any information would be appreciated.
Thanks;

pi@raspberrypi ~ $ tail /var/log/syslog
Sep 16 02:02:47 raspberrypi kernel: [ 223.025600] usb 1-1.3.4: reset full-speed USB device number 9 using dwc_otg
Sep 16 02:02:47 raspberrypi vhusbdpin: Device 1134 BOUND to connection 1
Sep 16 02:02:47 raspberrypi kernel: [ 223.134524] cp210x ttyUSB3: cp210x converter now disconnected from ttyUSB3
Sep 16 02:02:47 raspberrypi kernel: [ 223.134660] cp210x 1-1.5:1.0: device disconnected
Sep 16 02:02:47 raspberrypi kernel: [ 223.215382] usb 1-1.5: reset full-speed USB device number 5 using dwc_otg
Sep 16 02:02:47 raspberrypi vhusbdpin: Device 115 BOUND to connection 1
Sep 16 02:03:48 raspberrypi vhusbdpin: VirtualHere caught Abort signal, backtrace follows:
Sep 16 02:03:48 raspberrypi vhusbdpin: [bt]: (1) /lib/arm-linux-gnueabihf/libc.so.6(gsignal+0x40) [0xb6ca2cdc]
Sep 16 02:03:48 raspberrypi vhusbdpin: [bt]: (2) /lib/arm-linux-gnueabihf/libc.so.6(gsignal+0x40) [0xb6ca2cdc]
Sep 16 02:03:48 raspberrypi vhusbdpin: Exiting

Michael
.

1. ssh to your raspberry pi
2. Make sure virtualhere server is not running
3. type: ulimit -c unlimited
4. type: wget http://www.virtualhere.com/sites/default/files/usbserver/pmiller/vhusbdpin
5. Type: chmod +x ./vhusbdpin
6. Type: sudo ./vhusbdpin -b
7. When it crashes it will write a "core" file to the current directory
8. Send me that core file and ill see whats going on.

pmiller
Michael:

Michael:

I tried to get the dump but I could not even get it to connect properly with that version of vhusbppin.
It seems like it would connect with only one device but I needed all of them so I had to enter the license to allow that. Once I did that the client would come up and then almost immediately vhusbppin would crash or windows would Blue Screen but it never created the core in those cases. I was not able to get to a point where I could start the application to test.

This was in syslog one of the times it crashed.
Sep 17 01:58:10 raspberrypi vhusbdpin: Device 1134 BOUND to connection 2
Sep 17 01:58:11 raspberrypi kernel: [82862.238095] ftdi_sio ttyUSB0: FTDI USB Serial Device converter now disconnected from ttyUSB0
Sep 17 01:58:11 raspberrypi kernel: [82862.238300] ftdi_sio 1-1.3.2:1.0: device disconnected
Sep 17 01:58:12 raspberrypi kernel: [82862.317043] usb 1-1.3.2: reset full-speed USB device number 7 using dwc_otg
Sep 17 01:58:12 raspberrypi vhusbdpin: Device 1132 BOUND to connection 2
Sep 17 01:58:39 raspberrypi vhusbdpin: VirtualHere crashed, backtrace...
Sep 17 01:58:39 raspberrypi vhusbdpin: [bt]: (1) ./vhusbdpin(findURBByEp+0x4) [0x1008c]
Sep 17 01:58:39 raspberrypi vhusbdpin: [bt]: (2) ./vhusbdpin(findURBByEp+0x4) [0x1008c]
Sep 17 01:58:40 raspberrypi vhusbdpin: [bt]: (3) ./vhusbdpin(list_operation+0x48) [0x1ea9c]
Sep 17 01:58:40 raspberrypi vhusbdpin: Exiting

Michael
.

It looks like the raspbian kernel is corrupting the data.I recompiled the server, could you download the virtualhere server again from the same place as in the last message and try again. Could you send me the stack trace. The stack trace in the last message above was very useful.

pmiller
Michael:

Michael:
Not sure how to get you the stack trace, here is the syslog when it crashed.

pi@raspberrypi ~ $ tail /var/log/syslog
Sep 18 01:30:16 raspberrypi vhusbdpin: Found Full speed device [0403:6001] "FTDI, FT232R USB UART" at address 1132
Sep 18 01:30:16 raspberrypi kernel: [78140.817122] usb 1-1.3.2: reset full-speed USB device number 12 using dwc_otg
Sep 18 01:30:16 raspberrypi vhusbdpin: Device 1132 BOUND to connection 2
Sep 18 01:32:02 raspberrypi vhusbdpin: VirtualHere caught Abort signal, backtrace follows:
Sep 18 01:32:02 raspberrypi vhusbdpin: [bt]: (1) /lib/arm-linux-gnueabihf/libc.so.6(gsignal+0x40) [0xb6ba4cdc]
Sep 18 01:32:02 raspberrypi vhusbdpin: VirtualHere crashed, backtrace...
Sep 18 01:32:02 raspberrypi vhusbdpin: [bt]: (1) ./vhusbdpin(processCtrlIsoReapedUrb+0x38) [0x13b80]
Sep 18 01:32:02 raspberrypi vhusbdpin: [bt]: (2) ./vhusbdpin(processCtrlIsoReapedUrb+0x38) [0x13b80]
Sep 18 01:32:02 raspberrypi vhusbdpin: [bt]: (3) ./vhusbdpin(reapUrbs+0xe0) [0x13d9c]
Sep 18 01:32:02 raspberrypi vhusbdpin: Exiting

Michael
OK its crashing in a

OK its crashing in a completely normal function so its definately a corruption issue in raspbian. Are you still getting those "dropped" packets message from the kernel like in the prevous post? Perhaps that is the cause

pmiller
Michael:

Michael:
When you say it is completely normal function, do you have any idea as to why this would happen or what would cause it. Basically all I did was start the application that opens the serial ports and vhusbdpin would crash.
The latest version you posted yesterday does seem more stable for me when the windows client connects.
I have not seen the dropped packet errors lately, I did another firmware update as you suggested and since that time I have not seem those errors.
This VM that I am testing with is using ProxMox as the hypervisor, I am not sure if there could be some strange things because of that. I run other VM's with no problem but this is a much different application. I could probably spin it up on VMware or Hyper-V and see if that makes any difference but that would probably be a couple weeks before I could get that set up and running.

Do you have any other ideas ?

Thanks;

Michael
Dont install in other vm

Dont install in other vm hypervisors as it wont make a difference.

What i changed in 1.9.1 was i made a particular call more closely fit the usb spec. But because of that bug in raspbian this change i made i think has triggered the issue.

Specifically the change is a call in usb to "CLEAR HALT". When this is made by the device there should not be any outstanding data request to the device at this point, so i cancel them whereas in previous versions i didnt.

However i think these outstanding data requests are jammed because of a bug in raspbian and "canceling" them corrupts the stack.

I will remove that change to put it back how it was, therefore those outstanding requests just disappear into the kernel never to return but the server wont crash. Thats my theory as to why the previous version worked but this one didnt. I will make this change in 1.9.2

Michael
OK 1.9.2 released

OK 1.9.2 released

pmiller
Michael:

Michael:
I wanted to change hypervisors anyway so I moved it to Hyper-V, as we suspected there was no difference.
I am running the latest version of client and server.
I have narrowed it down and I believe it happens when my application opens one specific serial port. This port is using the same USB-Serial converter as another port that works fine. Driver is also the same.
I tried to enable debug on the client to try and get some info but Windows crashes both when debug is turned off and also on. When I turned it off the blue screen was in vhhub.sys, I tried to get a print screen but for some reason I lost it.
Where is the debug file located, couldn't find it ?
Not sure what I can get for you, hopefully you have some ideas.
Thanks;

Michael
IF it shows vhusb.sys thats

IF it shows vhusb.sys thats my driver and a crash dump would be great...

What happens is that windows will reboot and then when it restarts it will say "Windows encoutered a problem do you want to send this to microsoft" at that point leave that dialog there (dont press ok or cancel), then bring up windows explorer and navigate to the c:\windows directory.

In there will be a file called MEMORY.DMP, send me that file (zip it first), or instead if its too big you can send the file in c:\Windows\Minidump\xxxx.dmp where xxx is the date the crash occured. That will provde a stack trace inside the driver...

pmiller
I downloaded BlueScreen View,

I downloaded BlueScreen View, it indicates wd01000, vhhub.sys is in the stack though. I just clicked on the debug in the client and windows blue screened. I sent you the mini dump if you have a chance to take a look.
This one I can look at later, which is most important for me is getting back to why vhusbdpin is crashing when I start the application. If you could let me know what the best way to get some trace or log to look at that, that would be appreciated.
Thanks;

092314-17656-01.dmp 23/09/2014 6:41:42 PM BAD_POOL_CALLER 0x000000c2 0x00000007 0x0000109b 0x081e0004 0x8698f700 Wdf01000.sys Wdf01000.sys+7e53 32-bit ntkrnlpa.exe+120c6b Wdf01000.sys+ba85 Wdf01000.sys+6ac9 Wdf01000.sys+6fc2 C:\Users\pmiller.OSGOODE\Desktop\092314-17656-01.dmp 1 15 7601 155,136 23/09/2014 6:43:16 PM

ntkrnlpa.exe ntkrnlpa.exe+12ad20 0x8281d000 0x82c30000 0x00413000 0x53158c8f 04/03/2014 4:19:27 AM
vhhub.sys vhhub.sys+f467aa4c 0x95709000 0x95718000 0x0000f000 0x541c03cf 19/09/2014 6:22:07 AM
Wdf01000.sys Wdf01000.sys+7e53 0x8863a000 0x886bb000 0x00081000 0x51c50c11 21/06/2013 10:29:37 PM
halmacpi.dll 0x82c30000 0x82c67000 0x00037000 0x4ce788d2 20/11/2010 4:37:38 AM
kdcom.dll 0x80ba5000 0x80bad000 0x00008000 0x4a5bdaaa 13/07/2009 9:08:58 PM
mcupdate_GenuineIntel.dll 0x82e3c000 0x82ec1000 0x00085000 0x4ce7b876 20/11/2010 8:00:54 AM
PSHED.dll 0x82ec1000 0x82ed2000 0x00011000 0x4a5bdad0 13/07/2009 9:09:36 PM
BOOTVID.dll 0x82ed2000 0x82eda000 0x00008000 0x4a5bd9a2 13/07/2009 9:04:34 PM
CLFS.SYS 0x82eda000 0x82f1c000 0x00042000 0x4a5bbf0e 13/07/2009 7:11:10 PM
CI.dll 0x82f1c000 0x82fc7000 0x000ab000 0x4ce7b97d 20/11/2010 8:05:17 AM
WDFLDR.SYS 0x886bb000 0x886c9000 0x0000e000 0x5010ad36 25/07/2012 10:36:38 PM
ACPI.sys 0x886c9000 0x88711000 0x00048000 0x4ce788e0 20/11/2010 4:37:52 AM
WMILIB.SYS 0x88711000 0x8871a000 0x00009000 0x4a5bbf1a 13/07/2009 7:11:22 PM
msisadrv.sys 0x8871a000 0x88722000 0x00008000 0x4a5bbf0d 13/07/2009 7:11:09 PM
pci.sys 0x88722000 0x8874c000 0x0002a000 0x4ce788e5 20/11/2010 4:37:57 AM
vdrvroot.sys 0x8874c000 0x88757000 0x0000b000 0x4a5bc74b 13/07/2009 7:46:19 PM
partmgr.sys 0x88757000 0x88768000 0x00011000 0x4f641b0c 17/03/2012 1:03:08 AM
volmgr.sys 0x88768000 0x88778000 0x00010000 0x4ce788ee 20/11/2010 4:38:06 AM
volmgrx.sys 0x88778000 0x887c3000 0x0004b000 0x4a5bbf2d 13/07/2009 7:11:41 PM
intelide.sys 0x887c3000 0x887ca000 0x00007000 0x4a5bbf17 13/07/2009 7:11:19 PM
PCIIDEX.SYS 0x887ca000 0x887d8000 0x0000e000 0x4a5bbf13 13/07/2009 7:11:15 PM
vmbus.sys 0x887d8000 0x887eaf00 0x00012f00 0x52158eb2 22/08/2013 12:08:18 AM
vmbkmcl.sys 0x887eb000 0x887f8a00 0x0000da00 0x52158f2e 22/08/2013 12:10:22 AM
winhv.sys 0x88600000 0x88614000 0x00014000 0x52158f70 22/08/2013 12:11:28 AM
mountmgr.sys 0x88614000 0x8862a000 0x00016000 0x4ce788f1 20/11/2010 4:38:09 AM
atapi.sys 0x8862a000 0x88633000 0x00009000 0x4a5bbf13 13/07/2009 7:11:15 PM
ataport.SYS 0x82fc7000 0x82fea000 0x00023000 0x51fef603 04/08/2013 8:46:59 PM
amdxata.sys 0x82fea000 0x82ff3000 0x00009000 0x4ba3a3f5 19/03/2010 12:19:01 PM
fltmgr.sys 0x82e00000 0x82e34000 0x00034000 0x4a5bbf11 13/07/2009 7:11:13 PM
fileinfo.sys 0x8882c000 0x8883d000 0x00011000 0x4a5bc18f 13/07/2009 7:21:51 PM
Ntfs.sys 0x8883d000 0x8896c000 0x0012f000 0x52e1bb56 23/01/2014 9:01:10 PM
msrpc.sys 0x8896c000 0x88997000 0x0002b000 0x4a5bbf3f 13/07/2009 7:11:59 PM
ksecdd.sys 0x88997000 0x889aa000 0x00013000 0x53488fb1 11/04/2014 8:58:25 PM
cng.sys 0x88a1b000 0x88a78000 0x0005d000 0x501946b4 01/08/2012 11:09:40 AM
storvsc.sys 0x88a78000 0x88a83000 0x0000b000 0x52158edd 22/08/2013 12:09:01 AM
storport.sys 0x88a83000 0x88acb000 0x00048000 0x52f03fa3 03/02/2014 9:17:23 PM
pcw.sys 0x88acb000 0x88ad9000 0x0000e000 0x4a5bbf0e 13/07/2009 7:11:10 PM
Fs_Rec.sys 0x88ad9000 0x88ae2000 0x00009000 0x4f4eeb36 29/02/2012 11:21:26 PM
ndis.sys 0x88ae2000 0x88b99000 0x000b7000 0x5034f1da 22/08/2012 10:51:06 AM
NETIO.SYS 0x88b99000 0x88bd7000 0x0003e000 0x5294718f 26/11/2013 6:01:51 AM
ksecpkg.sys 0x88bd7000 0x88bfd000 0x00026000 0x5348939e 11/04/2014 9:15:10 PM
tcpip.sys 0x88c27000 0x88d73000 0x0014c000 0x533f5805 04/04/2014 9:10:29 PM
fwpkclnt.sys 0x88d73000 0x88da4000 0x00031000 0x533f579b 04/04/2014 9:08:43 PM
vmstorfl.sys 0x88da4000 0x88dab400 0x00007400 0x52158ec2 22/08/2013 12:08:34 AM
volsnap.sys 0x88dac000 0x88deb000 0x0003f000 0x4ce788f5 20/11/2010 4:38:13 AM
spldr.sys 0x88deb000 0x88df3000 0x00008000 0x4a084ebb 11/05/2009 12:13:47 PM
rdyboost.sys 0x889aa000 0x889d7000 0x0002d000 0x4ce78e17 20/11/2010 5:00:07 AM
mup.sys 0x88c00000 0x88c10000 0x00010000 0x4a5bbfc6 13/07/2009 7:14:14 PM
hwpolicy.sys 0x88c10000 0x88c18000 0x00008000 0x4ce788cf 20/11/2010 4:37:35 AM
fvevol.sys 0x88e22000 0x88e54000 0x00032000 0x51009f61 23/01/2013 10:41:37 PM
disk.sys 0x88e54000 0x88e65000 0x00011000 0x4a5bbf20 13/07/2009 7:11:28 PM
CLASSPNP.SYS 0x88e65000 0x88e8a000 0x00025000 0x4a5bbf18 13/07/2009 7:11:20 PM
cdrom.sys 0x88ebc000 0x88edb000 0x0001f000 0x4ce788f1 20/11/2010 4:38:09 AM
Null.SYS 0x88edb000 0x88ee2000 0x00007000 0x4a5bbf10 13/07/2009 7:11:12 PM
Beep.SYS 0x88ee2000 0x88ee9000 0x00007000 0x4a5bc6fc 13/07/2009 7:45:00 PM
vga.sys 0x88ee9000 0x88ef5000 0x0000c000 0x4a5bc27e 13/07/2009 7:25:50 PM
VIDEOPRT.SYS 0x88ef5000 0x88f16000 0x00021000 0x4a5bc27d 13/07/2009 7:25:49 PM
watchdog.sys 0x88f16000 0x88f23000 0x0000d000 0x4a5bc21a 13/07/2009 7:24:10 PM
RDPCDD.sys 0x88f23000 0x88f2b000 0x00008000 0x4ce7a15b 20/11/2010 6:22:19 AM
rdpencdd.sys 0x88f2b000 0x88f33000 0x00008000 0x4a5bcae3 13/07/2009 8:01:39 PM
rdprefmp.sys 0x88f33000 0x88f3b000 0x00008000 0x4a5bcae5 13/07/2009 8:01:41 PM
Msfs.SYS 0x88f3b000 0x88f46000 0x0000b000 0x4a5bbf1e 13/07/2009 7:11:26 PM
Npfs.SYS 0x88f46000 0x88f54000 0x0000e000 0x4a5bbf23 13/07/2009 7:11:31 PM
tdx.sys 0x88f54000 0x88f6b000 0x00017000 0x4ce78935 20/11/2010 4:39:17 AM
TDI.SYS 0x88f6b000 0x88f77000 0x0000c000 0x4ce78936 20/11/2010 4:39:18 AM
afd.sys 0x88f77000 0x88fd1000 0x0005a000 0x538826d6 30/05/2014 2:36:06 AM
netbt.sys 0x8d238000 0x8d26a000 0x00032000 0x4ce7893a 20/11/2010 4:39:22 AM
wfplwf.sys 0x8d26a000 0x8d271000 0x00007000 0x4a5bc90f 13/07/2009 7:53:51 PM
pacer.sys 0x8d271000 0x8d290000 0x0001f000 0x4a5bc916 13/07/2009 7:53:58 PM
netbios.sys 0x8d290000 0x8d29e000 0x0000e000 0x4a5bc912 13/07/2009 7:53:54 PM
serial.sys 0x8d29e000 0x8d2b8000 0x0001a000 0x4a5bc71d 13/07/2009 7:45:33 PM
wanarp.sys 0x8d2b8000 0x8d2cb000 0x00013000 0x4ce79df1 20/11/2010 6:07:45 AM
termdd.sys 0x8d2cb000 0x8d2dc000 0x00011000 0x4ce7a116 20/11/2010 6:21:10 AM
rdbss.sys 0x8d2dc000 0x8d31d000 0x00041000 0x4ce78a04 20/11/2010 4:42:44 AM
nsiproxy.sys 0x8d31d000 0x8d327000 0x0000a000 0x4a5bbf48 13/07/2009 7:12:08 PM
mssmbios.sys 0x8d327000 0x8d331000 0x0000a000 0x4a5bc0fd 13/07/2009 7:19:25 PM
discache.sys 0x8d331000 0x8d33d000 0x0000c000 0x4a5bc214 13/07/2009 7:24:04 PM
csc.sys 0x8d33d000 0x8d3a1000 0x00064000 0x4ce78a70 20/11/2010 4:44:32 AM
dfsc.sys 0x8d3a1000 0x8d3b9000 0x00018000 0x4ce789f8 20/11/2010 4:42:32 AM
blbdrive.sys 0x8d3b9000 0x8d3c7000 0x0000e000 0x4a5bc1d8 13/07/2009 7:23:04 PM
tunnel.sys 0x8d3c7000 0x8d3e8000 0x00021000 0x4ce79db0 20/11/2010 6:06:40 AM
i8042prt.sys 0x8d3e8000 0x8d400000 0x00018000 0x4a5bbf1b 13/07/2009 7:11:23 PM
kbdclass.sys 0x8d200000 0x8d20d000 0x0000d000 0x4a5bbf13 13/07/2009 7:11:15 PM
mouclass.sys 0x8d20d000 0x8d21a000 0x0000d000 0x4a5bbf13 13/07/2009 7:11:15 PM
serenum.sys 0x8d21a000 0x8d224000 0x0000a000 0x4a5bc717 13/07/2009 7:45:27 PM
fdc.sys 0x8d224000 0x8d22f000 0x0000b000 0x4a5bc729 13/07/2009 7:45:45 PM
VMBusHID.sys 0x8d22f000 0x8d233780 0x00004780 0x52158edd 22/08/2013 12:09:01 AM
HIDCLASS.SYS 0x88fd1000 0x88fe4000 0x00013000 0x51d39c38 02/07/2013 11:36:24 PM
HIDPARSE.SYS 0x88fe4000 0x88fea480 0x00006480 0x51d39c36 02/07/2013 11:36:22 PM
hyperkbd.sys 0x8d234000 0x8d237180 0x00003180 0x52158ee5 22/08/2013 12:09:09 AM
VMBusVideoM.sys 0x88ff7000 0x88ffa880 0x00003880 0x52158f53 22/08/2013 12:10:59 AM
netvsc60.sys 0x88e00000 0x88e12000 0x00012000 0x52158eb1 22/08/2013 12:08:17 AM
vms3cap.sys 0x88e12000 0x88e13980 0x00001980 0x52158f15 22/08/2013 12:09:57 AM
intelppm.sys 0x88a00000 0x88a12000 0x00012000 0x4a5bbf07 13/07/2009 7:11:03 PM
vmgencounter.sys 0x88e14000 0x88e16b80 0x00002b80 0x52158f0e 22/08/2013 12:09:50 AM
CompositeBus.sys 0x88c18000 0x88c25000 0x0000d000 0x4ce799dd 20/11/2010 5:50:21 AM
AgileVpn.sys 0x889d7000 0x889e9000 0x00012000 0x4a5bc954 13/07/2009 7:55:00 PM
rasl2tp.sys 0x88800000 0x88818000 0x00018000 0x4a5bc939 13/07/2009 7:54:33 PM
ndistapi.sys 0x88e17000 0x88e22000 0x0000b000 0x4a5bc930 13/07/2009 7:54:24 PM
ndiswan.sys 0x95625000 0x95647000 0x00022000 0x4ce79df4 20/11/2010 6:07:48 AM
raspppoe.sys 0x95647000 0x9565f000 0x00018000 0x4a5bc94d 13/07/2009 7:54:53 PM
raspptp.sys 0x9565f000 0x95676000 0x00017000 0x4a5bc947 13/07/2009 7:54:47 PM
rassstp.sys 0x95676000 0x9568d000 0x00017000 0x4a5bc951 13/07/2009 7:54:57 PM
rdpbus.sys 0x9568d000 0x95697000 0x0000a000 0x4a5bcb20 13/07/2009 8:02:40 PM
swenum.sys 0x95697000 0x95698380 0x00001380 0x4a5bc704 13/07/2009 7:45:08 PM
ks.sys 0x95699000 0x956cd000 0x00034000 0x4ce799d9 20/11/2010 5:50:17 AM
umbus.sys 0x956cd000 0x956db000 0x0000e000 0x4ce79c37 20/11/2010 6:00:23 AM
vhhcd.sys 0x956db000 0x956e3000 0x00008000 0x541c03ca 19/09/2014 6:22:02 AM
flpydisk.sys 0x956e3000 0x956ed000 0x0000a000 0x4a5bc729 13/07/2009 7:45:45 PM
mouhid.sys 0x956ed000 0x956f8000 0x0000b000 0x4a5bc704 13/07/2009 7:45:08 PM
NDProxy.SYS 0x956f8000 0x95709000 0x00011000 0x4ce79deb 20/11/2010 6:07:39 AM
cdfs.sys 0x95718000 0x9572e000 0x00016000 0x4a5bbf12 13/07/2009 7:11:14 PM
win32k.sys 0x967a0000 0x969f2000 0x00252000 0x53f7e37f 22/08/2014 8:42:39 PM
Dxapi.sys 0x9572e000 0x95738000 0x0000a000 0x4a5bc265 13/07/2009 7:25:25 PM
crashdmp.sys 0x95738000 0x95745000 0x0000d000 0x4a5bc72e 13/07/2009 7:45:50 PM
dump_dumpata.sys 0x95745000 0x95750000 0x0000b000 0x4a5bbf14 13/07/2009 7:11:16 PM
dump_atapi.sys 0x95750000 0x95759000 0x00009000 0x4a5bbf13 13/07/2009 7:11:15 PM
dump_dumpfve.sys 0x95759000 0x9576a000 0x00011000 0x4a5bbf6f 13/07/2009 7:12:47 PM
dxg.sys 0x96600000 0x96617000 0x00017000 0x4a5bc264 13/07/2009 7:25:24 PM
TSDDD.dll 0x96630000 0x96639000 0x00009000 0x00000000
VMBusVideoD.dll 0x96660000 0x96664d00 0x00004d00 0x52158f9e 22/08/2013 12:12:14 AM
luafv.sys 0x9576a000 0x95785000 0x0001b000 0x4a5bc020 13/07/2009 7:15:44 PM
lltdio.sys 0x95785000 0x95795000 0x00010000 0x4a5bc8ee 13/07/2009 7:53:18 PM
rspndr.sys 0x95795000 0x957a8000 0x00013000 0x4a5bc8f0 13/07/2009 7:53:20 PM
HTTP.sys 0x98423000 0x984a8000 0x00085000 0x4ce78971 20/11/2010 4:40:17 AM
bowser.sys 0x984a8000 0x984c1000 0x00019000 0x4d649164 23/02/2011 12:47:32 AM
mpsdrv.sys 0x984c1000 0x984d3000 0x00012000 0x4a5bc8d4 13/07/2009 7:52:52 PM
mrxsmb.sys 0x984d3000 0x984f6000 0x00023000 0x4db77cb0 26/04/2011 10:17:20 PM
mrxsmb10.sys 0x984f6000 0x98531000 0x0003b000 0x4e17bd25 08/07/2011 10:29:57 PM
mrxsmb20.sys 0x98531000 0x9854c000 0x0001b000 0x4db77cb6 26/04/2011 10:17:26 PM
peauth.sys 0x98564000 0x985fb000 0x00097000 0x4a5bd2e0 13/07/2009 8:35:44 PM
secdrv.SYS 0x98400000 0x9840a000 0x0000a000 0x45080528 13/09/2006 9:18:32 AM
srvnet.sys 0x957a8000 0x957c9000 0x00021000 0x4dba2670 28/04/2011 10:46:08 PM
tcpipreg.sys 0x9840a000 0x98417000 0x0000d000 0x506c5801 03/10/2012 11:21:37 AM
srv2.sys 0x99a18000 0x99a68000 0x00050000 0x4dba2675 28/04/2011 10:46:13 PM
srv.sys 0x99a68000 0x99aba000 0x00052000 0x4dba2686 28/04/2011 10:46:30 PM
asyncmac.sys 0x99bad000 0x99bb6000 0x00009000 0x4a5bc946 13/07/2009 7:54:46 PM
ser2pl.sys 0x99aef000 0x99b18000 0x00029000 0x53edb768 15/08/2014 3:31:52 AM
ftdibus.sys 0x99b18000 0x99b29680 0x00011680 0x52e66660 27/01/2014 10:00:00 AM
USBD.SYS 0x99b2a000 0x99b2b780 0x00001780 0x5295473d 26/11/2013 9:13:33 PM
usbccgp.sys 0x99b2c000 0x99b43000 0x00017000 0x52954748 26/11/2013 9:13:44 PM
ftser2k.sys 0x99b43000 0x99b59000 0x00016000 0x52e66656 27/01/2014 9:59:50 AM
usbaudio.sys 0x99b59000 0x99b6cc00 0x00013c00 0x51dfd578 12/07/2013 6:07:52 AM
hidusb.sys 0x99b6d000 0x99b78000 0x0000b000 0x4ce79c0a 20/11/2010 5:59:38 AM

pmiller
Michael:

Michael:

Since I have changed the USB sound controller to a Logitech one and I also changed the hub at the same time everything has been working perfectly.
Thank you for all your help.

Michael
OK great im glad to hear that

OK great im glad to hear that, thanks for your feedback

Log in or register to post comments