(Mostly) ntoskrnl.exe BSOD

[lrizzi1]

Hello, I would need some help about the analysis of a random BsoD.

It is TOTALLY random, on a fresh Windows 7 installation.

In the following is attached the report from the utility "whocrashed", which just does a recap of all the .dmp files. I have no idea on how to analyze it. Any suggestion?

It seems like 90% of the crashes are caused by "ntoskrnl.exe".

It might be a RAM issue? (I have run Memtest86, 10+ flawless runs)

My OS is Win7 Home, and the RAMs are running at the correct voltage.

Thanks a lot in advance for your help!

On Sun 18/07/2010 09:00:58 your computer crashed
This was likely caused by the following module: atikmpag.sys
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF88003EDE661, 0xFFFFF8800937F900, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
Dump file: C:\Windows\Minidump\071810-28657-01.dmp
file path: C:\Windows\system32\drivers\atikmpag.sys
product: AMD driver
company: Advanced Micro Devices, Inc.
description: AMD multi-vendor Miniport Driver



On Tue 29/06/2010 20:52:26 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x50 (0xFFFFDA8006103618, 0x0, 0xFFFFF80002F8D42E, 0x7)
Error: PAGE_FAULT_IN_NONPAGED_AREA
Dump file: C:\Windows\Minidump\062910-34242-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Tue 22/06/2010 17:18:22 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x50 (0xFFFFD8A0089F1000, 0x1, 0xFFFFF80002FA24F8, 0x7)
Error: PAGE_FAULT_IN_NONPAGED_AREA
Dump file: C:\Windows\Minidump\062210-28298-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Sat 05/06/2010 07:24:17 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x50 (0xFFFFB900C0896EAF, 0x0, 0xFFFFF80002A5954C, 0x7)
Error: PAGE_FAULT_IN_NONPAGED_AREA
Dump file: C:\Windows\Minidump\060510-17784-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Sat 22/05/2010 08:28:15 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0xA (0xFFFFBA8006139090, 0x2, 0x1, 0xFFFFF80002A95955)
Error: IRQL_NOT_LESS_OR_EQUAL
Dump file: C:\Windows\Minidump\052210-20935-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Tue 27/04/2010 11:12:02 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0xA (0xFFFFBA8003D2CDF8, 0x2, 0x1, 0xFFFFF80002B29A5F)
Error: IRQL_NOT_LESS_OR_EQUAL
Dump file: C:\Windows\Minidump\042710-16614-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Tue 13/04/2010 16:31:42 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x50 (0xFFFFBA8005DE6CC8, 0x0, 0xFFFFF80002AEFCF0, 0x7)
Error: PAGE_FAULT_IN_NONPAGED_AREA
Dump file: C:\Windows\Minidump\041310-18298-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Sun 11/04/2010 11:45:51 your computer crashed
This was likely caused by the following module: ntfs.sys
Bugcheck code: 0x50 (0xFFFFB8A016CCF518, 0x1, 0xFFFFF880012FC732, 0x7)
Error: PAGE_FAULT_IN_NONPAGED_AREA
Dump file: C:\Windows\Minidump\041110-25864-01.dmp
file path: C:\Windows\system32\drivers\ntfs.sys
product: Sistema operativo Microsoft® Windows®
company: Microsoft Corporation
description: Driver file system NT
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Sun 11/04/2010 09:12:55 your computer crashed
This was likely caused by the following module: atikmdag.sys
Bugcheck code: 0x50 (0xFFFFD8A00BCFEA0C, 0x0, 0xFFFFF880040C7296, 0x7)
Error: PAGE_FAULT_IN_NONPAGED_AREA
Dump file: C:\Windows\Minidump\041110-16598-01.dmp
file path: C:\Windows\system32\drivers\atikmdag.sys
product: ATI Radeon Family
company: ATI Technologies Inc.
description: ATI Radeon Kernel Mode Driver



