Randomly Reboots BSOD for months!

Page 2 of 2 FirstFirst 12

  1. Posts : 6,885
    Windows 7 Ultimate x64, Mint 9
       #11

    Appears to be caused in part by Chrome.

    ~Lordbob
      My Computer


  2. Posts : 11
    Windows 7 Ultimate 64x
    Thread Starter
       #12

    Well, maybe these ones but it still happens when Chrome wasn't installed and when it's not on...
      My Computer


  3. Posts : 11
    Windows 7 Ultimate 64x
    Thread Starter
       #13

    Well, I have a new minidump, everything was fine, then I turned Itunes on, it played a song for a couple of second and then BSOD'd. And the Sound froze. I'll check my audio drivers again.
      My Computer


  4. Posts : 5
    Windows 7
       #14

    Device problem solved


    I don't know if this might be any help, but I had the same problem with a new build for several weeks. The machine would start in the morning and 15 minutes later it would BSOD. Then randomly during the day the same thing would happen. I tested the RAM and it tested fine with Memtest and nothing was running hot. I had built an identical machine the same day that ran just fine. I was really stumped until...I realized the identical machine was not identical. I had used an older Logitech mouse with the problem machine and the other one had an older Microsoft mouse. I looked for new drivers for the older Logitech and could not find ones the were certified to work with Windows 7. So, I purchased a new Logitech wireless mouse and have not had a problem since. Sometimes it's the little things.
      My Computer


  5. Posts : 11
    Windows 7 Ultimate 64x
    Thread Starter
       #15

    and another one!
      My Computer


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

    Mkkl said:
    and another one!

    MKKI


    This one was caused by the directx portion of your video driver (dxgmms1.sys).

    You need to completely uninstall the video driver and install a fresh copy. Dont use the windows update, go to the mfr web site.

    Also run a system file check
    type cmd in search>right click and run as admin>sfc /scannow

    If you are overclocking stop

    Let us know the results

    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\021810-21637-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    Symbol search path is: SRV*d:\symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 7 Kernel Version 7600 MP (2 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
    Machine Name:
    Kernel base = 0xfffff800`02e0c000 PsLoadedModuleList = 0xfffff800`03049e50
    Debug session time: Thu Feb 18 09:38:22.040 2010 (GMT-5)
    System Uptime: 0 days 3:10:08.664
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ........................................
    Loading User Symbols
    Loading unloaded module list
    ............
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck C5, {108, 2, 0, fffff80002fb136b}
    
    Unable to load image \SystemRoot\System32\drivers\dxgkrnl.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for dxgkrnl.sys
    *** ERROR: Module load completed but symbols could not be loaded for dxgkrnl.sys
    *** WARNING: Unable to verify timestamp for atikmdag.sys
    *** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
    Probably caused by : 
    Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Users\K\Desktop\021810-21637-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    Symbol search path is: SRV*d:\symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 7 Kernel Version 7600 MP (2 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
    Machine Name:
    Kernel base = 0xfffff800`02e0c000 PsLoadedModuleList = 0xfffff800`03049e50
    Debug session time: Thu Feb 18 09:38:22.040 2010 (GMT-5)
    System Uptime: 0 days 3:10:08.664
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ........................................
    Loading User Symbols
    Loading unloaded module list
    ............
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck C5, {108, 2, 0, fffff80002fb136b}
    
    Unable to load image \SystemRoot\System32\drivers\dxgkrnl.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for dxgkrnl.sys
    *** ERROR: Module load completed but symbols could not be loaded for dxgkrnl.sys
    *** WARNING: Unable to verify timestamp for atikmdag.sys
    *** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
    Probably caused by : dxgmms1.sys ( dxgmms1!VidSchiSignalRegisteredEvent+e7 )
    
    Followup: MachineOwner
    ---------
    
    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    DRIVER_CORRUPTED_EXPOOL (c5)
    An attempt was made to access a pageable (or completely invalid) address at an
    interrupt request level (IRQL) that is too high.  This is
    caused by drivers that have corrupted the system pool.  Run the driver
    verifier against any new (or suspect) drivers, and if that doesn't turn up
    the culprit, then use gflags to enable special pool.
    Arguments:
    Arg1: 0000000000000108, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
    Arg4: fffff80002fb136b, address which referenced memory
    
    Debugging Details:
    ------------------
    
    
    BUGCHECK_STR:  0xC5_2
    
    CURRENT_IRQL:  2
    
    FAULTING_IP: 
    nt!ExFreePoolWithTag+2bb
    fffff800`02fb136b 418b8708010000  mov     eax,dword ptr [r15+108h]
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    PROCESS_NAME:  svchost.exe
    
    TRAP_FRAME:  fffff80000ba2610 -- (.trap 0xfffff80000ba2610)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000000000200 rbx=0000000000000000 rcx=fffff80002ff7e80
    rdx=0000000000000004 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff80002fb136b rsp=fffff80000ba27a8 rbp=0000000000000000
     r8=0000000000005f00  r9=0000000000000150 r10=fffff80002e0c000
    r11=0000000000000260 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl nz na po cy
    nt!ExFreePoolWithTag+0x2bb:
    fffff800`02fb136b 418b8708010000  mov     eax,dword ptr [r15+108h] ds:dd50:00000000`00000108=????????
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from fffff80002e7d469 to fffff80002e7df00
    
    STACK_TEXT:  
    fffff800`00ba24c8 fffff800`02e7d469 : 00000000`0000000a 00000000`00000108 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
    fffff800`00ba24d0 fffff800`02e7c0e0 : fffffa80`03d01b60 fffffa80`043e6878 00000000`00000001 00000000`00000002 : nt!KiBugCheckDispatch+0x69
    fffff800`00ba2610 fffff800`02fb136b : fffff880`03c0b76d fffffa80`06d3dd50 fffffa80`066e4ba8 fffffa80`68536956 : nt!KiPageFault+0x260
    fffff800`00ba27a8 fffffa80`066e4410 : fffff880`021c8bd0 fffffa80`066e4ba0 fffff880`03c0c47f fffffa80`066e4ba0 : nt!ExFreePoolWithTag+0x2bb
    fffff800`00ba2858 fffff880`021c8bd0 : fffffa80`066e4ba0 fffff880`03c0c47f fffffa80`066e4ba0 00000000`00000001 : 0xfffffa80`066e4410
    fffff800`00ba2860 fffffa80`066e4ba0 : fffff880`03c0c47f fffffa80`066e4ba0 00000000`00000001 00000000`00000000 : 0xfffff880`021c8bd0
    fffff800`00ba2868 fffff880`03c0c47f : fffffa80`066e4ba0 00000000`00000001 00000000`00000000 fffffa80`07130010 : 0xfffffa80`066e4ba0
    fffff800`00ba2870 fffff880`03c097da : fffffa80`00000000 fffffa80`00000000 00000000`00000002 00000000`00000000 : dxgmms1!VidSchiSignalRegisteredEvent+0xe7
    fffff800`00ba28c0 fffff880`03c08e00 : 00000000`00000000 fffffa80`066e4410 00000000`00000000 fffff800`02ff6e80 : dxgmms1!VidSchiProcessDpcCompletedPacket+0x3b6
    fffff800`00ba2960 fffff880`03c08c4c : fffffa80`05d13f08 fffffa80`066e4410 fffffa80`05be3f40 00000000`00000000 : dxgmms1!VidSchDdiNotifyDpcWorker+0x198
    fffff800`00ba29b0 fffff880`042d21cf : fffffa80`04b55480 fffffa80`00000000 00000000`00000001 00000000`00000004 : dxgmms1!VidSchDdiNotifyDpc+0x94
    fffff800`00ba2a00 fffffa80`04b55480 : fffffa80`00000000 00000000`00000001 00000000`00000004 fffffa80`05bdb000 : dxgkrnl+0x31cf
    fffff800`00ba2a08 fffffa80`00000000 : 00000000`00000001 00000000`00000004 fffffa80`05bdb000 fffff880`03cb7230 : 0xfffffa80`04b55480
    fffff800`00ba2a10 00000000`00000001 : 00000000`00000004 fffffa80`05bdb000 fffff880`03cb7230 fffff800`02ff6e80 : 0xfffffa80`00000000
    fffff800`00ba2a18 00000000`00000004 : fffffa80`05bdb000 fffff880`03cb7230 fffff800`02ff6e80 00000000`00000000 : 0x1
    fffff800`00ba2a20 fffffa80`05bdb000 : fffff880`03cb7230 fffff800`02ff6e80 00000000`00000000 00000000`000b28b7 : 0x4
    fffff800`00ba2a28 fffff880`03cb7230 : fffff800`02ff6e80 00000000`00000000 00000000`000b28b7 fffff800`02e865f7 : 0xfffffa80`05bdb000
    fffff800`00ba2a30 fffff800`02ff6e80 : 00000000`00000000 00000000`000b28b7 fffff800`02e865f7 00000000`00000000 : atikmdag+0x1e230
    fffff800`00ba2a38 00000000`00000000 : 00000000`000b28b7 fffff800`02e865f7 00000000`00000000 fffff880`03cc441a : nt!KiInitialPCR+0x180
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    dxgmms1!VidSchiSignalRegisteredEvent+e7
    fffff880`03c0c47f 440fb6de        movzx   r11d,sil
    
    SYMBOL_STACK_INDEX:  7
    
    SYMBOL_NAME:  dxgmms1!VidSchiSignalRegisteredEvent+e7
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: dxgmms1
    
    IMAGE_NAME:  dxgmms1.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc578
    
    FAILURE_BUCKET_ID:  X64_0xC5_2_dxgmms1!VidSchiSignalRegisteredEvent+e7
    
    BUCKET_ID:  X64_0xC5_2_dxgmms1!VidSchiSignalRegisteredEvent+e7
    
    Followup: MachineOwner
    ---------
    
     ( dxgmms1!VidSchiSignalRegisteredEvent+e7 )
    
    Followup: MachineOwner
    ---------
    
    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    DRIVER_CORRUPTED_EXPOOL (c5)
    An attempt was made to access a pageable (or completely invalid) address at an
    interrupt request level (IRQL) that is too high.  This is
    caused by drivers that have corrupted the system pool.  Run the driver
    verifier against any new (or suspect) drivers, and if that doesn't turn up
    the culprit, then use gflags to enable special pool.
    Arguments:
    Arg1: 0000000000000108, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
    Arg4: fffff80002fb136b, address which referenced memory
    
    Debugging Details:
    ------------------
    
    
    BUGCHECK_STR:  0xC5_2
    
    CURRENT_IRQL:  2
    
    FAULTING_IP: 
    nt!ExFreePoolWithTag+2bb
    fffff800`02fb136b 418b8708010000  mov     eax,dword ptr [r15+108h]
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    PROCESS_NAME:  svchost.exe
    
    TRAP_FRAME:  fffff80000ba2610 -- (.trap 0xfffff80000ba2610)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000000000200 rbx=0000000000000000 rcx=fffff80002ff7e80
    rdx=0000000000000004 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff80002fb136b rsp=fffff80000ba27a8 rbp=0000000000000000
     r8=0000000000005f00  r9=0000000000000150 r10=fffff80002e0c000
    r11=0000000000000260 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl nz na po cy
    nt!ExFreePoolWithTag+0x2bb:
    fffff800`02fb136b 418b8708010000  mov     eax,dword ptr [r15+108h] ds:dd50:00000000`00000108=????????
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from fffff80002e7d469 to fffff80002e7df00
    
    STACK_TEXT:  
    fffff800`00ba24c8 fffff800`02e7d469 : 00000000`0000000a 00000000`00000108 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
    fffff800`00ba24d0 fffff800`02e7c0e0 : fffffa80`03d01b60 fffffa80`043e6878 00000000`00000001 00000000`00000002 : nt!KiBugCheckDispatch+0x69
    fffff800`00ba2610 fffff800`02fb136b : fffff880`03c0b76d fffffa80`06d3dd50 fffffa80`066e4ba8 fffffa80`68536956 : nt!KiPageFault+0x260
    fffff800`00ba27a8 fffffa80`066e4410 : fffff880`021c8bd0 fffffa80`066e4ba0 fffff880`03c0c47f fffffa80`066e4ba0 : nt!ExFreePoolWithTag+0x2bb
    fffff800`00ba2858 fffff880`021c8bd0 : fffffa80`066e4ba0 fffff880`03c0c47f fffffa80`066e4ba0 00000000`00000001 : 0xfffffa80`066e4410
    fffff800`00ba2860 fffffa80`066e4ba0 : fffff880`03c0c47f fffffa80`066e4ba0 00000000`00000001 00000000`00000000 : 0xfffff880`021c8bd0
    fffff800`00ba2868 fffff880`03c0c47f : fffffa80`066e4ba0 00000000`00000001 00000000`00000000 fffffa80`07130010 : 0xfffffa80`066e4ba0
    fffff800`00ba2870 fffff880`03c097da : fffffa80`00000000 fffffa80`00000000 00000000`00000002 00000000`00000000 : dxgmms1!VidSchiSignalRegisteredEvent+0xe7
    fffff800`00ba28c0 fffff880`03c08e00 : 00000000`00000000 fffffa80`066e4410 00000000`00000000 fffff800`02ff6e80 : dxgmms1!VidSchiProcessDpcCompletedPacket+0x3b6
    fffff800`00ba2960 fffff880`03c08c4c : fffffa80`05d13f08 fffffa80`066e4410 fffffa80`05be3f40 00000000`00000000 : dxgmms1!VidSchDdiNotifyDpcWorker+0x198
    fffff800`00ba29b0 fffff880`042d21cf : fffffa80`04b55480 fffffa80`00000000 00000000`00000001 00000000`00000004 : dxgmms1!VidSchDdiNotifyDpc+0x94
    fffff800`00ba2a00 fffffa80`04b55480 : fffffa80`00000000 00000000`00000001 00000000`00000004 fffffa80`05bdb000 : dxgkrnl+0x31cf
    fffff800`00ba2a08 fffffa80`00000000 : 00000000`00000001 00000000`00000004 fffffa80`05bdb000 fffff880`03cb7230 : 0xfffffa80`04b55480
    fffff800`00ba2a10 00000000`00000001 : 00000000`00000004 fffffa80`05bdb000 fffff880`03cb7230 fffff800`02ff6e80 : 0xfffffa80`00000000
    fffff800`00ba2a18 00000000`00000004 : fffffa80`05bdb000 fffff880`03cb7230 fffff800`02ff6e80 00000000`00000000 : 0x1
    fffff800`00ba2a20 fffffa80`05bdb000 : fffff880`03cb7230 fffff800`02ff6e80 00000000`00000000 00000000`000b28b7 : 0x4
    fffff800`00ba2a28 fffff880`03cb7230 : fffff800`02ff6e80 00000000`00000000 00000000`000b28b7 fffff800`02e865f7 : 0xfffffa80`05bdb000
    fffff800`00ba2a30 fffff800`02ff6e80 : 00000000`00000000 00000000`000b28b7 fffff800`02e865f7 00000000`00000000 : atikmdag+0x1e230
    fffff800`00ba2a38 00000000`00000000 : 00000000`000b28b7 fffff800`02e865f7 00000000`00000000 fffff880`03cc441a : nt!KiInitialPCR+0x180
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    dxgmms1!VidSchiSignalRegisteredEvent+e7
    fffff880`03c0c47f 440fb6de        movzx   r11d,sil
    
    SYMBOL_STACK_INDEX:  7
    
    SYMBOL_NAME:  dxgmms1!VidSchiSignalRegisteredEvent+e7
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: dxgmms1
    
    IMAGE_NAME:  dxgmms1.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc578
    
    FAILURE_BUCKET_ID:  X64_0xC5_2_dxgmms1!VidSchiSignalRegisteredEvent+e7
    
    BUCKET_ID:  X64_0xC5_2_dxgmms1!VidSchiSignalRegisteredEvent+e7
    
    Followup: MachineOwner
    ---------
      My Computer


  7. Posts : 11
    Windows 7 Ultimate 64x
    Thread Starter
       #17

    Do you have a recommendation for an uninstall method? Because I hae done it before. Using all kinds of driver uninstaller like driver cleaner and driver sweeper. And what exactly do you mean by don't using the windows update? And I always get my drivers from the Sapphire website. I'm not overclocking and will begin my system file check. Thanks for your reaction!
      My Computer


  8. Posts : 11
    Windows 7 Ultimate 64x
    Thread Starter
       #18

    I did it but still have BSOD's including these ones
      My Computer


 
Page 2 of 2 FirstFirst 12

  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 04:01.
Find Us