Help please with BSOD !!


  1. Posts : 3
    Windows 7 Home Premium
       #1

    Help please with BSOD !!


    I've installed Windwos 7 Home Premium on a Acer Aspire One and i started getting BSOD,i don't know how to read the minidump files and i uploaded as .dmp hopeing it will help in sloveing my problem,i cannot tell the error cause of my monitor being 8'9 inches,when it craseh i cannot read it to tell at least some more detalis.But please if can someone help me,i would be more then gratefull.
    Thanks.
      My Computer


  2. Posts : 28,845
    Win 8 Release candidate 8400
       #2

    zapo said:
    I've installed Windwos 7 Home Premium on a Acer Aspire One and i started getting BSOD,i don't know how to read the minidump files and i uploaded as .dmp hopeing it will help in sloveing my problem,i cannot tell the error cause of my monitor being 8'9 inches,when it craseh i cannot read it to tell at least some more detalis.But please if can someone help me,i would be more then gratefull.
    Thanks.
    Pretty straight forward. This one was casused by memory corruption.

    To test yours:
    Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Boot from the CD, and leave it running for at least 5 or 6 passes.

    Let us know if you need help

    Ken

    Code:
    Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Users\K\Desktop\072310-27346-01 - Copy.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    Symbol search path is: SRV*C:\symbols*http://msdl.microsoft.com/download/symbols;srv*e:\symbols
    *http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 7600.16385.x86fre.win7_rtm.090713-1255
    Machine Name:
    Kernel base = 0x8183e000 PsLoadedModuleList = 0x8197d570
    Debug session time: Thu Jul 22 18:06:54.623 2010 (GMT-4)
    System Uptime: 0 days 4:11:00.342
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ..................
    Loading User Symbols
    Loading unloaded module list
    ......
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck A, {2c, 2, 0, 818feab8}
    
    Probably caused by : memory_corruption ( nt!MiReleaseConfirmedPageFileSpace+20 )
    
    Followup: MachineOwner
    ---------
    
    1: 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: 0000002c, memory referenced
    Arg2: 00000002, IRQL
    Arg3: 00000000, 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: 818feab8, address which referenced memory
    
    Debugging Details:
    ------------------
    
    
    READ_ADDRESS: GetPointerFromAddress: unable to read from 8199d700
    Unable to read MiSystemVaType memory at 8197d0c0
     0000002c 
    
    CURRENT_IRQL:  2
    
    FAULTING_IP: 
    nt!MiReleaseConfirmedPageFileSpace+20
    818feab8 8b7e2c          mov     edi,dword ptr [esi+2Ch]
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    BUGCHECK_STR:  0xA
    
    PROCESS_NAME:  System
    
    TRAP_FRAME:  ad302a94 -- (.trap 0xffffffffad302a94)
    ErrCode = 00000000
    eax=00000004 ebx=00304208 ecx=82c0603c edx=ad302b83 esi=00000000 edi=00000000
    eip=818feab8 esp=ad302b08 ebp=ad302b34 iopl=0         nv up ei pl nz na po nc
    cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010202
    nt!MiReleaseConfirmedPageFileSpace+0x20:
    818feab8 8b7e2c          mov     edi,dword ptr [esi+2Ch] ds:0023:0000002c=????????
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from 818feab8 to 81876b5b
    
    STACK_TEXT:  
    ad302a94 818feab8 badb0d00 ad302b83 00010022 nt!KiTrap0E+0x2cf
    ad302b34 818b60cb 00304208 000c0000 00000000 nt!MiReleaseConfirmedPageFileSpace+0x20
    ad302b8c 81a60cc0 83752b08 83752b08 83752b30 nt!MiDeleteSegmentPages+0x2ab
    ad302bbc 818b5848 83752b08 86de9120 83752b30 nt!MiSegmentDelete+0xec
    ad302be8 818b7e9a 83752b08 a9122000 a9122030 nt!MiCheckControlArea+0x202
    ad302c08 81a87005 83752b08 00000000 83576a80 nt!MiDereferenceControlAreaBySection+0x87
    ad302c2c 81a8621f 83752b08 a9122030 a9122018 nt!MiSectionDelete+0x103
    ad302c44 8189436a 00000000 844c9ac0 00000000 nt!ObpRemoveObjectRoutine+0x59
    ad302c58 818942da a9122030 818c7750 00000000 nt!ObfDereferenceObjectWithTag+0x88
    ad302c60 818c7750 00000000 844c9ac0 83b841f8 nt!ObfDereferenceObject+0xd
    ad302c78 818ca9b7 00000001 83b841f8 85a2f1e0 nt!CcDeleteSharedCacheMap+0xc4
    ad302ca8 818d1fb3 ad302cc4 b7a310de 835730d0 nt!CcWriteBehind+0x715
    ad302d00 81899043 835730d0 00000000 83b77b58 nt!CcWorkerThread+0x164
    ad302d50 81a25d16 80000000 b7a3104e 00000000 nt!ExpWorkerThread+0x10d
    ad302d90 818c7159 81898f36 80000000 00000000 nt!PspSystemThreadStartup+0x9e
    00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    nt!MiReleaseConfirmedPageFileSpace+20
    818feab8 8b7e2c          mov     edi,dword ptr [esi+2Ch]
    
    SYMBOL_STACK_INDEX:  1
    
    SYMBOL_NAME:  nt!MiReleaseConfirmedPageFileSpace+20
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nt
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bbffc
    
    IMAGE_NAME:  memory_corruption
    
    FAILURE_BUCKET_ID:  0xA_nt!MiReleaseConfirmedPageFileSpace+20
    
    BUCKET_ID:  0xA_nt!MiReleaseConfirmedPageFileSpace+20
    
    Followup: MachineOwner
    ---------
    
    1: 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: 0000002c, memory referenced
    Arg2: 00000002, IRQL
    Arg3: 00000000, 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: 818feab8, address which referenced memory
    
    Debugging Details:
    ------------------
    
    
    READ_ADDRESS: GetPointerFromAddress: unable to read from 8199d700
    Unable to read MiSystemVaType memory at 8197d0c0
     0000002c 
    
    CURRENT_IRQL:  2
    
    FAULTING_IP: 
    nt!MiReleaseConfirmedPageFileSpace+20
    818feab8 8b7e2c          mov     edi,dword ptr [esi+2Ch]
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    BUGCHECK_STR:  0xA
    
    PROCESS_NAME:  System
    
    TRAP_FRAME:  ad302a94 -- (.trap 0xffffffffad302a94)
    ErrCode = 00000000
    eax=00000004 ebx=00304208 ecx=82c0603c edx=ad302b83 esi=00000000 edi=00000000
    eip=818feab8 esp=ad302b08 ebp=ad302b34 iopl=0         nv up ei pl nz na po nc
    cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010202
    nt!MiReleaseConfirmedPageFileSpace+0x20:
    818feab8 8b7e2c          mov     edi,dword ptr [esi+2Ch] ds:0023:0000002c=????????
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from 818feab8 to 81876b5b
    
    STACK_TEXT:  
    ad302a94 818feab8 badb0d00 ad302b83 00010022 nt!KiTrap0E+0x2cf
    ad302b34 818b60cb 00304208 000c0000 00000000 nt!MiReleaseConfirmedPageFileSpace+0x20
    ad302b8c 81a60cc0 83752b08 83752b08 83752b30 nt!MiDeleteSegmentPages+0x2ab
    ad302bbc 818b5848 83752b08 86de9120 83752b30 nt!MiSegmentDelete+0xec
    ad302be8 818b7e9a 83752b08 a9122000 a9122030 nt!MiCheckControlArea+0x202
    ad302c08 81a87005 83752b08 00000000 83576a80 nt!MiDereferenceControlAreaBySection+0x87
    ad302c2c 81a8621f 83752b08 a9122030 a9122018 nt!MiSectionDelete+0x103
    ad302c44 8189436a 00000000 844c9ac0 00000000 nt!ObpRemoveObjectRoutine+0x59
    ad302c58 818942da a9122030 818c7750 00000000 nt!ObfDereferenceObjectWithTag+0x88
    ad302c60 818c7750 00000000 844c9ac0 83b841f8 nt!ObfDereferenceObject+0xd
    ad302c78 818ca9b7 00000001 83b841f8 85a2f1e0 nt!CcDeleteSharedCacheMap+0xc4
    ad302ca8 818d1fb3 ad302cc4 b7a310de 835730d0 nt!CcWriteBehind+0x715
    ad302d00 81899043 835730d0 00000000 83b77b58 nt!CcWorkerThread+0x164
    ad302d50 81a25d16 80000000 b7a3104e 00000000 nt!ExpWorkerThread+0x10d
    ad302d90 818c7159 81898f36 80000000 00000000 nt!PspSystemThreadStartup+0x9e
    00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    nt!MiReleaseConfirmedPageFileSpace+20
    818feab8 8b7e2c          mov     edi,dword ptr [esi+2Ch]
    
    SYMBOL_STACK_INDEX:  1
    
    SYMBOL_NAME:  nt!MiReleaseConfirmedPageFileSpace+20
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nt
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bbffc
    
    IMAGE_NAME:  memory_corruption
    
    FAILURE_BUCKET_ID:  0xA_nt!MiReleaseConfirmedPageFileSpace+20
    
    BUCKET_ID:  0xA_nt!MiReleaseConfirmedPageFileSpace+20
    
    Followup: MachineOwner
    ---------
    
    1: 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: 0000002c, memory referenced
    Arg2: 00000002, IRQL
    Arg3: 00000000, 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: 818feab8, address which referenced memory
    
    Debugging Details:
    ------------------
    
    
    READ_ADDRESS: GetPointerFromAddress: unable to read from 8199d700
    Unable to read MiSystemVaType memory at 8197d0c0
     0000002c 
    
    CURRENT_IRQL:  2
    
    FAULTING_IP: 
    nt!MiReleaseConfirmedPageFileSpace+20
    818feab8 8b7e2c          mov     edi,dword ptr [esi+2Ch]
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    BUGCHECK_STR:  0xA
    
    PROCESS_NAME:  System
    
    TRAP_FRAME:  ad302a94 -- (.trap 0xffffffffad302a94)
    ErrCode = 00000000
    eax=00000004 ebx=00304208 ecx=82c0603c edx=ad302b83 esi=00000000 edi=00000000
    eip=818feab8 esp=ad302b08 ebp=ad302b34 iopl=0         nv up ei pl nz na po nc
    cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010202
    nt!MiReleaseConfirmedPageFileSpace+0x20:
    818feab8 8b7e2c          mov     edi,dword ptr [esi+2Ch] ds:0023:0000002c=????????
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from 818feab8 to 81876b5b
    
    STACK_TEXT:  
    ad302a94 818feab8 badb0d00 ad302b83 00010022 nt!KiTrap0E+0x2cf
    ad302b34 818b60cb 00304208 000c0000 00000000 nt!MiReleaseConfirmedPageFileSpace+0x20
    ad302b8c 81a60cc0 83752b08 83752b08 83752b30 nt!MiDeleteSegmentPages+0x2ab
    ad302bbc 818b5848 83752b08 86de9120 83752b30 nt!MiSegmentDelete+0xec
    ad302be8 818b7e9a 83752b08 a9122000 a9122030 nt!MiCheckControlArea+0x202
    ad302c08 81a87005 83752b08 00000000 83576a80 nt!MiDereferenceControlAreaBySection+0x87
    ad302c2c 81a8621f 83752b08 a9122030 a9122018 nt!MiSectionDelete+0x103
    ad302c44 8189436a 00000000 844c9ac0 00000000 nt!ObpRemoveObjectRoutine+0x59
    ad302c58 818942da a9122030 818c7750 00000000 nt!ObfDereferenceObjectWithTag+0x88
    ad302c60 818c7750 00000000 844c9ac0 83b841f8 nt!ObfDereferenceObject+0xd
    ad302c78 818ca9b7 00000001 83b841f8 85a2f1e0 nt!CcDeleteSharedCacheMap+0xc4
    ad302ca8 818d1fb3 ad302cc4 b7a310de 835730d0 nt!CcWriteBehind+0x715
    ad302d00 81899043 835730d0 00000000 83b77b58 nt!CcWorkerThread+0x164
    ad302d50 81a25d16 80000000 b7a3104e 00000000 nt!ExpWorkerThread+0x10d
    ad302d90 818c7159 81898f36 80000000 00000000 nt!PspSystemThreadStartup+0x9e
    00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    nt!MiReleaseConfirmedPageFileSpace+20
    818feab8 8b7e2c          mov     edi,dword ptr [esi+2Ch]
    
    SYMBOL_STACK_INDEX:  1
    
    SYMBOL_NAME:  nt!MiReleaseConfirmedPageFileSpace+20
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nt
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bbffc
    
    IMAGE_NAME:  memory_corruption
    
    FAILURE_BUCKET_ID:  0xA_nt!MiReleaseConfirmedPageFileSpace+20
    
    BUCKET_ID:  0xA_nt!MiReleaseConfirmedPageFileSpace+20
    
    Followup: MachineOwner
    ---------
      My Computer


  3. Posts : 3
    Windows 7 Home Premium
    Thread Starter
       #3

    thanks,i will do a test and then come up with more dates,i hope it will do the BSOD :)
      My Computer


  4. Posts : 3
    Windows 7 Home Premium
    Thread Starter
       #4

    I did it,but found no errors.BSOD still appears:
    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: f4
    BCP1: 00000003
    BCP2: 84FA5B38
    BCP3: 84FA5CA4
    BCP4: 81A28810
    OS Version: 6_1_7600
    Service Pack: 0_0
    Product: 768_1

    Files that help describe the problem:
    C:\Windows\Minidump\072510-26223-01.dmp
    C:\Users\victor\AppData\Local\Temp\WER-36956-0.sysdata.xml

    Read our privacy statement online:
    Windows 7 Privacy Statement - Microsoft Windows

    If the online privacy statement is not available, please read our privacy statement offline:
    C:\Windows\system32\en-US\erofflps.txt


    ----

    And i atach the new dump file.Please can you help me more?
      My Computer


  5. Posts : 13,354
    Windows 7 Professional x64
       #5

    Please enable driver verifier: Using Driver Verifier to identify issues with Drivers

    There are some things I would like to check, but I need some more info. After your computer crashes a few more times, could you follow these instructions?
      My Computer


 

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