Totally frozen (in contradistinction to a blue screen) is usually hardware.
Maybe RAM - can you try removing a couple of sticks (assuming you have 4 sticks, try removing 2, depending on your motherboard's support for RAM configurations) and see if it works for a long time. If it does, swap RAM so the two good sticks come out and the other two sticks go in.
HDD will usually give lots of OS error messages before it dies.
CPU or mobo failing - difficult to diagnose, but if you eliminate everything else then this is probably the cause.
If you have an old spindle hard drive, you could be saturating the write I/O depending on how much you have coming in from your download stream. This will cause oddities as the system is forcing information to be queued and then written to the hard drive creating slowness and unresponsive behavior.
Your anti-virus could be causing your some trouble. Try disabling it and see if the same behavior occurs
Computer just froze multiple times in a row during regular internet browsing.
I'd happily format butI'm almost 100% certain it's hardware not sure which one?
I've been told having a SSD too full is bad, is it ?Show Image(http://puu.sh/joa3s/264504db11.png)
Any relevant errors in control panel>administrative tools>event viewer>custom views>administrative events?
Total computer lock-ups with screen freeze usually hints at harddrive issues. Could be a dying HDD or a bad SSD controller.
SMART tests aren't always conclusive. The drive could appear fine and still be dying. My advice is to make backups and watch the BIOS POST next time it happens. If after a crash, you see one of your drives take an unusually long time to be detected, there could be your culprit. But basically it's guesswork unless / until it fails completely.
If you still experience problems, try running MemTest86+: http://www.memtest.org/
It requires a boot disk, so you may have to make a bootable USB drive if you don't have a floppy drive. Very thorough memory testing app that works at low level without other parts of the PC getting involved.
I'm not sure the culprit is the graphics driver since you mentioned it never happens while gaming, but who knows.
If neither of those finds / solves the problem, then it could well be a hard drive issue.
You can run a HDTune benchmark (http://www.hdtune.com/download.html) on all your drives, or you can try to figure it out by conjecture. When the freezes happen, which harddrive is currently in use?
If, assuming:
It doesn't happen when playing games.
Your games are on a seprate drive?
It still happens intermittently doing various things.
-> It's probably the system drive.
Like I said. You could've found a clue here, but there are harddrive issues that don't show up at all. A faulty SSD controller or a dying HDD motor can both pass SMART inspection. I still maintain that the kind of freeze you're getting points at one of the harddrives or the SSD.
There is also a chance that a SATA controller driver is responsible. Recently changed OSes or drivers in that area?
I had this problem on my machine once. I was running my OS from an SSD. Freezes would happen at least once a day.
I switched my drive mode from IDE to AHCI. Never happened again.
Could be worth checking controller mode settings for all drives
Could be worth checking controller mode settings for all drives
How should I go about this?
Because it's been 2days without freeze, but I'm still non confident.
ps: on the list of things I done, I unplug and replug my GTX 670 , maybe poorly plugged, but I don't believe so.
@Leslieann: It's not likely to be CPU since it doesn't happen when gaming (which should stress the CPU more than browsing). Most likely has to do with swapping / caching as that happens a fair amount when browsing, especially when you have a lot of tabs open with Flash elements and such in them.
@Leslieann: It's not likely to be CPU since it doesn't happen when gaming (which should stress the CPU more than browsing). Most likely has to do with swapping / caching as that happens a fair amount when browsing, especially when you have a lot of tabs open with Flash elements and such in them.
Not entirely true.
10 years ago or more, I would agree with you, these days games focus much more on the video card than the CPU. Have a few browser windows open with crappy ads, a few Youtube videos, and you can put some heat on a processor pretty fast. I can idle with a browser open at 1-3% cpu, open a few windows and I can quite quickly pull 25%, keep in mind, this is on an I7. Flash uses a LOT of cpu power.
Has the op check to see just how full the hard drive is?
I think the whole bios thing you guys are zoning in on is off base.
Typically, if a system is installed in IDE mode, it will run stable that way. If it was installed in AHCI, it will remain stable as well. It's usually only when you switch on an installed system that something has a problem. Win7, can flat out refuse to boot if you switch from IDE to AHCI mode without first installing the AHCI driver (switching back to IDE mode allows it to start). The only other reason this should be an issue, without a hardware change, is if you recently updated the Bios or a driver was updated with a bad driver. Otherwise, there is no reason for a stable system to suddenly require AHCI.
Not to mention, "Backup and reformatting", that's taking the nuclear option, and may not even fix the problem.
You could go through all of that, and find the CPU fan was failing.
You could just be creating more work, risk and problems. It's fine if you know how to do it, and can accomplish it easily, but most people can't do that (especially without losing some data, some also lack an install disk), and what if the OP gets stuck and now has no computer to even look up advice on what's wrong.
Well, normally, you'd back up Right away after completing the build.. so you have a clean setup to go back to..I pretty much never do this.
But in this case, I'd still reformat first, just to get software out of the way. But ofcourse I'd make a backup THIS time right away as well.
BTW, it's horrific how poor some of the Seagate failure rates are according to Backblaze.. The 3TB ST3000DM001 in particular, with a 26.65% annual failure rate... yikes.It's been a while, but if I remember right, even they explained it was a statistical thing, not really an indication of bad drives.
I didn't have much luck with Samsung.
At least some Toshibas are now made by Seagate (I have one labeled Seagate that identifies as Toshiba). I had pretty good luck with Hitachi.
As far as I can tell, all spinners have become a bit less reliable long term, other than the Blacks and Raptors. I blame the technology, trying to cram more and more onto a platter. I think they may be pushing things a bit too hard to stay in front of SSD's.
As for Defraggler, don't use it to defrag as a check, go to the health tab, it will pull up a full SMART report. Note, the drive needs to be connected with SATA, not USB for it to read, but I think this is for all SMART systems.
Necro since I re-installed the computer and I'm still having issues, I'm now pretty certain it's the motherboard now.
How do I test it ?
Necro since I re-installed the computer and I'm still having issues, I'm now pretty certain it's the motherboard now.
How do I test it ?
ssd always plugged this is where I have windows
iirc the ssd was fine but I may need to recheck it, what is the tool again?
ssd always plugged this is where I have windows
iirc the ssd was fine but I may need to recheck it, what is the tool again?
and it still freezes with just the ssd plugged in.
A few years ago I bought an off brand SSD that did similar things. My system would lock up regardless of the OS I was using. Linux, Windows, everything crashed. I had to reformat several times because of corrupted drivers, system files, you name it.
My motherboard is AHCI compatible, I trimmed in Linux/Windows, it passed disk checks.. I finally dumped the data from it on to an IDE drive and tossed the SSD in the trash >:D. I'm kind of still fearful of SSD drives, as illogical as that may sound.
I really hope this is not the problem you're having.
ssd always plugged this is where I have windows
iirc the ssd was fine but I may need to recheck it, what is the tool again?
and it still freezes with just the ssd plugged in.
is it a question?
what tool do you recommand to test ssd?
Hey,freeze is usually caused by ram. You should monitor your ram with task manager and look at the behavior when it freezes
I have this problem for a little while now but it didn't happen enough for me to bother.
My computer freeze, nothing is responding no more, and I have to reboot it through the power button.
No error message whatsoever when it's rebooted.
Lately It's been happening a lot more because I'm torrenting stuff using my computer instead of my NAS.
It happens mainly when I'm browsing or downloading.
It never ever happens when gaming.
So I think it's either :
-RAM
- Disks
- Motherboard
- ??
What troubleshooting software would you recommand to identify the issue?
Can give you precise specs if that matters , Windows7.
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Mon 07/03/2016 16:14:18 GMT your computer crashed
crash dump file: C:\Windows\Minidump\030716-7254-01.dmp
This was probably caused by the following module: usbport.sys (0xFFFFF8800F25A560)
Bugcheck code: 0xD1 (0x0, 0x2, 0x0, 0xFFFFF8800F25A560)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\usbport.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote de port USB 1.1 & 2.0
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.
On Mon 07/03/2016 16:14:18 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: usbport.sys (USBPORT+0x11560)
Bugcheck code: 0xD1 (0x0, 0x2, 0x0, 0xFFFFF8800F25A560)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\usbport.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote de port USB 1.1 & 2.0
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.
On Wed 02/03/2016 22:34:26 GMT your computer crashed
crash dump file: C:\Windows\Minidump\030216-7831-01.dmp
This was probably caused by the following module: hidclass.sys (HIDCLASS+0xBB63)
Bugcheck code: 0x1E (0xFFFFFFFFC000001D, 0xFFFFF880045C7B63, 0x2, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\hidclass.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hid Class Library
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
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 Sun 28/02/2016 10:58:56 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022816-7644-01.dmp
This was probably caused by the following module: usbport.sys (0xFFFFF8800F036560)
Bugcheck code: 0xD1 (0x31656E44, 0x2, 0x0, 0xFFFFF8800F036560)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\usbport.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote de port USB 1.1 & 2.0
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.
On Sun 24/01/2016 02:16:11 GMT your computer crashed
crash dump file: C:\Windows\Minidump\012416-7472-01.dmp
This was probably caused by the following module: usbport.sys (USBPORT+0x2D2F1)
Bugcheck code: 0xFE (0x6, 0xFFFFFA800DCAF6A0, 0x354C535F, 0x0)
Error: BUGCODE_USB_DRIVER
file path: C:\Windows\system32\drivers\usbport.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote de port USB 1.1 & 2.0
Bug check description: This indicates that an error has occurred in a Universal Serial Bus (USB) driver.
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. Good! No SSD problems :) wth do you have in your USB ports?Code: [Select]--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Mon 07/03/2016 16:14:18 GMT your computer crashed
crash dump file: C:\Windows\Minidump\030716-7254-01.dmp
This was probably caused by the following module: usbport.sys (0xFFFFF8800F25A560)
Bugcheck code: 0xD1 (0x0, 0x2, 0x0, 0xFFFFF8800F25A560)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\usbport.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote de port USB 1.1 & 2.0
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.
On Mon 07/03/2016 16:14:18 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: usbport.sys (USBPORT+0x11560)
Bugcheck code: 0xD1 (0x0, 0x2, 0x0, 0xFFFFF8800F25A560)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\usbport.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote de port USB 1.1 & 2.0
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.
On Wed 02/03/2016 22:34:26 GMT your computer crashed
crash dump file: C:\Windows\Minidump\030216-7831-01.dmp
This was probably caused by the following module: hidclass.sys (HIDCLASS+0xBB63)
Bugcheck code: 0x1E (0xFFFFFFFFC000001D, 0xFFFFF880045C7B63, 0x2, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\hidclass.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hid Class Library
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
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 Sun 28/02/2016 10:58:56 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022816-7644-01.dmp
This was probably caused by the following module: usbport.sys (0xFFFFF8800F036560)
Bugcheck code: 0xD1 (0x31656E44, 0x2, 0x0, 0xFFFFF8800F036560)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\usbport.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote de port USB 1.1 & 2.0
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.
On Sun 24/01/2016 02:16:11 GMT your computer crashed
crash dump file: C:\Windows\Minidump\012416-7472-01.dmp
This was probably caused by the following module: usbport.sys (USBPORT+0x2D2F1)
Bugcheck code: 0xFE (0x6, 0xFFFFFA800DCAF6A0, 0x354C535F, 0x0)
Error: BUGCODE_USB_DRIVER
file path: C:\Windows\system32\drivers\usbport.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote de port USB 1.1 & 2.0
Bug check description: This indicates that an error has occurred in a Universal Serial Bus (USB) driver.
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.
Crash analysis dump I have, all seems relied to usb somehow, and I have one keyboard that doesn't wanna work on this computer.
@appleonama: memtest have been runned multiple times, I'll try again but I'm 99.9% convinced it's not that, it's the first thing I tried.
Ps: the SSD is fine.
Code: [Select]--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Mon 07/03/2016 16:14:18 GMT your computer crashed
crash dump file: C:\Windows\Minidump\030716-7254-01.dmp
This was probably caused by the following module: usbport.sys (0xFFFFF8800F25A560)
Bugcheck code: 0xD1 (0x0, 0x2, 0x0, 0xFFFFF8800F25A560)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\usbport.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote de port USB 1.1 & 2.0
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.
On Mon 07/03/2016 16:14:18 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: usbport.sys (USBPORT+0x11560)
Bugcheck code: 0xD1 (0x0, 0x2, 0x0, 0xFFFFF8800F25A560)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\usbport.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote de port USB 1.1 & 2.0
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.
On Wed 02/03/2016 22:34:26 GMT your computer crashed
crash dump file: C:\Windows\Minidump\030216-7831-01.dmp
This was probably caused by the following module: hidclass.sys (HIDCLASS+0xBB63)
Bugcheck code: 0x1E (0xFFFFFFFFC000001D, 0xFFFFF880045C7B63, 0x2, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\hidclass.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hid Class Library
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
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 Sun 28/02/2016 10:58:56 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022816-7644-01.dmp
This was probably caused by the following module: usbport.sys (0xFFFFF8800F036560)
Bugcheck code: 0xD1 (0x31656E44, 0x2, 0x0, 0xFFFFF8800F036560)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\usbport.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote de port USB 1.1 & 2.0
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.
On Sun 24/01/2016 02:16:11 GMT your computer crashed
crash dump file: C:\Windows\Minidump\012416-7472-01.dmp
This was probably caused by the following module: usbport.sys (USBPORT+0x2D2F1)
Bugcheck code: 0xFE (0x6, 0xFFFFFA800DCAF6A0, 0x354C535F, 0x0)
Error: BUGCODE_USB_DRIVER
file path: C:\Windows\system32\drivers\usbport.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote de port USB 1.1 & 2.0
Bug check description: This indicates that an error has occurred in a Universal Serial Bus (USB) driver.
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.
Crash analysis dump I have, all seems relied to usb somehow, and I have one keyboard that doesn't wanna work on this computer.
@appleonama: memtest have been runned multiple times, I'll try again but I'm 99.9% convinced it's not that, it's the first thing I tried.
Ps: the SSD is fine.
Code: [Select]--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Mon 07/03/2016 16:14:18 GMT your computer crashed
crash dump file: C:\Windows\Minidump\030716-7254-01.dmp
This was probably caused by the following module: usbport.sys (0xFFFFF8800F25A560)
Bugcheck code: 0xD1 (0x0, 0x2, 0x0, 0xFFFFF8800F25A560)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\usbport.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote de port USB 1.1 & 2.0
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.
On Mon 07/03/2016 16:14:18 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: usbport.sys (USBPORT+0x11560)
Bugcheck code: 0xD1 (0x0, 0x2, 0x0, 0xFFFFF8800F25A560)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\usbport.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote de port USB 1.1 & 2.0
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.
On Wed 02/03/2016 22:34:26 GMT your computer crashed
crash dump file: C:\Windows\Minidump\030216-7831-01.dmp
This was probably caused by the following module: hidclass.sys (HIDCLASS+0xBB63)
Bugcheck code: 0x1E (0xFFFFFFFFC000001D, 0xFFFFF880045C7B63, 0x2, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\hidclass.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hid Class Library
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
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 Sun 28/02/2016 10:58:56 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022816-7644-01.dmp
This was probably caused by the following module: usbport.sys (0xFFFFF8800F036560)
Bugcheck code: 0xD1 (0x31656E44, 0x2, 0x0, 0xFFFFF8800F036560)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\usbport.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote de port USB 1.1 & 2.0
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.
On Sun 24/01/2016 02:16:11 GMT your computer crashed
crash dump file: C:\Windows\Minidump\012416-7472-01.dmp
This was probably caused by the following module: usbport.sys (USBPORT+0x2D2F1)
Bugcheck code: 0xFE (0x6, 0xFFFFFA800DCAF6A0, 0x354C535F, 0x0)
Error: BUGCODE_USB_DRIVER
file path: C:\Windows\system32\drivers\usbport.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote de port USB 1.1 & 2.0
Bug check description: This indicates that an error has occurred in a Universal Serial Bus (USB) driver.
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.
Crash analysis dump I have, all seems relied to usb somehow, and I have one keyboard that doesn't wanna work on this computer.
@appleonama: memtest have been runned multiple times, I'll try again but I'm 99.9% convinced it's not that, it's the first thing I tried.
Ps: the SSD is fine.
Your usb port or drivers are causing the issue. Are you using an external usb port? (e.g usb hub, built-in case usb ports) or the mother board usb ports? try reinstalling your usb drivers
MoreGood! But also.. wth do you have in your USB portsCode: [Select]--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Mon 07/03/2016 16:14:18 GMT your computer crashed
crash dump file: C:\Windows\Minidump\030716-7254-01.dmp
This was probably caused by the following module: usbport.sys (0xFFFFF8800F25A560)
Bugcheck code: 0xD1 (0x0, 0x2, 0x0, 0xFFFFF8800F25A560)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\usbport.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote de port USB 1.1 & 2.0
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.
On Mon 07/03/2016 16:14:18 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: usbport.sys (USBPORT+0x11560)
Bugcheck code: 0xD1 (0x0, 0x2, 0x0, 0xFFFFF8800F25A560)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\usbport.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote de port USB 1.1 & 2.0
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.
On Wed 02/03/2016 22:34:26 GMT your computer crashed
crash dump file: C:\Windows\Minidump\030216-7831-01.dmp
This was probably caused by the following module: hidclass.sys (HIDCLASS+0xBB63)
Bugcheck code: 0x1E (0xFFFFFFFFC000001D, 0xFFFFF880045C7B63, 0x2, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\hidclass.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hid Class Library
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
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 Sun 28/02/2016 10:58:56 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022816-7644-01.dmp
This was probably caused by the following module: usbport.sys (0xFFFFF8800F036560)
Bugcheck code: 0xD1 (0x31656E44, 0x2, 0x0, 0xFFFFF8800F036560)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\usbport.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote de port USB 1.1 & 2.0
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.
On Sun 24/01/2016 02:16:11 GMT your computer crashed
crash dump file: C:\Windows\Minidump\012416-7472-01.dmp
This was probably caused by the following module: usbport.sys (USBPORT+0x2D2F1)
Bugcheck code: 0xFE (0x6, 0xFFFFFA800DCAF6A0, 0x354C535F, 0x0)
Error: BUGCODE_USB_DRIVER
file path: C:\Windows\system32\drivers\usbport.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote de port USB 1.1 & 2.0
Bug check description: This indicates that an error has occurred in a Universal Serial Bus (USB) driver.
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.
Crash analysis dump I have, all seems relied to usb somehow, and I have one keyboard that doesn't wanna work on this computer.
@appleonama: memtest have been runned multiple times, I'll try again but I'm 99.9% convinced it's not that, it's the first thing I tried.
Ps: the SSD is fine.
Lot of ****s, usbCode: [Select]--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Mon 07/03/2016 16:14:18 GMT your computer crashed
crash dump file: C:\Windows\Minidump\030716-7254-01.dmp
This was probably caused by the following module: usbport.sys (0xFFFFF8800F25A560)
Bugcheck code: 0xD1 (0x0, 0x2, 0x0, 0xFFFFF8800F25A560)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\usbport.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote de port USB 1.1 & 2.0
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.
On Mon 07/03/2016 16:14:18 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: usbport.sys (USBPORT+0x11560)
Bugcheck code: 0xD1 (0x0, 0x2, 0x0, 0xFFFFF8800F25A560)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\usbport.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote de port USB 1.1 & 2.0
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.
On Wed 02/03/2016 22:34:26 GMT your computer crashed
crash dump file: C:\Windows\Minidump\030216-7831-01.dmp
This was probably caused by the following module: hidclass.sys (HIDCLASS+0xBB63)
Bugcheck code: 0x1E (0xFFFFFFFFC000001D, 0xFFFFF880045C7B63, 0x2, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\hidclass.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hid Class Library
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
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 Sun 28/02/2016 10:58:56 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022816-7644-01.dmp
This was probably caused by the following module: usbport.sys (0xFFFFF8800F036560)
Bugcheck code: 0xD1 (0x31656E44, 0x2, 0x0, 0xFFFFF8800F036560)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\usbport.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote de port USB 1.1 & 2.0
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.
On Sun 24/01/2016 02:16:11 GMT your computer crashed
crash dump file: C:\Windows\Minidump\012416-7472-01.dmp
This was probably caused by the following module: usbport.sys (USBPORT+0x2D2F1)
Bugcheck code: 0xFE (0x6, 0xFFFFFA800DCAF6A0, 0x354C535F, 0x0)
Error: BUGCODE_USB_DRIVER
file path: C:\Windows\system32\drivers\usbport.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote de port USB 1.1 & 2.0
Bug check description: This indicates that an error has occurred in a Universal Serial Bus (USB) driver.
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.
Crash analysis dump I have, all seems relied to usb somehow, and I have one keyboard that doesn't wanna work on this computer.
@appleonama: memtest have been runned multiple times, I'll try again but I'm 99.9% convinced it's not that, it's the first thing I tried.
Ps: the SSD is fine.
Your usb port or drivers are causing the issue. Are you using an external usb port? (e.g usb hub, built-in case usb ports) or the mother board usb ports? try reinstalling your usb drivers
I just though of that, no hub but I updated the usb driver.
I has fixed one issue: one keyboard couldn't work on this computer (but worked on others), I'm typing on it right now.
I shall see if I encounter more freezes, but possibly fixed.
ssd always plugged this is where I have windows
iirc the ssd was fine but I may need to recheck it, what is the tool again?
and it still freezes with just the ssd plugged in.
is it a question?
what tool do you recommand to test ssd?