Windows 7 Forums

Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: Help! Bsod

26 Aug 2012   #1
MasterZhen

Windows 7 Ultimate 32 bit
 
 
Help! Bsod

Hi all! I keep getting BSODs .I tried many things but doesnt solved my problem.I dont know how to open the minidump files.All i can do is use WhoCrased or BlueScreeView.But i heared they are not showing all and i must take a look in minidumps.How do i open the .dmp files? Thanks!

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

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Sun 26.08.2012 07:29:29 GMT your computer crashed
crash dump file: C:\Windows\Minidump\082612-18828-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x2224FD)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFFFFF834784FD, 0xFFFFFFFF80786888, 0xFFFFFFFF80786460)
Error: SYSTEM_THREAD_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 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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Fri 24.08.2012 12:18:25 GMT your computer crashed
crash dump file: C:\Windows\Minidump\082412-23406-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xBD411)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF9722D411, 0xFFFFFFFF9B643B98, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
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 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 which cannot be identified at this time.


On Fri 24.08.2012 10:52:11 GMT your computer crashed
crash dump file: C:\Windows\Minidump\082412-22718-01.dmp
This was probably caused by the following module: cdd.dll (cdd+0xB7C7)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF8329E061, 0xFFFFFFFF9E7ECA4C, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\cdd.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Canonical Display Driver
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 which cannot be identified at this time.


On Sun 12.08.2012 12:37:50 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081212-21343-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x2224FD)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFFFFF834754FD, 0xFFFFFFFF80786888, 0xFFFFFFFF80786460)
Error: SYSTEM_THREAD_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 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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Sun 12.08.2012 07:19:35 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081212-21921-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x4682B)
Bugcheck code: 0xC5 (0x3098, 0x2, 0x0, 0xFFFFFFFF83160795)
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 Sun 12.08.2012 06:22:58 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081212-18265-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x4682B)
Bugcheck code: 0xC5 (0x33D8, 0x2, 0x0, 0xFFFFFFFF83167795)
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 06.08.2012 22:32:27 GMT your computer crashed
crash dump file: C:\Windows\Minidump\080712-22296-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x4682B)
Bugcheck code: 0xC5 (0xF488, 0x2, 0x0, 0xFFFFFFFF82F3D795)
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 06.08.2012 07:05:04 GMT your computer crashed
crash dump file: C:\Windows\Minidump\080612-23234-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x2228AF)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFFFFF830698AF, 0xFFFFFFFF8B11F618, 0xFFFFFFFF8B11F1F0)
Error: SYSTEM_THREAD_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 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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Fri 03.08.2012 10:16:34 GMT your computer crashed
crash dump file: C:\Windows\Minidump\080312-18140-01.dmp
This was probably caused by the following module: cdd.dll (cdd+0xB7C7)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF82EA7F01, 0xFFFFFFFF92B74A94, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\cdd.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Canonical Display Driver
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 which cannot be identified at this time.


On Wed 01.08.2012 10:47:39 GMT your computer crashed
crash dump file: C:\Windows\Minidump\080112-20109-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x467EB)
Bugcheck code: 0xC5 (0xE190, 0x2, 0x0, 0xFFFFFFFF82F35795)
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 Sun 29.07.2012 13:11:12 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072912-19046-01.dmp
This was probably caused by the following module: cdd.dll (cdd+0xB7C7)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF82E9DF01, 0xFFFFFFFFA580BA94, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\cdd.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Canonical Display Driver
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 which cannot be identified at this time.


On Fri 27.07.2012 03:18:27 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072712-19921-01.dmp
This was probably caused by the following module: eamonm.sys (eamonm+0x1618A)
Bugcheck code: 0xC5 (0xE008, 0x2, 0x0, 0xFFFFFFFF82F39795)
Error: DRIVER_CORRUPTED_EXPOOL
file path: C:\Windows\system32\drivers\eamonm.sys
product: ESET Smart Security
company: ESET
description: Amon monitor
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.
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: eamonm.sys (Amon monitor, ESET).
Google query: eamonm.sys ESET DRIVER_CORRUPTED_EXPOOL




On Wed 25.07.2012 13:03:27 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072512-18078-01.dmp
This was probably caused by the following module: cdd.dll (cdd+0xB7C7)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF82E94F01, 0xFFFFFFFF9ED70A94, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\cdd.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Canonical Display Driver
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 which cannot be identified at this time.


On Tue 24.07.2012 12:35:32 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072412-20593-01.dmp
This was probably caused by the following module: nvhda32v.sys (nvhda32v+0x14593)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0x0, 0xFFFFFFFF8B003B6C, 0xFFFFFFFF8B003750)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\nvhda32v.sys
product: NVIDIA HDMI Audio Driver
company: NVIDIA Corporation
description: NVIDIA HDMI Audio Driver
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.
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: nvhda32v.sys (NVIDIA HDMI Audio Driver, NVIDIA Corporation).
Google query: nvhda32v.sys NVIDIA Corporation SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M




