locked
Freeze Screens, crash to reboot and some Bsods RRS feed

  • Question

  • Hi Everyone! I have a Windows 7 Home basic running on 32-bit and I keep getting some very dismaying system crashes. Sometimes the whole screen just freezes and the computer wont respond to anything. Other times this freeze screen turns into a Bsod after a couple of seconds. Other times the computer just suddenly reboots. The crash sometimes also prevents my computer from rebooting properly. I think it has something to do with my internet browser google chrome, because majority of the crashes happen when I use it and surf the net but I am not so sure. I ran WinDbg  on MEMORY.dmp and here's what I got so far:

    Microsoft (R) Windows Debugger Version 6.2.8229.0 X86
    Copyright (c) Microsoft Corporation. All rights reserved.

    Loading Dump File [C:\Windows\MEMORY.DMP]
    Kernel Summary Dump File: Only kernel address space is available

    Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 7 Kernel Version 7600 MP (4 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 7600.16917.x86fre.win7_gdr.111118-2330
    Machine Name:
    Kernel base = 0x82e4a000 PsLoadedModuleList = 0x82f92810
    Debug session time: Fri Mar 23 17:53:58.979 2012 (UTC + 8:00)
    System Uptime: 0 days 0:03:22.540
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ..................
    Loading User Symbols
    PEB is paged out (Peb.Ldr = 7ffdf00c).  Type ".hh dbgerr001" for details
    Loading unloaded module list
    .....
    TRIAGER: Could not open triage file : C:\Program Files\Windows Kits\8.0\Debuggers\x86\triage\oca.ini, error 2
    TRIAGER: Could not open triage file : C:\Program Files\Windows Kits\8.0\Debuggers\x86\winxp\triage.ini, error 2
    TRIAGER: Could not open triage file : C:\Program Files\Windows Kits\8.0\Debuggers\x86\triage\user.ini, error 2
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    Use !analyze -v to get detailed debugging information.

    BugCheck A, {200, ff, 1, 82e9005a}

    TRIAGER: Could not open triage file : C:\Program Files\Windows Kits\8.0\Debuggers\x86\triage\modclass.ini, error 2
    Probably caused by : hardware ( nt!KiTrap0D+18e )


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


    3: 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: 00000200, memory referenced
    Arg2: 000000ff, IRQL
    Arg3: 00000001, 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: 82e9005a, address which referenced memory


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


    TRIAGER: Could not open triage file : C:\Program Files\Windows Kits\8.0\Debuggers\x86\triage\modclass.ini, error 2


    WRITE_ADDRESS:  00000200 


    CURRENT_IRQL:  0


    FAULTING_IP: 
    nt!KiTrap0D+18e
    82e9005a df0f            fisttp  word ptr [edi]


    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT


    BUGCHECK_STR:  0xA


    PROCESS_NAME:  chrome.exe


    TRAP_FRAME:  a7de7708 -- (.trap 0xffffffffa7de7708)
    ErrCode = 00000002
    eax=00000023 ebx=a7de7d0c ecx=879cf550 edx=a7de77fc esi=86715000 edi=00000200
    eip=82e9005a esp=a7de777c ebp=a7de777c iopl=0         nv up di pl nz na po nc
    cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010002
    nt!KiTrap0D+0x18e:
    82e9005a df0f            fisttp  word ptr [edi]           ds:0023:00000200=????
    Resetting default scope


    MISALIGNED_IP: 
    nt!KiTrap0D+18e
    82e9005a df0f            fisttp  word ptr [edi]


    LAST_CONTROL_TRANSFER:  from 82e9005a to 82e9086b


    STACK_TEXT:  
    a7de7708 82e9005a badb0d00 a7de77fc 00000000 nt!KiTrap0E+0x2cf
    a7de777c 82efc50e 00000000 84bffc40 82e18ba9 nt!KiTrap0D+0x18e
    a7de7820 82e76714 00000200 08000000 86f67100 nt!MiReleaseConfirmedPageFileSpace+0x52
    a7de7c84 82efe1e6 c0021978 87eb0748 85eb20e3 nt!MiDecommitPages+0x3b5
    a7de7d1c 82e8d48a ffffffff 01c1f820 01c1f824 nt!NtFreeVirtualMemory+0x882
    a7de7d1c 77c86194 ffffffff 01c1f820 01c1f824 nt!KiFastCallEntry+0x12a
    WARNING: Frame IP not in any known module. Following frames may be wrong.
    01c1f814 00000000 00000000 00000000 00000000 0x77c86194




    STACK_COMMAND:  kb


    FOLLOWUP_IP: 
    nt!KiTrap0D+18e
    82e9005a df0f            fisttp  word ptr [edi]

    SYMBOL_STACK_INDEX:  1

    SYMBOL_NAME:  nt!KiTrap0D+18e

    FOLLOWUP_NAME:  MachineOwner

    IMAGE_NAME:  hardware

    DEBUG_FLR_IMAGE_TIMESTAMP:  0

    MODULE_NAME: hardware

    FAILURE_BUCKET_ID:  IP_MISALIGNED

    BUCKET_ID:  IP_MISALIGNED

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


    3: kd> kL
    ChildEBP RetAddr  
    a7de7708 82e9005a nt!KiTrap0E+0x2cf
    a7de777c 82efc50e nt!KiTrap0D+0x18e
    a7de7820 82e76714 nt!MiReleaseConfirmedPageFileSpace+0x52
    a7de7c84 82efe1e6 nt!MiDecommitPages+0x3b5
    a7de7d1c 82e8d48a nt!NtFreeVirtualMemory+0x882
    a7de7d1c 77c86194 nt!KiFastCallEntry+0x12a
    WARNING: Frame IP not in any known module. Following frames may be wrong.
    01c1f814 00000000 0x77c86194
    3: kd> r
    eax=82f8117c ebx=a7de7700 ecx=0000000c edx=00000000 esi=8af38120 edi=00000000
    eip=82e9086b esp=a7de76f0 ebp=a7de7708 iopl=0         nv up ei pl nz na po nc
    cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00000202
    nt!KiTrap0E+0x2cf:
    82e9086b 833dc4dafa8200  cmp     dword ptr [nt!KiFreezeFlag (82fadac4)],0 ds:0023:82fadac4=00000000


    Here's sample from Event Viewer of the log of one of the crashes which turns out to be of a Kernel-Power source:

    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    - <System>
    <Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331C3B3A-2005-44C2-AC5E-77220C37D6B4}" />
    <EventID>41</EventID>
    <Version>2</Version>
    <Level>1</Level>
    <Task>63</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8000000000000002</Keywords>
    <TimeCreated SystemTime="2012-03-24T01:47:01.724410900Z" />
    <EventRecordID>40601</EventRecordID>
    <Correlation />
    <Execution ProcessID="4" ThreadID="8" />
    <Channel>System</Channel>
    <Computer>Lorenzo-PC</Computer>
    <Security UserID="S-1-5-18" />
    </System>
    - <EventData>
    <Data Name="BugcheckCode">0</Data>
    <Data Name="BugcheckParameter1">0x0</Data>
    <Data Name="BugcheckParameter2">0x0</Data>
    <Data Name="BugcheckParameter3">0x0</Data>
    <Data Name="BugcheckParameter4">0x0</Data>
    <Data Name="SleepInProgress">false</Data>
    <Data Name="PowerButtonTimestamp">0</Data>
    </EventData>
    </Event>

    I am really stupid when it comes to crash dump analysis and I just can't figure out from the WinDbg what really is causing my problem.  I really would appreciate some help. Please tell me if I need to post more information about the crashes or perhaps some more details from WinDbg. Thanks everyone!

    Saturday, March 24, 2012 2:18 AM

