BSOD at least ten times per day

Page 2 of 2 FirstFirst 12

  1. Posts : 23
    Windows 7 Home Premium 64Bit
    Thread Starter
       #11

    Okay, we just had another crash, here the mini dump
      My Computer


  2. Posts : 23
    Windows 7 Home Premium 64Bit
    Thread Starter
       #12

    The first one in a while, my system is getting more and more stable
      My Computer


  3. Posts : 11,269
    Windows 7 Home Premium 64 Bit
       #13

    Security Software:
    Code:
    msmpeng.exe	c:\program files\microsoft security client\antimalware\msmpeng.exe	2408	8	200	1380	3/16/2012 10:44 PM	3.0.8402.0	12.48 KB (12,784 bytes)	4/27/2011 5:21 PM
    nissrv.exe	c:\program files\microsoft security client\antimalware\nissrv.exe	2576	8	200	1380	3/16/2012 10:44 PM	3.0.8402.0	281.52 KB (288,272 bytes)	4/27/2011 5:21 PM
    msseces.exe	c:\program files\microsoft security client\msseces.exe	2372	8	200	1380	3/16/2012 10:46 PM	2.1.1116.0	1.37 MB (1,436,736 bytes)	6/15/2011 2:35 PM

    Possible out of date driver:
    Code:
    Rt64win7	fffff880`043c9000	fffff880`043fb000	Thu Feb 26 02:04:13 2009 (49a65b0d)	0002eb30		Rt64win7.sys
    Rt64win7.sys

    See if updating the above helps; if not, proceed to the next part.


    Code:
    Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [D:\Kingston\BSODDmpFiles\tjk2world\tjk2world\Windows_NT6_BSOD_jcgriff2\031612-20560-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (3 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
    Machine Name:
    Kernel base = 0xfffff800`02a06000 PsLoadedModuleList = 0xfffff800`02c4b670
    Debug session time: Fri Mar 16 20:42:58.248 2012 (UTC - 6:00)
    System Uptime: 0 days 5:17:39.684
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ....................
    Loading User Symbols
    Loading unloaded module list
    ..................
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 1A, {41790, fffffa80014d3840, ffff, 0}
    
    Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+36024 )
    
    Followup: MachineOwner
    ---------
    
    1: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    MEMORY_MANAGEMENT (1a)
        # Any other values for parameter 1 must be individually examined.
    Arguments:
    Arg1: 0000000000041790, The subtype of the bugcheck.
    Arg2: fffffa80014d3840
    Arg3: 000000000000ffff
    Arg4: 0000000000000000
    
    Debugging Details:
    ------------------
    
    
    BUGCHECK_STR:  0x1a_41790
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    PROCESS_NAME:  WmiPrvSE.exe
    
    CURRENT_IRQL:  0
    
    LAST_CONTROL_TRANSFER:  from fffff80002af2150 to fffff80002a82c40
    
    STACK_TEXT:  
    fffff880`077af828 fffff800`02af2150 : 00000000`0000001a 00000000`00041790 fffffa80`014d3840 00000000`0000ffff : nt!KeBugCheckEx
    fffff880`077af830 fffff800`02ab6569 : 00000000`00000000 00000000`029d4fff ffffbca9`00000000 fffff880`00000000 : nt! ?? ::FNODOBFM::`string'+0x36024
    fffff880`077af9f0 fffff800`02d9a221 : fffffa80`06e66e20 00000000`00000000 fffffa80`068999d0 fffffa80`068999d0 : nt!MiRemoveMappedView+0xd9
    fffff880`077afb10 fffff800`02d9a623 : 00000000`00000000 00000000`01be0000 fffffa80`00000001 00000000`00000001 : nt!MiUnmapViewOfSection+0x1b1
    fffff880`077afbd0 fffff800`02a81ed3 : 00000000`00000000 00000000`028e8e0c fffffa80`06886b30 00000000`00000002 : nt!NtUnmapViewOfSection+0x5f
    fffff880`077afc20 00000000`76e515ba : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    00000000`00fdc4f8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76e515ba
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    nt! ?? ::FNODOBFM::`string'+36024
    fffff800`02af2150 cc              int     3
    
    SYMBOL_STACK_INDEX:  1
    
    SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+36024
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nt
    
    IMAGE_NAME:  ntkrnlmp.exe
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3
    
    FAILURE_BUCKET_ID:  X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+36024
    
    BUCKET_ID:  X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+36024
    
    Followup: MachineOwner
    ---------

    Points to memory or drivers.
    • Run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).

      If you swap any memory components, follow these steps for ESD safety:
      1. Shut down and turn off your computer.
      2. Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
      3. Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
      4. Make sure you are grounded by using proper grounding techniques, i.e. work on an anti-static workbench, anti-static desk, or an anti-static pad. Hold something metallic while touching it to the anti-static surface, or use an anti-static wristband to attach to the anti-static material while working.

      Once these steps have been followed, it is safe to remove and replace components within your computer.




    And just as an FYI: NovaShield Kernel Module driver Believed to be a part of BullGuard Internet Security did cause a crash before it was removed, so probably good that it was removed for now so we can track down the real issue. You are welcome to re-install it once the crashes are resolved, but until then, it is good to keep it off the system so crashes do not falsely point to it. I do not know if you had the paid version, but if you did, don't fret about it yet.
      My Computer


  4. Posts : 23
    Windows 7 Home Premium 64Bit
    Thread Starter
       #14

    I updated my LAN drivers but ive still gotten a few blue screens
      My Computer


  5. Posts : 11,269
    Windows 7 Home Premium 64 Bit
       #15

    Code:
    1. Loading Dump File [D:\Kingston\BSODDmpFiles\tjk2world\Windows_NT6_BSOD_jcgriff2\031712-19702-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (3 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330 Machine Name: Kernel base = 0xfffff800`02a4c000 PsLoadedModuleList = 0xfffff800`02c90650 Debug session time: Sat Mar 17 18:40:29.362 2012 (UTC - 6:00) System Uptime: 0 days 0:07:03.798 Loading Kernel Symbols ............................................................... ................................................................ ...................... Loading User Symbols Loading unloaded module list .... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 19, {3, fffffa800668fc90, fffffa800600fc90, fffffa8006e9fc90} Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+a53 ) Followup: Pool_corruption --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* BAD_POOL_HEADER (19) The pool is already corrupt at the time of the current request. This may or may not be due to the caller. The internal pool links must be walked to figure out a possible cause of the problem, and then special pool applied to the suspect tags or the driver verifier to a suspect driver. Arguments: Arg1: 0000000000000003, the pool freelist is corrupt. Arg2: fffffa800668fc90, the pool entry being checked. Arg3: fffffa800600fc90, the read back flink freelist value (should be the same as 2). Arg4: fffffa8006e9fc90, the read back blink freelist value (should be the same as 2). Debugging Details: ------------------ BUGCHECK_STR: 0x19_3 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: lsass.exe CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from fffff80002bf54b3 to fffff80002ac8d40 STACK_TEXT: fffff880`06d44848 fffff800`02bf54b3 : 00000000`00000019 00000000`00000003 fffffa80`0668fc90 fffffa80`0600fc90 : nt!KeBugCheckEx fffff880`06d44850 fffff800`02dc179f : fffffa80`00000001 fffffa80`066a1f08 fffffa80`0775c130 00000000`00000000 : nt!ExDeferredFreePool+0xa53 fffff880`06d44940 fffff800`02dc15bb : fffffa80`00000000 fffffa80`06725800 00000000`00000050 fffff880`06d449e8 : nt!ObpAllocateObject+0x12f fffff880`06d449b0 fffff800`02d8fad4 : fffff880`06d44b60 00000000`00000002 fffff8a0`07e8a5a0 fffff8a0`07657060 : nt!ObCreateObject+0xdb fffff880`06d44a20 fffff800`02d9b85a : 00000000`00000000 00000000`0172eba0 00000000`00000001 fffffa80`08f20060 : nt!SepDuplicateToken+0xf4 fffff880`06d44ac0 fffff800`02d9bad5 : fffffa80`08f20060 fffff880`0000000a 00000000`00000001 00000000`00000000 : nt!NtOpenThreadTokenEx+0x33a fffff880`06d44be0 fffff800`02ac7fd3 : fffffa80`08f20060 00000000`00000000 00000000`00000000 fffffa80`0693f070 : nt!NtOpenThreadToken+0x11 fffff880`06d44c20 00000000`76ea155a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 00000000`0172eb58 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76ea155a STACK_COMMAND: kb FOLLOWUP_IP: nt!ExDeferredFreePool+a53 fffff800`02bf54b3 cc int 3 SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: nt!ExDeferredFreePool+a53 FOLLOWUP_NAME: Pool_corruption IMAGE_NAME: Pool_Corruption DEBUG_FLR_IMAGE_TIMESTAMP: 0 MODULE_NAME: Pool_Corruption FAILURE_BUCKET_ID: X64_0x19_3_nt!ExDeferredFreePool+a53 BUCKET_ID: X64_0x19_3_nt!ExDeferredFreePool+a53 Followup: Pool_corruption ---------
    2. Loading Dump File [D:\Kingston\BSODDmpFiles\tjk2world\Windows_NT6_BSOD_jcgriff2\031712-17472-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (3 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330 Machine Name: Kernel base = 0xfffff800`02a5a000 PsLoadedModuleList = 0xfffff800`02c9e650 Debug session time: Sat Mar 17 18:32:28.783 2012 (UTC - 6:00) System Uptime: 0 days 1:26:33.219 Loading Kernel Symbols ............................................................... ................................................................ ..................... Loading User Symbols Loading unloaded module list ..... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 4E, {99, 1bc256, 2, 1bc255} Probably caused by : memory_corruption ( nt!MiBadShareCount+4c ) Followup: MachineOwner --------- 2: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* PFN_LIST_CORRUPT (4e) Typically caused by drivers passing bad memory descriptor lists (ie: calling MmUnlockPages twice with the same list, etc). If a kernel debugger is available get the stack trace. Arguments: Arg1: 0000000000000099, A PTE or PFN is corrupt Arg2: 00000000001bc256, page frame number Arg3: 0000000000000002, current page state Arg4: 00000000001bc255, 0 Debugging Details: ------------------ BUGCHECK_STR: 0x4E_99 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: GameOverlayUI. CURRENT_IRQL: 2 LAST_CONTROL_TRANSFER: from fffff80002b5f20c to fffff80002ad6d40 STACK_TEXT: fffff880`02853ee8 fffff800`02b5f20c : 00000000`0000004e 00000000`00000099 00000000`001bc256 00000000`00000002 : nt!KeBugCheckEx fffff880`02853ef0 fffff800`02a7ef30 : 00000000`00000000 fffff680`001f81c8 00000000`00000002 00000000`00000001 : nt!MiBadShareCount+0x4c fffff880`02853f30 fffff800`02aa6873 : fffffa80`08d3eb30 fffff700`0000117e 0000007f`fffffff8 fffff8a0`005e2d90 : nt! ?? ::FNODOBFM::`string'+0x32968 fffff880`02853fc0 fffff800`02aa7942 : fffffa80`08d3eb30 fffffa80`00000000 fffff880`0000060c fffff800`00000000 : nt!MiDeleteAddressesInWorkingSet+0x307 fffff880`02854870 fffff800`02dab81a : fffff8a0`109c5060 fffff880`02854c20 00000000`00000000 fffffa80`090d1060 : nt!MmCleanProcessAddressSpace+0x96 fffff880`028548c0 fffff800`02d8ecfd : 00000000`c0000005 fffffa80`08294d01 00000000`7ef4a000 00000000`00000000 : nt!PspExitThread+0x56a fffff880`028549c0 fffff800`02ac97da : fffffa80`08294de0 fffffa80`0781d5b0 fffffa80`0781d500 fffff800`02ae7b9c : nt!PsExitSpecialApc+0x1d fffff880`028549f0 fffff800`02ac9b20 : 00000000`00000246 fffff880`02854a70 fffff800`02d8ec68 00000000`00000001 : nt!KiDeliverApc+0x2ca fffff880`02854a70 fffff800`02ad6077 : 00000000`00000000 fffff800`02dbe83c fffff880`02854ca0 00000000`00000000 : nt!KiInitiateUserApc+0x70 fffff880`02854bb0 00000000`74a32e09 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x9c 00000000`0441f0f8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x74a32e09 STACK_COMMAND: kb FOLLOWUP_IP: nt!MiBadShareCount+4c fffff800`02b5f20c cc int 3 SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: nt!MiBadShareCount+4c FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt DEBUG_FLR_IMAGE_TIMESTAMP: 4ec79dd2 IMAGE_NAME: memory_corruption FAILURE_BUCKET_ID: X64_0x4E_99_nt!MiBadShareCount+4c BUCKET_ID: X64_0x4E_99_nt!MiBadShareCount+4c Followup: MachineOwner ---------
    1. Possible cause is Drivers... (or possibly memory problems)
    2. Possible causes are Memory problems... Drivers...


    The crashes overall point to a memory problem. Have you run Memtest86+ for 7+ passes?
      My Computer


 
Page 2 of 2 FirstFirst 12

  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:50.
Find Us