On Mon 16.07.2012 09:13:57 GMT your computer crashed
crash dump file: C:\Windows\Minidump\071612-18125-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x467EB)
Bugcheck code: 0xA (0x9E30, 0x2, 0x0, 0xFFFFFFFF828222AA)
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.


This is what i get in WhoCrased


==================================================
Dump File : 082612-18828-01.dmp
Crash Time : 26.08.2012 10:42:16
Bug Check String : SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000007e
Parameter 1 : 0xc0000005
Parameter 2 : 0x834784fd
Parameter 3 : 0x80786888
Parameter 4 : 0x80786460
Caused By Driver : ntkrnlpa.exe
Caused By Address : ntkrnlpa.exe+2224fd
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16988 (win7_gdr.120401-1505)
Processor : 32-bit
Crash Address : ntkrnlpa.exe+2224fd
Stack Address 1 : ntkrnlpa.exe+2223db
Stack Address 2 : ntkrnlpa.exe+209451
Stack Address 3 : ntkrnlpa.exe+1a38f6
Computer Name :
Full Path : C:\Windows\Minidump\082612-18828-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7600
Dump File Size : 137.408
==================================================
This is in BlueScreenView. This is what i got today


My System SpecsSystem Spec
.
26 Aug 2012   #2
MasterZhen

Windows 7 Ultimate 32 bit
 
 
Minidumps

Pls take a look.
My System SpecsSystem Spec
26 Aug 2012   #3
centaur78

Windows 7 ultimate x64
 
 

Hi

First of all post all the files using this tool

then use this tool to update your system specs if you have not correctly done it
My System SpecsSystem Spec
.

26 Aug 2012   #4
MasterZhen

Windows 7 Ultimate 32 bit
 
 

take a look up....i post them with sf
My System SpecsSystem Spec
26 Aug 2012   #5
centaur78

Windows 7 ultimate x64
 
 

well it has only the dumps....

i need all other files as well
My System SpecsSystem Spec
26 Aug 2012   #6
MasterZhen

Windows 7 Ultimate 32 bit
 
 
Here

here are all
My System SpecsSystem Spec
26 Aug 2012   #7
MasterZhen

Windows 7 Ultimate 32 bit
 
 

and the system info tool isnt that great,i mean it doesnt show my RAM ,motherboard,etc Just CPU and sound,disk info,network and OS
My System SpecsSystem Spec
26 Aug 2012   #8
centaur78

Windows 7 ultimate x64
 
 

ok

1. As far you specs are concerned ... you only have a Nvidia graphics ..... then why is it that you have also installed ATI drivers ??? remove it .

2. Why do you have Windows Defender and NOD32..starting at the same time... Disable windows defender service...

3. the temps were high when you system shutdown

Quote:
Event[34973]:
Log Name: System
Source: Microsoft-Windows-Kernel-Power
Date: 2012-08-24T06:09:40.312
Event ID: 89
Task: N/A
Level: Information
Opcode: Info
Keyword: N/A
User: S-1-5-18
User Name: NT AUTHORITY\SYSTEM
Computer: Zhen-PC
Description:
ACPI thermal zone ACPI\ThermalZone\THRM has been enumerated.
_PSV = 395K
_TC1 = 4
_TC2 = 3
_TSP = 6000ms
_AC0 = 395K
_AC1 = 0K
_AC2 = 0K
_AC3 = 0K
_AC4 = 0K
_AC5 = 0K
_AC6 = 0K
_AC7 = 0K
_AC8 = 0K
_AC9 = 0K
_CRT = 397K
_HOT = 0K
_PSL - see event data.
_PSV = Temperature to start passive cooling by throttling down CPU, etc= 395K = 121.85 deg c
_AC0 = Temperatures at which to switch to the corresponding active cooling level. The lower the _ACx value, the higher the cooling power = 395K = 121.85 deg c
_CRT = Temperature to start critical shutdown (S5) = 397K = 123.85 deg C

so system shutdown at the this critical temp..... Please clean the system of dust

Let me know
My System SpecsSystem Spec
26 Aug 2012   #9
MasterZhen

Windows 7 Ultimate 32 bit
 
 

The Ati drivers i removed then....see that is an older dump.I will disable the windows defender and i cleaned my pc of dust ...didnt had to much dust and it's like brand new.I think the temp think is when i left my pc open like 24 h + and shut it down after.The temp in my room,in summer, is high :P
My System SpecsSystem Spec
26 Aug 2012   #10
centaur78

Windows 7 ultimate x64
 
 

i'm not sure when u uninstalled it but u will find it the latest system logs
Quote:
Event[34985]:
Log Name: System
Source: Service Control Manager
Date: 2012-08-24T06:09:48.250
Event ID: 7036
Task: N/A
Level: Information
Opcode: N/A
Keyword: Classic
User: N/A
User Name: N/A
Computer: Zhen-PC
Description:
The Ati External Event Utility service entered the running state.
My System SpecsSystem Spec
Reply

 Help! Bsod




Thread Tools Search this Thread
Search this Thread:

Advanced Search



Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd

All times are GMT -5. The time now is 01:25.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App