Its not a matter of which ones, its a matter of if it is on or if it is off it applies to any usb port on your pc. A hub is typically a device used to expand a single usb port into many usb ports like this: Rosewill RHB-320 Hub - Newegg.com
A usb port is just a single port one usb connection
Since last writing I follwed suggestion re the USB ports ans all seemed well, until theis weekend, when the BSODs occured again. They seem to concern
ntoskrnl.exe (nt+0x75C40) and ntkrnlmp.exe (nt!KeBugCheckEx+0x0). What the bits in brackets mean I have no idea!
I attach the SF zip and some other items in case they may be of use.
I hope you will be willing and able tohelp me again! The chameleon like BSODs are maddening.
Last edited by rundwald; 11 Mar 2013 at 12:27.
Delayed post now done, except that I have a full dump that I uploaded to two hosting sites, and neither sharing link is accepted by this forum's manage attachments facility. Hopefully http://www.**************/?kf1o5zkwr67s9cu will work
OK Had a look at the new files, it seems these new Blue screens are a whole other breed the stop codes are both 0xFC:
It is blaming memory corruption as the problem, these type of BSOD are caused by device drivers, so on that note please enable driver verifier and allow it to crash your computer then post back here with the new dumpfiles once it has:Code:******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck FC, {fffff88002bb7c60, 800000004407d963, fffff88002bb7a40, 2} Probably caused by : memory_corruption Followup: memory_corruption ---------
Driver Verifier
Tip: If you can not boot normally once driver verifier is enabled please boot into safe mode by tapping the F8 key before the windows logo appears and then disabling driver verifier from safe mode.
I get confused about driver verifier. How can I ensure that it actually is running or has completed?
Just before the latest incidents I had it going for 24+ hrs with nothing happening.
I am dense ( must be) but am not sure if you want me to do anything with bit enclosed in code.
If the problem is infact caused by a Driver, then Driver verifier will nine times out of ten cause the computer to BSOD, If it is not causing a BSOD then it is likely a hardware problem, however this particular BSOD (atleast according to its documentation) is caused by Driver problems.
I'll have another go with it to see if it reveals any more other than what I put in so far.
Trouble seems to be pin pointing the driver at fault.
driver verifier runs until you stop it. The memory corruption could be any memory in the machine, RAM, GPU, or CPU cache.
If you haven't, do this.
Loaded Verifier this morning, so will now wait and see. Used Memtest quite recently, whilst the earlier problems mentioned in the thread were on go. However will use it again idc.
Found something a little strange whilst looking for unwanted program folders. I have two of Nvidia Corporation.
The onw that has earlier dated contents has fewer folders than the later, but all the earlier dated folder's contemts are in the later. Why that is I don't understand, but might it be a possible cause of some of my troubles?
It may be contributing to the problem, it is likely that when updating your Nvidia driver(s) the old one(s) was/were not uninstalled prior to installing the new one(s) have a look at this tutorial you may want to think about uninstalling your Nvidia diver(s) then running through this tutorial before installing the latest available version(s):
Drivers - Clean Left over Files after Uninstalling
Quote