Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Msi Z97-G45 Usb problems ( restarts)


  • Please log in to reply
4 replies to this topic

#1 johnny15

johnny15

  • Members
  • 22 posts
  • OFFLINE
  •  
  • Local time:11:24 PM

Posted 16 December 2015 - 05:45 PM

Hello Everyone!

 

Here I am again, and I guess bad luck keeps following me!

After 8 years I decided to upgrade my computer, with the help of some guys here I got the following system ( you will find it at the end of the topic )

I installed everything fine, formated the previous hdd and started with a new installation of win 7 64bit on the SSD
1 or 2 days after I realized that when I forget the external hdd pluged in  the pc gets stuck on the loading screen and then restarts (when i removed the external HDD it started normally sometimes I get a blue screen, you will find it attached here).

So I did a little bit of searching on google and found that disabling usb debugging will solve the problem, ( in fact it did, but now I have another problem, my gaming controller doesn't work unless I unplug it and plug it in again, and sometimes when i plug in the external hdd keyboard doesn't work and i have to unplug it and plug it in again to work.)

I forgot to mention that I updated the bios and installed the latest motherboard drivers.

I'd like your help here guys because most of the people I asked don't know anything about that problem

thanks a lot for your time and sorry for the length of my post + my bad english

 

PC SPECIFICATIONS

CPU : i5 4690K

Motherboard: MSI Z97-G45 Gaming

RAM: G.SKILL Sniper 8GB (2x4GB) DDR3 1866MHz CL9

Graphics Card: ASUS GTX750TI-OC-2GD5 GeForce GTX 750 Ti 2GB

 

PSU :  ETASIS ET650 GAMING POWER SUPPLY 650W

Operating System: Windows 7 64Bit

Monitor: Samsung Syncmaster 2032BW 20’’

 

HDD1: Samsung Evo 850 260 Gb

HDD2 : Sata II 320GB Seagate

HDD3: 1ΤΒ Western Digital

Attached Files



BC AdBot (Login to Remove)

 


#2 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,091 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:05:24 PM

Posted 17 December 2015 - 05:49 PM

Please describe exactly how you disabled USB debugging.

The BSOD blames the USB 3.0 drivers for your motherboard.

 

Have you updated those, and are they enabled in Device Manager?

 

 

Please provide this information so we can provide a complete analysis (from the Pinned Topic at the top of the forum):  http://www.bleepingcomputer.com/forums/t/576314/blue-screen-of-death-bsod-posting-instructions-windows-10-81-8-7-vista/

