locked
BSOD occurring recently. RRS feed

  • Question

  • Hey everyone first time posting.

     

    Basically my problem is I've started to get BSOD while i'm playing games on my computer. I never have any BSOD's other than when I'm playing a game. The crashes just happen randomly and they just started little more than three days ago. This is what was on the pop-up that came after the computer restarted. My computer is more than capable of running all the games that I play so I don't know what's the problem. 

     

    Problem signature:

      Problem Event Name: BlueScreen

      OS Version: 6.1.7600.2.0.0.768.3

      Locale ID: 1033

     

    Additional information about the problem:

      BCCode: be

      BCP1: FFFFF8A003F52334

      BCP2: 000000011EADD121

      BCP3: FFFFF88003124710

      BCP4: 000000000000000B

      OS Version: 6_1_7600

      Service Pack: 0_0

      Product: 768_1

     

    Files that help describe the problem:

      C:\Windows\Minidump\110210-16531-01.dmp

      C:\Users\DeathMachine\AppData\Local\Temp\WER-24156-0.sysdata.xml

     

    Read our privacy statement online:

      http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

     

    If the online privacy statement is not available, please read our privacy statement offline:

      C:\Windows\system32\en-US\erofflps.txt

     

    If you guys need any additional info I'd be happy to oblige. 


    Thursday, November 4, 2010 2:47 AM

