blue screen error windows 7!

January 22, 2012 at 05:43:43
Specs: windows 7, Pentium 5 2GHz
i previousely had a probem of restarting of pc again and again..so i installed sp1 for windows 7...and now after installation of sp1..there is problem of restarting again and again but this time the blue screen error is also occuring as pc restarts automatically!!!!

See More: blue screen error windows 7!

Report •

#1
January 23, 2012 at 05:24:37
Probably faulty hardware, but you need to post what it says on the BSOD for us to have any chance of diagnosing what's causing it.

Report •

#2
January 23, 2012 at 05:53:12
Can you start your PC in Safe Mode ? If your PC works well in Safe Mode, then it could just be a bad drivers issue.

CoolGuy


Report •

#3
January 24, 2012 at 08:55:15
HERE IS THE REPORT WHEN I USED WHO CRASHED SOFTWARE


Home Edition Notice
--------------------------------------------------------------------------------

This version of WhoCrashed is free for use at home only. If you would like to use this software at work or in a commercial environment you should get the professional edition of WhoCrashed which also allows analysis of crashdumps on remote drives and computers on the network and offers a range of additional features.

Click here for more information on the professional edition.
Click here to buy the the professional edition of WhoCrashed.

--------------------------------------------------------------------------------
System Information (local)
--------------------------------------------------------------------------------

computer name: ABHISHEK-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: GenuineIntel Pentium(R) Dual-Core CPU E5200 @ 2.50GHz Intel586, level: 6
2 logical processors, active mask: 3
RAM: 2137186304 total
VM: 2147352576, free: 2001879040

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

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Tue 1/24/2012 2:44:39 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012412-17019-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x8E41B)
Bugcheck code: 0x50 (0xFFFFFFFFBFFFFFFF, 0x0, 0xFFFFFFFF82C85F65, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntkrnlpa.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 which cannot be identified at this time.


On Tue 1/24/2012 11:45:02 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012412-15990-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x9F8BB)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF82AA48BB, 0xFFFFFFFF8DCD5A98, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\ntkrnlpa.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 which cannot be identified at this time.


On Tue 1/24/2012 11:39:24 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012412-15100-01.dmp
This was probably caused by the following module: ndis.sys (ndis+0x12B2)
Bugcheck code: 0xA (0x1B, 0x2, 0x1, 0xFFFFFFFF82AC1408)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\ndis.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NDIS 6.20 driver
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.


On Tue 1/24/2012 5:40:19 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012412-18439-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0xDEF20)
Bugcheck code: 0x4E (0x99, 0x7C42C, 0x2, 0x7C42B)
Error: PFN_LIST_CORRUPT
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that the page frame number (PFN) list is corrupted.
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 which cannot be identified at this time.


On Mon 1/23/2012 9:25:28 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012312-18189-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x415CB)
Bugcheck code: 0xC5 (0x4, 0x2, 0x1, 0xFFFFFFFF82B2A4C1)
Error: DRIVER_CORRUPTED_EXPOOL
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that the system attempted to access invalid 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. 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 which cannot be identified at this time.


On Mon 1/23/2012 2:28:00 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012312-18922-01.dmp
This was probably caused by the following module: hal.sys (hal+0x3839)
Bugcheck code: 0xA (0xFFFFFFFFFFFCFCFC, 0x2, 0x1, 0xFFFFFFFF82A1F839)
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.
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: hal.sys .
Google query: hal.sys IRQL_NOT_LESS_OR_EQUAL


On Mon 1/23/2012 12:52:37 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012312-16333-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0x74A95)
Bugcheck code: 0x1A (0x41284, 0x7A11001, 0x0, 0xFFFFFFFFC0802000)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
Bug check description: This indicates that a severe memory management error occurred.
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.


On Sun 1/22/2012 2:58:01 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012212-15568-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x14B45)
Bugcheck code: 0x24 (0xC08A5, 0x0, 0x0, 0x0)
Error: NTFS_FILE_SYSTEM
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This indicates a problem occurred in the NTFS file system.
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 which cannot be identified at this time.


On Sun 1/22/2012 12:44:01 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012212-16988-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x10EF7)
Bugcheck code: 0x50 (0xFFFFFFFF87400000, 0x0, 0xFFFFFFFF82A7F7F3, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.


On Sun 1/22/2012 8:49:13 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012212-17128-01.dmp
This was probably caused by the following module: classpnp.sys (CLASSPNP+0x4498)
Bugcheck code: 0xA (0x1A, 0x2, 0x0, 0xFFFFFFFF82A83F66)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\classpnp.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: SCSI Class System Dll
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.


On Sat 1/21/2012 3:51:27 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012112-15927-02.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x415CB)
Bugcheck code: 0xA (0xFFFFFFFFFFFFFFDF, 0x2, 0x0, 0xFFFFFFFF82AE33AB)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntkrnlpa.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 which cannot be identified at this time.


On Sat 1/21/2012 3:27:21 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012112-17378-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x30ACF)
Bugcheck code: 0x50 (0xFFFFFFFFFFFFFFFF, 0x0, 0xFFFFFFFF8DB26ACF, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.


On Sat 1/21/2012 9:31:33 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012112-15927-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x267F53)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF82C74F53, 0xFFFFFFFF8C4FDBF4, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\ntkrnlpa.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 which cannot be identified at this time.


On Sat 1/21/2012 8:08:25 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012112-15912-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x121C6B)
Bugcheck code: 0x19 (0x20, 0xFFFFFFFF8582C368, 0xFFFFFFFF8582CF60, 0x97FFFFF)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\ntkrnlpa.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 which cannot be identified at this time.


On Thu 1/19/2012 3:30:37 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\011912-15818-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x415CB)
Bugcheck code: 0xA (0xFFFFFFFFF0000017, 0x2, 0x0, 0xFFFFFFFF82A34326)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntkrnlpa.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 which cannot be identified at this time.

--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

21 crash dumps have been found and analyzed. Only 15 are included in this report. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

hal.sys

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.


Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.


Report •

Related Solutions

#4
January 24, 2012 at 09:48:11
I would start with checking the RAM. Download memtest proggy and create a bootable CD with it. Boot to this CD and run it for as long as you can.

If memtest comes out clean, then open a command prompt with admin privileges and run
CHKDSK /F /R
and then
SFC /SCANNOW
Note there are blank spaces before the slashes.

For further info, please see this MS document and this MS KB article

Hope the above helps.

CoolGuy


Report •

Ask Question