Should you have problems with the perfmon report, please disregard it (I don't use it very much anyway).

Should the app lock up for more than 15 minutes while searching for Network information (it does this in my copy of W10), go ahead and kill the app. 
Then navigate to the Documents folder and zip up the 18 reports in the SysnativeFileCollectionApp folder - then upload that with your next post.

If that doesn't work, then you can try this new app (from a friend of mine):  http://omgdebugging.com/bsod-inspector/
When done a Notepad document will open with the name of the file and it's location.
By default it'll be a .zip file located on your Desktop
Simply upload the .zip file with your next post and we'll move on from there.
***********************************************************************************************************

 


My browser caused a flood of traffic, sio my IP address was banned. Hope to fix it soon. Will get back to posting as soon as Im able.

- John  (my website: http://www.carrona.org/ )**If you need a more detailed explanation, please ask for it. I have the Knack. **  If I haven't replied in 48 hours, please send me a message. My eye problems have recently increased and I'm having difficult reading posts. (23 Nov 2017)FYI - I am completely blind in the right eye and ~30% blind in the left eye.<p>If the eye problems get worse suddenly, I may not be able to respond.If that's the case and help is needed, please PM a staff member for assistance.

#3 johnny15

johnny15
  • Topic Starter

  • Members
  • 22 posts
  • OFFLINE
  •  
  • Local time:11:24 PM

Posted 18 December 2015 - 09:54 AM

I went to the bios screen and turned  usb legacy support from "enabled" to "disabled" ,

I have installed the drivers from  here : http://us.msi.com/product/motherboard/support/Z97-G45-GAMING.html#down-driver&Win7%2064

How can I check if they are installed correctly? Because at the device manager there isnt any strange icon, everything is fine

btw I didn't know there was a specific way of posting bsod, I'll check and reply as soon as possible (probably tomorrow)

 

thanks ;)

 

I hope I posted the zip files correctly

Attached Files


Edited by johnny15, 18 December 2015 - 05:15 PM.


#4 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,091 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:05:24 PM

Posted 20 December 2015 - 02:01 PM

Unfortunately it appears that the OS installed isn't legitimate.
Please get a legitimate copy of the OS installed and we'll be glad to help.

Here's suggestions on how to ensure that your version is legitimate:  http://windows.microsoft.com/en-us/windows/genuine

As a courtesy, I provide an initial diagnosis - but I do not answer questions about the diagnosis until you have obtained a legal copy of the operating system.

 

You had USB 3 memory dumps (BSOD's) in October of this year.

The most recent memory dump is from 15 December and it blames your wireless drivers.

Please download a fresh set of wireless drivers, then uninstall the current ones and install the freshly downloaded ones.

 

Daemon Tools (and Alcohol % software) are known to cause BSOD's on some Windows systems (mostly due to the sptd.sys driver, although I have seen both dtsoftbus01.sys and dtscsibus.sys blamed on several occasions).

 

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):  New link (15 Aug 2012):  http://www.duplexsecure.com/downloads (pick the appropriate version for your system and select "Un-install" when you run it).
Alternate link:  http://www.disc-tools.com/download/sptd
Manual procedure here:  http://daemonpro-help.com/en/problems_and_solutions/registry_and_sptd_problems.html


Numerous instances of NTIOLib_X64.sys - a known BSOD causing driver.

Search your system for this file - then uninstall the MSI software that belongs to it (it'll be in the directory names).

Do not just delete the files - it can render the system unbootable.  You must use the uninstaller to uninstall the program.

 

Analysis:
The following is for informational purposes only.
**************************Tue Dec 15 18:53:30.281 2015 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\SysnativeBSODApps\121615-5101-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: 7601.19045.amd64fre.win7sp1_gdr.151019-1254
System Uptime: 0 days 0:15:08.452
*** WARNING: Unable to verify timestamp for e22w7x64.sys
*** ERROR: Module load completed but symbols could not be loaded for e22w7x64.sys
Probably caused by : e22w7x64.sys ( e22w7x64+70c0 )
BugCheck D1, {28, 2, 0, fffff880020c0480}
BugCheck Info: DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
Arguments:
Arg1: 0000000000000028, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff880020c0480, address which referenced memory
BUGCHECK_STR:  0xD1
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xD1_e22w7x64+70c0
CPUID:        "Intel® Core™ i5-4690K CPU @ 3.50GHz"
MaxSpeed:     3500
CurrentSpeed: 3500
  BIOS Version                  V2.8
  BIOS Release Date             08/13/2015
  Manufacturer                  MSI
  Product Name                  MS-7821
  Baseboard Product             Z97-G45 GAMING (MS-7821)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sun Oct 25 07:56:06.680 2015 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\SysnativeBSODApps\102515-5366-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime: 0 days 0:00:14.851
*** WARNING: Unable to verify timestamp for iusb3xhc.sys
*** ERROR: Module load completed but symbols could not be loaded for iusb3xhc.sys
Probably caused by : iusb3xhc.sys ( iusb3xhc+4d6e0 )
BugCheck 1000007E, {ffffffffc0000005, fffff880031816e0, fffff880035ee5a8, fffff880035ede00}
BugCheck Info: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff880031816e0, The address that the exception occurred at
Arg3: fffff880035ee5a8, Exception Record Address
Arg4: fffff880035ede00, Context Record Address
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
FAILURE_BUCKET_ID:  X64_0x7E_iusb3xhc+4d6e0
CPUID:        "Intel® Core™ i5-4690K CPU @ 3.50GHz"
MaxSpeed:     3500
CurrentSpeed: 3500
  BIOS Version                  V2.4
  BIOS Release Date             09/19/2014
  Manufacturer                  MSI
  Product Name                  MS-7821
  Baseboard Product             Z97-G45 GAMING (MS-7821)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sun Oct 25 07:33:11.679 2015 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\SysnativeBSODApps\102515-6396-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime: 0 days 0:00:12.850
*** WARNING: Unable to verify timestamp for iusb3xhc.sys
*** ERROR: Module load completed but symbols could not be loaded for iusb3xhc.sys
Probably caused by : iusb3xhc.sys ( iusb3xhc+4d6e0 )
BugCheck 1000007E, {ffffffffc0000005, fffff8800489b6e0, fffff880035d25a8, fffff880035d1e00}
BugCheck Info: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff8800489b6e0, The address that the exception occurred at
Arg3: fffff880035d25a8, Exception Record Address
Arg4: fffff880035d1e00, Context Record Address
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
FAILURE_BUCKET_ID:  X64_0x7E_iusb3xhc+4d6e0
CPUID:        "Intel® Core™ i5-4690K CPU @ 3.50GHz"
MaxSpeed:     3500
CurrentSpeed: 3500
  BIOS Version                  V2.4
  BIOS Release Date             09/19/2014
  Manufacturer                  MSI
  Product Name                  MS-7821
  Baseboard Product             Z97-G45 GAMING (MS-7821)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``


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.
**************************Tue Dec 15 18:53:30.281 2015 (UTC - 5:00)**************************
flashud.sys                 Fri Mar  6 04:57:27 2009 (49B0F387)
intelppm.sys                Mon Jul 13 19:19:25 2009 (4A5BC0FD)
MBfilt64.sys                Thu Jul 30 23:40:32 2009 (4A7267B0)
amdxata.sys                 Fri Mar 19 12:18:18 2010 (4BA3A3CA)
SCDEmu.SYS                  Wed Jun 15 04:29:27 2011 (4DF86D67)
nuvserial.sys               Wed Nov 30 02:59:28 2011 (4ED5E260)
nuvserenum.sys              Wed Nov 30 02:59:36 2011 (4ED5E268)
AcpiCtlDrv.sys              Tue Jul 17 13:07:16 2012 (50059BC4)
NTIOLib_X64.sys             Thu Oct 25 06:27:58 2012 (5089142E)
NTIOLib_X64.sys             Thu Oct 25 21:46:44 2012 (5089EB84)
PLTGC.sys                   Wed Nov 14 21:04:25 2012 (50A44DA9)
cm_km_w.sys                 Thu Dec 20 11:47:26 2012 (50D3411E)
ICCWDT.sys                  Mon Aug 12 13:59:08 2013 (5209226C)
NTIOLib_X64.sys             Mon Mar 17 06:24:03 2014 (5326CD43)
e22w7x64.sys                Wed Mar 26 11:59:01 2014 (5332F945)
bflwfx64.sys                Thu Apr 10 11:40:47 2014 (5346BB7F)
iocbios2.sys                Wed May 21 04:58:24 2014 (537C6AB0)
TeeDriverx64.sys            Tue Sep 23 16:01:14 2014 (5421D18A)
nvhda64v.sys                Thu Oct  9 13:02:27 2014 (5436BFA3)
iaStorA.sys                 Thu Nov  6 14:00:02 2014 (545BC532)
iaStorF.sys                 Thu Nov  6 14:00:09 2014 (545BC539)
RTKVHD64.sys                Tue Feb  3 09:11:16 2015 (54D0D704)
nvlddmkm.sys                Thu Feb  5 13:01:37 2015 (54D3B001)
iusb3hub.sys                Mon Mar 23 12:28:54 2015 (55103F46)
iusb3xhc.sys                Mon Mar 23 12:28:57 2015 (55103F49)
iusb3hcs.sys                Mon Mar 23 12:30:31 2015 (55103FA7)
klflt.sys                   Sat Mar 28 05:48:54 2015 (55167906)
klim6.sys                   Mon Apr 20 15:08:27 2015 (55354EAB)
klpd.sys                    Mon Apr 20 15:48:21 2015 (55355805)
kldisk.sys                  Mon Apr 20 15:48:28 2015 (5535580C)
klwtp.sys                   Mon Apr 20 15:56:28 2015 (553559EC)
klmouflt.sys                Tue Apr 28 15:35:11 2015 (553FE0EF)
klkbdflt.sys                Tue Apr 28 15:38:26 2015 (553FE1B2)
kl1.sys                     Tue Jun  2 09:18:40 2015 (556DAD30)
kltdi.sys                   Wed Jun 10 08:28:21 2015 (55782D65)
kneps.sys                   Fri Jun 19 08:48:36 2015 (55840FA4)
klhk.sys                    Wed Jun 24 04:11:12 2015 (558A6620)
klif.sys                    Thu Aug 27 06:18:18 2015 (55DEE3EA)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sun Oct 25 07:56:06.680 2015 (UTC - 5:00)**************************
ISCTD.sys                   Wed Jan 22 14:37:35 2014 (52E01DFF)
TeeDriverx64.sys            Thu Mar 13 14:21:52 2014 (5321F740)
iusb3hub.sys                Fri May 30 09:16:45 2014 (538884BD)
iusb3hcs.sys                Fri May 30 09:18:22 2014 (5388851E)
iusb3xhc.sys                Tue Jan 27 11:27:38 2015 (54C7BC7A)
dtlitescsibus.sys           Thu Mar 26 22:05:54 2015 (5514BB02)
http://www.carrona.org/drivers/driver.php?id=flashud.sys
http://www.carrona.org/drivers/driver.php?id=intelppm.sys
http://www.carrona.org/drivers/driver.php?id=MBfilt64.sys
http://www.carrona.org/drivers/driver.php?id=amdxata.sys
http://www.carrona.org/drivers/driver.php?id=SCDEmu.SYS
http://www.carrona.org/drivers/driver.php?id=nuvserial.sys
http://www.carrona.org/drivers/driver.php?id=nuvserenum.sys
http://www.carrona.org/drivers/driver.php?id=AcpiCtlDrv.sys
http://www.carrona.org/drivers/driver.php?id=NTIOLib_X64.sys
http://www.carrona.org/drivers/driver.php?id=NTIOLib_X64.sys
http://www.carrona.org/drivers/driver.php?id=PLTGC.sys
http://www.carrona.org/drivers/driver.php?id=cm_km_w.sys
http://www.carrona.org/drivers/driver.php?id=ICCWDT.sys
http://www.carrona.org/drivers/driver.php?id=NTIOLib_X64.sys
http://www.carrona.org/drivers/driver.php?id=e22w7x64.sys
http://www.carrona.org/drivers/driver.php?id=bflwfx64.sys
http://www.carrona.org/drivers/driver.php?id=iocbios2.sys
http://www.carrona.org/drivers/driver.php?id=TeeDriverx64.sys
http://www.carrona.org/drivers/driver.php?id=nvhda64v.sys
http://www.carrona.org/drivers/driver.php?id=iaStorA.sys
http://www.carrona.org/drivers/driver.php?id=iaStorF.sys
http://www.carrona.org/drivers/driver.php?id=RTKVHD64.sys
http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
http://www.carrona.org/drivers/driver.php?id=iusb3hub.sys
http://www.carrona.org/drivers/driver.php?id=iusb3xhc.sys
http://www.carrona.org/drivers/driver.php?id=iusb3hcs.sys
http://www.carrona.org/drivers/driver.php?id=klflt.sys
http://www.carrona.org/drivers/driver.php?id=klim6.sys
http://www.carrona.org/drivers/driver.php?id=klpd.sys
http://www.carrona.org/drivers/driver.php?id=kldisk.sys
http://www.carrona.org/drivers/driver.php?id=klwtp.sys
http://www.carrona.org/drivers/driver.php?id=klmouflt.sys
http://www.carrona.org/drivers/driver.php?id=klkbdflt.sys
http://www.carrona.org/drivers/driver.php?id=kl1.sys
http://www.carrona.org/drivers/driver.php?id=kltdi.sys
http://www.carrona.org/drivers/driver.php?id=kneps.sys
http://www.carrona.org/drivers/driver.php?id=klhk.sys
http://www.carrona.org/drivers/driver.php?id=klif.sys
http://www.carrona.org/drivers/driver.php?id=ISCTD.sys
http://www.carrona.org/drivers/driver.php?id=TeeDriverx64.sys
http://www.carrona.org/drivers/driver.php?id=iusb3hub.sys
http://www.carrona.org/drivers/driver.php?id=iusb3hcs.sys
http://www.carrona.org/drivers/driver.php?id=iusb3xhc.sys
http://www.carrona.org/drivers/driver.php?id=dtlitescsibus.sys
 


Edited by usasma, 20 December 2015 - 02:03 PM.

My browser caused a flood of traffic, sio my IP address was banned. Hope to fix it soon. Will get back to posting as soon as Im able.

- John  (my website: http://www.carrona.org/ )**If you need a more detailed explanation, please ask for it. I have the Knack. **  If I haven't replied in 48 hours, please send me a message. My eye problems have recently increased and I'm having difficult reading posts. (23 Nov 2017)FYI - I am completely blind in the right eye and ~30% blind in the left eye.<p>If the eye problems get worse suddenly, I may not be able to respond.If that's the case and help is needed, please PM a staff member for assistance.

#5 johnny15

johnny15
  • Topic Starter

  • Members
  • 22 posts
  • OFFLINE
  •  
  • Local time:11:24 PM

Posted 26 December 2015 - 05:56 AM

Thanks a lot for your help!  the problem is solved,

there was a problem with the killer network drivers + usb 3.0.

uninstalling these drivers and installing them correctly solved the problem!

Merry christmas! ;)






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users