Random bsod

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

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Fri 5/9/2014 5:53:18 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\050914-56363-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x4211)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF8800ABFDE88, 0xFFFFF8800ABFD6E0, 0xFFFFF800030B9622)
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 Fri 5/9/2014 5:53:18 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x4211)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF8800ABFDE88, 0xFFFFF8800ABFD6E0, 0xFFFFF800030B9622)
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 Thu 5/8/2014 8:05:38 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\050814-15771-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xA6622)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF800030C5622, 0xFFFFF880035E0598, 0xFFFFF880035DFDF0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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 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 Thu 5/8/2014 4:29:02 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\050814-16224-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B90)
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 which cannot be identified at this time.


On Thu 5/8/2014 3:23:41 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\050814-17784-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B90)
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 which cannot be identified at this time.


On Wed 5/7/2014 7:10:30 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\050714-26847-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xA6622)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80003105622, 0xFFFFF8800769F748, 0xFFFFF8800769EFA0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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 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 Thu 5/1/2014 1:16:32 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\050114-27892-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xA6622)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF800030AF622, 0xFFFFF880035E0598, 0xFFFFF880035DFDF0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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 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 Tue 4/22/2014 7:28:50 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\042214-16816-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xA6622)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80002F08622, 0xFFFFF880039135C8, 0xFFFFF88003912E20)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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 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 Mon 4/7/2014 6:55:01 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\040714-15787-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xA6622)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80002EB0622, 0xFFFFF880009A9868, 0xFFFFF880009A90C0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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 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 Wed 4/2/2014 12:25:58 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\040214-18610-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xA6622)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80002EF4622, 0xFFFFF880009A9868, 0xFFFFF880009A90C0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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 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 3/30/2014 2:37:40 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\033014-17784-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xA6622)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80002F06622, 0xFFFFF880035E06D8, 0xFFFFF880035DFF30)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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 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 Thu 3/27/2014 2:34:34 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\032714-15428-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B90)
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 which cannot be identified at this time.


On Tue 3/25/2014 12:38:38 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\032514-18844-01.dmp
This was probably caused by the following module: Unknown (0xFFFFF80002E87BC0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002EB8622, 0xFFFFF8800AEF6FC0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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.
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: Unknown .
Google query: Unknown SYSTEM_SERVICE_EXCEPTION




On Wed 3/5/2014 5:29:31 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\030514-19297-01.dmp
This was probably caused by the following module: Unknown (0xFFFFF80002E7BB90)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
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.
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: Unknown .
Google query: Unknown KMODE_EXCEPTION_NOT_HANDLED




On Wed 2/26/2014 8:21:24 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\022614-15678-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xA6622)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80002EF2622, 0xFFFFF880009A9758, 0xFFFFF880009A8FB0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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 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.

Can someone tell me why my post is not getting any attention? Did I do something wrong? I followed the instructions.
Thanks!

I appreciate your help, I will try those utilities and let you all know what happens. In the meantime here is a little more background.

In my office I have approximately 20 workstations running basically the same software and hardware. That is why it is so odd that only a few of the machines are having this issue. So far my best fix has been to format and re-install. The machines range from custom built machines to stock Dell Precision workstations. I assumed that video card at first as well but I upgraded my NVIDIA QFX 1800 to the ATI and the problem remained. Some of the workstations that are having problems are running NVIDIA cards. I will keep looking for commonalities.
I am attaching “dm log collector.exe” scans from two other computers. Just for reference.
SERVER 3 is a Dell Precision 380 running Windows Home Server 2011 – It is basically running as a NAS that I use for backup.
CAD23-64BIT is a Dell Precision 390 running Windows 7 Pro 64bit – It is a workstation used for mostly clerical work no graphic heavy work at all.

2WRofGeorgia said:

