Blue Screen of Death

Seryizor

Honorable
Jul 12, 2013
4
0
10,510
0
Hi, I'm getting this BSOD problem and here's my crash log via WhoCrashed, should I post anything else?


On Fri 7/12/2013 7:44:16 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\071213-11668-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x68D80)
Bugcheck code: 0xD1 (0x0, 0x6, 0x8, 0x0)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Thu 7/11/2013 5:35:40 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\071113-12027-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x68D80)
Bugcheck code: 0x50 (0xFFFFC380069C5FE8, 0x1, 0xFFFFF800031CCFCD, 0x7)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Thu 7/11/2013 1:06:15 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\071013-12152-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x68D50)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
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.
 

bob1033

Honorable
Jul 11, 2013
233
0
10,760
33
You can insert you windows installation disk and try to repair windows, or try to system restore you system to a later date. If all that fails, type chkdsk /c into command prompt. NOTE:This deletes all corrupted files on the system, its unlikely, but some corrupted personal files may be deleted. Reinstalling all your drivers will help also.
 

bob1033

Honorable
Jul 11, 2013
233
0
10,760
33
BSOD can be caused by alot of factors, and this ntoskrnl.exe has been causing a lot of people problems. Unfortunately, you can't really track this one to a driver, so trying to find errors in windows is your best bet. I would also scan you computer for viruses, sometimes BSOD's can be caused by them also.
 

Seryizor

Honorable
Jul 12, 2013
4
0
10,510
0
Well I recently reinstalled windows 7, so I'm not sure if I got all my drivers, is it possible that a missing driver is the issue instead?
 

bob1033

Honorable
Jul 11, 2013
233
0
10,760
33


No, usually its a corrupted driver thats causing the problem. Try to remember if any driver had a hard time installing. It maybe be a good idea to uninstall all the non-windows drivers and the reinstall them with the most recent ones
 

bob1033

Honorable
Jul 11, 2013
233
0
10,760
33


Checking the drive for errors may find and repair the faulty driver. You can download a windows 7 iso from here(scroll down some to find it), burn to a drive with software like imgburn, and then boot your computer from it and choose repair windows.
 

ASK THE COMMUNITY

TRENDING THREADS