On Sun 11/04/2010 08:34:10 your computer crashed
This was likely caused by the following module: ntfs.sys
Bugcheck code: 0x50 (0xFFFFF0A000E53A10, 0x1, 0xFFFFF880012F7404, 0x7)
Error: PAGE_FAULT_IN_NONPAGED_AREA
Dump file: C:\Windows\Minidump\041110-18642-01.dmp
file path: C:\Windows\system32\drivers\ntfs.sys
product: Sistema operativo Microsoft® Windows®
company: Microsoft Corporation
description: Driver file system NT
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Mon 29/03/2010 19:46:18 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x50 (0xFFFFBA8006362060, 0x0, 0xFFFFF80002BC441D, 0x7)
Error: PAGE_FAULT_IN_NONPAGED_AREA
Dump file: C:\Windows\Minidump\032910-15958-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Tue 23/03/2010 22:00:03 your computer crashed
This was likely caused by the following module: ntfs.sys
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF88009129CF8, 0xFFFFF88009129550, 0xFFFFF80002D945CD)
Error: NTFS_FILE_SYSTEM
Dump file: C:\Windows\Minidump\032310-15818-01.dmp
file path: C:\Windows\system32\drivers\ntfs.sys
product: Sistema operativo Microsoft® Windows®
company: Microsoft Corporation
description: Driver file system NT
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Sun 14/03/2010 21:24:12 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002A51F4F, 0xFFFFF880087756B0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
Dump file: C:\Windows\Minidump\031410-17518-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Sun 14/03/2010 10:00:27 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1A (0x782, 0xFFFFFA8005D8E810, 0xFFFFF98006580000, 0xFFFFF8A0043CA620)
Error: MEMORY_MANAGEMENT
Dump file: C:\Windows\Minidump\031410-17596-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Sat 06/03/2010 16:18:39 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x50 (0xFFFFF28003B7CD08, 0x1, 0xFFFFF80002A684AE, 0x7)
Error: PAGE_FAULT_IN_NONPAGED_AREA
Dump file: C:\Windows\Minidump\030610-28407-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Tue 02/03/2010 20:45:22 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0xC2 (0x7, 0x1097, 0x0, 0xFFFFFA8003CD5050)
Error: BAD_POOL_CALLER
Dump file: C:\Windows\Minidump\030210-15163-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Mon 01/03/2010 20:40:29 your computer crashed
This was likely caused by the following module: ntfs.sys
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF88007962E48, 0xFFFFF880079626A0, 0xFFFFF80002D35F2A)
Error: NTFS_FILE_SYSTEM
Dump file: C:\Windows\Minidump\030110-17128-01.dmp
file path: C:\Windows\system32\drivers\ntfs.sys
product: Sistema operativo Microsoft® Windows®
company: Microsoft Corporation
description: Driver file system NT
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Mon 01/03/2010 20:01:05 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x50 (0xFFFFF6DC50011A60, 0x0, 0xFFFFF80002AEDC9E, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
Dump file: C:\Windows\Minidump\030110-22510-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Sat 27/02/2010 13:24:06 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0xA (0xFFFFBA8005F2B2A8, 0x2, 0x1, 0xFFFFF80002B31ABF)
Error: IRQL_NOT_LESS_OR_EQUAL
Dump file: C:\Windows\Minidump\022710-18002-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Thu 11/02/2010 21:19:42 your computer crashed
This was likely caused by the following module: fltmgr.sys
Bugcheck code: 0x50 (0xFFFFB8A010EF51E0, 0x0, 0xFFFFF880010B2366, 0x7)
Error: PAGE_FAULT_IN_NONPAGED_AREA
Dump file: C:\Windows\Minidump\021110-15600-01.dmp
file path: C:\Windows\system32\drivers\fltmgr.sys
product: Sistema operativo Microsoft® Windows®
company: Microsoft Corporation
description: Gestione filtri file system Microsoft
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.

 

[Jonathan_King]

Please follow these directions: http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html

 

[lrizzi1]

Ok, here it is the required attachement.

Thanks again for your assistance!

My Windows 7 is 64bit, full retail version. The hardware is about 8 months old! I have also updated my system's spec.

 

[Jonathan_King]

Thanks.

First, I suggest updating your graphics driver. Is is blamed by one crash.

If that doesn't work, please remove Avira and replace it with Microsoft Security Essentials.

Here is the removal tool for Avira: http://www.avira.com/en/documents/utils/av7_tools/en/avuninstXPeng.zip

Here's a link to MSE: http://www.microsoft.com/security_essentials

If that still doesn't work, enable driver verifier: http://www.sevenforums.com/crash-lo...-driver-verifier-identify-issues-drivers.html

Of course, you can upload the new dumps at any time and we'll take a look.

...Summary of the Dumps:

[font=lucida console]
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sat May 22 04:22:43.400 2010 (UTC - 4:00)
System Uptime: 0 days 1:02:23.102
BugCheck A, {ffffba8006139090, 2, 1, fffff80002a95955}
Probably caused by : ntkrnlmp.exe ( nt!ExpWorkerFactoryCompletionPacketRoutine+6d )
BUGCHECK_STR:  0xA
PROCESS_NAME:  svchost.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Tue Apr 27 07:07:15.937 2010 (UTC - 4:00)
System Uptime: 0 days 3:41:22.248
BugCheck A, {ffffba8003d2cdf8, 2, 1, fffff80002b29a5f}
Probably caused by : memory_corruption ( nt!MiIdentifyPfn+26f )
BUGCHECK_STR:  0xA
PROCESS_NAME:  svchost.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Tue Apr 13 12:06:55.902 2010 (UTC - 4:00)
System Uptime: 0 days 9:05:12.603
BugCheck 50, {ffffba8005de6cc8, 0, fffff80002aefcf0, 7}
Probably caused by : memory_corruption ( nt!MiLocateAddress+40 )
BUGCHECK_STR:  0x50
PROCESS_NAME:  msnmsgr.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sun Jul 18 04:58:54.635 2010 (UTC - 4:00)
System Uptime: 0 days 1:29:48.363
BugCheck 3B, {c0000005, fffff88003ede661, fffff8800937f900, 0}
Probably caused by : atikmpag.sys ( atikmpag+9661 )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  League of Lege
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Tue Jun 29 16:50:00.049 2010 (UTC - 4:00)
System Uptime: 0 days 2:43:19.375
BugCheck 50, {ffffda8006103618, 0, fffff80002f8d42e, 7}
Probably caused by : ntkrnlmp.exe ( nt!ObpCloseHandleTableEntry+3e )
BUGCHECK_STR:  0x50
PROCESS_NAME:  svchost.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Tue Jun 22 13:13:55.823 2010 (UTC - 4:00)
System Uptime: 0 days 0:07:19.135
BugCheck 50, {ffffd8a0089f1000, 1, fffff80002fa24f8, 7}
Probably caused by : memory_corruption ( nt!MiRelocateImageAgain+48 )
BUGCHECK_STR:  0x50
PROCESS_NAME:  svchost.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Fri Jun  4 15:48:37.348 2010 (UTC - 4:00)
System Uptime: 0 days 4:10:22.049
BugCheck 50, {ffffb900c0896eaf, 0, fffff80002a5954c, 7}
Probably caused by : win32k.sys ( win32k!DestroyClass+18c )
BUGCHECK_STR:  0x50
PROCESS_NAME:  iexplore.exe[/font]

 

[lrizzi1]

Ok, I'll try to implement your suggestion. Do you really think it could be an issue caused by AVIRA? Does it commonly cause troubles with Windows 7?

 

[Jonathan_King]

Anti-virus programs are notorious for causing problems in Windows 7 and Vista. There are few programs I trust as a result. ESET Nod32 is a great paid program, but I honestly don't see a need for it. Free programs work well enough.

Microsoft Security Essentials is the other AV I trust. Made by Microsoft (hence the name!), it is well-designed for Windows.

In direct answer to your question, I have seen many BSODs with Avira as the cause.

 

[lrizzi1]

Thanks for the fast answer. I'll uninstall AVIRA and give a chance to MSE as an alternative! I'll keep you posted with any further update : )

 

