Computer Freezing

[Dongulator]

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 ?

So before you go doing a bunch of stuff, have you checked event viewer for any application issues?
edit: Nvm.. missed that post

[tp4tissue]

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 ?

does it freeze with just the ssd plugged in

[azhdar]

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?

[tp4tissue]

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.

[azhdar]

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?

[xtrafrood]

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 . 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.

[azhdar]

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 . 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.

It isn't a off-brand SSD:

[dgneo]

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?

IIRC Crystal Disk Info should be a good test.

[appleonama]

Hey,
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.

freeze is usually caused by ram. You should monitor your ram with task manager and look at the behavior when it freezes

edit: i didn't read the rest but ram is usually the culprit

if it was your harddrive you would blue screen right away

[azhdar]

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.

[xtrafrood]

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.

Good! No SSD problems wth do you have in your USB ports?

[appleonama]

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

[azhdar]

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

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.

[appleonama]

More

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.

Good! But also.. wth do you have in your USB ports

Lot of ****s, usb

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

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.

Nice hopefully your issues are gone now. That is weird.. if a driver malfunctions your computer should blue screen immediately and according to your dump file it did, but it froze too soon for it to trigger the blue screen.

[azhdar]

one man can pray

[tp4tissue]

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?

I don't think you need to test the SSD..

Pull the Gpu and everything you can out of the PC.

Run on integrated graphics for now.

Turn off all overclocking, and make sure all Power-Saving  feature of the motherboard is disabled. (asus digi tpm stuff like that)

Set the memory timings manually.


Then.. make a partition on the SSD,   install JUST WINDOWS, nothing else.. just windows. - this should be quick, takes like 20 minutes.


Then test using prime95..   do the small fft test first..  for a few hours, then do the large fft test, you need to manually set the memory usage to maximum for the large fft test.

If it doesn't crash under this scenario..  then we can rule out software,  cpu and ram..

[azhdar]

UPDATE: ever since I updated the driver no more freezes

[xtrafrood]

*knocks on wood*