Multiple BSOD, running idle

Page 1 of 2 12 LastLast

  1. Posts : 5
    Windows 7 HP 64-Bit
       #1

    Multiple BSOD, running idle


    Ok, here goes.

    Specifications:
    Motherboard: ASUS P8Z68-V PRO/GEN3
    BIOS: Ver. 3603 I think...
    CPU: Intel Core i5 2500-K 3.30Ghz
    Memory: Corsair Vengeance DDR3 PC3-10700H 1600Mhz
    Video: Onboard (Driver is up to date)
    PSU: Antec 750W
    HDD: Seagate 500GB ST3500
    WD 500GB x2
    Here is the list of BSOD's

    041713-27705-01.dmp 4/17/2013 10:30:28 AM NTFS_FILE_SYSTEM 0x00000024 00000000`001904fb fffff880`07e9b5c8 fffff880`07e9ae20 fffff800`02e9892c Ntfs.sys Ntfs.sys+48d8
    x64 ntoskrnl.exe+75c00
    C:\Windows\Minidump\041713-27705-01.dmp 4 15 7601 281,544

    041613-27066-01.dmp 4/16/2013 12:01:33 PM SYSTEM_SERVICE_EXCEPTION 0x0000003b 00000000`c0000005 fffff800`0331a09e fffff880`03b246c0 00000000`00000000 hal.dll hal.dll+462f
    x64 ntoskrnl.exe+75c00
    C:\Windows\Minidump\041613-27066-01.dmp 4 15 7601 281,544

    041313-37830-01.dmp 4/13/2013 7:27:43 PM MEMORY_MANAGEMENT 0x0000001a 00000000`00041287 00000000`000000f2 00000000`00000000 00000000`00000000 ntoskrnl.exe ntoskrnl.exe+75c00 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7601.18113 (win7sp1_gdr.130318-1533)
    x64 ntoskrnl.exe+75c00
    C:\Windows\Minidump\041313-37830-01.dmp 4 15 7601 281,544

    041113-22760-01.dmp 4/11/2013 12:11:58 PM MEMORY_MANAGEMENT 0x0000001a 00000000`00003452 00000000`01711000 fffff700`01082058 b7a00001`9ef4b0c8 ntoskrnl.exe ntoskrnl.exe+75c40 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7601.18113 (win7sp1_gdr.130318-1533)
    x64 ntoskrnl.exe+75c40
    C:\Windows\Minidump\041113-22760-01.dmp 4 15 7601 281,544

    040313-28267-01.dmp 4/3/2013 5:34:14 AM IRQL_NOT_LESS_OR_EQUAL 0x0000000a 00000000`00000001 00000000`00000002 00000000`00000001 fffff800`02e8ca7c ntoskrnl.exe ntoskrnl.exe+75c40 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7601.18113 (win7sp1_gdr.130318-1533)
    x64 ntoskrnl.exe+75c40
    C:\Windows\Minidump\040313-28267-01.dmp 4 15 7601 281,824

    040113-33446-01.dmp 4/1/2013 2:22:26 AM KMODE_EXCEPTION_NOT_HANDLED 0x0000001e ffffffff`c0000005 fffff800`0300f147 00000000`00000001 00000000`00000008 Ntfs.sys Ntfs.sys+a4a20
    x64 ntoskrnl.exe+75c40
    C:\Windows\Minidump\040113-33446-01.dmp 4 15 7601 281,824

    033113-42135-01.dmp 3/31/2013 11:12:47 AM NTFS_FILE_SYSTEM 0x00000024 00000000`001904fb fffff880`0892a208 fffff880`08929a60 fffff880`012ef64f Ntfs.sys Ntfs.sys+a864f
    x64 ntoskrnl.exe+75c40
    C:\Windows\Minidump\033113-42135-01.dmp 4 15 7601 281,824

    032913-38048-01.dmp 3/29/2013 6:56:37 PM MEMORY_MANAGEMENT 0x0000001a 00000000`00005003 fffff700`01080000 00000000`0000055e 00000560`00000a6c ntoskrnl.exe ntoskrnl.exe+75c40 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7601.18113 (win7sp1_gdr.130318-1533)
    x64 ntoskrnl.exe+75c40
    C:\Windows\Minidump\032913-38048-01.dmp 4 15 7601 281,824

    032713-29562-01.dmp 3/27/2013 4:57:43 PM SYSTEM_SERVICE_EXCEPTION 0x0000003b 00000000`c0000005 fffff800`0318a8b1 fffff880`0a8fb970 00000000`00000000 ntoskrnl.exe ntoskrnl.exe+75c40 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7601.18113 (win7sp1_gdr.130318-1533)
    x64 ntoskrnl.exe+75c40
    C:\Windows\Minidump\032713-29562-01.dmp 4 15 7601 281,824

    032313-29452-01.dmp 3/23/2013 11:21:42 AM KMODE_EXCEPTION_NOT_HANDLED 0x0000001e 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 tcpip.sys tcpip.sys+57500
    x64 ntoskrnl.exe+75c10
    C:\Windows\Minidump\032313-29452-01.dmp 4 15 7601 322,480

    031713-30264-01.dmp 3/17/2013 4:32:24 PM SYSTEM_SERVICE_EXCEPTION 0x0000003b 00000000`c0000005 fffff880`03f71f33 fffff880`098378e0 00000000`00000000 dxgmms1.sys dxgmms1.sys+1bf33
    x64 ntoskrnl.exe+75c40
    C:\Windows\Minidump\031713-30264-01.dmp 4 15 7601 281,824

    031613-33602-01.dmp 3/16/2013 8:40:19 PM SYSTEM_SERVICE_EXCEPTION 0x0000003b 00000000`c0000005 fffff800`030d698e fffff880`0683e6c0 00000000`00000000 ntoskrnl.exe ntoskrnl.exe+75c40 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7601.18113 (win7sp1_gdr.130318-1533)
    x64 ntoskrnl.exe+75c40
    C:\Windows\Minidump\031613-33602-01.dmp 4 15 7601 281,824

    031613-52151-01.dmp 3/16/2013 6:08:25 PM SYSTEM_SERVICE_EXCEPTION 0x0000003b 00000000`c0000005 fffff800`02f9c30e fffff880`05ad95e0 00000000`00000000 ntoskrnl.exe ntoskrnl.exe+75c40 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7601.18113 (win7sp1_gdr.130318-1533)
    x64 ntoskrnl.exe+75c40
    C:\Windows\Minidump\031613-52151-01.dmp 4 15 7601 281,824

    022713-24585-01.dmp 2/27/2013 5:33:15 PM PAGE_FAULT_IN_NONPAGED_AREA 0x00000050 ffffffff`fffffff6 00000000`00000000 fffff800`02da90f3 00000000`00000000 ataport.SYS ataport.SYS+e1ec
    x64 ntoskrnl.exe+70700
    C:\Windows\Minidump\022713-24585-01.dmp 4 15 7600 281,488

    022713-22027-01.dmp 2/27/2013 4:00:54 PM MEMORY_MANAGEMENT 0x0000001a 00000000`00003452 00000000`09677000 fffff700`010a3348 00000000`00000200 ntoskrnl.exe ntoskrnl.exe+70740 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7601.18113 (win7sp1_gdr.130318-1533)
    x64 ntoskrnl.exe+70740
    C:\Windows\Minidump\022713-22027-01.dmp 4 15 7600 281,488

    This is off of Blue Screen Viewer

    BSOD's are random.

    Any response will be useful.

    Also, I have run CHKDSK /r on all three HDD's: all good
    I have also ran a virus scan: Clean as well

    Late,

    Metal
      My Computer


  2. Posts : 1,735
    Windows 7 enterprise 64 bit, Windows 7 Pro 64 bit ,Windows 8 64bit
       #2
      My Computer


  3. Posts : 5
    Windows 7 HP 64-Bit
    Thread Starter
       #3

    Here is the proper catcher
      My Computer


  4. Posts : 1,735
    Windows 7 enterprise 64 bit, Windows 7 Pro 64 bit ,Windows 8 64bit
       #4

    OK so I looked through the files you provided and it looks like a couple of things are happening here first it looks like your AVG is causing most of the problem:

    Code:
    fffff880`07e9aaf8  fffff880`04390eb5Unable to load image \SystemRoot\system32\DRIVERS\avgidsdrivera.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for avgidsdrivera.sys
    *** ERROR: Module load completed but symbols could not be loaded for avgidsdrivera.sys
     avgidsdrivera+0x10eb5
    Driver Reference Table - avgidsdrivera.sys


    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck A, {1, 2, 1, fffff80002e8ca7c}
    
    *** WARNING: Unable to verify timestamp for avgmfx64.sys
    *** ERROR: Module load completed but symbols could not be loaded for avgmfx64.sys
    Probably caused by : avgmfx64.sys ( avgmfx64+3167 )
    
    Followup: MachineOwner
    ---------
    Driver Reference Table - avgmfx64.sys

    Please uninstall AVG using the AVG Removal Tool, then replace it with a combination of Microsoft Security Essentials and Malwarebytes Antimalware. Tip when installing Malwarebytes be sure to uncheck the box offering ot start a free trial and also see this post for preventing a possible problem with Malwarebytes: Malwarebytes Update causes Massive false positives.

    Once that is done please run the system file checker to help with any potential file system corruption:

    SFC.EXE /SCANNOW
    Go to Start and type in "cmd.exe" (without the quotes)
    At the top of the search box, right click on the cmd.exe and select "Run as adminstrator"
    In the black window that opens, type "SFC.EXE /SCANNOW" (without the quotes) and press Enter.
    Let the program run and post back what it says when it's done.
      My Computer


  5. Posts : 4,161
    Windows 7 Pro-x64
       #5

    You beat me to the AVG Dsprague; However, the OP is also running SuperAntiSpyware and is getting NTFS access violations. It's never a good idea to run two real-time AV packages. A "read file exclusive" failed most likely because one or the other AV has the file locked. The OP should remove one and keep one or remove both before installing MSE.

    Also, I wasn't seeing those timestamp errors on my dump view. I wonder what's up with that?
      My Computer


  6. Posts : 5
    Windows 7 HP 64-Bit
    Thread Starter
       #6

    Thanks for the quick reply's gentlemen. I can understand the two AV's running, so I uninstalled both and installed MSE, updated, and restarted. I ran SFC /scannow and here is the screen shot. Also, I will note that when running a quick scan with MSE I received a BSOD I have included the dump for it as well.

    Thanks,

    MT
      My Computer


  7. Posts : 5
    Windows 7 HP 64-Bit
    Thread Starter
       #7

    Apologies, the attached SF file was not the one I needed to post, I have included the supplemental BSOD mdump I was referring to.

    Thanks,

    MT
      My Computer


  8. Posts : 1,735
    Windows 7 enterprise 64 bit, Windows 7 Pro 64 bit ,Windows 8 64bit
       #8

    Hmm the dump file seems to be silent about the cause, please enable driver verifer and allow it to crash your computer then post the new dump files here:

    Driver Verifier - Enable and Disable

    Tip: If you can not boot normally into windows after enabling Driver Verifier boot into safe mode by pressing the F8 key before the windows logo appears then disable driver verifier from safe mode.
      My Computer


  9. Posts : 4,161
    Windows 7 Pro-x64
       #9

    Metaltechnician said:
    Apologies, the attached SF file was not the one I needed to post, I have included the supplemental BSOD mdump I was referring to.

    Thanks,

    MT
    Pooled memory corruption.

    AVG is still running. It's a primary cause of BSODs.

    Code:
     
    fffff880`043ba000 fffff880`043fd000   avgidsdrivera avgidsdrivera.sys Tue Feb 26 16:27:18 2013 (512D36C6)
    fffff880`015e3000 fffff880`015f8000   avgidsha avgidsha.sys Thu Feb 07 21:14:48 2013 (51146DA8)
    fffff880`04383000 fffff880`043ba000   avgldx64 avgldx64.sys Thu Feb 07 21:14:24 2013 (51146D90)
    fffff880`01800000 fffff880`0184f000   avgloga  avgloga.sys  Thu Feb 07 21:14:29 2013 (51146D95)
    fffff880`013e0000 fffff880`013ff000   avgmfx64 avgmfx64.sys Thu Feb 07 21:14:48 2013 (51146DA8)
    fffff880`019e0000 fffff880`019ed000   avgrkx64 avgrkx64.sys Thu Feb 07 21:14:05 2013 (51146D7D)
    fffff880`04101000 fffff880`0413f000   avgtdia  avgtdia.sys  Wed Feb 13 20:38:15 2013 (511C4E17)
    fffff880`011e6000 fffff880`011f4000   avgtpx64 avgtpx64.sys Tue Mar 12 12:56:44 2013 (513F6C5C)
      My Computer


  10. Posts : 5
    Windows 7 HP 64-Bit
    Thread Starter
       #10

    Alright,

    I found remnants of AVG still on the computer and removed those promptly, restarted with DV and no BSOD's as of yet. Thanks gentlemen on the quick reply and help on this one. I am a tier one technician, and I would love to learn how you guys do these diagnostics. I wish to become a BSOD guru myself. Thanks.

    Late,

    MT
      My Computer


 
Page 1 of 2 12 LastLast

  Related Discussions
Our Sites
Site Links
About 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 03:34.
Find Us