Answers

  • No problem.

    Try run memory scan using Windows 7 installation DVD. Pass language to install and select Repair your computer.

    It will open System Recovery Options from where Windows Memory Diagnostic will be available.

    I am still not convinced about RAM or even CPU.

    Try other browser such I.E for a while to indicate if the system behave the same way.

    Bart


    Bartosz Kurowski Senior Desktop Support, Microsoft Cerified Trainer. MCP, MCT, MCTS, MCITP, MOS

    • Marked as answer by Cloud_TS Wednesday, March 28, 2012 1:51 AM
    Saturday, March 24, 2012 8:34 AM

All replies

  • Hi IhateBSODS,

    From what I read, it seems to me it is a hardware problem rather then the browser. Google Chrom uses internal RAM to allocate its files to run.

    I would start investigation from scanning RAM and / or replacing it. Use built-in hardware scan or DART from Microsoft.

    Bart 


    Bartosz Kurowski Senior Desktop Support, Microsoft Cerified Trainer. MCP, MCT, MCTS, MCITP, MOS

    Saturday, March 24, 2012 7:02 AM
  • Thanks BArt IT. I'll get right on it. I recently had a memory scan and my technician said it was okay, I don't know about the drives though. Where can i get the DART from microsoft? Thanks again!


    Lorenzo de Vera

    Saturday, March 24, 2012 8:00 AM
  • No problem.

    Try run memory scan using Windows 7 installation DVD. Pass language to install and select Repair your computer.

    It will open System Recovery Options from where Windows Memory Diagnostic will be available.

    I am still not convinced about RAM or even CPU.

    Try other browser such I.E for a while to indicate if the system behave the same way.

    Bart


    Bartosz Kurowski Senior Desktop Support, Microsoft Cerified Trainer. MCP, MCT, MCTS, MCITP, MOS

    • Marked as answer by Cloud_TS Wednesday, March 28, 2012 1:51 AM
    Saturday, March 24, 2012 8:34 AM
  • memtest86+ is more reliable for testing memory,

    http://mikemstech.blogspot.com/2011/11/troubleshooting-memory-errors.html

    The fault bucket is saying the instruction pointer is misaligned, indicating more of a software issue. Does the error occur if chrome is shut down and you use another browser like Firefox or IE?
    Thursday, March 29, 2012 7:25 PM
  • I have a question. what if you don't have the windows 7 installation dvd. what do you do

    Saturday, January 3, 2015 8:31 PM