All replies

  • ATTEMPTED_WRITE_TO_READONLY_MEMORY -
     
    Please zip up and post the files in C:\Windows\Minidump and post them to
    skydrive for further analysis. Note that you may need to copy the files
    to your desktop or to your documents folder before you zip them up,
     
     

    -- Mike Burr
    Thursday, November 4, 2010 5:01 AM
  • Alright man here is the minidump. 

     

     

    http://cid-970e1795e86b8811.office.live.com/embedicon.aspx/.Documents/110210-18750-01.dmp

     

    The one above is the one that just happened yesteday and these are all of the minidumps on my comp.

     

    http://cid-970e1795e86b8811.office.live.com/embedicon.aspx/.Documents/100810-18500-01.zip

    Thursday, November 4, 2010 12:06 PM
  • Hey guys, sorry for posting again so soon but I had another bluescreen and this wasn't when I was playing a game. I was about to listen to some music on google chrome when I had the bluescreen, which has never happened to me before.

    Here is the minidump for this blue screen. I'm pretty sure it's different from the others since It had 0x19 as the BCCode.

     http://cid-970e1795e86b8811.office.live.com/embedicon.aspx/.Documents/110310-17062-01.dmp

    Thursday, November 4, 2010 12:47 PM
  • Possible video card issue...

    I'd start by making sure that you have the latest BIOS update applied and I would make sure that your NVidia drivers are the newest version (even though your's is from Oct 2010):

    http://www.msi.com/index.php?func=downloaddetail&type=bios&maincat_no=1&prod_no=1833

    From there, please ensure that the rest of the drivers for your system are up to date and please post the latest dumps.

    *******************************************************************************
    *                                       *
    *            Bugcheck Analysis                  *
    *                                       *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 19, {20, fffffa8003d19d20, fffffa8003d1a1d0, 44b0002}
    
    Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for nvlddmkm.sys
    *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
    Probably caused by : nvlddmkm.sys ( nvlddmkm+1b379d )
    
    Followup: MachineOwner
    ---------
    
    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: 0000000000000020, a pool block header size is corrupt.
    Arg2: fffffa8003d19d20, The pool entry we were looking for within the page.
    Arg3: fffffa8003d1a1d0, The next pool entry.
    Arg4: 00000000044b0002, (reserved)
    
    Debugging Details:
    ------------------
    
    
    BUGCHECK_STR: 0x19_20
    
    POOL_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ab70e0
     fffffa8003d19d20 
    
    CUSTOMER_CRASH_COUNT: 1
    
    DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
    
    PROCESS_NAME: Sexy Beach Zer
    
    CURRENT_IRQL: 0
    
    LAST_CONTROL_TRANSFER: from fffff800029b26d3 to fffff8000287f740
    
    STACK_TEXT: 
    fffff880`0672fd28 fffff800`029b26d3 : 00000000`00000019 00000000`00000020 fffffa80`03d19d20 fffffa80`03d1a1d0 : nt!KeBugCheckEx
    fffff880`0672fd30 fffff880`049c179d : fffffa80`05523000 00000000`00000001 00000000`4d52564e fffff880`04f8e730 : nt!ExDeferredFreePool+0x12c4
    fffff880`0672fde0 fffffa80`05523000 : 00000000`00000001 00000000`4d52564e fffff880`04f8e730 fffff880`06730001 : nvlddmkm+0x1b379d
    fffff880`0672fde8 00000000`00000001 : 00000000`4d52564e fffff880`04f8e730 fffff880`06730001 fffff880`04f0c573 : 0xfffffa80`05523000
    fffff880`0672fdf0 00000000`4d52564e : fffff880`04f8e730 fffff880`06730001 fffff880`04f0c573 fffffa80`04211010 : 0x1
    fffff880`0672fdf8 fffff880`04f8e730 : fffff880`06730001 fffff880`04f0c573 fffffa80`04211010 fffffa80`04d07000 : 0x4d52564e
    fffff880`0672fe00 fffff880`06730001 : fffff880`04f0c573 fffffa80`04211010 fffffa80`04d07000 00000000`00000003 : nvlddmkm+0x780730
    fffff880`0672fe08 fffff880`04f0c573 : fffffa80`04211010 fffffa80`04d07000 00000000`00000003 fffffa80`04d07000 : 0xfffff880`06730001
    fffff880`0672fe10 fffffa80`04211010 : fffffa80`04d07000 00000000`00000003 fffffa80`04d07000 00000000`00000001 : nvlddmkm+0x6fe573
    fffff880`0672fe18 fffffa80`04d07000 : 00000000`00000003 fffffa80`04d07000 00000000`00000001 00000000`00000000 : 0xfffffa80`04211010
    fffff880`0672fe20 00000000`00000003 : fffffa80`04d07000 00000000`00000001 00000000`00000000 00000000`00000000 : 0xfffffa80`04d07000
    fffff880`0672fe28 fffffa80`04d07000 : 00000000`00000001 00000000`00000000 00000000`00000000 fffff880`04f8e730 : 0x3
    fffff880`0672fe30 00000000`00000001 : 00000000`00000000 00000000`00000000 fffff880`04f8e730 fffff880`06730001 : 0xfffffa80`04d07000
    fffff880`0672fe38 00000000`00000000 : 00000000`00000000 fffff880`04f8e730 fffff880`06730001 fffff880`04a10a3b : 0x1
    
    
    STACK_COMMAND: kb
    
    FOLLOWUP_IP: 
    nvlddmkm+1b379d
    fffff880`049c179d ??       ???
    
    SYMBOL_STACK_INDEX: 2
    
    SYMBOL_NAME: nvlddmkm+1b379d
    
    FOLLOWUP_NAME: MachineOwner
    
    MODULE_NAME: nvlddmkm
    
    IMAGE_NAME: nvlddmkm.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP: 4cb9dd0e
    
    FAILURE_BUCKET_ID: X64_0x19_20_nvlddmkm+1b379d
    
    BUCKET_ID: X64_0x19_20_nvlddmkm+1b379d
    
    Followup: MachineOwner
    ---------
    
    0: kd> lmvm nvlddmkm
    start       end         module name
    fffff880`0480e000 fffff880`053e7a80  nvlddmkm T (no symbols)      
      Loaded symbol image file: nvlddmkm.sys
      Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
      Image name: nvlddmkm.sys
      Timestamp:    Sat Oct 16 11:12:46 2010 (4CB9DD0E)
      CheckSum:     00BE35D8
      ImageSize:    00BD9A80
      Translations:   0000.04b0 0000.04e4 0409.04b0 0409.04e4
    0: kd> !sysinfo machineid
    Machine ID Information [From Smbios 2.6, DMIVersion 0, Size=2067]
    BiosMajorRelease = 8
    BiosMinorRelease = 16
    BiosVendor = American Megatrends Inc.
    BiosVersion = V4.0
    BiosReleaseDate = 06/11/2009
    SystemManufacturer = MICRO-STAR INTERNATIONAL CO.,LTD
    SystemProductName = MS-7529
    SystemFamily = To Be Filled By O.E.M.
    SystemVersion = 1.0
    SystemSKU = To Be Filled By O.E.M.
    BaseBoardManufacturer = MICRO-STAR INTERNATIONAL CO.,LTD
    BaseBoardProduct = G31TM-P21 (MS-7529)
    BaseBoardVersion = 1.0
    
    *******************************************************************************
    *                                       *
    *            Bugcheck Analysis                  *
    *                                       *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 1000007E, {ffffffffc0000005, fffff88003da22a1, fffff88004321418, fffff88004320c80}
    
    Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_SEGMENT::TrimProcess+a5 )
    
    Followup: MachineOwner
    ---------
    
    0: kd> !analyze -v
    *******************************************************************************
    *                                       *
    *            Bugcheck Analysis                  *
    *                                       *
    *******************************************************************************
    
    SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
    This is a very common bugcheck. Usually the exception address pinpoints
    the driver/function that caused the problem. Always note this address
    as well as the link date of the driver/image that contains this address.
    Some common problems are exception code 0x80000003. This means a hard
    coded breakpoint or assertion was hit, but this system was booted
    /NODEBUG. This is not supposed to happen as developers should never have
    hardcoded breakpoints in retail code, but ...
    If this happens, make sure a debugger gets connected, and the
    system is booted /DEBUG. This will let us see why this breakpoint is
    happening.
    Arguments:
    Arg1: ffffffffc0000005, The exception code that was not handled
    Arg2: fffff88003da22a1, The address that the exception occurred at
    Arg3: fffff88004321418, Exception Record Address
    Arg4: fffff88004320c80, Context Record Address
    
    Debugging Details:
    ------------------
    
    
    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
    
    FAULTING_IP: 
    dxgmms1!VIDMM_SEGMENT::TrimProcess+a5
    fffff880`03da22a1 488b38     mov   rdi,qword ptr [rax]
    
    EXCEPTION_RECORD: fffff88004321418 -- (.exr 0xfffff88004321418)
    ExceptionAddress: fffff88003da22a1 (dxgmms1!VIDMM_SEGMENT::TrimProcess+0x00000000000000a5)
      ExceptionCode: c0000005 (Access violation)
     ExceptionFlags: 00000000
    NumberParameters: 2
      Parameter[0]: 0000000000000000
      Parameter[1]: 00000000000feafe
    Attempt to read from address 00000000000feafe
    
    CONTEXT: fffff88004320c80 -- (.cxr 0xfffff88004320c80)
    rax=00000000000feafe rbx=fffffa8004e19120 rcx=0000000000000000
    rdx=0000000000000000 rsi=fffff8a007fc2dd8 rdi=fffff8a006a43c50
    rip=fffff88003da22a1 rsp=fffff88004321650 rbp=fffffa800597bb30
     r8=0000000009e93000 r9=0000000028000000 r10=fffffa8004e190d0
    r11=0000000078100500 r12=fffff8a007fc2dd8 r13=fffff8a006c27e50
    r14=00000000c0000001 r15=000000001ef90000
    iopl=0     nv up ei pl nz na pe nc
    cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b       efl=00010202
    dxgmms1!VIDMM_SEGMENT::TrimProcess+0xa5:
    fffff880`03da22a1 488b38     mov   rdi,qword ptr [rax] ds:002b:00000000`000feafe=????????????????
    Resetting default scope
    
    CUSTOMER_CRASH_COUNT: 1
    
    DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
    
    PROCESS_NAME: System
    
    CURRENT_IRQL: 0
    
    ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
    
    EXCEPTION_PARAMETER1: 0000000000000000
    
    EXCEPTION_PARAMETER2: 00000000000feafe
    
    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ab50e0
     00000000000feafe 
    
    FOLLOWUP_IP: 
    dxgmms1!VIDMM_SEGMENT::TrimProcess+a5
    fffff880`03da22a1 488b38     mov   rdi,qword ptr [rax]
    
    BUGCHECK_STR: 0x7E
    
    LAST_CONTROL_TRANSFER: from fffff88003da175b to fffff88003da22a1
    
    STACK_TEXT: 
    fffff880`04321650 fffff880`03da175b : 00000000`000b0000 00000000`00000001 00000000`00000000 fffffa80`28000000 : dxgmms1!VIDMM_SEGMENT::TrimProcess+0xa5
    fffff880`043216c0 fffff880`03d92015 : 00000000`01560000 00000000`00000002 fffff880`04321800 fffffa80`059b0c80 : dxgmms1!VIDMM_SEGMENT::ReserveResource+0x283
    fffff880`04321770 fffff880`03d9137b : fffff8a0`035d5470 00000000`1ef90000 00000000`00000000 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::AcquireGPUResourcesFromHintedBankInformation+0x215
    fffff880`04321810 fffff880`03d8e27c : 00000000`000000bf 00000000`00000000 00000000`00000101 fffffa80`00000000 : dxgmms1!VIDMM_GLOBAL::FindResourcesForOneAllocation+0x25f
    fffff880`043218d0 fffff880`03da865d : 00000000`00000000 fffff8a0`02ab0cf0 fffffa80`00000000 fffffa80`045d8130 : dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0x7e8
    fffff880`04321aa0 fffff880`03da8398 : fffff880`009ecec0 fffff880`03da7d00 fffffa80`00000000 fffffa80`00000000 : dxgmms1!VidSchiSubmitRenderCommand+0x241
    fffff880`04321c90 fffff880`03da7e96 : 00000000`00000000 fffffa80`05fae590 00000000`00000080 fffffa80`0598e010 : dxgmms1!VidSchiSubmitQueueCommand+0x50
    fffff880`04321cc0 fffff800`02b21c06 : 00000000`02353ded fffffa80`056d4640 fffffa80`039cc040 fffffa80`056d4640 : dxgmms1!VidSchiWorkerThread+0xd6
    fffff880`04321d00 fffff800`0285bc26 : fffff880`009e8180 fffffa80`056d4640 fffff880`009f2f40 fffff880`01213534 : nt!PspSystemThreadStartup+0x5a
    fffff880`04321d40 00000000`00000000 : fffff880`04322000 fffff880`0431c000 fffff880`04321650 00000000`00000000 : nt!KxStartSystemThread+0x16
    
    
    SYMBOL_STACK_INDEX: 0
    
    SYMBOL_NAME: dxgmms1!VIDMM_SEGMENT::TrimProcess+a5
    
    FOLLOWUP_NAME: MachineOwner
    
    MODULE_NAME: dxgmms1
    
    IMAGE_NAME: dxgmms1.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc578
    
    STACK_COMMAND: .cxr 0xfffff88004320c80 ; kb
    
    FAILURE_BUCKET_ID: X64_0x7E_dxgmms1!VIDMM_SEGMENT::TrimProcess+a5
    
    BUCKET_ID: X64_0x7E_dxgmms1!VIDMM_SEGMENT::TrimProcess+a5
    
    Followup: MachineOwner
    ---------
    

    -- Mike Burr
    Thursday, November 4, 2010 10:12 PM
  • Thanks for the reply.  I'm gonna try and update my BIOS and I'm pretty sure I have the latest nividia graphics card setting. Also, it seems the Blue screens have stopped. I had uninstalled something and now my computer has been running fine although I'm still gonna do what you suggested and post the results here once I get done.
    Thursday, November 4, 2010 11:32 PM
  • After a few weeks with no problems I started having BSOD's again. The only programs I have open when they happen is google chrome and I highly doubt that's what's causing the problems. Here is the problem signiture that popped up after my computer rebooted.

    Problem signature:

      Problem Event Name: BlueScreen

      OS Version: 6.1.7600.2.0.0.768.3

      Locale ID: 1033

     

    Additional information about the problem:

      BCCode: 19

      BCP1: 0000000000000022

      BCP2: 0000000000400000

      BCP3: 0000000000000000

      BCP4: 0000000000000000

      OS Version: 6_1_7600

      Service Pack: 0_0

      Product: 768_1


    Here are the two most recent minidump files. I had previously checked if I had updated all of my graphic drivers to there most recent date and I did, and I tried to update my BIOS but it won't update since I have windows 7 x64 and I need to use some other method like using a flash drive to update my BIOS. 

    http://cid-970e1795e86b8811.office.live.com/embedicon.aspx/.Documents/111410-18406-01.dmp

    http://cid-970e1795e86b8811.office.live.com/embedicon.aspx/.Documents/111410-18109-01.dmp

    Tuesday, November 16, 2010 2:42 AM
  • Bump. The BSOD's seem to have stopped for now but I still would like to know what caused them.

    Tuesday, November 16, 2010 10:50 PM
  • This is a slightly different error than before,

    http://msdn.microsoft.com/en-us/library/ff557389%28v=VS.85%29.aspx

    I would verify ram with memtest86+, www.memtest.org, and also enable driver verifier with all checks for all drivers, http://support.microsoft.com/kb/244617

    When you receive errors after enabling driver verifier, please post the dumps. Note that in rare circumstances the system won't boot normally after enabling the driver verifier and you will need to use safe mode to disable it.

     

    *******************************************************************************
    *                                       *
    *            Bugcheck Analysis                  *
    *                                       *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 19, {22, 400000, 0, 0}
    
    GetPointerFromAddress: unable to read from fffff80002d050e0
    GetUlongFromAddress: unable to read from fffff80002c731b0
    Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+72f8 )
    
    Followup: MachineOwner
    ---------
    
    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: 0000000000000022, 
    Arg2: 0000000000400000
    Arg3: 0000000000000000
    Arg4: 0000000000000000
    
    Debugging Details:
    ------------------
    
    GetUlongFromAddress: unable to read from fffff80002c731b0
    
    BUGCHECK_STR: 0x19_22
    
    POOL_ADDRESS: 0000000000400000 
    
    CUSTOMER_CRASH_COUNT: 1
    
    DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
    
    PROCESS_NAME: System
    
    CURRENT_IRQL: 2
    
    LAST_CONTROL_TRANSFER: from fffff80002b22c80 to fffff80002acd740
    
    STACK_TEXT: 
    fffff880`02fc4798 fffff800`02b22c80 : 00000000`00000019 00000000`00000022 00000000`00400000 00000000`00000000 : nt!KeBugCheckEx
    fffff880`02fc47a0 fffff800`02c02518 : 00000000`00000000 fffff880`02fc48f0 fffff880`02fc4860 fffff880`00000001 : nt! ?? ::FNODOBFM::`string'+0x72f8
    fffff880`02fc4830 fffff800`02aba102 : 00000000`00000000 00000000`00001000 00000000`00000000 00000000`00000000 : nt!ExFreePoolWithTag+0x468
    fffff880`02fc48e0 fffff800`02ae2cbe : 00000000`ffffffff fffff880`02fc4a68 00000000`00000001 fffff8a0`00358598 : nt!ExDeleteResourceLite+0x1a2
    fffff880`02fc4940 fffff800`02abd0b7 : fffffa80`04c76c30 fffff880`02fc4a68 00000000`00000001 fffffa80`04c76c30 : nt!CcUnpinFileDataEx+0x3fe
    fffff880`02fc49c0 fffff800`02ab92bb : 00000000`000058c6 fffff880`02fc4c18 00000000`00001000 00000000`00000000 : nt!CcReleaseByteRangeFromWrite+0xa7
    fffff880`02fc4a10 fffff800`02ac094b : fffffa80`049aa970 fffff800`00000001 00000000`00000001 fffff800`00001000 : nt!CcFlushCache+0x64b
    fffff880`02fc4b10 fffff800`02ac1520 : fffff880`0418ed00 fffff880`02fc4c18 00000000`00000000 fffff800`00000000 : nt!CcWriteBehind+0x1eb
    fffff880`02fc4bc0 fffff800`02ada961 : fffffa80`03a23190 fffff800`02ac1358 fffff800`02cd4140 fffffa80`00000003 : nt!CcWorkerThread+0x1c8
    fffff880`02fc4c70 fffff800`02d71c06 : 00730073`0061006c fffffa80`039ff680 00000000`00000080 fffffa80`039e7040 : nt!ExpWorkerThread+0x111
    fffff880`02fc4d00 fffff800`02aabc26 : fffff880`009e6180 fffffa80`039ff680 fffff880`009f0f40 ffffffff`00078d88 : nt!PspSystemThreadStartup+0x5a
    fffff880`02fc4d40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
    
    
    STACK_COMMAND: kb
    
    FOLLOWUP_IP: 
    nt! ?? ::FNODOBFM::`string'+72f8
    fffff800`02b22c80 cc       int   3
    
    SYMBOL_STACK_INDEX: 1
    
    SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+72f8
    
    FOLLOWUP_NAME: MachineOwner
    
    MODULE_NAME: nt
    
    IMAGE_NAME: ntkrnlmp.exe
    
    DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c44a9
    
    FAILURE_BUCKET_ID: X64_0x19_22_nt!_??_::FNODOBFM::_string_+72f8
    
    BUCKET_ID: X64_0x19_22_nt!_??_::FNODOBFM::_string_+72f8
    
    Followup: MachineOwner
    ---------
    
    1: 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: fffffa8003d19d20, the pool entry being checked.
    Arg3: fffffa8006325d70, the read back flink freelist value (should be the same as 2).
    Arg4: fffffa8003d19d20, 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: chrome.exe
    
    CURRENT_IRQL: 2
    
    LAST_CONTROL_TRANSFER: from fffff80002bab130 to fffff80002a78740
    
    STACK_TEXT: 
    fffff880`0a62c738 fffff800`02bab130 : 00000000`00000019 00000000`00000003 fffffa80`03d19d20 fffffa80`06325d70 : nt!KeBugCheckEx
    fffff880`0a62c740 fffff800`02bad4c1 : fffffa80`0413b000 fffffa80`0413b000 00000000`00000000 00000000`00000000 : nt!ExDeferredFreePool+0xca0
    fffff880`0a62c7d0 fffff880`02dd8fbd : fffff880`0a62c9e0 00000000`034ff010 fffffa80`7246704e fffff880`0a62cb58 : nt!ExFreePoolWithTag+0x411
    fffff880`0a62c880 fffff880`02ddbf9e : fffff880`0a62c9f0 00000000`00000001 fffff880`0a62c980 00000000`00000000 : Npfs!NpRemoveDataQueueEntry+0xa5
    fffff880`0a62c8c0 fffff880`02ddbd32 : fffff880`0a62c980 fffff8a0`06c37310 fffffa80`03db1901 fffff880`01036400 : Npfs!NpReadDataQueue+0x20e
    fffff880`0a62c930 fffff880`02ddbab5 : fffffa80`06623c40 fffffa80`04516d20 00000000`00000000 fffffa80`06623b70 : Npfs!NpCommonRead+0x18e
    fffff880`0a62c9b0 fffff800`02d8eca9 : 00000000`00000000 fffff800`02a878b1 00000000`062e2264 fffffa80`04516d70 : Npfs!NpFsdRead+0x51
    fffff880`0a62ca10 fffff800`02d964a3 : fffffa80`04516d20 fffffa80`04516d20 fffffa80`04516d20 fffff880`009e6180 : nt!IopSynchronousServiceTail+0xf9
    fffff880`0a62ca80 fffff800`02a77993 : fffffa80`041cf620 00000000`00000000 00000000`00000001 00000000`062e2204 : nt!NtReadFile+0x631
    fffff880`0a62cb70 00000000`73972dd9 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    00000000`034fef98 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x73972dd9
    
    
    STACK_COMMAND: kb
    
    FOLLOWUP_IP: 
    nt!ExDeferredFreePool+ca0
    fffff800`02bab130 cc       int   3
    
    SYMBOL_STACK_INDEX: 1
    
    SYMBOL_NAME: nt!ExDeferredFreePool+ca0
    
    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+ca0
    
    BUCKET_ID: X64_0x19_3_nt!ExDeferredFreePool+ca0
    
    Followup: Pool_corruption
    ---------
    


    -- Mike Burr
    Thursday, November 18, 2010 11:07 AM
  • Hey thanks man I appreciate the response. Okay so I did the driver verifier and it found no unsigned drivers. I'm about to do memtest right after I get done with this chkdsk. 

     

    Also I just had a BSOD after a few days without one occurring, here is the minidump file for it. I have no idea what's causing these problems, they occur once or twice and then I stop having them for a long while.

     

    http://cid-970e1795e86b8811.office.live.com/embedicon.aspx/.Documents/112310-21625-01.dmp

     

     

    Wednesday, November 24, 2010 11:40 PM
  • This one could point to a filesystem issue, you might want to try a

    chkdsk /r c:

    from an administrative command prompt (note that it may prompt you to scan at the next reboot).

     

    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck A, {29, 2, 1, fffff80002cceb23}

    Probably caused by : ntkrnlmp.exe ( nt!CcUnpinFileDataEx+263 )

    Followup: MachineOwner
    ---------

    0: kd> !analyze -v
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    IRQL_NOT_LESS_OR_EQUAL (a)
    An attempt was made to access a pageable (or completely invalid) address at an
    interrupt request level (IRQL) that is too high. This is usually
    caused by drivers using improper addresses.
    If a kernel debugger is available get the stack backtrace.
    Arguments:
    Arg1: 0000000000000029, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000001, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
    Arg4: fffff80002cceb23, address which referenced memory

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


    WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ef10e0
    0000000000000029

    CURRENT_IRQL: 2

    FAULTING_IP:
    nt!CcUnpinFileDataEx+263
    fffff800`02cceb23 48294828 sub qword ptr [rax+28h],rcx

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

    BUGCHECK_STR: 0xA

    PROCESS_NAME: System

    TRAP_FRAME: fffff880047ae7b0 -- (.trap 0xfffff880047ae7b0)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000000000001 rbx=0000000000000000 rcx=0000000000000001
    rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff80002cceb23 rsp=fffff880047ae940 rbp=fffff880047aea68
    r8=0000000000000002 r9=0000000000000000 r10=fffff80002ef3800
    r11=0000000000f63000 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0 nv up ei pl nz na po nc
    nt!CcUnpinFileDataEx+0x263:
    fffff800`02cceb23 48294828 sub qword ptr [rax+28h],rcx ds:0001:00000000`00000029=????????????????
    Resetting default scope

    LAST_CONTROL_TRANSFER: from fffff80002cb8ca9 to fffff80002cb9740

    STACK_TEXT:
    fffff880`047ae668 fffff800`02cb8ca9 : 00000000`0000000a 00000000`00000029 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
    fffff880`047ae670 fffff800`02cb7920 : 00000000`00000000 00000000`00000001 fffff880`047ae878 fffffa80`04a39250 : nt!KiBugCheckDispatch+0x69
    fffff880`047ae7b0 fffff800`02cceb23 : fffffa80`04977430 fffff800`02ca58d8 fffff8a0`002a8b10 fffff8a0`002a8b18 : nt!KiPageFault+0x260
    fffff880`047ae940 fffff800`02ca909f : fffffa80`04977430 fffff880`047aea68 00000000`00000001 fffffa80`04977430 : nt!CcUnpinFileDataEx+0x263
    fffff880`047ae9c0 fffff800`02ca52bb : 00000000`0101e106 fffff880`047aec18 00000000`00001000 00000000`00000000 : nt!CcReleaseByteRangeFromWrite+0x8f
    fffff880`047aea10 fffff800`02cac94b : fffffa80`04a37240 fffff800`00000001 00000000`00000001 fffff800`00001000 : nt!CcFlushCache+0x64b
    fffff880`047aeb10 fffff800`02cad520 : fffff800`02ec0100 fffff880`047aec18 00000000`00000000 fffff800`00000000 : nt!CcWriteBehind+0x1eb
    fffff880`047aebc0 fffff800`02cc6961 : fffffa80`039d86d0 fffff800`02cad358 fffff800`02ec0140 fffffa80`00000005 : nt!CcWorkerThread+0x1c8
    fffff880`047aec70 fffff800`02f5dc06 : 00000000`00000000 fffffa80`07b1bb60 00000000`00000080 fffffa80`039cd040 : nt!ExpWorkerThread+0x111
    fffff880`047aed00 fffff800`02c97c26 : fffff800`02e33e80 fffffa80`07b1bb60 fffffa80`039e0680 fffff880`01246534 : nt!PspSystemThreadStartup+0x5a
    fffff880`047aed40 00000000`00000000 : fffff880`047af000 fffff880`047a9000 fffff880`047adc50 00000000`00000000 : nt!KxStartSystemThread+0x16


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    nt!CcUnpinFileDataEx+263
    fffff800`02cceb23 48294828 sub qword ptr [rax+28h],rcx

    SYMBOL_STACK_INDEX: 3

    SYMBOL_NAME: nt!CcUnpinFileDataEx+263

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: nt

    IMAGE_NAME: ntkrnlmp.exe

    DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c44a9

    FAILURE_BUCKET_ID: X64_0xA_nt!CcUnpinFileDataEx+263

    BUCKET_ID: X64_0xA_nt!CcUnpinFileDataEx+263

    Followup: MachineOwner
    ---------

    0: kd> .trap 0xfffff880047ae7b0
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000000000001 rbx=0000000000000000 rcx=0000000000000001
    rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff80002cceb23 rsp=fffff880047ae940 rbp=fffff880047aea68
    r8=0000000000000002 r9=0000000000000000 r10=fffff80002ef3800
    r11=0000000000f63000 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0 nv up ei pl nz na po nc
    nt!CcUnpinFileDataEx+0x263:
    fffff800`02cceb23 48294828 sub qword ptr [rax+28h],rcx ds:0001:00000000`00000029=????????????????
    0: kd> kv
    *** Stack trace for last set context - .thread/.cxr resets it
    Child-SP RetAddr : Args to Child : Call Site
    fffff880`047ae940 fffff800`02ca909f : fffffa80`04977430 fffff880`047aea68 00000000`00000001 fffffa80`04977430 : nt!CcUnpinFileDataEx+0x263
    fffff880`047ae9c0 fffff800`02ca52bb : 00000000`0101e106 fffff880`047aec18 00000000`00001000 00000000`00000000 : nt!CcReleaseByteRangeFromWrite+0x8f
    fffff880`047aea10 fffff800`02cac94b : fffffa80`04a37240 fffff800`00000001 00000000`00000001 fffff800`00001000 : nt!CcFlushCache+0x64b
    fffff880`047aeb10 fffff800`02cad520 : fffff800`02ec0100 fffff880`047aec18 00000000`00000000 fffff800`00000000 : nt!CcWriteBehind+0x1eb
    fffff880`047aebc0 fffff800`02cc6961 : fffffa80`039d86d0 fffff800`02cad358 fffff800`02ec0140 fffffa80`00000005 : nt!CcWorkerThread+0x1c8
    fffff880`047aec70 fffff800`02f5dc06 : 00000000`00000000 fffffa80`07b1bb60 00000000`00000080 fffffa80`039cd040 : nt!ExpWorkerThread+0x111
    fffff880`047aed00 fffff800`02c97c26 : fffff800`02e33e80 fffffa80`07b1bb60 fffffa80`039e0680 fffff880`01246534 : nt!PspSystemThreadStartup+0x5a
    fffff880`047aed40 00000000`00000000 : fffff880`047af000 fffff880`047a9000 fffff880`047adc50 00000000`00000000 : nt!KxStartSystemThread+0x16
    0: kd> !chkimg -d nt
    0 errors : nt


    -- Mike Burr
    MS Technologies - Development - *nix
    Saturday, November 27, 2010 4:21 PM
  • Okay i've been getting BSOD's since I've installed bitdefender. I can't even start my computer in normal mode and have to run in safe mode. I don't think bitdefender itself is the problem, so i'm going to upload some dump files and hope someone can tell me what exactly is up. 

    http://cid-970e1795e86b8811.office.live.com/embedicon.aspx/.Documents/Desktop.zip

     

    And this is a minidump from a BSOD from a couple of days back.

     

    http://cid-970e1795e86b8811.office.live.com/embedicon.aspx/.Documents/120210-25796-01.dmp

     

     

    Saturday, December 4, 2010 7:56 PM
  • Well I did a system restore to the point before I installed bitdefender and now I can log into windows without getting an automatic bluescreen but I still got bluescreens here and there. I uninstall daemon tools, which gave me a bluescreen when I tried to uninstall it until I removed the stmd.sys then uninstalled it, and I thought that would be an end to my problems. I put malewarebytes on a full scan then went to sleep and when I woke up in the morning my computer had the crash prompt up and malewarebytes showed that it didn't finish the full scan. Right now I don't know what's causing these errors. This is the minidump from that crash.

     

    http://cid-970e1795e86b8811.office.live.com/embedicon.aspx/.Documents/120510-20703-01.dmp

     

    I hope i'm getting closer to pinpointing the overall reason why i'm having these BSOD's in the first place.

    Monday, December 6, 2010 1:13 PM
  • Okay so after a few days of no BSOD's I tried to run malewarebytes full scan again only to get a BSOD around 2 hours into it. Here is the minidump. 

     

    http://cid-970e1795e86b8811.office.live.com/embedicon.aspx/.Documents/121010-20062-01.dmp

     

    I have no clue what's causing these problems. 

     

    EDIT:So I just had a BSOD while trying to install a game. I wasn't to concerned about the previous two bsod's because I was pretty sure I didn't have any sort of antivirus on my computer, now that I can't even install anything onto my comp I really need to pinpoint what's causing these problems. Here is the minidump for said BSOD.

    http://cid-970e1795e86b8811.office.live.com/embedicon.aspx/.Documents/121010-25406-01.dmp

     

     

     

     

     

    • Edited by AwsomeX Saturday, December 11, 2010 11:12 PM new information
    Saturday, December 11, 2010 8:44 PM
  • Do you have MagicDisk installed? This could be related. If you do, maybe try uninstalling it and running the malwarebytes scan.

     

    *******************************************************************************
    *                                       *
    *            Bugcheck Analysis                  *
    *                                       *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck C4, {81, fffff98013cf4fc0, 82, 0}
    
    Unable to load image \SystemRoot\system32\DRIVERS\mcdbus.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for mcdbus.sys
    *** ERROR: Module load completed but symbols could not be loaded for mcdbus.sys
    Probably caused by : mcdbus.sys ( mcdbus+36823 )
    
    Followup: MachineOwner
    ---------
    
    0: kd> !analyze -v
    *******************************************************************************
    *                                       *
    *            Bugcheck Analysis                  *
    *                                       *
    *******************************************************************************
    
    DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
    A device driver attempting to corrupt the system has been caught. This is
    because the driver was specified in the registry as being suspect (by the
    administrator) and the kernel has enabled substantial checking of this driver.
    If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA will
    be among the most commonly seen crashes.
    Arguments:
    Arg1: 0000000000000081, MmMapLockedPages called without MDL_MAPPING_CAN_FAIL
    Arg2: fffff98013cf4fc0, MDL address.
    Arg3: 0000000000000082, MDL flags.
    Arg4: 0000000000000000, 0.
    
    Debugging Details:
    ------------------
    
    
    BUGCHECK_STR: 0xc4_81
    
    CUSTOMER_CRASH_COUNT: 1
    
    DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP
    
    PROCESS_NAME: System
    
    CURRENT_IRQL: 0
    
    LAST_CONTROL_TRANSFER: from fffff8000310e3dc to fffff80002c84740
    
    STACK_TEXT: 
    fffff880`02ff64b8 fffff800`0310e3dc : 00000000`000000c4 00000000`00000081 fffff980`13cf4fc0 00000000`00000082 : nt!KeBugCheckEx
    fffff880`02ff64c0 fffff800`0312189a : fffff980`13cf4fc0 00000000`00000002 fffffa80`05a52990 fffff880`02ff7000 : nt!VerifierBugCheckIfAppropriate+0x3c
    fffff880`02ff6500 fffff880`03e36823 : fffff980`47924ea0 fffff980`2ff96fc0 fffffa80`059a73f0 fffffa80`000007ad : nt!VerifierMmMapLockedPages+0x4a
    fffff880`02ff6540 fffff980`47924ea0 : fffff980`2ff96fc0 fffffa80`059a73f0 fffffa80`000007ad fffff980`47924ea0 : mcdbus+0x36823
    fffff880`02ff6548 fffff980`2ff96fc0 : fffffa80`059a73f0 fffffa80`000007ad fffff980`47924ea0 fffff980`47924f70 : 0xfffff980`47924ea0
    fffff880`02ff6550 fffffa80`059a73f0 : fffffa80`000007ad fffff980`47924ea0 fffff980`47924f70 fffff880`02ff6a60 : 0xfffff980`2ff96fc0
    fffff880`02ff6558 fffffa80`000007ad : fffff980`47924ea0 fffff980`47924f70 fffff880`02ff6a60 fffff980`2ff96fc0 : 0xfffffa80`059a73f0
    fffff880`02ff6560 fffff980`47924ea0 : fffff980`47924f70 fffff880`02ff6a60 fffff980`2ff96fc0 fffffa80`05a52ae0 : 0xfffffa80`000007ad
    fffff880`02ff6568 fffff980`47924f70 : fffff880`02ff6a60 fffff980`2ff96fc0 fffffa80`05a52ae0 fffff880`02ff6a70 : 0xfffff980`47924ea0
    fffff880`02ff6570 fffff880`02ff6a60 : fffff980`2ff96fc0 fffffa80`05a52ae0 fffff880`02ff6a70 fffff880`00000000 : 0xfffff980`47924f70
    fffff880`02ff6578 fffff980`2ff96fc0 : fffffa80`05a52ae0 fffff880`02ff6a70 fffff880`00000000 fffff980`2ff96fe8 : 0xfffff880`02ff6a60
    fffff880`02ff6580 fffffa80`05a52ae0 : fffff880`02ff6a70 fffff880`00000000 fffff980`2ff96fe8 fffffa80`069b1e00 : 0xfffff980`2ff96fc0
    fffff880`02ff6588 fffff880`02ff6a70 : fffff880`00000000 fffff980`2ff96fe8 fffffa80`069b1e00 fffff800`0312009d : 0xfffffa80`05a52ae0
    fffff880`02ff6590 fffff880`00000000 : fffff980`2ff96fe8 fffffa80`069b1e00 fffff800`0312009d fffff980`47924ea0 : 0xfffff880`02ff6a70
    fffff880`02ff6598 fffff980`2ff96fe8 : fffffa80`069b1e00 fffff800`0312009d fffff980`47924ea0 00000000`00000002 : 0xfffff880`00000000
    fffff880`02ff65a0 fffffa80`069b1e00 : fffff800`0312009d fffff980`47924ea0 00000000`00000002 fffffa80`6264636d : 0xfffff980`2ff96fe8
    fffff880`02ff65a8 fffff800`0312009d : fffff980`47924ea0 00000000`00000002 fffffa80`6264636d fffffa80`05a52990 : 0xfffffa80`069b1e00
    fffff880`02ff65b0 fffff880`03e362db : fffffa80`05a52990 00000000`00000000 fffff880`00edd0c2 00000000`00000000 : nt!VerifierExAllocatePoolWithTag+0x1d
    fffff880`02ff65f0 fffffa80`05a52990 : 00000000`00000000 fffff880`00edd0c2 00000000`00000000 00000000`00000000 : mcdbus+0x362db
    fffff880`02ff65f8 00000000`00000000 : fffff880`00edd0c2 00000000`00000000 00000000`00000000 fffff880`02ff68a0 : 0xfffffa80`05a52990
    
    
    STACK_COMMAND: kb
    
    FOLLOWUP_IP: 
    mcdbus+36823
    fffff880`03e36823 ??       ???
    
    SYMBOL_STACK_INDEX: 3
    
    SYMBOL_NAME: mcdbus+36823
    
    FOLLOWUP_NAME: MachineOwner
    
    MODULE_NAME: mcdbus
    
    IMAGE_NAME: mcdbus.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP: 49a3cd1f
    
    FAILURE_BUCKET_ID: X64_0xc4_81_VRF_mcdbus+36823
    
    BUCKET_ID: X64_0xc4_81_VRF_mcdbus+36823
    
    Followup: MachineOwner
    ---------
    


    -- Mike Burr
    MS Technologies - Development - *nix
    Saturday, December 11, 2010 11:01 PM
  • Actually I had magicdisc installed because someone told me it was a good substitute of daemon tools lite, which I have just reinstalled because I needed it for a quick second but i'm going to get ride of it once i'm done with it, but it was causing a mess of problems on my comp so I got ride of every piece of it on my comp. I don't think that's the cause of why malewarebytes couldn't finish the scan since it wouldn't finish a complete scan before I even knew magicdisc existed. Anyway just had another BSOD while I was looking up some vids on google chrome here is the minidump.

     

    http://cid-970e1795e86b8811.office.live.com/embedicon.aspx/.Documents/121010-28687-01.dmp

    Sunday, December 12, 2010 3:57 AM
  • SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION (c1)
    Special pool has detected memory corruption.  Typically the current thread's
    stack backtrace will reveal the guilty party.
    Arguments:
    Arg1: fffff98053fa2fc0, address trying to free
    Arg2: fffff98053fa2108, address where one bit is corrupted
    Arg3: 0000000000934040, (reserved)
    Arg4: 0000000000000032, caller is freeing an address where nearby bytes within the same page have a single bit error

    =====

    Please run the aforementioned memtest as suggested by mike and let us know of the results. Its possible you may have problems with your memory but you have not confirmed whether or not you managed to perform this action. I would also do a hard disk check just to rule out problems with that. here is a link to help you do it. - http://www.mypchealth.co.uk/GuideTests.php

    =====

    Previous dmp -DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
    I cant see any mention of you updating all your drivers to the latest versions including chipset etc? I would definately double check this. I know you said you may have the latest version for your video card but i would double check as they can be real pains. Visit the manufacturers website rather than updating through windows.

     


    www.mypchealth.co.uk
    Thursday, December 16, 2010 2:25 PM