win 7 crashes suggested USB issues

jjbandit · 18 May 2015

Hi My sons PC is crashing lots, it did not do this until he updated windows 8, however having produced a fresh w8 install it still does it, I then installed w7 as a fresh install it does the same, the diagnostic info from the crash dumps from (whocrashed) are given below, this suggests USB issues. Sometimes the computer will last an hour before it crashes others it lasts seconds. When I start it in safe mode there are no crashes.
It does this with the original MOBO chipset disks and also the latest set from gigabytes website, for both w8 and w7
Is it software or hardware processor or Mobo, any help gratefully given. Would flashing the bios help?
Thanks
--
System Information (local)
computer name: JAY-PC
windows version: Windows 7 , 6.1, build: 7600
windows dir: C:\Windows
Hardware: Gigabyte Technology Co., Ltd., H61M-S2PV
CPU: GenuineIntel Intel(R) Core(TM) i5-3330 CPU @ 3.00GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 8478183424 total
Crash Dump Analysis
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Sat 16/05/2015 21:18:53 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051615-5928-01.dmp
This was probably caused by the following module: usbport.sys (0xFFFFF88004626068)
Bugcheck code: 0x50 (0xFFFFFA880B4E5500, 0x1, 0xFFFFF88004626068, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\usbport.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: USB 1.1 & 2.0 Port Driver
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Sat 16/05/2015 21:18:53 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: usbport.sys (USBPORT+0x26068)
Bugcheck code: 0x50 (0xFFFFFA880B4E5500, 0x1, 0xFFFFF88004626068, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\usbport.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: USB 1.1 & 2.0 Port Driver
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Sat 16/05/2015 18:46:17 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051615-6068-01.dmp
This was probably caused by the following module: usbehci.sys (0xFFFFF88004799360)
Bugcheck code: 0xD1 (0xFFFFF888009FC1E8, 0x2, 0x0, 0xFFFFF88004799360)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\usbehci.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: EHCI eUSB Miniport Driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.

z3r010 · 18 May 2015

Please follow the instructions in the big note at the top of the page.

essenbe · 18 May 2015

Please upload the BSOD Posting Instructions https://www.sevenforums.com/bsod-help-support/96879-blue-screen-death-bsod-posting-instructions.html. Upload the files here, this will tell you how. https://www.sevenforums.com/tutorials/9733-screenshots-files-upload-post-seven-forums.html

jjbandit · 19 May 2015

One addition to my earlier post is that I don't actually get a BSOD, my pc just crashes and re-boots, not sure this means I should post elsewhere.

My worry is I have a hardware problem, mobo or ram

essenbe · 19 May 2015

jjbandit, You had 2 BSODs both dated 5/16.

Code:

 
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {fffff888009fc1e8, 2, 0, fffff88004799360}
Probably caused by : usbehci.sys ( usbehci!EHCI_RemoveQueueHeadFromPeriodicList+a8 )
Followup: MachineOwner

Code:

 
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 50, {fffffa880b4e5500, 1, fffff88004626068, 5}
Could not read faulting driver name
Probably caused by : USBPORT.SYS ( USBPORT!USBPORT_ClosePipe+88 )

Both drivers are essentially for the same purpose and from the same place, Windows Update. I suggest you run all recommended and important Windows Updates. Also, please tell me why you do not have Service Pack 1 installed. If you don't install SP1, you will continue having these problems and more.

Please open an elevated command prompt ( click start, type cmd in the search box, right click on the cmd entry and select run as administrator) in the black box that opens, copy/paste sfc /scannow. If you decide to type it, notice the space between the sfc and the /. It is a system file checker which will scan your system files and attempt to correct any missing or corrupt files. What we want are the results to say windows found no integrity violations. If it says files were found but could not be repaired, close the box, reboot and run it again, after opening the administrative command prompt. You may have to reboot and run it three times for it to repair all system files. If it can't repair them after 3 reboots, let us know.

jjbandit · 20 May 2015

Ran scannow in full (non safe mode) and it found no violations.

I am downloading SP1 from MS website, will install that and let you know. have to say I am not hopeful, as I got the same error when trying to run it with recently purchased w8 disk, before I reverted back to w7. Fingers crossed.

GY

win 7 crashes suggested USB issues

win 7 crashes suggested USB issues

Apologies for not posting properly

Windows found no integrity violations