[Jonathan_King]

Sounds good. I hope it works!

 

[lrizzi1]

There we are, it crashed again

Then, we can safely rule out Avira (still I'll keep using microsoft essential for safety)

Any other idea, Jonathan_King?

 

[Jonathan_King]

It appears you did not run the program as administrator.

No worries, just upload the dumps manually: http://www.sevenforums.com/tutorials/83172-dump-files-upload-seven-forums.html

 

[lrizzi1]

Dumps attached! Thanks again!

 

[Jonathan_King]

I wonder if it is caused by your video card.

[FONT=lucida console]
BugCheck A, {0, 2, 1, fffff80002c7dab8}
Probably caused by : memory_corruption ( nt!MiRemoveUnusedSubsection+88 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck 3B, {c0000005, fffff88003ede661, fffff8800937f900, 0}
[COLOR=Red]Probably caused by : atikmpag.sys ( atikmpag+9661 )[/COLOR]
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck 50, {ffffda8006103618, 0, fffff80002f8d42e, 7}
Probably caused by : ntkrnlmp.exe ( nt!ObpCloseHandleTableEntry+3e )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck 50, {ffffd8a0089f1000, 1, fffff80002fa24f8, 7}
Probably caused by : memory_corruption ( nt!MiRelocateImageAgain+48 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck 50, {ffffb900c0896eaf, 0, fffff80002a5954c, 7}
[COLOR=Red]Probably caused by : win32k.sys ( win32k!DestroyClass+18c )[/COLOR]
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck 50, {ffffba8006362060, 0, fffff80002bc441d, 7}
[COLOR=Red]Probably caused by : dxgkrnl.sys ( dxgkrnl!DXGDEVICE::DestroyAllocations+72d )[/COLOR]
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck 24, {1904fb, fffff88007962e48, fffff880079626a0, fffff80002d35f2a}
Probably caused by : Ntfs.sys ( Ntfs!NtfsCommonCleanup+1f55 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
[/FONT]

The text in Red is only what is evidence in my mind. The other ones do not suggest video card in particular, but in light of a bad card, they don't surprise me at all.

I believe there was a new ATI video card driver released in either June or July. I see you are using the April version. Please install the latest one: Graphics Drivers & Software

Hopefully the driver change will take care of it. If not, do you have another video card you can test with? Perhaps one from another computer?

 

[lrizzi1]

I'll try to do as you suggest.

I'll keep you posted!

 

[lrizzi1]

Sadly, it happened again. There it is the dump file for this last crash.

Thanks again for the support.

 

[Jonathan_King]

I see you are using the latest drivers for your ATI card, but still, the dump blames dxgmms1.sys.

Try this tutorial: http://www.sevenforums.com/tutorials/100356-video-card-stress-test-furmark.html

Be sure to report the maximum temperature it achieves.

...Summary of the Dumps:

[font=lucida console]
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sat Aug 14 10:34:28.245 2010 (UTC - 4:00)
System Uptime: 0 days 6:06:29.572
BugCheck 1000007E, {ffffffffc0000005, fffff88004020cee, fffff88003c0d6a8, fffff88003c0cf10}
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+22 )
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
[/font]

 

[lrizzi1]

The maximum temperature achieved is 77°C, which should be normal for a Radeon HD 4890 under stress, according to most online reviews.

And, of course, no artifacts appeared.

 

[Jonathan_King]

Try unplugging your video card, and blowing the dust out of the slot. Then attach it again, being careful to seat it firmly.

You may also try the card in another machine. If you have access to another card (a friend, another computer), test it in your machine.

 

[lrizzi1]

I can assure you that the video card is perfectly clean. Do you believe that 77°C achieved under full load is too hot?

According to some reviews I found online, the full load temperatures for HD 4890 range from 70° to 80°.

 

[Jonathan_King]

No, it sounds like heat is not the problem.

Could you try another video card?

 

[lrizzi1]

I'll try another Video Card as soon as possible. In the meanwhile, another crash occourred, the dump is attached! Thanks again