Windows 7 Ultimate x64, uTorrent & AVG

Page 1 of 4 123 ... LastLast

  1. Posts : 12
    Windows 7 Ultimate x64
       #1

    Windows 7 Ultimate x64, uTorrent & AVG


    I have those installed for about a week or so, but only last night I had the first bsod, and the second this morning.

    All I did recently was to update my chipset drivers (from asrock's website) and install safari. If of any use, the display and sound first froze for a few seconds, then the bs appeared, with the sound continuing to "broom".

    Also mentionable - i only downloaded small files until last night ( >2GB ), when I added something larger (<11GB). I am at work for now, and I'll post the dump files when I get home, but it's on my nerves.
      My Computer


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

    Welcome!

    We do need the dmp files, but for now, try a system restore to get to a point before the troubles.
      My Computer


  3. JMH
    Posts : 7,952
    Win 7 Ultimate 64-bit. SP1.
       #3

    dreadboy said:
    I have those installed for about a week or so, but only last night I had the first bsod, and the second this morning.

    All I did recently was to update my chipset drivers (from asrock's website) and install safari. If of any use, the display and sound first froze for a few seconds, then the bs appeared, with the sound continuing to "broom".

    Also mentionable - i only downloaded small files until last night ( >2GB ), when I added something larger (<11GB). I am at work for now, and I'll post the dump files when I get home, but it's on my nerves.
    Hi ,
    We will get a more definitive overview of your problems if you follow this advice.https://www.sevenforums.com/crash-loc...d-problem.html
    Upload all of the minidump files located in C:\Windows\Minidump

    Please also provide the following information -
    1. How was Windows 7 installed? Was it an upgrade installation or a clean installation?
    2. List red error messages in the Event Log for more information:
    a. Click "Start", input "eventvwr" (without quotation marks) in the Start Search bar and press Enter.
    b. Go to Windows Logs - Application - note red errors.
    Thanks.
    Jan.
      My Computer


  4. Posts : 12
    Windows 7 Ultimate x64
    Thread Starter
       #4

    I did try a system restore this morning, after which I got the second BSOD. I will upload the dump files as soon as I get home. Just wanted to have a confirmation for my peace of mind for now, that it's not the hardware going wrong. I did test the memory this morning too and it's ok.

    Windows 7 was installed on the clean. No upgrade

    I am guessing (hopping it's not the hardware because I changed absolutely nothing hardware-wise) and everything was working fine as is. Only changes made are the ones above. Thanks you for your time
      My Computer


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

    We'll see in a bit. Good luck!
      My Computer


  6. Posts : 12
    Windows 7 Ultimate x64
    Thread Starter
       #6

    I uploaded the dump file here

    Awaiting your reply/replies and thank you in advance. now that I see how things go, I have uTorrent open since I got home and nothing happened.

    There's only one thing that changed -> safari is not installed and not running anymore. Both times that I got BSoD Safari was running. I`m installing it after the download finishes in uTorrent just to check this hypothesis
    Last edited by dreadboy; 14 Apr 2010 at 11:49. Reason: because i'm dumn and forget things.
      My Computer


  7. Posts : 12
    Windows 7 Ultimate x64
    Thread Starter
       #7

    in the mean time, i got the bsod again. with safari running already.

    this time i got to read the top of the bs, irq less or equal . here is the new minidump from about 5 minutes ago.
      My Computer


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

    That one looks like bad RAM. Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder. Boot from the CD, and run at least 5 passes.

    Also, uninstall AVG with Revo Uninstaller, as it is known to cause many issues, including BSODs.

    Then install Microsoft Security Essentials.

    Code:
    Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Users\Jonathan\AppData\Local\Temp\Temp1_041410-26625-01.zip\041410-26625-01.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
    Executable search path is: 
    Windows 7 Kernel Version 7600 MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
    Machine Name:
    Kernel base = 0xfffff800`02813000 PsLoadedModuleList = 0xfffff800`02a50e50
    Debug session time: Wed Apr 14 14:17:27.625 2010 (GMT-4)
    System Uptime: 0 days 2:09:37.000
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ............
    Loading User Symbols
    Loading unloaded module list
    .......
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck A, {fffff68000007650, 0, 0, fffff80002898ae2}
    
    Probably caused by : memory_corruption ( nt!MiAgeWorkingSet+1c2 )
    
    Followup: MachineOwner
    ---------
    
    2: 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: fffff68000007650, memory referenced
    Arg2: 0000000000000000, IRQL
    Arg3: 0000000000000000, 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: fffff80002898ae2, address which referenced memory
    
    Debugging Details:
    ------------------
    
    
    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002abb0e0
     fffff68000007650 
    
    CURRENT_IRQL:  0
    
    FAULTING_IP: 
    nt!MiAgeWorkingSet+1c2
    fffff800`02898ae2 488b19          mov     rbx,qword ptr [rcx]
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    BUGCHECK_STR:  0xA
    
    PROCESS_NAME:  csrss.exe
    
    TRAP_FRAME:  fffff880031db760 -- (.trap 0xfffff880031db760)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000007ffffffff8 rbx=0000000000000000 rcx=fffff68000007650
    rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff80002898ae2 rsp=fffff880031db8f0 rbp=0000000000007656
     r8=0000000000000001  r9=fffffa8002cafb88 r10=0000000000000005
    r11=0000000000000005 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei ng nz na po cy
    nt!MiAgeWorkingSet+0x1c2:
    fffff800`02898ae2 488b19          mov     rbx,qword ptr [rcx] ds:fffff680`00007650=2100000021420005
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from fffff80002884469 to fffff80002884f00
    
    STACK_TEXT:  
    fffff880`031db618 fffff800`02884469 : 00000000`0000000a fffff680`00007650 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
    fffff880`031db620 fffff800`028830e0 : 00000000`00000000 00000980`00000000 00000000`00001000 fffff800`029b7bfe : nt!KiBugCheckDispatch+0x69
    fffff880`031db760 fffff800`02898ae2 : 00000000`00000f6b 00000000`00000001 00000000`00000002 00000000`00000f5d : nt!KiPageFault+0x260
    fffff880`031db8f0 fffff800`02905a0e : fffffa80`02cafb88 fffff880`00000001 00000000`00000001 fffff880`031dbb70 : nt!MiAgeWorkingSet+0x1c2
    fffff880`031dbaa0 fffff800`028996e2 : 00000000`00001e62 00000000`00000000 fffffa80`00000000 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x49926
    fffff880`031dbb40 fffff800`0289996f : 00000000`00000008 fffff880`031dbbd0 00000000`00000001 fffffa80`00000000 : nt!MmWorkingSetManager+0x6e
    fffff880`031dbb90 fffff800`02b28166 : fffffa80`018c9040 00000000`00000080 fffffa80`0184a890 00000000`00000001 : nt!KeBalanceSetManager+0x1c3
    fffff880`031dbd00 fffff800`02863486 : fffff880`02f63180 fffffa80`018c9040 fffff880`02f6dfc0 3e1e9953`bab7fe93 : nt!PspSystemThreadStartup+0x5a
    fffff880`031dbd40 00000000`00000000 : fffff880`031dc000 fffff880`031d6000 fffff880`031db6d0 00000000`00000000 : nt!KxStartSystemThread+0x16
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    nt!MiAgeWorkingSet+1c2
    fffff800`02898ae2 488b19          mov     rbx,qword ptr [rcx]
    
    SYMBOL_STACK_INDEX:  3
    
    SYMBOL_NAME:  nt!MiAgeWorkingSet+1c2
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nt
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc600
    
    IMAGE_NAME:  memory_corruption
    
    FAILURE_BUCKET_ID:  X64_0xA_nt!MiAgeWorkingSet+1c2
    
    BUCKET_ID:  X64_0xA_nt!MiAgeWorkingSet+1c2
    
    Followup: MachineOwner
    ---------
      My Computer


  9. Posts : 12
    Windows 7 Ultimate x64
    Thread Starter
       #9

    Thank you very much. Good thing I just bought the RAM, so I can take it back.

    One question though. If it's the RAM then it should also crash like that when I will be using Photoshop right?

    I see the "An attempt was made to access a pageable (or completely invalid) address at an
    interrupt request level (IRQL) that is too high." so I could have set the pagefile too low?

    Also consider that on average [ just a browser and messenger open ] I still have less than 50% free physical memory.
      My Computer


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

    Bad RAM can crash at any moment, for no apparent reason. Right now, I am suffering from memory errors. I only get them when the last 2GB are being used, when I am running my virtual machines. Funny thing is, though, that even loaded to the max, it doesn't always crash.
      My Computer


 
Page 1 of 4 123 ... 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 15:47.
Find Us