PLEASE READ BSOD mostly Graphics and Harddisk errors..at random times

Page 2 of 3 FirstFirst 123 LastLast

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

    Oh also I got a kernel error again from my graphics card....it made the screen go different colors and then froze for a sec..then said it just recovered from ....want me to upload dump files again?
      My Computer


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

    So I decided to try driver verifier for the hell of it...its not letting me into Windows. I'm going to boot in safe mode but what does that mean for me? I soon as I started it up I got the bsod lol..doesn't sound good.
      My Computer


  3. Posts : 16
    Windows 7 Professional x64 bit
    Thread Starter
       #13

    nvm
    Last edited by misanthropic42; 27 Feb 2012 at 23:28. Reason: wish i could delete
      My Computer


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

    New Dump files and report


    Well now I'm thinking its driver problems. Here's the new dump files and system report after the crashing and all that nonsense. Thank you again for the help.
      My Computer


  5. Posts : 11,269
    Windows 7 Home Premium 64 Bit
       #15

    Antivirus Software:
    Code:
    ccsvchst.exe	c:\program files (x86)\norton internet security\engine\18.7.0.13\ccsvchst.exe	1876	8	1024	10240	2/27/2012 7:18 PM	10.1.1.16	126.96 KB (130,008 bytes)	2/17/2012 6:37 PM
    ccsvchst.exe	c:\program files (x86)\norton internet security\engine\18.7.0.13\ccsvchst.exe	2504	8	1024	10240	2/27/2012 7:18 PM	10.1.1.16	126.96 KB (130,008 bytes)	2/17/2012 6:37 PM


    Possible out of date drivers:
    Code:
    gdrv	fffff880`098ea000	fffff880`098f3000	Thu Mar 12 21:22:29 2009 (49b9d175)	000105ce		gdrv.sys
    ALSysIO64	fffff880`0b4eb000	fffff880`0b4f3000	Sun Apr 19 13:41:04 2009 (49eb7e50)	0000bbad		ALSysIO64.sys


    Code:
    Loading Dump File [D:\Kingston\BSODDmpFiles\misanthropic42\Windows_NT6_BSOD_jcgriff2\022512-16348-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.17640.amd64fre.win7sp1_gdr.110622-1506
    Machine Name:
    Kernel base = 0xfffff800`03009000 PsLoadedModuleList = 0xfffff800`0324e670
    Debug session time: Sat Feb 25 23:20:39.422 2012 (UTC - 7:00)
    System Uptime: 0 days 0:52:09.639
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    .......................................
    Loading User Symbols
    Loading unloaded module list
    .......
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 109, {a3a039d8a39ca79e, b3b7465ef61a85d8, fffff88001636880, 1}
    
    Probably caused by : memory_corruption
    
    Followup: memory_corruption
    ---------
    
    2: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    CRITICAL_STRUCTURE_CORRUPTION (109)
    This bugcheck is generated when the kernel detects that critical kernel code or
    data have been corrupted. There are generally three causes for a corruption:
    1) A driver has inadvertently or deliberately modified critical kernel code
     or data. See http://www.microsoft.com/whdc/driver/kernel/64bitPatching.mspx
    2) A developer attempted to set a normal kernel breakpoint using a kernel
     debugger that was not attached when the system was booted. Normal breakpoints,
     "bp", can only be set if the debugger is attached at boot time. Hardware
     breakpoints, "ba", can be set at any time.
    3) A hardware corruption occurred, e.g. failing RAM holding kernel code or data.
    Arguments:
    Arg1: a3a039d8a39ca79e, Reserved
    Arg2: b3b7465ef61a85d8, Reserved
    Arg3: fffff88001636880, Failure type dependent information
    Arg4: 0000000000000001, Type of corrupted region, can be
    	0 : A generic data region
    	1 : Modification of a function or .pdata
    	2 : A processor IDT
    	3 : A processor GDT
    	4 : Type 1 process list corruption
    	5 : Type 2 process list corruption
    	6 : Debug routine modification
    	7 : Critical MSR modification
    
    Debugging Details:
    ------------------
    
    
    BUGCHECK_STR:  0x109
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  CODE_CORRUPTION
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  0
    
    LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff80003085c40
    
    STACK_TEXT:  
    fffff880`033a1498 00000000`00000000 : 00000000`00000109 a3a039d8`a39ca79e b3b7465e`f61a85d8 fffff880`01636880 : nt!KeBugCheckEx
    
    
    STACK_COMMAND:  kb
    
    CHKIMG_EXTENSION: !chkimg -lo 50 -d !ndis
        fffff880016368eb - ndis!ndisQueuedMiniportDpcWorkItem+6b
    	[ 8b:8a ]
    1 error : !ndis (fffff880016368eb)
    
    MODULE_NAME: memory_corruption
    
    IMAGE_NAME:  memory_corruption
    
    FOLLOWUP_NAME:  memory_corruption
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    
    MEMORY_CORRUPTOR:  ONE_BIT
    
    FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT
    
    BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT
    
    Followup: memory_corruption
    ---------
    The crash points to memory problems or drivers.

    Begin by removing Gigabyte Easy Saver - mobo power utility since it is known to cause crashes on some systems. Post back whether the system is more stable.
      My Computer


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

    Thanks for the heads up. So I did have some updates again, but they were updates from within the last week. That hasn't helped anything yet. I've only ran one stick over night so far and the results were clean. So I've uninstalled the unnessesary Gigabyte utilities because I didn't really use any of them anyway. I noticed Norton was mentioned on there. The Norton I have was a free version that came with the OS. Should I uninstall it? I also uninstalled Iobit and pretty much all the crud I don't use on my computer. So pretty much I'm just at the wait and see phase, but I'll let you know how it goes. And thanks again for the help.
      My Computer


  7. Posts : 11,269
    Windows 7 Home Premium 64 Bit
       #17

    If you have any more crashes, we do see Norton cause crashes from time to time, so it is a good idea to remove it to test whether it was causing crashes. If you do decide to remove it, use the Norton Removal Tool and you can replace it with the Good and Free system security combination. You can also replace it with something else, but Microsoft Security Essentials is known to be stable on Windows 7, so that is what we usually recommend. It is included in that link for a combination.
      My Computer


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

    Awesome! I was using AVG but it seems to have gotten lousy over the past few years. Really great tips guys, and so far no crashes!
      My Computer


  9. Posts : 11,269
    Windows 7 Home Premium 64 Bit
       #19

    No problem. Run for a few days and see if it remains stable, and then post back.
      My Computer


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

    Huhbluh..another blue screen


    Bleh, another blue screen. At least it hasn't been hapenning as frequently. Here's my recent dump files and report. I guess back to testing the memory individually.
      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 05:51.
Find Us