Windows 7 In Need of BSOD Diagnosing

[ProWreck]

This BSOD has been plauging since I began using my ethernet cable. I got a wireless adapter, and stopped using it, and got maybe two bluescreens and then it stopped. Now im using my ethernet cable and again my rig is getting bsod's more often. I have updated my drivers, and everything. Not sure what it could be.

Here are a few of my minidumps.

 

[jcgriff2]

Hi -

The issue with your Ethernet could be the driver -

[FONT=lucida console]
RTL8192su.sys               Wed Nov 11 03:54:46 2009 (4AFA7BD6) - Realtek USB wifi
Rt64win7.sys                Thu Oct 25 05:20:09 2012 (50890449) - Realtek Ethernet
[/FONT]

http://www.sysnative.com/drivers/driver.php?id=RTL8192su.sys
http://www.sysnative.com/drivers/driver.php?id=Rt64win7.sys

Update with Jan 2013 driver - Link Removed

Unplug & disable the USB wifi; use Ethernet only. The USB wifi driver is loading into RAM, eventhough it is not being used.

Regards. . .

jcgriff2


BSOD SUMMARY

[font=lucida console]
Debug session time: Thu Mar  7 19:25:56.564 2013 (UTC - 5:00)
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\030713-20701-01.dmp]
Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime: 0 days 3:37:48.937
Probably caused by : win32k.sys ( win32k!xxxClearWakeMask+12 )
BugCheck 50, {fffff901407a21d4, 0, fffff960000f6132, 5}
BugCheck Info: [B]Link Removed[/B]
Bugcheck code 00000050
Arguments: 
Arg1: fffff901407a21d4, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff960000f6132, If non-zero, the instruction address which referenced the bad memory
 address.
Arg4: 0000000000000005, (reserved)
BUGCHECK_STR:  0x50
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  Skype.exe
FAILURE_BUCKET_ID:  X64_0x50_win32k!xxxClearWakeMask+12
BiosVersion = F5
BiosReleaseDate = 10/19/2012
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = GA-78LMT-S2
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Fri Feb 22 23:29:10.436 2013 (UTC - 5:00)
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\022213-44881-01.dmp]
Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime: 2 days 8:49:44.144
Probably caused by : usbehci.sys ( usbehci!EHCI_MapAsyncTransferToTd+5a )
BugCheck D1, {18, 2, 0, fffff88006a048fe}
BugCheck Info: [B]Link Removed[/B]
Bugcheck code 000000d1
Arguments: 
Arg1: 0000000000000018, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff88006a048fe, address which referenced memory
BUGCHECK_STR:  0xD1
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xD1_usbehci!EHCI_MapAsyncTransferToTd+5a
BiosVersion = F5
BiosReleaseDate = 10/19/2012
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = GA-78LMT-S2
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Tue Feb 12 02:05:15.855 2013 (UTC - 5:00)
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\021113-22651-01.dmp]
Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime: 1 days 1:31:37.229
Probably caused by : USBPORT.SYS ( USBPORT!USBPORT_iSetGlobalEndpointStateTx+8e2 )
BugCheck D1, {4f4446ca, 2, 1, fffff88006c06af2}
BugCheck Info: [B]Link Removed[/B]
Bugcheck code 000000d1
Arguments: 
Arg1: 000000004f4446ca, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff88006c06af2, address which referenced memory
BUGCHECK_STR:  0xD1
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xD1_USBPORT!USBPORT_iSetGlobalEndpointStateTx+8e2
BiosVersion = F5
BiosReleaseDate = 10/19/2012
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = GA-78LMT-S2
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Tue Feb  5 18:06:11.110 2013 (UTC - 5:00)
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\020513-17643-01.dmp]
Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime: 0 days 0:00:20.500
*** WARNING: Unable to verify timestamp for PxHlpa64.sys
*** ERROR: Module load completed but symbols could not be loaded for PxHlpa64.sys
*** WARNING: Unable to verify timestamp for dtsoftbus01.sys
*** ERROR: Module load completed but symbols could not be loaded for dtsoftbus01.sys
Probably caused by : dtsoftbus01.sys ( dtsoftbus01+1324 )
BugCheck C9, {23e, fffff8800148b324, fffff98004fc8e10, 0}
BugCheck Info: [B]Link Removed[/B]
Bugcheck code 000000c9
Arguments: 
Arg1: 000000000000023e, A driver has marked an IRP pending but didn't return STATUS_PENDING.
Arg2: fffff8800148b324, The address in the driver's code where the error was detected.
Arg3: fffff98004fc8e10, IRP address.
Arg4: 0000000000000000, Status code.
BUGCHECK_STR:  0xc9_23e
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xc9_23e_VRF_dtsoftbus01+1324
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

         
       J. C. Griffith, Microsoft MVP (jcgriff2)   
             
           [URL="http://mvp.microsoft.com/profiles/Griffith"][/URL][U][B]Link Removed[/B][/U]   
           [URL="http://sysnative.com"][/URL][U][URL="http://www.sysnative.com"]www.sysnative.com[/URL][/U]
             
           [B]Link Removed[/B][U][B]Link Removed[/B][/U] 

¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨

 

[ProWreck]

Hi -

The issue with your Ethernet could be the driver -

[FONT=lucida console]
RTL8192su.sys               Wed Nov 11 03:54:46 2009 (4AFA7BD6) - Realtek USB wifi
Rt64win7.sys                Thu Oct 25 05:20:09 2012 (50890449) - Realtek Ethernet
[/FONT]

http://www.sysnative.com/drivers/driver.php?id=RTL8192su.sys
http://www.sysnative.com/drivers/driver.php?id=Rt64win7.sys

Update with Jan 2013 driver - Link Removed

Unplug & disable the USB wifi; use Ethernet only. The USB wifi driver is loading into RAM, eventhough it is not being used.

Regards. . .

jcgriff2


BSOD SUMMARY

[font=lucida console]
Debug session time: Thu Mar  7 19:25:56.564 2013 (UTC - 5:00)
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\030713-20701-01.dmp]
Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime: 0 days 3:37:48.937
Probably caused by : win32k.sys ( win32k!xxxClearWakeMask+12 )
BugCheck 50, {fffff901407a21d4, 0, fffff960000f6132, 5}
BugCheck Info: [B]Link Removed[/B]
Bugcheck code 00000050
Arguments: 
Arg1: fffff901407a21d4, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff960000f6132, If non-zero, the instruction address which referenced the bad memory
 address.
Arg4: 0000000000000005, (reserved)
BUGCHECK_STR:  0x50
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  Skype.exe
FAILURE_BUCKET_ID:  X64_0x50_win32k!xxxClearWakeMask+12
BiosVersion = F5
BiosReleaseDate = 10/19/2012
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = GA-78LMT-S2
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Fri Feb 22 23:29:10.436 2013 (UTC - 5:00)
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\022213-44881-01.dmp]
Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime: 2 days 8:49:44.144
Probably caused by : usbehci.sys ( usbehci!EHCI_MapAsyncTransferToTd+5a )
BugCheck D1, {18, 2, 0, fffff88006a048fe}
BugCheck Info: [B]Link Removed[/B]
Bugcheck code 000000d1
Arguments: 
Arg1: 0000000000000018, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff88006a048fe, address which referenced memory
BUGCHECK_STR:  0xD1
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xD1_usbehci!EHCI_MapAsyncTransferToTd+5a
BiosVersion = F5
BiosReleaseDate = 10/19/2012
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = GA-78LMT-S2
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Tue Feb 12 02:05:15.855 2013 (UTC - 5:00)
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\021113-22651-01.dmp]
Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime: 1 days 1:31:37.229
Probably caused by : USBPORT.SYS ( USBPORT!USBPORT_iSetGlobalEndpointStateTx+8e2 )
BugCheck D1, {4f4446ca, 2, 1, fffff88006c06af2}
BugCheck Info: [B]Link Removed[/B]
Bugcheck code 000000d1
Arguments: 
Arg1: 000000004f4446ca, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff88006c06af2, address which referenced memory
BUGCHECK_STR:  0xD1
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xD1_USBPORT!USBPORT_iSetGlobalEndpointStateTx+8e2
BiosVersion = F5
BiosReleaseDate = 10/19/2012
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = GA-78LMT-S2
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Tue Feb  5 18:06:11.110 2013 (UTC - 5:00)
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\020513-17643-01.dmp]
Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime: 0 days 0:00:20.500
*** WARNING: Unable to verify timestamp for PxHlpa64.sys
*** ERROR: Module load completed but symbols could not be loaded for PxHlpa64.sys
*** WARNING: Unable to verify timestamp for dtsoftbus01.sys
*** ERROR: Module load completed but symbols could not be loaded for dtsoftbus01.sys
Probably caused by : dtsoftbus01.sys ( dtsoftbus01+1324 )
BugCheck C9, {23e, fffff8800148b324, fffff98004fc8e10, 0}
BugCheck Info: [B]Link Removed[/B]
Bugcheck code 000000c9
Arguments: 
Arg1: 000000000000023e, A driver has marked an IRP pending but didn't return STATUS_PENDING.
Arg2: fffff8800148b324, The address in the driver's code where the error was detected.
Arg3: fffff98004fc8e10, IRP address.
Arg4: 0000000000000000, Status code.
BUGCHECK_STR:  0xc9_23e
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xc9_23e_VRF_dtsoftbus01+1324
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

         
       J. C. Griffith, Microsoft MVP (jcgriff2)   
             
           [U][B]Link Removed[/B][/U]   
           [U][URL="http://www.sysnative.com"]www.sysnative.com[/URL][/U]
             
           [U][B]Link Removed[/B][/U] 

¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨

And how would one go about disabling the driver?

I have actually used two usb network adapters. I check my network connections and only my ethernet shows up there. The usb adapters were disconnected at the time of the bsod's. Im currently updating though. On a side note, I really appreciate the help. Thank you.

 

[Vir Gnarus]

Disable just by unplugging the device. If you want to be extra sure, open Device manager and locate the USB wifi device listed and right click and click Disable.

If updating the drivers doesn't resolve the issue, run Driver Verifier again and provide us some more crashdumps. I noticed you had Force Pending I/O Requests and IRP Logging options on for DV. Please do not use these options for future DV runs.

DV did detect a potential bug in Daemon Tools. You'll want to update Daemon Tools or switch to another virtual drive solution. Virtual drive software can often harbor bugs so it's necessary to be vigilant in updating them (your Daemon Tools is over a year old). I also see that it's possibly conflicting with the Sonic DVD/CD filter driver. Again, an update may fix this, but it may come time to alter your use of both software (or remove one of them) to work around the conflict. However I'm not sure this is much of an issue really since this DV 'catch' was caused by you using the Force Pending I/O Request check, which often creates false positives. Only driver devs should use that option.

 

[ProWreck]

Disable just by unplugging the device. If you want to be extra sure, open Device manager and locate the USB wifi device listed and right click and click Disable.

If updating the drivers doesn't resolve the issue, run Driver Verifier again and provide us some more crashdumps. I noticed you had Force Pending I/O Requests and IRP Logging options on for DV. Please do not use these options for future DV runs.

DV did detect a potential bug in Daemon Tools. You'll want to update Daemon Tools or switch to another virtual drive solution. Virtual drive software can often harbor bugs so it's necessary to be vigilant in updating them (your Daemon Tools is over a year old). I also see that it's possibly conflicting with the Sonic DVD/CD filter driver. Again, an update may fix this, but it may come time to alter your use of both software (or remove one of them) to work around the conflict. However I'm not sure this is much of an issue really since this DV 'catch' was caused by you using the Force Pending I/O Request check, which often creates false positives. Only driver devs should use that option.

I was unsure of whether or not going to devices was the proper way to disable them. Again, the device hasn't been plugged in since the bsod's began to happen. I will go and uninstall both to be safe those softwares though, as I don't use them anymore. Furthermore, I was told by someone else to enable these options when running DV. Lastly, where would I find the crash dumps?

 

[Vir Gnarus]

Yeah, those options in DV are commonly recommended as most people aren't aware of what they do. They are only familiar with not checking Low Resource Sim since that also is a no-no and restricted for use by driver developers only.

As for where the crashdumps are, where'd you get the previous ones? It should be the same place (C:\Windows\Minidump).

 

[ProWreck]

Yeah, those options in DV are commonly recommended as most people aren't aware of what they do. They are only familiar with not checking Low Resource Sim since that also is a no-no and restricted for use by driver developers only.

As for where the crashdumps are, where'd you get the previous ones? It should be the same place (C:\Windows\Minidump).

Since uninstalling the Dameon tools, I have had no issues so far. Might be speaking to soon, but hopefully not.

 

[Vir Gnarus]

Good to hear. report back to us in a couple days of any update on the situation. You may mark this thread as solved at your discretion, though I recommend waiting it out a bit longer to see if things are truly stable.