Sign in with
Sign up | Sign in
Your question

Blue Screen Errors

Last response: in Windows 7
Share
May 8, 2013 12:26:51 PM

For around the past week or so I've been experiencing numerous instances of blue screen crashes.
I haven't installed any new hardware recently and I actually reverted my computer back to factory settings in the hope that it would fix the errors somehow.
I've updated my video drivers, but the problem persists and the blue screen errors seem to be happening much more frequently now.
I'm not particularly computer savvy, but any help would be greatly appreciated.

windows version: Windows 7 , 6.1, build: 7600
Intel Intel(R) Core(TM)2 Quad CPU Q8300 @ 2.50GHz
RAM: 6GB
Graphics: NVIDIA GeForce GT 240
Hard Drive: 460GB
VM: 2147352576, free: 1952595968




--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Wed 08/05/2013 19:18:35 GMT your computer crashed
crash dump file: C:\Windows\Minidump\050813-21356-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x6F880)
Bugcheck code: 0xA (0x100000101, 0x2, 0x1, 0xFFFFF80002EA3165)
Error: 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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 08/05/2013 19:18:35 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: 0xA (0x100000101, 0x2, 0x1, 0xFFFFF80002EA3165)
Error: IRQL_NOT_LESS_OR_EQUAL
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 08/05/2013 19:12:17 GMT your computer crashed
crash dump file: C:\Windows\Minidump\050813-22011-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x6F880)
Bugcheck code: 0xA (0x848, 0x2, 0x0, 0xFFFFF80002E7EA31)
Error: 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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 08/05/2013 18:55:06 GMT your computer crashed
crash dump file: C:\Windows\Minidump\050813-20904-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x6F880)
Bugcheck code: 0xA (0xFFFFFA7FFFFFFCD8, 0x2, 0x1, 0xFFFFF80002EEB2D4)
Error: 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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 08/05/2013 18:53:04 GMT your computer crashed
crash dump file: C:\Windows\Minidump\050813-20794-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x6F880)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800031DEE82, 0xFFFFF88007299100, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 08/05/2013 18:42:17 GMT your computer crashed
crash dump file: C:\Windows\Minidump\050813-20186-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x6F880)
Bugcheck code: 0x3B (0xC0000094, 0xFFFFF8000316CC06, 0xFFFFF880094C2A70, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 08/05/2013 18:12:09 GMT your computer crashed
crash dump file: C:\Windows\Minidump\050813-27315-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x394FD)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF880053594FD, 0xFFFFF8800266B838, 0xFFFFF8800266B0A0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
Bug check description: This indicates that a system thread 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 Wed 08/05/2013 17:46:44 GMT your computer crashed
crash dump file: C:\Windows\Minidump\050813-23509-01.dmp
This was probably caused by the following module: watchdog.sys (watchdog+0x122F)
Bugcheck code: 0x10E (0x1F, 0xFFFFF8A001A96A50, 0x0, 0x1584F)
Error: VIDEO_MEMORY_MANAGEMENT_INTERNAL
file path: C:\Windows\system32\drivers\watchdog.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Watchdog Driver
Bug check description: This indicates that the video memory manager has encountered a condition that it is unable to recover from.
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 08/05/2013 17:19:27 GMT your computer crashed
crash dump file: C:\Windows\Minidump\050813-23680-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x6F880)
Bugcheck code: 0x19 (0x20, 0xFFFFF8A0030DB850, 0xFFFFF8A0030DB9E0, 0x5190103)
Error: BAD_POOL_HEADER
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 pool header is corrupt.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
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 08/05/2013 17:13:05 GMT your computer crashed
crash dump file: C:\Windows\Minidump\050813-24741-01.dmp
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0xB4C94)
Bugcheck code: 0xA (0x100060081, 0x2, 0x1, 0xFFFFF80002EC0951)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 314.22
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 314.22
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 314.22 , NVIDIA Corporation).
Google query: NVIDIA Corporation IRQL_NOT_LESS_OR_EQUAL



On Wed 08/05/2013 12:08:41 GMT your computer crashed
crash dump file: C:\Windows\Minidump\050813-30201-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x6F880)
Bugcheck code: 0x19 (0x3, 0xFFFFFA80054794F0, 0xFFFFFA80054794E0, 0xFFFFFA80054794E0)
Error: BAD_POOL_HEADER
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 pool header is corrupt.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
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 07/05/2013 15:55:48 GMT your computer crashed
crash dump file: C:\Windows\Minidump\050713-22370-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0x19 (0x3, 0xFFFFFA80054793D0, 0xFFFFFA80054793C0, 0xFFFFFA80054793C0)
Error: BAD_POOL_HEADER
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 pool header is corrupt.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

More about : blue screen errors

a b $ Windows 7
May 8, 2013 2:28:24 PM

What method did you use to "revert" to factory settings?
m
0
l
May 8, 2013 2:34:55 PM

I went to Control Panel and through to Advanced Recovery Methods and selected 'Return your computer to factory condition'.
The blue screen errors I'm getting now are still the same as before I did so, but they're now happening far more often.
m
0
l
Related resources
a b $ Windows 7
May 8, 2013 2:40:46 PM

OK - so you did a factory restore from the recovery partition?

What motherboard, cpu, gpu and psu?
m
0
l
May 8, 2013 3:52:44 PM

Yeah, that's correct.

Packard Bell ixtreme M5722
Intel(R) Core(TM)2 Quad CPU Q8300 @ 2.50GHz
NVIDIA GeForce GT 240
Delta DPS-250AB-22 D 250 Watt Power Supply
m
0
l
a b $ Windows 7
May 8, 2013 4:22:22 PM

Download and install the latest drivers for your video card and see if that cures the problem.

Also, that gpu pulls a bit of current for its size. You may be stressing that psu which is only really capable of about 175w max on a good day. You may be seeing psu fluctuations giving your system fits - kernal panic would be one of those symptoms.

Mark
m
0
l
!