Hello,
I have several machines in my office that are generating random BSOD’s. I am hoping you can help. I am going to use my workstation (13-2) as my first example. You should be aware that the problems is on machines running Windows XP, Windows 7, and Windows Home Server 2011.
I have noticed I get the BSOD’s on my workstation when doing tasks that require a lot of processing power. I get them a lot when attempting to render in Autodesk REVIT 2014. I do however still get them randomly when performing less intensive tasks.
I built this machine about six months ago, have built three others with exactly the same components. So far they have not had the same issues.
I am confident it is a driver issue but I am hoping you all can help me isolate which one. I have checked and they all are up to date.

I want to thank you in advance for any help you can provide.

On this one here, there are quite a few pointing to your video driver,

Code:

Unable to load image \SystemRoot\system32\DRIVERS\atikmdag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
 atikmdag+0x4d179

From March of 2012,

Code:

start             end                 module name
fffff880`04a66000 fffff880`054bc000   atikmdag T (no symbols)           
    Loaded symbol image file: atikmdag.sys
    Image path: \SystemRoot\system32\DRIVERS\atikmdag.sys
    Image name: atikmdag.sys
    Timestamp:        Fri Mar 09 10:30:41 2012 (4F5A4C51)
    CheckSum:         00A06E49
    ImageSize:        00A56000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

(Version 8.14.1.6237)

Using the info in your post I do find a newer driver, (Version 9.003.3)

AMD FirePro? Professional Graphics Certified Applications

A couple of your Bugcheck codes also point to Disk corruption, Disk/Drive Failure so running the SFC and Disk Check recommended by ICit2lol would be wise.

Option two, Disk Check chkdsk /r

SFC /SCANNOW Command - System File Checker

I'll check your other two machines in a minute.

2WRofGeorgia said:

I appreciate your help, I will try those utilities and let you all know what happens. In the meantime here is a little more background.

In my office I have approximately 20 workstations running basically the same software and hardware. That is why it is so odd that only a few of the machines are having this issue. So far my best fix has been to format and re-install. The machines range from custom built machines to stock Dell Precision workstations. I assumed that video card at first as well but I upgraded my NVIDIA QFX 1800 to the ATI and the problem remained. Some of the workstations that are having problems are running NVIDIA cards. I will keep looking for commonalities.
I am attaching “dm log collector.exe” scans from two other computers. Just for reference.
SERVER 3 is a Dell Precision 380 running Windows Home Server 2011 – It is basically running as a NAS that I use for backup.
CAD23-64BIT is a Dell Precision 390 running Windows 7 Pro 64bit – It is a workstation used for mostly clerical work no graphic heavy work at all.

On CAD23 your dumps aren't pointing to any specific driver (I only checked the March,April, May Dumps) all but one are pointing to memory, I would test the RAM in that machine,

   Information

MemTest86+

Run a minimum of 8 passes, preferably overnight, or until errors occur using MemTest86+.

Use this tutorial to help you use MemTest86+:
RAM - Test with MemTest86+

The other was disk corruption from March 19, so you may want to run the chkdsk on that as well.

*********************************************************************

The Server is pretty much the same, memory management and no specific driver pointed to.

And that is with driver verifier enabled,

Code:

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041284, A PTE or the working set list is corrupt.
Arg2: 000007fffffdb001
Arg3: 0000000000000000
Arg4: fffff70001080000

Debugging Details:
------------------


BUGCHECK_STR:  0x1a_41284

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

There are others that can dig deeper in these but for the time being I would test your RAM to make sure.

Please take Derekimo's advice first but I have a hunch.
If updating the driver doesn't work and the hardware tests all pass then I would like you to switch to Kernel Memory Dumps as it will give us a bigger insight as to what's happening.
Follow these instructions on how to change it.

Dump Files - Configure Windows to Create on BSOD

Once changed and you receive a BSOD upload the file in C:/Windows/memory.dmp to a program like OneDrive then post the download link here.

THANKS EVERYONE!
I will get to work on these solutions asap!