Crashes/Bluescreens for a year, no solution found

Page 1 of 3 123 LastLast

  1. Posts : 15
    Windows 7 64bit
       #1

    Crashes/Bluescreens for a year, no solution found


    I'll try to keep this problem short, it dates back about a year when i had my XP OS which started randomly bluescreening while in gameplay, and only in gameplay. Made me think that its my gfx so i RMA:d my card(radeon 9800 pro), got back a xfx gtx260, didn't help, so i thought that maybe they sent me a broken card, so i rmad again, and got a xfx gtx275 which is currently in. Upgraded to Windows 7 at some point. Also got a new motherboard from my supplier for testing, doesn't work. (P5N-T Deluxe To -> P5QNT XYZ(Currently in))

    Short description of how the crash happens:

    Sound scrambles, loops slightly.
    Fps drops to solid 0. Forcing me to reboot manually, bluescreen RARELY occurs in the actual crash, however after booting the computer i quite often get massive artifaction on BIOS screen.

    After the crash the system is very sensitive even if no artifaction is present at boot, meaning the instant i start a 3d accelerated program the system halts.

    Steps i've taken along the way:

    Replaced Graphics Card for 2 Times.
    Replaced motherboard.
    Formated and fresh installed Win7 roughly 5 times(each after anything changed in the hardware)
    Tested my memory(through the night, no errors), my processor(OK) and my HD(Ok)
    Tried every alternate driver for every software/hardware i use.

    Most common event viewer errors:

    1101 Audit events have been dropped by the transport. 0
    Source: EventLog

    This happens fairly often right before the crash
    ------------
    So i finally managed to get a bluescreen(for the minidump), however it didn't come from while playing a game, but on boot to windows. I received bunch of stuff in the eventmanager that i haven't seen before/in a while. Theres too many of them to post each here so i'll post the ones that seem most important. (Bear in mind i have a Finnish Win7 so ill try to keep them simple.)

    7001
    Service Control Manager
    The <WebCatalogService>(translated by me) service depends on the <Network Location Awareness> service which failed to start because of the following error: <%%1068/or a joined application did not start>(translated again)

    10005
    Distributed Com
    - <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    - <System>
    <Provider Name="Microsoft-Windows-DistributedCOM" Guid="{1B562E86-B7AA-4131-BADC-B6F3A001407E}" EventSourceName="DCOM" />

    <EventID Qualifiers="49152">10005</EventID>

    <Version>0</Version>

    <Level>2</Level>

    <Task>0</Task>

    <Opcode>0</Opcode>

    <Keywords>0x80000000000000</Keywords>

    <TimeCreated SystemTime="2010-04-26T09:27:32.000000000Z" />

    <EventRecordID>2020</EventRecordID>

    <Correlation />

    <Execution ProcessID="0" ThreadID="0" />

    <Channel>System</Channel>

    <Computer>Esa-PC</Computer>

    <Security />

    </System>


    - <EventData>
    <Data Name="param1">1084</Data>

    <Data Name="param2">WSearch</Data>

    <Data Name="param3" />

    <Data Name="param4">{9E175B6D-F52A-11D8-B9A5-505054503030}</Data>

    </EventData>


    </Event>



    And tons of others, most which are related to networking.

    Attaching minidump and dxdiag

    Feel free to ask any information related to this matter, i really need the help.
      My Computer


  2. Posts : 845
    Windows 7 - Vista
       #2

    Hi -

    The bugcheck on the lone dump =

    Update this Asus AI Suite ATK0110 driver - too old for Windows 7 -
    Code:
    ASACPI.sys   Sun Mar 27 22:30:36 2005 (42476C4C)
    Asus driver updates --> ASUSTeK Computer Inc.-Support-
    ATK0110 driver Download --> Motherboard--> Utility--> Tools

    I'd like additional system information, please.

    Download the EXE file to your Documents folder --> windows7_vista_v2.57_jcgriff2_.exe

    Download SysInernals AutoRuns to Documents --> http://live.sysinternals.com/autoruns.exe

    Go to Documents folder, RIGHT-click on the windows7_vista_v2.57_jcgriff2_.exe file, select "Run as Administrator"

    Detailed instructions --> Blue Screen of Death (BSOD) Posting Instructions

    Zip up the output and attach to your next post.

    Regards. . .

    jcgriff2

    .
      My Computer


  3. Posts : 5,056
    Windows 7 x64 pro/ Windows 7 x86 Pro/ XP SP3 x86
       #3

    Ruoja,

    the bsod was apparently caused by the nvidia graphics driver. But more importantly, it was a TDR fault. TDR stands for Timeout Detection and Recovery. Its a process through which windows tries to detect problematic hang situations and recover the desktop dynamically i.e. without reboot by resetting the GPU and re-initializing the video driver. That is why the system appears frozen and the user reboots to resolve.

    As the FPS decreases, the likelihood of the GPU resetting increases. I noticed your FPS drops to zero.

    But the TDR fault may be happening for other reasons e.g. overheating GPU, insufficient system cooling, overclocking, basically whatever you can think of. Many people have resolved their TDR problems simply by increasing fan speed.

    There are some informative pages. pl. go through them.

    NVIDIA Statement on TDR Errors - NVIDIA Forums

    Fixed my TDR - display driver stopped working - issues - NVIDIA Forums

    You can also consider upgrading RAM to the max your system supports. Its cheap.
      My Computer


  4. Posts : 15
    Windows 7 64bit
    Thread Starter
       #4

    jcgriff2 said:
    Hi -

    The bugcheck on the lone dump =

    Update this Asus AI Suite ATK0110 driver - too old for Windows 7 -
    Code:
    ASACPI.sys   Sun Mar 27 22:30:36 2005 (42476C4C)
    Asus driver updates --> ASUSTeK Computer Inc.-Support-
    ATK0110 driver Download --> Motherboard--> Utility--> Tools

    I'd like additional system information, please.

    Download the EXE file to your Documents folder --> windows7_vista_v2.57_jcgriff2_.exe

    Download SysInernals AutoRuns to Documents --> http://live.sysinternals.com/autoruns.exe

    Go to Documents folder, RIGHT-click on the windows7_vista_v2.57_jcgriff2_.exe file, select "Run as Administrator"

    Detailed instructions --> Blue Screen of Death (BSOD) Posting Instructions

    Zip up the output and attach to your next post.

    Regards. . .

    jcgriff2

    .
    Thanks for the reply,

    Updated the driver, zipped the infos

    Also, i know the minidump is a loner, thats one of the problems since i can't get it to BSOD reliably and i just formated my comp when i installed the new motherboard.
    Last edited by Ruoja; 26 Apr 2010 at 06:14. Reason: info
      My Computer


  5. Posts : 15
    Windows 7 64bit
    Thread Starter
       #5

    Bill2 said:
    Ruoja,

    the bsod was apparently caused by the nvidia graphics driver. But more importantly, it was a TDR fault. TDR stands for Timeout Detection and Recovery. Its a process through which windows tries to detect problematic hang situations and recover the desktop dynamically i.e. without reboot by resetting the GPU and re-initializing the video driver. That is why the system appears frozen and the user reboots to resolve.

    As the FPS decreases, the likelihood of the GPU resetting increases. I noticed your FPS drops to zero.

    But the TDR fault may be happening for other reasons e.g. overheating GPU, insufficient system cooling, overclocking, basically whatever you can think of. Many people have resolved their TDR problems simply by increasing fan speed.

    There are some informative pages. pl. go through them.

    NVIDIA Statement on TDR Errors - NVIDIA Forums

    Fixed my TDR - display driver stopped working - issues - NVIDIA Forums

    You can also consider upgrading RAM to the max your system supports. Its cheap.
    Thanks for the reply, and sorry for double post.

    Yeah i am aware if fps drops to 0 TDR might think the graphics card has malfunctioned and will try to reset, however this is not the case for no game can drop my normal fps under 40. I don't believe they'd send me 2 malfunctioning cards from RMA so thats why i'm here. Beyond my skill level.

    I tried the cooling, used multiple monitoring software, even installed 2 new fans for the gtx260 but heat is not the problem, regardless of heat the crash will occur sooner or later.

    Also nothing is OC:d everything is as default as it can be right now.
    Last edited by Ruoja; 26 Apr 2010 at 06:17. Reason: info
      My Computer


  6. Posts : 845
    Windows 7 - Vista
       #6

    Ruoja said:
    Thanks for the reply,

    Updated the driver, zipped the infos

    Also, i know the minidump is a loner, thats one of the problems since i can't get it to BSOD reliably and i just formated my comp when i installed the new motherboard.
    Hi -

    Thanks for the files.

    Update your Atheros AR8121/AR8113/AR8114 PCI-E Ethernet driver -
    Code:
    L1E62x64.sys Thu Jun 11 02:45:22 2009 (4A30A802) - Atheros Ethernet
    Atheros Driver downloads --> Atheros Communications

    I see manually configured page file with min/ max = 2047/ 3040

    Boot into safemode, turn virtual memory = OFF. Re-boot into safemode again and delete page file. RIGHT-click on c:\pagefile.sys, hold down SHIFT key while clicking on 'delete'. This will bypass recycle bin. Then set page file to system managed, OS drive. Re-boot into normal Windows.

    To help speed the BSOD process up, verify all 3rd party drivers.

    Run --> DRIVER VERIFIER - Windows 7 & Vista

    My apologies for not completing the bugcheck info in my prior post. Bill2 provided info on TDR. I agree with RAM upgrade. You have 2GB installed.

    The bugcheck was in fact 0x117 = video TDR timeout

    I checked WERCON out from your files and found four 0x116 "Live Kernel Events", one step below a 0x117 BSOD. The difference between the two is that when a 0x116 occurs, the video driver ultimately recovers; 0x117 it does not, hence the BSOD.

    From WERCON, the 0x117 BSOD, the 0x116 Live Kernel Events and a sampling of the 105 Windows Update Failures -
    Code:
    --->   SCROLL TO RIGHT
     
    26.4.2010 9:27 WER Vikasailio , tyyppi 0&#x000d;&#x000a;Tapahtuman nimi: LiveKernelEvent&#x000d;&#x000a;Vastaus: Ei kaytettavissa&#x000d;&#x0
    26.4.2010 9:27 WER Vikasailio , tyyppi 0&#x000d;&#x000a;Tapahtuman nimi: LiveKernelEvent&#x000d;&#x000a;Vastaus: Ei kaytettavissa&#x000d;&#x0
    26.4.2010 9:27 WER Vikasailio , tyyppi 0&#x000d;&#x000a;Tapahtuman nimi: LiveKernelEvent&#x000d;&#x000a;Vastaus: Ei kaytettavissa&#x000d;&#x0
    26.4.2010 9:27 WER Vikasailio , tyyppi 0&#x000d;&#x000a;Tapahtuman nimi: BlueScreen&#x000d;&#x000a;Vastaus: Ei kaytettavissa&#x000d;&#x000a;
    26.4.2010 10:15 WER Vikasailio 646544354, tyyppi 5&#x000d;&#x000a;Tapahtuman nimi: RADAR_PRE_LEAK_WOW64&#x000d;&#x000a;Vastaus: Ei kaytettavissa&#x000d;&#x000a;C
    23.4.2010 17:11 WER Vikasailio 1070761457, tyyppi 5&#x000d;&#x000a;Tapahtuman nimi: RADAR_PRE_LEAK_WOW64&#x000d;&#x000a;Vastaus: Ei kaytettavissa&#x000d;&#x000a;
    23.4.2010 14:35 WER Vikasailio , tyyppi 0&#x000d;&#x000a;Tapahtuman nimi: LiveKernelEvent&#x000d;&#x000a;Vastaus: Ei kaytettavissa&#x000d;&#x0
    21.4.2010 22:39 WER Vikasailio 720074973, tyyppi 5&#x000d;&#x000a;Tapahtuman nimi: AEAPPINV2&#x000d;&#x000a;Vastaus: Ei kaytettavissa&#x000d;&#x000a;Cab Id: 0&#x
    21.4.2010 20:48 WER Vikasailio 822876855, tyyppi 5&#x000d;&#x000a;Tapahtuman nimi: RADAR_PRE_LEAK_WOW64&#x000d;&#x000a;Vastaus: Ei kaytettavissa&#x000d;&#x000a;C
    21.4.2010 20:16 WER Vikasailio , tyyppi 0&#x000d;&#x000a;Tapahtuman nimi: APPCRASH&#x000d;&#x000a;Vastaus: Ei kaytettavissa&#x000d;&#x000a;Cab Id: 0&#x000d;&#x00
    21.4.2010 20:16 Application Error Viallisen sovelluksen nimi: client.exe, versio: 6.0.1.6, aikaleima: 0x46814986&#x000d;&#x000a;Viallisen moduulin nimi: client
    21.4.2010 18:12 WER Vikasailio 294939446, tyyppi 1&#x000d;&#x000a;Tapahtuman nimi: APPCRASH&#x000d;&#x000a;Vastaus: Ei kaytettavissa&#x000d;&#x000a;Cab Id: 0&#x0
    21.4.2010 18:12 WER Vikasailio , tyyppi 0&#x000d;&#x000a;Tapahtuman nimi: APPCRASH&#x000d;&#x000a;Vastaus: Ei kaytettavissa&#x000d;&#x000a;Cab Id: 0&#x000d;&#x00
    21.4.2010 18:12 Application Error Viallisen sovelluksen nimi: uoml_setup.exe, versio: 11.0.0.28844, aikaleima: 0x4250bcf6&#x000d;&#x000a;Viallisen moduulin nim
    21.4.2010 17:15 WER Vikasailio 719948344, tyyppi 5&#x000d;&#x000a;Tapahtuman nimi: WindowsUpdateFailure&#x000d;&#x000a;Vastaus: Ei ka
    21.4.2010 16:42 WER Vikasailio 924319992, tyyppi 5&#x000d;&#x000a;Tapahtuman nimi: WindowsUpdateFailure&#x000d;&#x000a;Vastaus: Ei ka
    21.4.2010 16:37 WER Vikasailio 543120424, tyyppi 5&#x000d;&#x000a;Tapahtuman nimi: ResponseEffectiveness&#x000d;&#x000a;Vastaus: Ei kaytettavissa&#x000d;&#x000a;
    21.4.2010 16:37 WER Vikasailio , tyyppi 0&#x000d;&#x000a;Tapahtuman nimi: ResponseEffectiveness&#x000d;&#x000a;Vastaus: Ei kaytettavissa&#x000d;&#x000a;Cab Id: 0
    21.4.2010 16:34 WER Vikasailio 978757159, tyyppi 5&#x000d;&#x000a;Tapahtuman nimi: WindowsUpdateFailure&#x000d;&#x000a;Vastaus: Ei ka
    21.4.2010 16:34 WER Vikasailio 1005850186, tyyppi 5&#x000d;&#x000a;Tapahtuman nimi: WindowsUpdateFailure&#x000d;&#x000a;Vastaus: Ei k
    21.4.2010 16:32 WER Vikasailio 1093405866, tyyppi 5&#x000d;&#x000a;Tapahtuman nimi: WindowsUpdateFailure&#x000d;&#x000a;Vastaus: Ei k
    21.4.2010 16:31 WER Vikasailio , tyyppi 0&#x000d;&#x000a;Tapahtuman nimi: WindowsUpdateFailure&#x000d;&#x000a;Vastaus: Ei kaytettavis

    `



    You mentioned change of mobo and you have OEM version Windows 7 x64. Re-validate your OS install at Microsoft WGA site.

    WGA Validation --> www.microsoft.com/genuine

    Regards. . .

    jcgriff2

    .
      My Computer


  7. Posts : 15
    Windows 7 64bit
    Thread Starter
       #7

    Thanks for the reply,

    I validated Windows, installed Atheros drivers and some new updates that came after validation.

    Running Driver Verifier as we speak, however i did not remember to fix the page file, i hope thats not a problem(its not something thats identical to every fresh install anyway so i doubt it has anything to with the problem).

    I find it funny i'm actually hoping for a bsod now ^^.

    Thanks for all the effort so far.
      My Computer


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

    Ruoja said:
    I'll try to keep this problem short, it dates back about a year when i had my XP OS which started randomly bluescreening while in gameplay, and only in gameplay. Made me think that its my gfx so i RMA:d my card(radeon 9800 pro), got back a xfx gtx260, didn't help, so i thought that maybe they sent me a broken card, so i rmad again, and got a xfx gtx275 which is currently in. Upgraded to Windows 7 at some point. Also got a new motherboard from my supplier for testing, doesn't work. (P5N-T Deluxe To -> P5QNT XYZ(Currently in))

    Short description of how the crash happens:

    Sound scrambles, loops slightly.
    Fps drops to solid 0. Forcing me to reboot manually, bluescreen RARELY occurs in the actual crash, however after booting the computer i quite often get massive artifaction on BIOS screen.

    After the crash the system is very sensitive even if no artifaction is present at boot, meaning the instant i start a 3d accelerated program the system halts.

    Steps i've taken along the way:

    Replaced Graphics Card for 2 Times.
    Replaced motherboard.
    Formated and fresh installed Win7 roughly 5 times(each after anything changed in the hardware)
    Tested my memory(through the night, no errors), my processor(OK) and my HD(Ok)
    Tried every alternate driver for every software/hardware i use.

    Most common event viewer errors:

    1101 Audit events have been dropped by the transport. 0
    Source: EventLog

    This happens fairly often right before the crash
    ------------
    So i finally managed to get a bluescreen(for the minidump), however it didn't come from while playing a game, but on boot to windows. I received bunch of stuff in the eventmanager that i haven't seen before/in a while. Theres too many of them to post each here so i'll post the ones that seem most important. (Bear in mind i have a Finnish Win7 so ill try to keep them simple.)

    7001
    Service Control Manager
    The <WebCatalogService>(translated by me) service depends on the <Network Location Awareness> service which failed to start because of the following error: <%%1068/or a joined application did not start>(translated again)

    10005
    Distributed Com
    - <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    - <System>
    <Provider Name="Microsoft-Windows-DistributedCOM" Guid="{1B562E86-B7AA-4131-BADC-B6F3A001407E}" EventSourceName="DCOM" />

    <EventID Qualifiers="49152">10005</EventID>

    <Version>0</Version>

    <Level>2</Level>

    <Task>0</Task>

    <Opcode>0</Opcode>

    <Keywords>0x80000000000000</Keywords>

    <TimeCreated SystemTime="2010-04-26T09:27:32.000000000Z" />

    <EventRecordID>2020</EventRecordID>

    <Correlation />

    <Execution ProcessID="0" ThreadID="0" />

    <Channel>System</Channel>

    <Computer>Esa-PC</Computer>

    <Security />

    </System>


    - <EventData>
    <Data Name="param1">1084</Data>

    <Data Name="param2">WSearch</Data>

    <Data Name="param3" />

    <Data Name="param4">{9E175B6D-F52A-11D8-B9A5-505054503030}</Data>

    </EventData>


    </Event>



    And tons of others, most which are related to networking.

    Attaching minidump and dxdiag

    Feel free to ask any information related to this matter, i really need the help.
    Pretty straight forward. This crash was caused by your video driver. You need to remove all remnants of the current driver (like control panels, etc) before you install a fresh copy.

    I believe there is an un-install tool at the Nvidia site.

    Let us know if you need help


    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\Minidumps\042610-24414-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    Symbol search path is: SRV*F:\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 Personal
    Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
    Machine Name:
    Kernel base = 0xfffff800`02853000 PsLoadedModuleList = 0xfffff800`02a90e50
    Debug session time: Mon Apr 26 05:25:42.696 2010 (GMT-4)
    System Uptime: 0 days 0:00:34.257
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ......
    Loading User Symbols
    Loading unloaded module list
    ....
    Unable to load image 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
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 116, {fffffa80029b6010, fffff8800f171d50, 0, 2}
    
    Unable to load image nvlddmkm.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for nvlddmkm.sys
    *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
    Probably caused by : nvlddmkm.sys ( nvlddmkm+11bd50 )
    
    Followup: MachineOwner
    ---------
    
    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    VIDEO_TDR_FAILURE (116)
    Attempt to reset the display driver and recover from timeout failed.
    Arguments:
    Arg1: fffffa80029b6010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
    Arg2: fffff8800f171d50, The pointer into responsible device driver module (e.g. owner tag).
    Arg3: 0000000000000000, Optional error code (NTSTATUS) of the last failed operation.
    Arg4: 0000000000000002, Optional internal context dependent data.
    
    Debugging Details:
    ------------------
    
    
    OVERLAPPED_MODULE: Address regions for 'dump_dumpfve' and 'crashdmp.sys' overlap
    
    FAULTING_IP: 
    nvlddmkm+11bd50
    fffff880`0f171d50 803d815cb70000  cmp     byte ptr [nvlddmkm+0xc919d8 (fffff880`0fce79d8)],0
    
    DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT
    
    CUSTOMER_CRASH_COUNT:  1
    
    BUGCHECK_STR:  0x116
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  0
    
    STACK_TEXT:  
    fffff880`033de9c8 fffff880`03eb3ef8 : 00000000`00000116 fffffa80`029b6010 fffff880`0f171d50 00000000`00000000 : nt!KeBugCheckEx
    fffff880`033de9d0 00000000`00000116 : fffffa80`029b6010 fffff880`0f171d50 00000000`00000000 00000000`00000002 : dxgkrnl+0x5cef8
    fffff880`033de9d8 fffffa80`029b6010 : fffff880`0f171d50 00000000`00000000 00000000`00000002 00000000`00000000 : 0x116
    fffff880`033de9e0 fffff880`0f171d50 : 00000000`00000000 00000000`00000002 00000000`00000000 00000000`00000000 : 0xfffffa80`029b6010
    fffff880`033de9e8 00000000`00000000 : 00000000`00000002 00000000`00000000 00000000`00000000 fffff880`03eb3c02 : nvlddmkm+0x11bd50
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    nvlddmkm+11bd50
    fffff880`0f171d50 803d815cb70000  cmp     byte ptr [nvlddmkm+0xc919d8 (fffff880`0fce79d8)],0
    
    SYMBOL_STACK_INDEX:  4
    
    SYMBOL_NAME:  nvlddmkm+11bd50
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nvlddmkm
    
    IMAGE_NAME:  nvlddmkm.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4bb7d7fd
    
    FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys
    
    BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys
    
    Followup: MachineOwner
    ---------
    EDIT. THERE MIGHT BE TWO OTHER THINGS YOU HAVE NOT TRIED

    First, it might be a heat issue (download cpu-z, and gpu-z both free) to keep an eye on the temps

    Second-- you haven't mentioned your power supply unit. It may not have enough power on the video rail. Check to see how much your card needs, and how much the power supply can deliver on the video rail

    Also noticed 2 gigs of ram you may be starving the video card out os shared ram which could make it crash. The problem might be easily cured for ram is inexpensive


    K
      My Computer


  9. Posts : 15
    Windows 7 64bit
    Thread Starter
       #9

    zigzag3143 said:
    EDIT. THERE MIGHT BE TWO OTHER THINGS YOU HAVE NOT TRIED

    First, it might be a heat issue (download cpu-z, and gpu-z both free) to keep an eye on the temps

    Second-- you haven't mentioned your power supply unit. It may not have enough power on the video rail. Check to see how much your card needs, and how much the power supply can deliver on the video rail

    Also noticed 2 gigs of ram you may be starving the video card out os shared ram which could make it crash. The problem might be easily cured for ram is inexpensive


    K
    Heat issue it is not, however i do have to force the fan on software like EVGA precision, and as said earlier i even tried 2 additional fans on the former gtx260 just to see what it would do, nothing changed on that part.

    Power should not be an issue, just bought a new one because i thought it might be a power issue, i can't tell you the model exactly right now but i will check it if you think it might be an issue. However it was bought from my supplier which is also the father of my friend and i trust his judgement on what the sufficient power might be. (ie. it was handpicked for this comp setup)

    Ram, you might be on to something, actually you really really might be on to something with that. I will call my supplier for how to best set up the ram in my comp.

    Artifaction on bios screen is usually caused by malfunctioning ram is it not?
    Last edited by Ruoja; 28 Apr 2010 at 06:10. Reason: Q
      My Computer


  10. Posts : 15
    Windows 7 64bit
    Thread Starter
       #10

    Allright, the second i attempted to start Global Agenda game i BSOD:d due driver verifier, heres the dump.
      My Computer


 
Page 1 of 3 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 10:24.
Find Us