Computer keeps blue screening

Toggle sidebar Toggle sidebar
X

Xreaper19

Reputable
Mar 26, 2014
3
0
4,510
Hi everyone,

So lately I have been having issues with my computer blue screening. I will turn on my computer and it will boot fine. Then it will either randomly blue screen or just shutdown. But every time it blue screens it give me a different error code. Here are some I was able to write down:

IRQL_NOT_LESS_OR_EQUAL
BAD_POOL_HEADER
BUGCODE_USB_DRIVER
kmode_exception_not_handled

Then after blue screen or shutdown, when I go to start my computer my motherboard gives me a really long beep for about 3-4 seconds. So to be able to get it to boot again I have to remove my ram, graphic card, and hard drives. I have tried different ram, graphics cards, system restore, updating everything I could find, and still having the same issues. The last thing I tried seems to be working but I'm not sure for how long. I went back one version of my graphics card and my computer is letting me wright this post.(Nvidia driver 335.23 to 331.65) Any help would be great, Thanks.

My Computer

GPU: ASUS Geforce GTX 570
CPU: AMD Phenom II X6 1055T
Memory: 8GB
OS: Windows 8.1 Pro
 
Sort by date Sort by votes
X

Xreaper19

Reputable
Mar 26, 2014
3
0
4,510
Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.

On Wed 3/26/2014 1:07:54 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\032614-29265-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14DCA0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF801FC670974, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Wed 3/26/2014 1:07:54 PM GMT your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF801FC670974, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Tue 3/25/2014 11:31:38 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\032514-22500-01.dmp
This was probably caused by the following module: usbport.sys (USBPORT+0x237F8)
Bugcheck code: 0xFE (0x6, 0xFFFFE00002C4F050, 0x63706458, 0x0)
Error: BUGCODE_USB_DRIVER
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 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.



On Tue 3/25/2014 9:58:59 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\032514-26250-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14DCA0)
Bugcheck code: 0x139 (0x3, 0xFFFFD00029970230, 0xFFFFD00029970188, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The kernel has detected the corruption of a critical data structure.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
 
Upvote 0 Downvote
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom