Random BSOD - inconsistent bug check numbers

jutley · 22 Oct 2014

I have a fairly new HP Z420 workstation with an i7-4770 and 16 GB of RAM running Win 7 Pro. I am having random BSODs over the past month and the bug check numbers are not always the same. I have run the DM log collector and attached the file here.

Thanks in advance for any help!

Justin

essenbe · 23 Oct 2014

Hello, jutley and Welcome to Seven Forums. I will try to help you with this problem. I haven't looked at all the dump files, I only looked at the last 5. What I would like you to do is fill out your system specs as detailed as possible. Sometimes we need to look up a component and need the Manufacturer and model number to do that. Hopefully this will help.

Please fill out your System Specs

Information

Your System Specs will help us to help you, and doing it in this manner will make them available to all helpers in every post and keep us from hunting for them. We ask that you fill them out in as much detail as possible including Desktop or Laptop, Model number if it is an OEM computer and all components with the Manufacturer and Model number if possible.

If you will go to your last post and click the 'System Specs' in the bottom left of the post, you will find a link to update your system specs. Please fill those out in as much detail as possible, making sure to click save at the bottom of the page. If you would like to know what we would like, you can click 'My System Specs' at the bottom left of this post to see mine. If you do not know what your components are, this will help you accomplish this task. System Info - See Your System Specs

This is what the dump files listed.

Code:

Ntfs
start             end                 module name
fffff880`03405000 fffff880`035ae000   Ntfs       (pdb symbols)          c:\symcache\ntfs.pdb\CF8C94B9CD6A4D5697235BA5374DA2532\ntfs.pdb
    Loaded symbol image file: Ntfs.sys
    Mapped memory image file: c:\symcache\Ntfs.sys\52E1BE8A1a9000\Ntfs.sys
    Image path: \SystemRoot\System32\Drivers\Ntfs.sys
    Image name: Ntfs.sys
    Timestamp:        Thu Jan 23 19:14:50 2014 (52E1BE8A)
    CheckSum:         0019F25D
    ImageSize:        001A9000
    File version:     6.1.7601.18378
    Product version:  6.1.7601.18378
    File flags:       0 (Mask 3F)
    File OS:          40004 NT Win32
    File type:        3.7 Driver
    File date:        00000000.00000000
    Translations:     0409.04b0
    CompanyName:      Microsoft Corporation
    ProductName:      Microsoft® Windows® Operating System
    InternalName:     ntfs.sys
    OriginalFilename: ntfs.sys
    ProductVersion:   6.1.7601.18378
    FileVersion:      6.1.7601.18378 (win7sp1_gdr.140123-1436)
    FileDescription:  NT File System Driver
    LegalCopyright:   © Microsoft Corporation. All rights reserved.

That is a driver from Windows Update which is for the file system on your hard drive

Code:

Use !analyze -v to get detailed debugging information.
BugCheck 1E, {ffffffffc0000005, fffff8800a703980, 0, 0}
*** WARNING: Unable to verify timestamp for EX64.SYS
*** ERROR: Module load completed but symbols could not be loaded for EX64.SYS
Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+257 )
Followup: Pool_corruption
---------
0: kd> lmvm EX64
start             end                 module name
fffff880`06c74000 fffff880`06e82000   EX64     T (no symbols)           
    Loaded symbol image file: EX64.SYS
    Image path: \??\C:\PROGRA~3\Symantec\DEFINI~1\VIRUSD~1\20141022.003\EX64.SYS
    Image name: EX64.SYS
    Timestamp:        Mon Aug 11 05:19:41 2014 (53E898BD)
    CheckSum:         0020E921
    ImageSize:        0020E000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
Norton Anti-Virus

That is your Norton anti Virus. In the 5 dumps I looked at, it showed up as the cause of the crash twice. Norton is a know cause of BSODs and I would recommend you uninstall it and use the Norton Removal Tool and replace it with MSE (Microsoft Security Essentials - Microsoft Windows).

I also found

Code:

DAMDrv64
start             end                 module name
fffff880`094e6000 fffff880`094f9000   DAMDrv64 T (no symbols)           
    Loaded symbol image file: DAMDrv64.sys
    Image path: \SystemRoot\system32\DRIVERS\DAMDrv64.sys
    Image name: DAMDrv64.sys
    Timestamp:        Mon Oct 07 06:18:51 2013 (5252989B)
    CheckSum:         000152B2
    ImageSize:        00013000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

which is the HP ProtectTools Device Access Manager, which I am not familiar with, but do know that HP puts a lot of junkware on their computers. Most enthusiasts do a clean install to get rid of it and use this tutorial to get a perfect install, Clean Reinstall - Factory OEM Windows 7 Which is something you may want to consider doing.

Please remove the Norton Anti Virus and replace it and see if your results are any better. Also, make sure your Windows is fully updated through Windows Update. When you compete this please open a elevated command prompt ( click start, type cmd in the search box, right click on the cmd entry and select run as administrator) in the black box that opens, copy/paste sfc /scannow. If you decide to type it, notice the space between the sfc and the /. It is a system file checker which will scan your system files and attempt to correct any missing or corrupt files. What we want are the results to say windows found no integrity violations. If it says files were found but could not be repaired, close the box, reboot and run it again, after opening the administrative command prompt. You may have to reboot and run it three times for it to repair all system files. If it can't repair them after 3 reboots, let us know.