BSOD Using Google Chrome or while playing any of my games

Page 2 of 3 FirstFirst 123 LastLast

  1. Posts : 17
    Windows 7 Professional x64
    Thread Starter
       #11

    Ok I couldn't get the on board graphics to work so I thought leave it for a bit and see what happens and all of a sudden it blue screens I thought it would of been fixed but know it is evident that it isn't

    The most recent BSOD info has been uploaded

    Problem signature:
    Problem Event Name: BlueScreen
    OS Version: 6.1.7601.2.1.0.256.48
    Locale ID: 2057

    Additional information about the problem:
    BCCode: 50
    BCP1: FFFFF6A0000B29A8
    BCP2: 0000000000000000
    BCP3: FFFFF80002BAE3B6
    BCP4: 0000000000000005
    OS Version: 6_1_7601
    Service Pack: 1_0
    Product: 256_1
      My Computer


  2. Posts : 17
    Windows 7 Professional x64
    Thread Starter
       #12

    I realise that there are a load of post in the BSOD Help and Support area at the moment so shall wait patiently
      My Computer


  3. Posts : 15,026
    Windows 10 Home 64Bit
       #13

    Code:
    Microsoft (R) Windows Debugger Version 6.2.9200.20512 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Users\USER\Downloads\Compressed\SF_24-11-2014\SF_24-11-2014\112414-11778-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 7601 (Service Pack 1) MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144
    Machine Name:
    Kernel base = 0xfffff800`02a10000 PsLoadedModuleList = 0xfffff800`02c53890
    Debug session time: Tue Nov 25 01:59:23.973 2014 (UTC + 6:00)
    System Uptime: 0 days 8:33:54.222
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ...............
    Loading User Symbols
    Loading unloaded module list
    ......
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 50, {fffff6a0000b29a8, 0, fffff80002bae3b6, 5}
    
    
    Could not read faulting driver name
    Probably caused by : memory_corruption ( nt!MiGetWorkingSetInfo+286 )
    
    Followup: MachineOwner
    ---------
    
    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    PAGE_FAULT_IN_NONPAGED_AREA (50)
    Invalid system memory was referenced.  This cannot be protected by try-except,
    it must be protected by a Probe.  Typically the address is just plain bad or it
    is pointing at freed memory.
    Arguments:
    Arg1: fffff6a0000b29a8, memory referenced.
    Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
    Arg3: fffff80002bae3b6, If non-zero, the instruction address which referenced the bad memory
    	address.
    Arg4: 0000000000000005, (reserved)
    
    Debugging Details:
    ------------------
    
    
    Could not read faulting driver name
    
    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cbd100
    GetUlongFromAddress: unable to read from fffff80002cbd1c0
     fffff6a0000b29a8 Nonpaged pool
    
    FAULTING_IP: 
    nt!MiGetWorkingSetInfo+286
    fffff800`02bae3b6 488b0408        mov     rax,qword ptr [rax+rcx]
    
    MM_INTERNAL_CODE:  5
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    
    BUGCHECK_STR:  0x50
    
    PROCESS_NAME:  chrome.exe
    
    CURRENT_IRQL:  0
    
    TRAP_FRAME:  fffff88009a98760 -- (.trap 0xfffff88009a98760)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=00000020000b29a8 rbx=0000000000000000 rcx=fffff68000000000
    rdx=000000000e9b8004 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff80002bae3b6 rsp=fffff88009a988f0 rbp=fffff88009a98b60
     r8=fffff880047aadf0  r9=fffff700010e2ea0 r10=fffffa80005b0170
    r11=fffff700010f0de0 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl nz na pe nc
    nt!MiGetWorkingSetInfo+0x286:
    fffff800`02bae3b6 488b0408        mov     rax,qword ptr [rax+rcx] ds:fffff6a0`000b29a8=????????????????
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from fffff80002b025b3 to fffff80002a85bc0
    
    STACK_TEXT:  
    fffff880`09a985f8 fffff800`02b025b3 : 00000000`00000050 fffff6a0`000b29a8 00000000`00000000 fffff880`09a98760 : nt!KeBugCheckEx
    fffff880`09a98600 fffff800`02a83cee : 00000000`00000000 fffff6a0`000b29a8 fffffa80`06ddca00 fffffa80`06b0f060 : nt! ?? ::FNODOBFM::`string'+0x43801
    fffff880`09a98760 fffff800`02bae3b6 : fffff880`09a98b60 00000000`00000000 00000000`00000088 fffff880`00000000 : nt!KiPageFault+0x16e
    fffff880`09a988f0 fffff800`02de5a25 : 00000000`fffeffff 00000000`1357f001 fffffa80`06b0f060 fffffa80`00000001 : nt!MiGetWorkingSetInfo+0x286
    fffff880`09a98980 fffff800`02a84e53 : 00000000`0000130c fffffa80`06b0f060 00000000`00000000 00000000`05c8e388 : nt! ?? ::NNGAKEGL::`string'+0x4c5f3
    fffff880`09a98a70 00000000`775e14ea : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    00000000`05c8e368 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x775e14ea
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    nt!MiGetWorkingSetInfo+286
    fffff800`02bae3b6 488b0408        mov     rax,qword ptr [rax+rcx]
    
    SYMBOL_STACK_INDEX:  3
    
    SYMBOL_NAME:  nt!MiGetWorkingSetInfo+286
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nt
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  531590fb
    
    IMAGE_NAME:  memory_corruption
    
    FAILURE_BUCKET_ID:  X64_0x50_nt!MiGetWorkingSetInfo+286
    
    BUCKET_ID:  X64_0x50_nt!MiGetWorkingSetInfo+286
    
    Followup: MachineOwner
    ---------
    Take memtest. Run for 8 passes and test each stick in a know good slot for an additional 6 passes.

     
    The goal is to test all the RAM sticks and all the motherboard slots.

    Check your motherboard manual to ensure the RAM sticks are in the recommended motherboard slots. Some motherboards have very specific slots required for the number of RAM sticks installed.

    If you get errors, stop the test and continue with the next step.

    1. Remove all but one stick of RAM from your computer (this will be RAM stick #1), and run Memtest86 again, for 7 passes.
    *Be sure to note the RAM stick, use a piece of tape with a number, and note the motherboard slot.
    If this stick passes the test then go to step #3.

    2. If RAM stick #1 has errors, repeat the test with RAM stick #2 in the same motherboard slot.
    *If RAM stick #2 passes, this indicates that RAM stick #1 may be bad. If you want to be absolutely sure, re-test RAM stick #1 in another known good slot.
    *If RAM stick #2 has errors, this indicates another possible bad RAM stick, a possible motherboard slot failure or inadequate settings.
    3. Test the next stick of RAM (stick #2) in the next motherboard slot.
    *If this RAM stick has errors repeat step #2 using a known good stick if possible, or another stick.
    *If this RAM stick has no errors and both sticks failed in slot#1, test RAM stick #1 in this slot.
    4. If you find a stick that passes the test, test it in all the other motherboard slots.

    If Part 2 testing shows errors, and all tests in Part 3 show errors, you will need to test the RAM sticks in another computer and/or test other RAM in your computer to identify the problem.

    In this way, you can identify whether it is a bad stick of RAM, a bad motherboard, or incompatibility between the sticks.
       Information
    Errors are sometimes found after 8 passes.

       Tip
    Memtest should be done overnight.
      My Computer


  4. Posts : 17
    Windows 7 Professional x64
    Thread Starter
       #14

    Ok I have literally been with out the internet for a while so I did that mem-test and I got no errors.

    However while I've been without the internet the computer still blue screens even if have it just sat doing nothing when I'm afk. I'll comeback to a login screen and an error after I logged back in.

    I'll post the most recent dump file's.
      My Computer


  5. Posts : 17
    Windows 7 Professional x64
    Thread Starter
       #15

    Here are the dump file's
      My Computer


  6. Posts : 17
    Windows 7 Professional x64
    Thread Starter
       #16

    Also I have replaced the Graphics Card recently and re-installed the drivers so I hope that rules out the possibility of it being that
      My Computer


  7. Posts : 15,026
    Windows 10 Home 64Bit
       #17

    Code:
    
    Microsoft (R) Windows Debugger Version 6.3.9600.16384 X86
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Users\YUSRA\Downloads\Compressed\SF_01-02-2015\SF_01-02-2015\013015-16676-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    
    ************* Symbol Path validation summary **************
    Response                         Time (ms)     Location
    Deferred                                       SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
    Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7601.18700.amd64fre.win7sp1_gdr.141211-1742
    Machine Name:
    Kernel base = 0xfffff800`02e4a000 PsLoadedModuleList = 0xfffff800`0308d890
    Debug session time: Fri Jan 30 15:44:41.559 2015 (UTC + 6:00)
    System Uptime: 0 days 0:14:32.808
    Loading Kernel Symbols
    .
    
    Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
    Run !sym noisy before .reload to track down problems loading symbols.
    
    ..............................................................
    ................................................................
    ......................
    Loading User Symbols
    Loading unloaded module list
    ....
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 50, {fffff6a00000d5a0, 0, fffff80002eaa85b, 5}
    
    
    Could not read faulting driver name
    Probably caused by : memory_corruption ( nt!MiAgeWorkingSet+1d1 )
    
    Followup: MachineOwner
    ---------
    
    2: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    PAGE_FAULT_IN_NONPAGED_AREA (50)
    Invalid system memory was referenced.  This cannot be protected by try-except,
    it must be protected by a Probe.  Typically the address is just plain bad or it
    is pointing at freed memory.
    Arguments:
    Arg1: fffff6a00000d5a0, memory referenced.
    Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
    Arg3: fffff80002eaa85b, If non-zero, the instruction address which referenced the bad memory
    	address.
    Arg4: 0000000000000005, (reserved)
    
    Debugging Details:
    ------------------
    
    
    Could not read faulting driver name
    
    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030f7100
    GetUlongFromAddress: unable to read from fffff800030f71c0
     fffff6a00000d5a0 Nonpaged pool
    
    FAULTING_IP: 
    nt!MiAgeWorkingSet+1d1
    fffff800`02eaa85b 488b19          mov     rbx,qword ptr [rcx]
    
    MM_INTERNAL_CODE:  5
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    
    BUGCHECK_STR:  0x50
    
    PROCESS_NAME:  MsMpEng.exe
    
    CURRENT_IRQL:  0
    
    ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) x86fre
    
    TRAP_FRAME:  fffff8800375c680 -- (.trap 0xfffff8800375c680)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000007ffffffff8 rbx=0000000000000000 rcx=fffff6a00000d5a0
    rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff80002eaa85b rsp=fffff8800375c810 rbp=000000200000d5a6
     r8=0000000000000001  r9=fffffa8008832ec8 r10=0000000000000005
    r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei ng nz na po cy
    nt!MiAgeWorkingSet+0x1d1:
    fffff800`02eaa85b 488b19          mov     rbx,qword ptr [rcx] ds:fffff6a0`0000d5a0=????????????????
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from fffff80002f3c603 to fffff80002ec0e80
    
    STACK_TEXT:  
    fffff880`0375c518 fffff800`02f3c603 : 00000000`00000050 fffff6a0`0000d5a0 00000000`00000000 fffff880`0375c680 : nt!KeBugCheckEx
    fffff880`0375c520 fffff800`02ebefae : 00000000`00000000 fffff6a0`0000d5a0 00000000`00000000 00000980`00000000 : nt! ?? ::FNODOBFM::`string'+0x43801
    fffff880`0375c680 fffff800`02eaa85b : 00000003`00000000 cbc00000`8262a867 00000000`00000000 00000000`00000cbc : nt!KiPageFault+0x16e
    fffff880`0375c810 fffff800`02f40f75 : fffffa80`08832ec8 fffff880`00000001 00000000`00000001 fffff880`0375ca70 : nt!MiAgeWorkingSet+0x1d1
    fffff880`0375c9c0 fffff800`02eaae06 : 00000000`0000036a 00000000`00000000 fffffa80`00000000 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x4c7f6
    fffff880`0375ca40 fffff800`02eab2b3 : 00000000`00000008 fffff880`0375cad0 00000000`00000001 fffffa80`00000000 : nt!MmWorkingSetManager+0x6e
    fffff880`0375ca90 fffff800`0315d0ca : fffffa80`036c19d0 00000000`00000080 fffffa80`0369e9e0 00000000`00000001 : nt!KeBalanceSetManager+0x1c3
    fffff880`0375cc00 fffff800`02eb1be6 : fffff880`03365180 fffffa80`036c19d0 fffff880`0336ffc0 e52d4c87`00d2e548 : nt!PspSystemThreadStartup+0x5a
    fffff880`0375cc40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    nt!MiAgeWorkingSet+1d1
    fffff800`02eaa85b 488b19          mov     rbx,qword ptr [rcx]
    
    SYMBOL_STACK_INDEX:  3
    
    SYMBOL_NAME:  nt!MiAgeWorkingSet+1d1
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nt
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  548a6e28
    
    IMAGE_VERSION:  6.1.7601.18700
    
    IMAGE_NAME:  memory_corruption
    
    FAILURE_BUCKET_ID:  X64_0x50_nt!MiAgeWorkingSet+1d1
    
    BUCKET_ID:  X64_0x50_nt!MiAgeWorkingSet+1d1
    
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:x64_0x50_nt!miageworkingset+1d1
    
    FAILURE_ID_HASH:  {0084eabb-4ea6-521c-73e7-0324b9249566}
    
    Followup: MachineOwner
    ---------
    
    Looks like the same error.

    Please uninstall Daemon Tools. It uses a driver called sptd.sys which is known to cause BSODs in Windows 7.

     SPTD Removal:

    • Uninstall the software using Add/Remove Programs.
    • Reboot the system.
    • Once the program is uninstalled, run sptd.sys uninstaller to remove the driver from your system.
    • DuplexSecure - Downloads
    As an alternative, many people recommend the use of Total Mounter or Magic ISO

     Clean boot


    Reduce items at start-up. No software except anti-virus is required plus doing this improves the time for logging into windows:

    Run Disk Check on your Hard Drive for file system errors and bad sectors on it.

     Hard Drive Diagnostics


    • Double click and open my computer.
    • Right click on desired drive and hit properties.
    • Click on tools tab and Check now.


    Read complete instructions on the tutorial: Disk Check

    Other Tests:
     



      My Computer


  8. Posts : 17
    Windows 7 Professional x64
    Thread Starter
       #18

    ok I'll do these step by step and see if it blue screens after doing each one. At this point it'll be the removal of daemon tools and SPTD.
      My Computer


  9. Posts : 17
    Windows 7 Professional x64
    Thread Starter
       #19

    ok so did the removal of Daemon Tools and SPTD and still got a blue screen going to do the next step.

    I'll upload the Dump files as well.
      My Computer


  10. Posts : 17
    Windows 7 Professional x64
    Thread Starter
       #20

    ok did a disk check no errors there now to do a clean start up
      My Computer


 
Page 2 of 3 FirstFirst 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 03:08.
Find Us