So i created a previous post about system crashes and BSOD a few days ago. I later found that some of my RAM timings were incorrect and thought that this might have solved the issue. I was wrong. I have had 2 more BSOD crashes since then and have attached the recommended files, including those from my last post.
I put the PC together last week and it's my first time building my own system. It's running Win 7 Pro 64bit on a Gigabyte GA-880GA-UD3H board with an AMD Phenom II X4 3.4GHz processor and 4x2Gb A-Data RAM. I have a Radeon 6870 graphics card.
Any help would be much appreciated.
Alex
Also, here is the link to my last post,
http://www.sevenforums.com/crashes-d...m-timings.html
I put the PC together last week and it's my first time building my own system. It's running Win 7 Pro 64bit on a Gigabyte GA-880GA-UD3H board with an AMD Phenom II X4 3.4GHz processor and 4x2Gb A-Data RAM. I have a Radeon 6870 graphics card.
Any help would be much appreciated.
Alex
Also, here is the link to my last post,
http://www.sevenforums.com/crashes-d...m-timings.html
�� Quote: Originally Posted by alderosa 
So i created a previous post about system crashes and BSOD a few days ago. I later found that some of my RAM timings were incorrect and thought that this might have solved the issue. I was wrong. I have had 2 more BSOD crashes since then and have attached the recommended files, including those from my last post.
I put the PC together last week and it's my first time building my own system. It's running Win 7 Pro 64bit on a Gigabyte GA-880GA-UD3H board with an AMD Phenom II X4 3.4GHz processor and 4x2Gb A-Data RAM. I have a Radeon 6870 graphics card.
Any help would be much appreciated.
Alex
Also, here is the link to my last post,
http://www.sevenforums.com/crashes-d...m-timings.html
I put the PC together last week and it's my first time building my own system. It's running Win 7 Pro 64bit on a Gigabyte GA-880GA-UD3H board with an AMD Phenom II X4 3.4GHz processor and 4x2Gb A-Data RAM. I have a Radeon 6870 graphics card.
Any help would be much appreciated.
Alex
Also, here is the link to my last post,
http://www.sevenforums.com/crashes-d...m-timings.html
Memory management caused by your video driver
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\Windows_NT6_BSOD_jcgriff2\120910-21684-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: C:\symbols;srv*e:\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.16617.amd64fre.win7_gdr.100618-1621 Machine Name: Kernel base = 0xfffff800`0300a000 PsLoadedModuleList = 0xfffff800`03247e50 Debug session time: Thu Dec 9 12:40:36.512 2010 (GMT-5) System Uptime: 0 days 1:01:40.182 Loading Kernel Symbols ............................................................... ................................................................ ........................ Loading User Symbols Loading unloaded module list ...... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 10E, {24, fffff8a004b3fe50, 200000000000000, 0} Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::DestroyOneAllocation+28c ) Followup: MachineOwner --------- 3: kd> t ^ No runnable debuggees error in 't' 3: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* VIDEO_MEMORY_MANAGEMENT_INTERNAL (10e) The video memory manager encountered a condition that it can't recover from. By crashing, the video memory manager is attempting to get enough information into the minidump such that somebody can pinpoint what lead to this condition. Arguments: Arg1: 0000000000000024, The subtype of the bugcheck: Arg2: fffff8a004b3fe50 Arg3: 0200000000000000 Arg4: 0000000000000000 Debugging Details: ------------------ BUGCHECK_STR: 0x10e_24 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: csrss.exe CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from fffff88003ebd22f to fffff8000307a740 STACK_TEXT: fffff880`03b95188 fffff880`03ebd22f : 00000000`0000010e 00000000`00000024 fffff8a0`04b3fe50 02000000`00000000 : nt!KeBugCheckEx fffff880`03b95190 fffff880`0421ac64 : fffffa80`0941b000 fffff8a0`04b3fe50 fffffa80`0941b000 fffff8a0`02352000 : watchdog!WdLogEvent5+0x11b fffff880`03b951e0 fffff880`0420198f : fffffa80`000008a8 fffff8a0`04607120 fffffa80`0941b000 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::DestroyOneAllocation+0x28c fffff880`03b952c0 fffff880`042ccfb3 : fffff8a0`04cc14e0 00000000`00000000 fffff8a0`02352000 00000000`00000174 : dxgmms1!VidMmDestroyAllocation+0x4f fffff880`03b952f0 fffff880`042cd2f0 : fffff8a0`04cc14e0 00000000`00000000 00000000`00000001 fffff8a0`02352000 : dxgkrnl!DXGDEVICE::DestroyAllocations+0x5eb fffff880`03b953e0 fffff880`042cc53d : fffff8a0`02352000 fffff8a0`02352000 fffff8a0`0346f8a0 fffffa80`092dcc20 : dxgkrnl!DXGDEVICE::DestroyResource+0x84 fffff880`03b95410 fffff880`042cc825 : fffffa80`0940caf0 fffff8a0`02352000 00000000`00000001 fffff8a0`04ffc4b0 : dxgkrnl!DXGDEVICE::ProcessTerminationList+0x95 fffff880`03b95460 fffff880`042d032b : fffff8a0`02352000 00000000`c0001f40 fffff8a0`021df840 fffff880`042973af : dxgkrnl!DXGDEVICE::TerminateAllocations+0xb9 fffff880`03b954b0 fffff880`042d9ef5 : fffff8a0`02352000 fffff880`03b955a8 00000000`00000000 fffff8a0`021df840 : dxgkrnl!DXGDEVICE::DestroyAllocation+0x93 fffff880`03b95540 fffff960`00698804 : 00000000`00000000 00000000`00000000 fffff8a0`02204970 fffff8a0`02204970 : dxgkrnl!DxgkCddDestroyAllocation+0x241 fffff880`03b955f0 fffff960`00699a19 : 00000000`00000004 fffff900`c00c04e8 fffff900`c00c0d20 fffff900`c2213940 : cdd!CDDPDEV::DestroyAllocation+0x68 fffff880`03b95660 fffff960`0069b450 : 00000000`00000000 00000000`00000000 fffff900`c00bf020 ffffffff`fffe7960 : cdd!CHwCommandBuffer::FlushDestroyAllocationList+0x3d fffff880`03b95690 fffff960`006995d5 : fffffa80`092c3b40 fffffa80`092c3b40 00000000`00000000 fffff900`c00bf020 : cdd!CHwCommandBuffer::FlushGdiCommands+0x2a0 fffff880`03b95980 fffff960`00695c6e : ffffffff`fffd74f6 00000000`00000010 00000000`00000001 fffffa80`00000000 : cdd!CDDPDEV::FlushGdiOutput+0x81 fffff880`03b959b0 fffff800`0331ec06 : 00000000`0462bd4b fffffa80`092e5b60 00000000`00000080 fffffa80`0925eb30 : cdd!PresentWorkerThread+0x902 fffff880`03b95d40 fffff800`03058c26 : fffff880`02f64180 fffffa80`092e5b60 fffff880`02f6efc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a fffff880`03b95d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16 STACK_COMMAND: kb FOLLOWUP_IP: dxgmms1!VIDMM_GLOBAL::DestroyOneAllocation+28c fffff880`0421ac64 c78424e000000057f7ffff mov dword ptr [rsp+0E0h],0FFFFF757h SYMBOL_STACK_INDEX: 2 SYMBOL_NAME: dxgmms1!VIDMM_GLOBAL::DestroyOneAllocation+28c FOLLOWUP_NAME: MachineOwner MODULE_NAME: dxgmms1 IMAGE_NAME: dxgmms1.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc578 FAILURE_BUCKET_ID: X64_0x10e_24_dxgmms1!VIDMM_GLOBAL::DestroyOneAllocation+28c BUCKET_ID: X64_0x10e_24_dxgmms1!VIDMM_GLOBAL::DestroyOneAllocation+28c Followup: MachineOwner --------- When upgrading your graphic driver you MUST remove all traces of the current driver. In order to do that we recommend using Guru3D - Driver Sweeper
When it is removed then download and install the fresh copy.
Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Boot from the CD, and leave it running for at least 5 or 6 passes.
Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot. Test the sticks individually, and if you find a good one, test it in all slots.
Thanks for taking a look for me Zigzag3143. I was coming to the conclusion that it was drivers or RAM after reading other posts but didn't know which. I've reinstalled the graphics drivers and left out the Catalyst Control Centre and other bundled 'goodies' that generally are a waste of space. Hopefully this will resolve the issue. I'm also running Memtest86+ as I type (so far so good!).
I had a few concerns about my RAM and have also been fiddling with the timings/voltages. I have 4x A-DATA AX3U1333GB2G8-2G and have read in a few places that they are pretty fussy about the voltages, etc that are used with them. When left on auto my Mobo seems to change the stable settings on each boot so I manually set them to the recommended and upped the voltage. Hopefully this helps too.
Again, thanks for having a look at this for me. I hope this sorts the problem!
Alex
This is the RAM I have btw (A-Data website is rubbish);
Newegg.com - A-DATA Gaming Series 4GB (2 x 2GB) 240-Pin DDR3 SDRAM DDR3 1333G (PC3 10666) Desktop Memory Model AX3U1333GB2G8-2G
I had a few concerns about my RAM and have also been fiddling with the timings/voltages. I have 4x A-DATA AX3U1333GB2G8-2G and have read in a few places that they are pretty fussy about the voltages, etc that are used with them. When left on auto my Mobo seems to change the stable settings on each boot so I manually set them to the recommended and upped the voltage. Hopefully this helps too.
Again, thanks for having a look at this for me. I hope this sorts the problem!
Alex
This is the RAM I have btw (A-Data website is rubbish);
Newegg.com - A-DATA Gaming Series 4GB (2 x 2GB) 240-Pin DDR3 SDRAM DDR3 1333G (PC3 10666) Desktop Memory Model AX3U1333GB2G8-2G
One error showed up in Memtest86+ when all sticks were in. I'm currently testing one stick at a time and I'm on the first stick. Could be a while...
Just found out I have defective RAM. 2 of the sticks were ok. One of the others wasn't Windows Memory Test didn't pick it up when I first put the PC together but Memtest86+ did. I guess this was actually the problem and not the graphics drivers?
Scratch that. I tested all the sticks with Memtest86+ for 6 passes and found 1 defective. I thne used one of the good sticks to test all the motherboard slots out. All of these checked out fine too. I tried to run with 2 good sticks in the Mobo and the system crashed into BSOD almost straight after I booted (I got into Windows first). I've attached the dump file here... This is really starting to annoy me. The other dump files were attached previously. I am using the manufacturer recommended settings for my RAM, not the Mobo auto ones.
So system won't shut down without BSOD now. It's got worse with the 2 RAM sticks instead of 4. Could this issue be related to something else? I can send more .dmp files if people want.
�� Quote: Originally Posted by alderosa So system won't shut down without BSOD now. It's got worse with the 2 RAM sticks instead of 4. Could this issue be related to something else? I can send more .dmp files if people want.
Dont forget as I told you on the other site. SPTD.sys needs to be removed.
Please remove any CD virtualization programs such as Daemon Tools and Alcohol 120%. They use a driver, found in your dmp, sptd.sys, that is notorious for causing BSODs. Use this SPTD uninstaller when you're done: DuplexSecure - Downloads
You can use MagicDisc as an alternative.
Freeware MagicISO Virtual CD/DVD-ROM(MagicDisc) Overview
Are you sure that this is the problem? Could all this be a symptom of RAM problems or other hardware isuues? Should I update my BIOS?
Is he sure sptd.sys is the problem? No. Is sptd.sys a known problem? Yes. In troubleshooting you have to eliminate all possible causes of crashes. This includes removing sptd.sys and updating out of date drivers. Troubleshooting is a process of elimination. I recommend you follow Ken's expert advice.
Sorry, I didn't mean to offend, I just had read about something else that might be the cause and wanted some advice. I'll definitely by removing these drivers too.
No offense taken at all. I just wanted to explain why we do things the way we do in the troubleshooting process.
I'll let you know when I've made the changes. The problem is the BSODs are random so it might be a while before I know if it's solved the issue.
Just had another BSOD. I think it's the graphics drivers. I found a program called BlueScreenView and looked at some stuff. Seems the drivers below were the cause. Am I correct in thinking that they are graphics related? They're the same as some of the earlier ones in the other dump files I posted previously.
Drivers that caused problem according to BlueScreenView;
atikmpag.sys+6f94
dxgkrnl.sys+5cef8
dxgmms1.sys+ff07
I've attached a new set of files, this has all my dump files so far. The latest crash (that I just had) is the one occurring on 12/10/2010. Note that I was just about to remove the driver you told me to remove before when it crashed.
Drivers that caused problem according to BlueScreenView;
atikmpag.sys+6f94
dxgkrnl.sys+5cef8
dxgmms1.sys+ff07
I've attached a new set of files, this has all my dump files so far. The latest crash (that I just had) is the one occurring on 12/10/2010. Note that I was just about to remove the driver you told me to remove before when it crashed.
Ok guys, sptd.sys is gone. As is my old BIOS. I have updated to version F7 and changed some of the RAM settings too. I have heard that the ADATA gaming series RAM I have is particularly power hungry so upped the voltage and reduced the timings to mobo recommended 9-9-9-24. We'll see how it goes...
Thank you very much for the update on what you have done so far. Good job.
�� Quote: Originally Posted by alderosa atikmpag.sys - ATI Video driver (remove the Catalyst Control Center and only install the Display Driver)Global Provider of Innovative Graphics, Processors and Media Solutions | AMD. This is a video driver.
dxgkrnl.sys - A Windows system Direct X driver and very unlikely to cause a crash.
dxgmms1.sys - A Windows system Direct X driver and very unlikely to cause a crash.
CCC is known to cause problems on some systems. I also suggest you check the temps of your video card. Overheating can also cause BSOD's. Other drivers can cause conflicts the interfere with the video system.
You actually have three dumps dated 12/10/10. All are different error codes and all blame different drivers. One of them is a VIDEO_TDR_FAILURE error. However, since you updated your BIOS, uninstalled sptd.sys and changed RAM settings, these dumps files are moot.
�� Quote: Originally Posted by alderosa I hope your news will be good. Keep us posted. If you get another BSOD, upload it, and we will tackle it again.
�� Quote: Originally Posted by alderosa Just had another BSOD. I think it's the graphics drivers. I found a program called BlueScreenView and looked at some stuff. Seems the drivers below were the cause. Am I correct in thinking that they are graphics related? They're the same as some of the earlier ones in the other dump files I posted previously.
Drivers that caused problem according to BlueScreenView;
atikmpag.sys+6f94
dxgkrnl.sys+5cef8
dxgmms1.sys+ff07
I've attached a new set of files, this has all my dump files so far. The latest crash (that I just had) is the one occurring on 12/10/2010. Note that I was just about to remove the driver you told me to remove before when it crashed.
Drivers that caused problem according to BlueScreenView;
atikmpag.sys+6f94
dxgkrnl.sys+5cef8
dxgmms1.sys+ff07
I've attached a new set of files, this has all my dump files so far. The latest crash (that I just had) is the one occurring on 12/10/2010. Note that I was just about to remove the driver you told me to remove before when it crashed.
dxgkrnl.sys - A Windows system Direct X driver and very unlikely to cause a crash.
dxgmms1.sys - A Windows system Direct X driver and very unlikely to cause a crash.
CCC is known to cause problems on some systems. I also suggest you check the temps of your video card. Overheating can also cause BSOD's. Other drivers can cause conflicts the interfere with the video system.
You actually have three dumps dated 12/10/10. All are different error codes and all blame different drivers. One of them is a VIDEO_TDR_FAILURE error. However, since you updated your BIOS, uninstalled sptd.sys and changed RAM settings, these dumps files are moot.
�� Quote: Originally Posted by alderosa Ok guys, sptd.sys is gone. As is my old BIOS. I have updated to version F7 and changed some of the RAM settings too. I have heard that the ADATA gaming series RAM I have is particularly power hungry so upped the voltage and reduced the timings to mobo recommended 9-9-9-24. We'll see how it goes...
Thanks for taking a look at the files for me Carl. I had already looked at the video card drivers and replaced them (without the extra fluff like the CCC) yesterday I think? Ken found these to be a problem in one of the earlier dump files he examined. Does this mean the issue might be a problem elsewhere if I've already tried to sort this out before?
I've been meaning to update my BIOS for a while, I didn't realise it would render the files I have previously uploaded obsolete though. Sorry about this
. If the past few days are anything to go by, I should get a BSOD either later tonight or tomorrow if something's still wrong. I'll keep you posted!
I've been meaning to update my BIOS for a while, I didn't realise it would render the files I have previously uploaded obsolete though. Sorry about this
. If the past few days are anything to go by, I should get a BSOD either later tonight or tomorrow if something's still wrong. I'll keep you posted! You are welcome and thank you for the update. As far as that dump goes, we will just have to see how your system does.
There is certainly nothing to be sorry about; you updated your system and that is a good thing. It does change the hardware aspect and makes the previous dumps obsolete or at least partially obsolete - just like if you installed a new video card or uninstalled an obsolete program. I hope you do not get a BSOD later tonight. I hope you have solved your problem. But if you do get one, upload the dump and we will be here to look at it.
There is certainly nothing to be sorry about; you updated your system and that is a good thing. It does change the hardware aspect and makes the previous dumps obsolete or at least partially obsolete - just like if you installed a new video card or uninstalled an obsolete program. I hope you do not get a BSOD later tonight. I hope you have solved your problem. But if you do get one, upload the dump and we will be here to look at it.
Thanks Carl. I'll let you know how I get on. Your help is much appreciated. Fingers crossed!
So i had another BSOD on my first reboot this morning. I had to revert to an earlier system restore point in order to get through the start up. I made sure to remove the files you suggested though (like the sptd.sys again) when I finally got back into windows. It said some stuff about startup registry needing repair and tried to check the disk for errors before loading the OS. I've attached the dump file.
This crash occurred after only 25 seconds of uptime. This means it is most likely either a hard issue or a driver issue. Can you boot in the Safe mode without a BSOD? If you can, that points to a likely driver issue. If you get a BSOD in the Safe mode, it is likely a hardware issue. I see this BSOD occurred during a cold boot. A failing power supply can cause this.
Your dump blames wininit.exe for the crash. This file is a Windows system startup file. There are some viruses that disguise themselves as wininit.exe. I suggest you download and install Malwarebytes. Update it and then run a scan to make sure you don't have a nasty lurking about on your system.
I find two outdated drivers loaded on your system. The rest of your drivers look good. Update these two drivers and see if they make a difference.
Let me know if you can cold boot in the Safe mode without a BSOD. That will tell us what we should try next. If you can boot in the Safe mode, enable Driver Verifier. Driver Verifier will cause a BSOD if it encounters a problem driver. Upload any and all Driver Verifier enabled dumps. Follow the instructions in this tutorial precisely: Driver Verifier - Enable and Disable. If you get a BSOD in the Safe mode, run Memtest again from a cold boot after your computer has been off for a while. RAM - Test with Memtest86+
Your dump blames wininit.exe for the crash. This file is a Windows system startup file. There are some viruses that disguise themselves as wininit.exe. I suggest you download and install Malwarebytes. Update it and then run a scan to make sure you don't have a nasty lurking about on your system.
I find two outdated drivers loaded on your system. The rest of your drivers look good. Update these two drivers and see if they make a difference.
Hi Carl. I only seem to get BSOD (most of the time) when I boot from a real cold start, i.e. after several hours of PC downtime so the safe mode test you suggest probably won't be too useful. I did however have a problem with driver verifier. I ran it and got a BSOD on restart resulting from RTKVHD64.sys which gave a stop error code 0.0000005.
I've uploaded the dumps here too. Note that the last 2 dumps from today (12/10/2010) are the ones relevant to the driver verifier (I missed the safe mode option once so got another BSOD before I turned off driver verifier).
I did not have any malware and have updated the logitech drivers also.
I've uploaded the dumps here too. Note that the last 2 dumps from today (12/10/2010) are the ones relevant to the driver verifier (I missed the safe mode option once so got another BSOD before I turned off driver verifier).
I did not have any malware and have updated the logitech drivers also.
So I had left my PC alone for a couple of hours and when I tried to reboot this time I had 'disk read error' press ctrl+alt+del to restart. I did and it restarted fine. Thought I'd mention it though. I've also reduced my RAM timings and voltage to 9-9-9-25 and 1.65V on the recommendation of someone I was talking to about RAM settings.
I see that you successfully updated the Logitech drivers. Very good. Your RTKVHD64.sys driver is up to date. The 0.0000005 error code means memory corruption. One of the two Driver Verifier enabled dumps contained no data; it is corrupt. Make sure Driver Verifier is turned off for now.
Run Memtest again from a cold boot after your computer has been off for at least two hours. RAM - Test with Memtest86+. I want to be as certain as we can be (Memtest is not perfect) that RAM is not causing the problem. Post your results.
Run Memtest again from a cold boot after your computer has been off for at least two hours. RAM - Test with Memtest86+. I want to be as certain as we can be (Memtest is not perfect) that RAM is not causing the problem. Post your results.
Code:
Windows 7 Kernel Version 7600 MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7600.16617.amd64fre.win7_gdr.100618-1621 Machine Name: Kernel base = 0xfffff800`03059000 PsLoadedModuleList = 0xfffff800`03296e50 Debug session time: Sat Dec 11 14:10:18.711 2010 (GMT-5) System Uptime: 0 days 0:00:25.428 Loading Kernel Symbols ............................................................... ................................................................ ...... Loading User Symbols Loading unloaded module list .... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck D5, {fffff98002e08d60, 0, fffff8800691cef6, 0} Unable to load image \SystemRoot\system32\drivers\RTKVHD64.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for RTKVHD64.sys *** ERROR: Module load completed but symbols could not be loaded for RTKVHD64.sys Could not read faulting driver name Probably caused by : RTKVHD64.sys ( RTKVHD64+d9ef6 ) Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* DRIVER_PAGE_FAULT_IN_FREED_SPECIAL_POOL (d5) Memory was referenced after it was freed. This cannot be protected by try-except. When possible, the guilty driver's name (Unicode string) is printed on the bugcheck screen and saved in KiBugCheckDriver. Arguments: Arg1: fffff98002e08d60, memory referenced Arg2: 0000000000000000, value 0 = read operation, 1 = write operation Arg3: fffff8800691cef6, if non-zero, the address which referenced memory. Arg4: 0000000000000000, (reserved) Debugging Details: ------------------ Could not read faulting driver name READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800033010e0 fffff98002e08d60 FAULTING_IP: RTKVHD64+d9ef6 fffff880`0691cef6 8b4630 mov eax,dword ptr [rsi+30h] MM_INTERNAL_CODE: 0 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP BUGCHECK_STR: 0xD5 PROCESS_NAME: svchost.exe CURRENT_IRQL: 0 TRAP_FRAME: fffff88003cc82b0 -- (.trap 0xfffff88003cc82b0) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=0000000000000000 rbx=0000000000000000 rcx=fffff88003cc84d8 rdx=fffff88003cc8440 rsi=0000000000000000 rdi=0000000000000000 rip=fffff8800691cef6 rsp=fffff88003cc8440 rbp=0000000000000002 r8=0000000000000000 r9=fffff8800691cef6 r10=0000000000000000 r11=fffff80003243e80 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei ng nz na po nc RTKVHD64+0xd9ef6: fffff880`0691cef6 8b4630 mov eax,dword ptr [rsi+30h] ds:3e80:00000000`00000030=???????? Resetting default scope LAST_CONTROL_TRANSFER: from fffff80003149f14 to fffff800030c9740 STACK_TEXT: fffff880`03cc8148 fffff800`03149f14 : 00000000`00000050 fffff980`02e08d60 00000000`00000000 fffff880`03cc82b0 : nt!KeBugCheckEx fffff880`03cc8150 fffff800`030c782e : 00000000`00000000 fffff8a0`0140910c fffffa80`07038000 fffff800`030fc33f : nt! ?? ::FNODOBFM::`string'+0x42837 fffff880`03cc82b0 fffff880`0691cef6 : fffff880`03cc84d8 00000000`00000000 fffff8a0`0140910c fffffa80`06d0ef40 : nt!KiPageFault+0x16e fffff880`03cc8440 fffff880`03cc84d8 : 00000000`00000000 fffff8a0`0140910c fffffa80`06d0ef40 00000000`00000000 : RTKVHD64+0xd9ef6 fffff880`03cc8448 00000000`00000000 : fffff8a0`0140910c fffffa80`06d0ef40 00000000`00000000 fffff800`00000000 : 0xfffff880`03cc84d8 STACK_COMMAND: kb FOLLOWUP_IP: RTKVHD64+d9ef6 fffff880`0691cef6 8b4630 mov eax,dword ptr [rsi+30h] SYMBOL_STACK_INDEX: 3 SYMBOL_NAME: RTKVHD64+d9ef6 FOLLOWUP_NAME: MachineOwner MODULE_NAME: RTKVHD64 IMAGE_NAME: RTKVHD64.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4c80ab93 FAILURE_BUCKET_ID: X64_0xD5_VRF_RTKVHD64+d9ef6 BUCKET_ID: X64_0xD5_VRF_RTKVHD64+d9ef6 Followup: MachineOwner --------- Hi Carl. I'll do a memtest86+ run on each stick again, I guess I'll have the results by tomorrow afternoon maybe? I'll post as soon as I get them. Today and yesterday the system has only crashed from initial startup i.e. the first time it is turned on or if it left off for few hours before power up. Weird huh?
Yes it is weird and it really sounds like a power supply problem.
Odd thing is, that wasn't how it happened before! It would BSOD in the middle of running Firefox or watching a movie!
*Sorry, ignore this. I actually had a bad RAM stick when I first had errors (it's being RMA's at the moment).
*Sorry, ignore this. I actually had a bad RAM stick when I first had errors (it's being RMA's at the moment).
As per usual, BSOD on first start up this morning. I'm running Memtest86+ now so I'll post the results when available. My error this time was BAD POOL HEADER Stop code 0x00000019. It also went into startup repair next boot and couldn't fix anything, thought it was a driver problem though. Do you want the dump file for this one too?
I read this post (see link below) about someone with a similar issue and they seemed to come to the conclusion it might be a hard disk issue? I only mention it because it's the same type of problem and I had that 'disk read error' yesterday. Any thoughts? I also did read another post where it was software related and clean install fixed all however...
It's all fun & games isn't it.
http://www.sevenforums.com/crashes-d...-start-up.html
I read this post (see link below) about someone with a similar issue and they seemed to come to the conclusion it might be a hard disk issue? I only mention it because it's the same type of problem and I had that 'disk read error' yesterday. Any thoughts? I also did read another post where it was software related and clean install fixed all however...
It's all fun & games isn't it.
http://www.sevenforums.com/crashes-d...-start-up.html
Run Check Disk
Copy/paste the results into your next post.
I also suggest that your run an SFC (System File Checker) scan. SFC /SCANNOW Command - System File Checker.
Quote:
Run CHKDSK /R /F from an elevated (Run as adminstrator) Command Prompt. Please do this for each hard drive on your system.
When it tells you it can't do it right now - and asks you if you'd like to do it at the next reboot - answer Y (for Yes) and press Enter. Then reboot and let the test run. It may take a while for it to run, but keep an occasional eye on it to see if it generates any errors. See "CHKDSK LogFile" below in order to check the results of the test.
Elevated Command Prompt:
Go to Start and type in "cmd.exe" (without the quotes)
At the top of the Search Box, right click on Cmd.exe and select "Run as administrator"
CHKDSK LogFile:
Go to Start and type in "eventvwr.msc" (without the quotes) and press Enter
Expand the Windows logs heading, then select the Application log file entry.
Double click on the Source column header.
Scroll down the list until you find the Chkdsk entry (wininit for Windows 7).
When it tells you it can't do it right now - and asks you if you'd like to do it at the next reboot - answer Y (for Yes) and press Enter. Then reboot and let the test run. It may take a while for it to run, but keep an occasional eye on it to see if it generates any errors. See "CHKDSK LogFile" below in order to check the results of the test.
Elevated Command Prompt:
Go to Start and type in "cmd.exe" (without the quotes)
At the top of the Search Box, right click on Cmd.exe and select "Run as administrator"
CHKDSK LogFile:
Go to Start and type in "eventvwr.msc" (without the quotes) and press Enter
Expand the Windows logs heading, then select the Application log file entry.
Double click on the Source column header.
Scroll down the list until you find the Chkdsk entry (wininit for Windows 7).
Copy/paste the results into your next post.
I also suggest that your run an SFC (System File Checker) scan. SFC /SCANNOW Command - System File Checker.
I tried to run a chkdsk on my secondary drive yesterday from in Windows (it's only got my work and pictures on it - no system files) and it got to the end of the scan and simply started again. I selected both the options to scan for and fix any errors. Is this usual? I also couldn't view the results of this in the event viewer. Should I have let in run through again?
I'm still on the memtest at the moment, stick 1 looks ok. I'll try stick 2 in a second then go onto the disk checking. I can also get copies of the Samsung and WD hard drive checkers for my respective drives. Should I use those too?
I'm still on the memtest at the moment, stick 1 looks ok. I'll try stick 2 in a second then go onto the disk checking. I can also get copies of the Samsung and WD hard drive checkers for my respective drives. Should I use those too?
So memtest86+ on the second stick came up with lots of errors. Weird cos it didn't before and I did 6 passes but I guess that's life. I guess I'll have to RMA this one too. Hopefully, if I boot with just the 1 stick it won't blue screen. Should be a good test of the RAM. I might see if the guys at Newegg will refund me and let me have other RAM, 2 defective sticks out of 4 is pretty bad.
Yes, sometimes it will run twice. The log should show up in Event Viewer under Application. Look for the wininit entry.
It certainly will not hurt to run the manufacturers' hard drive checkers. These are much more thorough than Check Disk.
Indeed, two bad sticks out four is bad; but it does happen. Don't for get to test you motherboard slots with the good stick. Post back with how your computer does on the one good stick.
It certainly will not hurt to run the manufacturers' hard drive checkers. These are much more thorough than Check Disk.
Indeed, two bad sticks out four is bad; but it does happen. Don't for get to test you motherboard slots with the good stick. Post back with how your computer does on the one good stick.
I'll do some disk checks now, I'll have to RMA that RAM though. I guess the fact it didn't show errors the first time was just a fluke? It definitely seems bad now. Hopefully it was this that was the cause. I'll let you know.
Memtest is not 100% perfect. It is not unusual for it to miss something the first time or even miss it altogether. We have seen this happen before.
My chkdsk results, there are a couple of inconsistencies;
Checking file system on C:
The type of the file system is NTFS.
A disk check has been scheduled.
Windows will now check the disk.
CHKDSK is verifying files (stage 1 of 3)...
211200 file records processed. File verification completed.
281 large file records processed. 0 bad file records processed. 2 EA records processed. 44 reparse records processed. CHKDSK is verifying indexes (stage 2 of 3)...
266716 index entries processed. Index verification completed.
0 unindexed files scanned. 0 unindexed files recovered. CHKDSK is verifying security descriptors (stage 3 of 3)...
The hash value 0xc2a48011 of the security descriptor entry with Id
0x15c at offset 0x5110 is invalid. The correct value is 0xc2a48019.
The hash value 0xc0e6f51d of the security descriptor entry with Id
0x246 at offset 0x10ff0 is invalid. The correct value is 0xc0eaf51d.
Repairing the security file record segment.
211200 file SDs/SIDs processed. Cleaning up 77 unused index entries from index $SII of file 9.
Cleaning up 77 unused index entries from index $SDH of file 9.
Cleaning up 77 unused security descriptors.
Security descriptor verification completed.
27759 data files processed. CHKDSK is verifying Usn Journal...
35685712 USN bytes processed. Usn Journal verification completed.
Windows has made corrections to the file system.
976657407 KB total disk space.
37704660 KB in 182952 files.
89840 KB in 27760 indexes.
0 KB in bad sectors.
342387 KB in use by the system.
65536 KB occupied by the log file.
938520520 KB available on disk.
4096 bytes in each allocation unit.
244164351 total allocation units on disk.
234630130 allocation units available on disk.
Internal Info:
00 39 03 00 23 37 03 00 af 98 05 00 00 00 00 00 .9..#7..........
9a 00 00 00 2c 00 00 00 00 00 00 00 00 00 00 00 ....,...........
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
Windows has finished checking your disk.
Please wait while your computer restarts.
Checking file system on C:
The type of the file system is NTFS.
A disk check has been scheduled.
Windows will now check the disk.
CHKDSK is verifying files (stage 1 of 3)...
211200 file records processed. File verification completed.
281 large file records processed. 0 bad file records processed. 2 EA records processed. 44 reparse records processed. CHKDSK is verifying indexes (stage 2 of 3)...
266716 index entries processed. Index verification completed.
0 unindexed files scanned. 0 unindexed files recovered. CHKDSK is verifying security descriptors (stage 3 of 3)...
The hash value 0xc2a48011 of the security descriptor entry with Id
0x15c at offset 0x5110 is invalid. The correct value is 0xc2a48019.
The hash value 0xc0e6f51d of the security descriptor entry with Id
0x246 at offset 0x10ff0 is invalid. The correct value is 0xc0eaf51d.
Repairing the security file record segment.
211200 file SDs/SIDs processed. Cleaning up 77 unused index entries from index $SII of file 9.
Cleaning up 77 unused index entries from index $SDH of file 9.
Cleaning up 77 unused security descriptors.
Security descriptor verification completed.
27759 data files processed. CHKDSK is verifying Usn Journal...
35685712 USN bytes processed. Usn Journal verification completed.
Windows has made corrections to the file system.
976657407 KB total disk space.
37704660 KB in 182952 files.
89840 KB in 27760 indexes.
0 KB in bad sectors.
342387 KB in use by the system.
65536 KB occupied by the log file.
938520520 KB available on disk.
4096 bytes in each allocation unit.
244164351 total allocation units on disk.
234630130 allocation units available on disk.
Internal Info:
00 39 03 00 23 37 03 00 af 98 05 00 00 00 00 00 .9..#7..........
9a 00 00 00 2c 00 00 00 00 00 00 00 00 00 00 00 ....,...........
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
Windows has finished checking your disk.
Please wait while your computer restarts.
The chkdsk results for the other drive, all ok by the looks of it;
Checking file system on D:
The type of the file system is FAT32.
A disk check has been scheduled.
Windows will now check the disk.
Volume Serial Number is DD94-6957
Windows is verifying free space...
Free space verification is complete.
Windows has checked the file system and found no problems.
976513536 KB total disk space.
118496 KB in 3596 hidden files.
105984 KB in 3308 folders.
522518720 KB in 37721 files.
453770304 KB are available.
32768 bytes in each allocation unit.
30516048 total allocation units on disk.
14180322 allocation units available on disk.
Checking file system on D:
The type of the file system is FAT32.
A disk check has been scheduled.
Windows will now check the disk.
Volume Serial Number is DD94-6957
Windows is verifying free space...
Free space verification is complete.
Windows has checked the file system and found no problems.
976513536 KB total disk space.
118496 KB in 3596 hidden files.
105984 KB in 3308 folders.
522518720 KB in 37721 files.
453770304 KB are available.
32768 bytes in each allocation unit.
30516048 total allocation units on disk.
14180322 allocation units available on disk.
Alderosa
A quick question.
Why is that drive formatted FAT32??
A quick question.
Why is that drive formatted FAT32??
It's an external hard drive from about 4 years ago and the power supply to it (transformer) broke so I bunged it into this PC when I set it up. I didn't have a large drive (till I bought the main one for this PC) to transfer the stuff on it to and reformat (which I've been meaning to do) but I've got bigger fish to fry at the moment in terms of trouble shooting!
What do you think of the results for the other drive posted above the FAT32 one? Is there anything to worry about?
Hopefully it is just the RAM that's defective and been causing my problem. I should know tomorrow morning if it BSODs on the first boot of the day again. The RAM in it now (1 stick of 2Gb) has gone through 2 memtests of 6 passes each so hopefully it is actually good. I'm going to have to return it though and tbh I think I'm going to get a different brand. I'll reformat the hard disk when the other issues are sorted, unless you think it might be a problem?
What do you think of the results for the other drive posted above the FAT32 one? Is there anything to worry about?
Hopefully it is just the RAM that's defective and been causing my problem. I should know tomorrow morning if it BSODs on the first boot of the day again. The RAM in it now (1 stick of 2Gb) has gone through 2 memtests of 6 passes each so hopefully it is actually good. I'm going to have to return it though and tbh I think I'm going to get a different brand. I'll reformat the hard disk when the other issues are sorted, unless you think it might be a problem?
Just had results of SFC check, no problems reported.
Drive C: looks fine. There were a few things wrong in the file system; but Check Disk fixed them. There are no bad sectors - that is a good thing. It is a good idea to run Check disk every now and then to keep the file system in good shape. And if you start seeing many bad sectors popping up, that may be a sign the hard drive is on its way out. A few bad sectors is normal. Drive D: is fine. I, too, was surprised to see it was FAT32.
Yeah I know, it's a bit of an old relic that drive. I got it a long while back and never had another drive with enough space to move the stuff I wanted over and reformat it after I'd already put stuff onto it. It'll get done eventually, hopefully when I fix the issues I'm currently having.
No BSOD yet today. I know well enough not to get excited just yet! Hopefully it was the memory causing problems but I guess I'll find out soon enough when I stick some 'good' sticks in.
That is wonderful news! thank you for the update. We will be waiting to see what happens.
No BSOD at startup today either. I get my new RAM today too. I'll let you know what happens. I really appreciate all your help, thanks Carl.
You are very welcome. Here's hoping the new RAM does the trick!!
Got the new RAM. 8Gb of G.Skill. Working great so far. I'm away over Christmas so haven't memtested it or anything but I will when I get back in January. Fingers crossed it's good. Thanks for all the help guys and Happy Holidays!
Great news and you are very welcome. You have a wonderful Holiday season.
Hi guys! I just got back from Christmas break. Had a great time as I hadn't seen my family in 4 months! I hope you all had a good holiday too.
Unfortunately it's not quite a happy new year in computing though as I got a BSOD on the first startup today i.e. the first since before the holidays. I'll run some memtests and post the results. The drivers that crashed were atimpag.sys and dxg related. These have crashed before on my system.
Unfortunately it's not quite a happy new year in computing though as I got a BSOD on the first startup today i.e. the first since before the holidays. I'll run some memtests and post the results. The drivers that crashed were atimpag.sys and dxg related. These have crashed before on my system.
No memtests done yet but another 2 cold restarts and no BSOD. Fingers crossed it was a fluke! I'm still going to run the memtests though and will post results.
Another BSOD this morning. I've attached the dump files for the last 2 crashes.
�� Quote: Originally Posted by alderosa Another BSOD this morning. I've attached the dump files for the last 2 crashes.
STOP 0x116: VIDEO_TDR_ERROR troubleshooting
Code:
BugCheck 116, {fffffa8009a70010, fffff88003f6df94, 0, 2} Unable to load image \SystemRoot\system32\DRIVERS\atikmpag.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for atikmpag.sys *** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys Probably caused by : atikmpag.sys ( atikmpag+6f94 ) Hi, Alex, and welcome back. I am glad you had a good holiday and got to spend time with your family.
All of your drivers appear to be up to date. Good job with the drivers. As Yowan said both dumps are video card errors, bugcheck 116. Read the article in the link he posted. Take your video card out, make sure the slot is clean, and reseat it. Make sure the connections are secure.
If you get another BSOD, please run the JC Griff tool again and upload all of the newly generated files. Since you have made changes to your system - new RAM, updated BIOS, updated drivers - I would like to see the updated files. http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html.
There is the possibility that your RAM settings are not quite right. RAM can trigger all sorts of errors. Run Memtest again from a cold boot after your computer has been off for a while. Run it for at least seven passes with your RAM sticks and configurations as they are when you get your last BSOD. Depending on what Memtest shows, I will ask the hardware Gurus to take a look at this thread. We have some guys who are experts on RAM and RAM settings.
All of your drivers appear to be up to date. Good job with the drivers. As Yowan said both dumps are video card errors, bugcheck 116. Read the article in the link he posted. Take your video card out, make sure the slot is clean, and reseat it. Make sure the connections are secure.
If you get another BSOD, please run the JC Griff tool again and upload all of the newly generated files. Since you have made changes to your system - new RAM, updated BIOS, updated drivers - I would like to see the updated files. http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html.
There is the possibility that your RAM settings are not quite right. RAM can trigger all sorts of errors. Run Memtest again from a cold boot after your computer has been off for a while. Run it for at least seven passes with your RAM sticks and configurations as they are when you get your last BSOD. Depending on what Memtest shows, I will ask the hardware Gurus to take a look at this thread. We have some guys who are experts on RAM and RAM settings.
I just finished running memtests and everything checked out clean. As it was new RAM (to replace the last lot of dodgy stuff I had before Christmas) I ran tests on each stick and all the slots again just to be sure. It took a while but I guess it was worth it to try and rule defective RAM out as a cause of my problems.
As for RAM settings, the RAM I have is on the mobo compatibility list as tried and tested to work and is set with manufacturers recommended timings, voltages, etc. I'll get on trying trying the videocard stuff and see how that works out. I'll let you know. The video card I have works fine under load though (i.e. running games and movies) and doesn't crash. Weird huh?
I hope you guys all had a good weekend. Alex
As for RAM settings, the RAM I have is on the mobo compatibility list as tried and tested to work and is set with manufacturers recommended timings, voltages, etc. I'll get on trying trying the videocard stuff and see how that works out. I'll let you know. The video card I have works fine under load though (i.e. running games and movies) and doesn't crash. Weird huh?
I hope you guys all had a good weekend. Alex
Glad to know your RAM problem is cleared up. Now for the results of the video card stress test.
Hey guys, which stress tester should I use for my gfx card? I noticed that furmark seems to be for 32 bit (and vista). Is there a something else or a newer version? Should I try ATItool? I have an ATI card.
Use Furmark first and then the ATI tool. Compare the results. Furmark does fine with a 64 bit system.
I ran Furmark just now and had no problems after half an hour. The min temp was 45C and the max was 83C. I didn't notice any problems visually either. Was there anything else I should have been looking for?
Also, I haven't had a BSOD since the last time I posted about it (the 7th of this month).
Also, I haven't had a BSOD since the last time I posted about it (the 7th of this month).
That is good news about not having another BSOD! I hope that continues. Based on your Furmark report, you GPX adapter is probably OK.
I guess is it a matter of wait and see what my next BSOD is if/when I have one?
That about nails where we are.
I guess I'll post again when I next have a problem. Thanks to all of you who've helped up to now. It's been really good having someone who knows what they're doing telling what to do/where to look and trying to get this sorted out. Thanks again guys.
Alex
Alex
You are welcome, Alex. And we thank you for following suggestions and reporting back on what you have done.
So I had another BSOD on cold startup today. Looks to have been the same atimpag.sys fault. I've attached the files.
Yes, it is another bugcheck 116 blaming atimpag.sys. All of your drivers look to be up to date. I do not see anything that I suspect causing conflict. And your RAM and video card test out fine. I will recommend one more hardware test. Run Prime95 to test both your hardware and RAM. Follow the instructions carefully in this tutorial: http://www.sevenforums.com/tutorials...t-prime95.html. Run 3 separate tests, one on each of the settings (Blend, Small FFTs, Large FFTs). Post back with your results.
Code:
Windows 7 Kernel Version 7600 MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7600.16617.amd64fre.win7_gdr.100618-1621 Machine Name: Kernel base = 0xfffff800`0305a000 PsLoadedModuleList = 0xfffff800`03297e50 Debug session time: Fri Jan 14 12:23:34.979 2011 (GMT-5) System Uptime: 0 days 0:00:34.259 Loading Kernel Symbols ............................................................... ................................................................ ..................... Loading User Symbols Loading unloaded module list .... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 116, {fffffa8009ad3010, fffff88004006f94, 0, 2} *** WARNING: Unable to verify timestamp for atikmpag.sys *** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys Probably caused by : atikmpag.sys ( atikmpag+6f94 ) Followup: MachineOwner --------- 2: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* VIDEO_TDR_FAILURE (116) Attempt to reset the display driver and recover from timeout failed. Arguments: Arg1: fffffa8009ad3010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT). Arg2: fffff88004006f94, 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: ------------------ FAULTING_IP: atikmpag+6f94 fffff880`04006f94 4883ec28 sub rsp,28h DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_FAULT CUSTOMER_CRASH_COUNT: 1 BUGCHECK_STR: 0x116 PROCESS_NAME: System CURRENT_IRQL: 0 STACK_TEXT: fffff880`029c09c8 fffff880`042f0ef8 : 00000000`00000116 fffffa80`09ad3010 fffff880`04006f94 00000000`00000000 : nt!KeBugCheckEx fffff880`029c09d0 fffff880`042f0c02 : fffff880`04006f94 fffffa80`09ad3010 fffffa80`09157d50 fffffa80`06a43410 : dxgkrnl!TdrBugcheckOnTimeout+0xec fffff880`029c0a10 fffff880`04397f07 : fffffa80`09ad3010 00000000`00000000 fffffa80`09157d50 fffffa80`06a43410 : dxgkrnl!TdrIsRecoveryRequired+0x1a2 fffff880`029c0a40 fffff880`043c1b75 : 00000000`ffffffff 00000000`00000573 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b fffff880`029c0b20 fffff880`043c02bb : 00000000`00000102 00000000`00000000 00000000`00000573 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71 fffff880`029c0b50 fffff880`043932c6 : ffffffff`ff676980 fffffa80`06a43410 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb fffff880`029c0bf0 fffff880`043bfe7a : 00000000`00000000 fffffa80`09157d50 00000000`00000080 fffffa80`06a43410 : dxgmms1!VidSchiScheduleCommandToRun+0x1da fffff880`029c0d00 fffff800`0336ec06 : 00000000`044abdad fffffa80`090d2b60 fffffa80`06a0b040 fffffa80`090d2b60 : dxgmms1!VidSchiWorkerThread+0xba fffff880`029c0d40 fffff800`030a8c26 : fffff800`03244e80 fffffa80`090d2b60 fffff800`03252c40 00000000`00000000 : nt!PspSystemThreadStartup+0x5a fffff880`029c0d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16 STACK_COMMAND: .bugcheck ; kb FOLLOWUP_IP: atikmpag+6f94 fffff880`04006f94 4883ec28 sub rsp,28h SYMBOL_NAME: atikmpag+6f94 FOLLOWUP_NAME: MachineOwner MODULE_NAME: atikmpag IMAGE_NAME: atikmpag.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4ca29309 FAILURE_BUCKET_ID: X64_0x116_IMAGE_atikmpag.sys BUCKET_ID: X64_0x116_IMAGE_atikmpag.sys Followup: MachineOwner --------- 2: kd> lmtsmn start end module name fffff880`019b6000 fffff880`019f4000 1394ohci 1394ohci.sys Mon Jul 13 20:07:12 2009 (4A5BCC30) fffff880`00e00000 fffff880`00e57000 ACPI ACPI.sys Mon Jul 13 19:19:34 2009 (4A5BC106) fffff880`03e95000 fffff880`03f1f000 afd afd.sys Mon Jul 13 19:21:40 2009 (4A5BC184) fffff880`041dc000 fffff880`041f2000 AgileVpn AgileVpn.sys Mon Jul 13 20:10:24 2009 (4A5BCCF0) fffff880`041be000 fffff880`041d3000 amdppm amdppm.sys Mon Jul 13 19:19:25 2009 (4A5BC0FD) fffff880`00df3000 fffff880`00dfe000 amdxata amdxata.sys Tue May 19 13:56:59 2009 (4A12F2EB) fffff880`00eeb000 fffff880`00ef4000 atapi atapi.sys Mon Jul 13 19:19:47 2009 (4A5BC113) fffff880`00dc9000 fffff880`00df3000 ataport ataport.SYS Mon Jul 13 19:19:52 2009 (4A5BC118) fffff880`04819000 fffff880`04fef000 atikmdag atikmdag.sys Tue Sep 28 21:41:26 2010 (4CA29946) fffff880`04000000 fffff880`0404b000 atikmpag atikmpag.sys Tue Sep 28 21:14:49 2010 (4CA29309) fffff880`0186c000 fffff880`01874000 AtiPcie AtiPcie.sys Tue May 05 11:00:22 2009 (4A005486) fffff880`0190a000 fffff880`01911000 Beep Beep.SYS Mon Jul 13 20:00:13 2009 (4A5BCA8D) fffff880`04187000 fffff880`04198000 blbdrive blbdrive.sys Mon Jul 13 19:35:59 2009 (4A5BC4DF) fffff880`069e2000 fffff880`06a00000 bowser bowser.sys Mon Jul 13 19:23:50 2009 (4A5BC206) fffff960`00700000 fffff960`00727000 cdd cdd.dll unavailable (00000000) fffff880`018aa000 fffff880`018d4000 cdrom cdrom.sys Mon Jul 13 19:19:54 2009 (4A5BC11A) fffff880`00d09000 fffff880`00dc9000 CI CI.dll Mon Jul 13 21:32:13 2009 (4A5BE01D) fffff880`0183c000 fffff880`0186c000 CLASSPNP CLASSPNP.SYS Mon Jul 13 19:19:58 2009 (4A5BC11E) fffff880`00cab000 fffff880`00d09000 CLFS CLFS.SYS Mon Jul 13 19:19:57 2009 (4A5BC11D) fffff880`01152000 fffff880`011c5000 cng cng.sys Mon Jul 13 19:49:40 2009 (4A5BC814) fffff880`04800000 fffff880`04810000 CompositeBus CompositeBus.sys Mon Jul 13 20:00:33 2009 (4A5BCAA1) fffff880`06645000 fffff880`0664e000 cpuz134_x64 cpuz134_x64.sys Fri Jul 09 07:16:58 2010 (4C37052A) fffff880`068b9000 fffff880`068c7000 crashdmp crashdmp.sys Mon Jul 13 20:01:01 2009 (4A5BCABD) fffff880`040e6000 fffff880`04169000 csc csc.sys Mon Jul 13 19:24:26 2009 (4A5BC22A) fffff880`04169000 fffff880`04187000 dfsc dfsc.sys Mon Jul 13 19:23:44 2009 (4A5BC200) fffff880`03e68000 fffff880`03e77000 discache discache.sys Mon Jul 13 19:37:18 2009 (4A5BC52E) fffff880`013e3000 fffff880`013f9000 disk disk.sys Mon Jul 13 19:19:57 2009 (4A5BC11D) fffff880`0643e000 fffff880`06460000 drmk drmk.sys Mon Jul 13 21:01:25 2009 (4A5BD8E5) fffff880`068d3000 fffff880`068dc000 dump_atapi dump_atapi.sys Mon Jul 13 19:19:47 2009 (4A5BC113) fffff880`068c7000 fffff880`068d3000 dump_dumpata dump_dumpata.sys Mon Jul 13 19:19:47 2009 (4A5BC113) fffff880`068dc000 fffff880`068ef000 dump_dumpfve dump_dumpfve.sys Mon Jul 13 19:21:51 2009 (4A5BC18F) fffff880`068ad000 fffff880`068b9000 Dxapi Dxapi.sys Mon Jul 13 19:38:28 2009 (4A5BC574) fffff880`04294000 fffff880`04388000 dxgkrnl dxgkrnl.sys Thu Oct 01 21:00:14 2009 (4AC5509E) fffff880`04388000 fffff880`043ce000 dxgmms1 dxgmms1.sys Mon Jul 13 19:38:32 2009 (4A5BC578) fffff880`0404b000 fffff880`04081000 fastfat fastfat.SYS Mon Jul 13 19:23:28 2009 (4A5BC1F0) fffff880`010e0000 fffff880`010f4000 fileinfo fileinfo.sys Mon Jul 13 19:34:25 2009 (4A5BC481) fffff880`01094000 fffff880`010e0000 fltmgr fltmgr.sys Mon Jul 13 19:19:59 2009 (4A5BC11F) fffff880`013d0000 fffff880`013da000 Fs_Rec Fs_Rec.sys Mon Jul 13 19:19:45 2009 (4A5BC111) fffff880`011c5000 fffff880`011ff000 fvevol fvevol.sys Fri Sep 25 22:34:26 2009 (4ABD7DB2) fffff880`01584000 fffff880`015ce000 fwpkclnt fwpkclnt.sys Mon Jul 13 19:21:08 2009 (4A5BC164) fffff800`03011000 fffff800`0305a000 hal hal.dll Mon Jul 13 21:27:36 2009 (4A5BDF08) fffff880`043ce000 fffff880`043f2000 HDAudBus HDAudBus.sys Mon Jul 13 20:06:13 2009 (4A5BCBF5) fffff880`068fd000 fffff880`06916000 HIDCLASS HIDCLASS.SYS Mon Jul 13 20:06:21 2009 (4A5BCBFD) fffff880`06916000 fffff880`0691e080 HIDPARSE HIDPARSE.SYS Mon Jul 13 20:06:17 2009 (4A5BCBF9) fffff880`068ef000 fffff880`068fd000 hidusb hidusb.sys Mon Jul 13 20:06:22 2009 (4A5BCBFE) fffff880`06466000 fffff880`0652e000 HTTP HTTP.sys Mon Jul 13 19:22:16 2009 (4A5BC1A8) fffff880`013da000 fffff880`013e3000 hwpolicy hwpolicy.sys Mon Jul 13 19:19:22 2009 (4A5BC0FA) fffff880`00fab000 fffff880`00fcb000 jraid jraid.sys Wed Jan 27 03:58:17 2010 (4B600029) fffff880`050dc000 fffff880`050eb000 kbdclass kbdclass.sys Mon Jul 13 19:19:50 2009 (4A5BC116) fffff880`06934000 fffff880`06942000 kbdhid kbdhid.sys Mon Jul 13 20:00:20 2009 (4A5BCA94) fffff800`00bd2000 fffff800`00bdc000 kdcom kdcom.dll Mon Jul 13 21:31:07 2009 (4A5BDFDB) fffff880`050fc000 fffff880`0513f000 ks ks.sys Wed Mar 03 23:32:25 2010 (4B8F37D9) fffff880`013a5000 fffff880`013bf000 ksecdd ksecdd.sys Mon Jul 13 19:20:54 2009 (4A5BC156) fffff880`01559000 fffff880`01584000 ksecpkg ksecpkg.sys Fri Dec 11 01:03:32 2009 (4B21E0B4) fffff880`06460000 fffff880`06465200 ksthunk ksthunk.sys Mon Jul 13 20:00:19 2009 (4A5BCA93) fffff880`0691f000 fffff880`06934000 LHidFilt LHidFilt.Sys Tue Aug 24 13:21:36 2010 (4C73FFA0) fffff880`069b5000 fffff880`069ca000 lltdio lltdio.sys Mon Jul 13 20:08:50 2009 (4A5BCC92) fffff880`0694f000 fffff880`06963000 LMouFilt LMouFilt.Sys Tue Aug 24 13:21:43 2010 (4C73FFA7) fffff880`06971000 fffff880`06994000 luafv luafv.sys Mon Jul 13 19:26:13 2009 (4A5BC295) fffff880`00c8a000 fffff880`00c97000 mcupdate_AuthenticAMD mcupdate_AuthenticAMD.dll Mon Jul 13 21:29:09 2009 (4A5BDF65) fffff880`06963000 fffff880`06971000 monitor monitor.sys Mon Jul 13 19:38:52 2009 (4A5BC58C) fffff880`050eb000 fffff880`050fa000 mouclass mouclass.sys Mon Jul 13 19:19:50 2009 (4A5BC116) fffff880`06942000 fffff880`0694f000 mouhid mouhid.sys Mon Jul 13 20:00:20 2009 (4A5BCA94) fffff880`00c5c000 fffff880`00c76000 mountmgr mountmgr.sys Mon Jul 13 19:19:54 2009 (4A5BC11A) fffff880`018d4000 fffff880`01901000 MpFilter MpFilter.sys Sat Mar 20 01:58:08 2010 (4BA463F0) fffff880`06600000 fffff880`06618000 mpsdrv mpsdrv.sys Mon Jul 13 20:08:25 2009 (4A5BCC79) fffff880`06618000 fffff880`06645000 mrxsmb mrxsmb.sys Sat Feb 27 02:52:19 2010 (4B88CF33) fffff880`0652e000 fffff880`0657c000 mrxsmb10 mrxsmb10.sys Sat Feb 27 02:52:28 2010 (4B88CF3C) fffff880`0657c000 fffff880`0659f000 mrxsmb20 mrxsmb20.sys Sat Feb 27 02:52:26 2010 (4B88CF3A) fffff880`0196f000 fffff880`0197a000 Msfs Msfs.SYS Mon Jul 13 19:19:47 2009 (4A5BC113) fffff880`00e60000 fffff880`00e6a000 msisadrv msisadrv.sys Mon Jul 13 19:19:26 2009 (4A5BC0FE) fffff880`010f4000 fffff880`01152000 msrpc msrpc.sys Mon Jul 13 19:21:32 2009 (4A5BC17C) fffff880`03e5d000 fffff880`03e68000 mssmbios mssmbios.sys Mon Jul 13 19:31:10 2009 (4A5BC3BE) fffff880`015e6000 fffff880`015f8000 mup mup.sys Mon Jul 13 19:23:45 2009 (4A5BC201) fffff880`01407000 fffff880`014f9000 ndis ndis.sys Mon Jul 13 19:21:40 2009 (4A5BC184) fffff880`041f2000 fffff880`041fe000 ndistapi ndistapi.sys Mon Jul 13 20:10:00 2009 (4A5BCCD8) fffff880`0504c000 fffff880`0507b000 ndiswan ndiswan.sys Mon Jul 13 20:10:11 2009 (4A5BCCE3) fffff880`051c3000 fffff880`051d8000 NDProxy NDProxy.SYS Mon Jul 13 20:10:05 2009 (4A5BCCDD) fffff880`03f93000 fffff880`03fa2000 netbios netbios.sys Mon Jul 13 20:09:26 2009 (4A5BCCB6) fffff880`03f1f000 fffff880`03f64000 netbt netbt.sys Mon Jul 13 19:21:28 2009 (4A5BC178) fffff880`014f9000 fffff880`01559000 NETIO NETIO.SYS Mon Jul 13 19:21:46 2009 (4A5BC18A) fffff880`0197a000 fffff880`0198b000 Npfs Npfs.SYS Mon Jul 13 19:19:48 2009 (4A5BC114) fffff880`03e51000 fffff880`03e5d000 nsiproxy nsiproxy.sys Mon Jul 13 19:21:02 2009 (4A5BC15E) fffff800`0305a000 fffff800`03636000 nt ntkrnlmp.exe Sat Jun 19 00:16:41 2010 (4C1C44A9) fffff880`01202000 fffff880`013a5000 Ntfs Ntfs.sys Mon Jul 13 19:20:47 2009 (4A5BC14F) fffff880`01901000 fffff880`0190a000 Null Null.SYS Mon Jul 13 19:19:37 2009 (4A5BC109) fffff880`05151000 fffff880`05169000 nusb3hub nusb3hub.sys Thu Apr 22 21:34:35 2010 (4BD0F92B) fffff880`04200000 fffff880`04230000 nusb3xhc nusb3xhc.sys Thu Apr 22 21:34:36 2010 (4BD0F92C) fffff880`03f6d000 fffff880`03f93000 pacer pacer.sys Mon Jul 13 20:09:41 2009 (4A5BCCC5) fffff880`00eaa000 fffff880`00ebf000 partmgr partmgr.sys Mon Jul 13 19:19:58 2009 (4A5BC11E) fffff880`00e77000 fffff880`00eaa000 pci pci.sys Mon Jul 13 19:19:51 2009 (4A5BC117) fffff880`00ed4000 fffff880`00edb000 pciide pciide.sys Mon Jul 13 19:19:49 2009 (4A5BC115) fffff880`00edb000 fffff880`00eeb000 PCIIDEX PCIIDEX.SYS Mon Jul 13 19:19:48 2009 (4A5BC114) fffff880`013bf000 fffff880`013d0000 pcw pcw.sys Mon Jul 13 19:19:27 2009 (4A5BC0FF) fffff880`06e16000 fffff880`06ebc000 peauth peauth.sys Mon Jul 13 21:01:19 2009 (4A5BD8DF) fffff880`06401000 fffff880`0643e000 portcls portcls.sys Mon Jul 13 20:06:27 2009 (4A5BCC03) fffff880`00c97000 fffff880`00cab000 PSHED PSHED.dll Mon Jul 13 21:32:23 2009 (4A5BE027) fffff880`01800000 fffff880`01824000 rasl2tp rasl2tp.sys Mon Jul 13 20:10:11 2009 (4A5BCCE3) fffff880`0507b000 fffff880`05096000 raspppoe raspppoe.sys Mon Jul 13 20:10:17 2009 (4A5BCCE9) fffff880`05096000 fffff880`050b7000 raspptp raspptp.sys Mon Jul 13 20:10:18 2009 (4A5BCCEA) fffff880`050b7000 fffff880`050d1000 rassstp rassstp.sys Mon Jul 13 20:10:25 2009 (4A5BCCF1) fffff880`03e00000 fffff880`03e51000 rdbss rdbss.sys Mon Jul 13 19:24:09 2009 (4A5BC219) fffff880`050d1000 fffff880`050dc000 rdpbus rdpbus.sys Mon Jul 13 20:17:46 2009 (4A5BCEAA) fffff880`01954000 fffff880`0195d000 RDPCDD RDPCDD.sys Mon Jul 13 20:16:34 2009 (4A5BCE62) fffff880`0195d000 fffff880`01966000 rdpencdd rdpencdd.sys Mon Jul 13 20:16:34 2009 (4A5BCE62) fffff880`01966000 fffff880`0196f000 rdprefmp rdprefmp.sys Mon Jul 13 20:16:35 2009 (4A5BCE63) fffff880`0104c000 fffff880`01086000 rdyboost rdyboost.sys Mon Jul 13 19:34:34 2009 (4A5BC48A) fffff880`069ca000 fffff880`069e2000 rspndr rspndr.sys Mon Jul 13 20:08:50 2009 (4A5BCC92) fffff880`04232000 fffff880`04289000 Rt64win7 Rt64win7.sys Mon Mar 22 05:57:14 2010 (4BA73EFA) fffff880`05000000 fffff880`05036d80 RtHDMIVX RtHDMIVX.sys Tue Jan 26 22:04:58 2010 (4B5FAD5A) fffff880`06651000 fffff880`068acd80 RTKVHD64 RTKVHD64.sys Fri Sep 03 04:02:27 2010 (4C80AB93) fffff880`00fcb000 fffff880`00ffa000 SCSIPORT SCSIPORT.SYS Mon Jul 13 20:01:04 2009 (4A5BCAC0) fffff880`06ebc000 fffff880`06ec7000 secdrv secdrv.SYS Wed Sep 13 09:18:38 2006 (4508052E) fffff880`043f2000 fffff880`043fe000 serenum serenum.sys Mon Jul 13 20:00:33 2009 (4A5BCAA1) fffff880`03fa2000 fffff880`03fbf000 serial serial.sys Mon Jul 13 20:00:40 2009 (4A5BCAA8) fffff880`015de000 fffff880`015e6000 spldr spldr.sys Mon May 11 12:56:27 2009 (4A0858BB) fffff880`07c91000 fffff880`07d27000 srv srv.sys Thu Aug 26 23:38:00 2010 (4C773318) fffff880`06f06000 fffff880`06f6d000 srv2 srv2.sys Thu Aug 26 23:37:46 2010 (4C77330A) fffff880`06ec7000 fffff880`06ef4000 srvnet srvnet.sys Thu Aug 26 23:37:24 2010 (4C7732F4) fffff880`050fa000 fffff880`050fb480 swenum swenum.sys Mon Jul 13 20:00:18 2009 (4A5BCA92) fffff880`01601000 fffff880`017fe000 tcpip tcpip.sys Sun Jun 13 23:39:04 2010 (4C15A458) fffff880`06ef4000 fffff880`06f06000 tcpipreg tcpipreg.sys Mon Jul 13 20:09:49 2009 (4A5BCCCD) fffff880`019a9000 fffff880`019b6000 TDI TDI.SYS Mon Jul 13 19:21:18 2009 (4A5BC16E) fffff880`0198b000 fffff880`019a9000 tdx tdx.sys Mon Jul 13 19:21:15 2009 (4A5BC16B) fffff880`03fda000 fffff880`03fee000 termdd termdd.sys Mon Jul 13 20:16:36 2009 (4A5BCE64) fffff960`00510000 fffff960`0051a000 TSDDD TSDDD.dll unavailable (00000000) fffff880`04198000 fffff880`041be000 tunnel tunnel.sys Mon Jul 13 20:09:37 2009 (4A5BCCC1) fffff880`0513f000 fffff880`05151000 umbus umbus.sys Mon Jul 13 20:06:56 2009 (4A5BCC20) fffff880`04230000 fffff880`04231f00 USBD USBD.SYS Mon Jul 13 20:06:23 2009 (4A5BCBFF) fffff880`04fef000 fffff880`05000000 usbehci usbehci.sys Mon Jul 13 20:06:30 2009 (4A5BCC06) fffff880`05169000 fffff880`051c3000 usbhub usbhub.sys Mon Jul 13 20:07:09 2009 (4A5BCC2D) fffff880`04289000 fffff880`04294000 usbohci usbohci.sys Mon Jul 13 20:06:30 2009 (4A5BCC06) fffff880`04081000 fffff880`040d7000 USBPORT USBPORT.SYS Mon Jul 13 20:06:31 2009 (4A5BCC07) fffff880`00e6a000 fffff880`00e77000 vdrvroot vdrvroot.sys Mon Jul 13 20:01:31 2009 (4A5BCADB) fffff880`01911000 fffff880`0191f000 vga vga.sys Mon Jul 13 19:38:47 2009 (4A5BC587) fffff880`0191f000 fffff880`01944000 VIDEOPRT VIDEOPRT.SYS Mon Jul 13 19:38:51 2009 (4A5BC58B) fffff880`015ce000 fffff880`015de000 vmstorfl vmstorfl.sys Mon Jul 13 19:42:54 2009 (4A5BC67E) fffff880`00ebf000 fffff880`00ed4000 volmgr volmgr.sys Mon Jul 13 19:19:57 2009 (4A5BC11D) fffff880`00c00000 fffff880`00c5c000 volmgrx volmgrx.sys Mon Jul 13 19:20:33 2009 (4A5BC141) fffff880`01000000 fffff880`0104c000 volsnap volsnap.sys Mon Jul 13 19:20:08 2009 (4A5BC128) fffff880`03fbf000 fffff880`03fda000 wanarp wanarp.sys Mon Jul 13 20:10:21 2009 (4A5BCCED) fffff880`01944000 fffff880`01954000 watchdog watchdog.sys Mon Jul 13 19:37:35 2009 (4A5BC53F) fffff880`00ef8000 fffff880`00f9c000 Wdf01000 Wdf01000.sys Mon Jul 13 19:22:07 2009 (4A5BC19F) fffff880`00f9c000 fffff880`00fab000 WDFLDR WDFLDR.SYS Mon Jul 13 19:19:54 2009 (4A5BC11A) fffff880`03f64000 fffff880`03f6d000 wfplwf wfplwf.sys Mon Jul 13 20:09:26 2009 (4A5BCCB6) fffff960`00020000 fffff960`00330000 win32k win32k.sys unavailable (00000000) fffff880`041d3000 fffff880`041dc000 wmiacpi wmiacpi.sys Mon Jul 13 19:31:02 2009 (4A5BC3B6) fffff880`00e57000 fffff880`00e60000 WMILIB WMILIB.SYS Mon Jul 13 19:19:51 2009 (4A5BC117) fffff880`06994000 fffff880`069b5000 WudfPf WudfPf.sys Mon Jul 13 20:05:37 2009 (4A5BCBD1) Unloaded modules: fffff880`01874000 fffff880`01882000 crashdmp.sys Timestamp: unavailable (00000000) Checksum: 00000000 fffff880`01882000 fffff880`0188e000 dump_ataport Timestamp: unavailable (00000000) Checksum: 00000000 fffff880`0188e000 fffff880`01897000 dump_atapi.s Timestamp: unavailable (00000000) Checksum: 00000000 fffff880`01897000 fffff880`018aa000 dump_dumpfve Timestamp: unavailable (00000000) Checksum: 00000000 Hey all, I haven't had the chance to run the hardware tests yet (my research supervisor has really been kicking my ass to get some serious amounts of stuff done) but I have a had a couple more problems. They are all still display driver related.
I have had several screen crashes and then the computer refreshes and I get a message saying that the ATI display drivers crashed but recovered. I haven't had a BSOD as a result of this. Do you think I might have a faulty driver install and that I should try reinstalling the drivers when I get the chance? I wanted to mention this as I wasn't sure if it would give us a clue as to the source of the problem?
Thanks guys, hope you all had a good weekend.
Alex
I have had several screen crashes and then the computer refreshes and I get a message saying that the ATI display drivers crashed but recovered. I haven't had a BSOD as a result of this. Do you think I might have a faulty driver install and that I should try reinstalling the drivers when I get the chance? I wanted to mention this as I wasn't sure if it would give us a clue as to the source of the problem?
Thanks guys, hope you all had a good weekend.
Alex
Alex, I had similar problems with an nVida graphics card. I solved by experimenting with various drivers until I found the ones that worked. They were not the latest; they were third or fourth down the list.
Finally getting round to running Prime95 tests. I also reinstalled my ATI drivers. I haven't had a BSOD since I last reported one (a week or so back) but have had a fair few driver crashes which have managed to recover - all ATI driver related, this is even with the new install of drivers.
While running Prime95, core temp is currently below 60oC.
While running Prime95, core temp is currently below 60oC.
1st test (small FFT) ok.
So far, so good.
Small fft & large fft tests with prime95 both ran fine and gave no errors. The blend test is currently running and so far, so good. Core temps have been below 60oC in all tests. Does this mean that I'm most likely looking at a software issue rather than hardware? I would assume it's the ATI drivers as this is what's been throwing the errors every time (display driver related usually).
All Prime95 tests run and no errors.
Just found out that the new ATI drivers for my card (Radeon HD 6870) are out - released yesterday. I'll download these and install ASAP then post results i.e. do I still have crashes, etc. I'll also be sure to use driver sweeper when removing the old drivers. Fingers crossed this fixes the issue.
Any other thoughts at the moment? Especially related to the fact that Prime95 seemed to flag no errors?
Thanks, Alex
Any other thoughts at the moment? Especially related to the fact that Prime95 seemed to flag no errors?
Thanks, Alex
Prime showing no errors tells us your CPU and RAM are probably OK. Let's see if the new ATI drivers solve the problem.
New drivers installed last night. Fingers crossed guys!
My fingers, legs and toes are crossed! 
So far, no problems since I installed the new drivers. Let's hope it stays that way. Have a good weekend everyone.
Just had a display drivers crashed but responded error again 
That isn't what I was hoping to hear.
This is the only problem I've had in almost a week though and it was fairly minor. Still an issue though. I had gone out for a while so the PC was idle and then when I woke it up I got the driver error.
At least the system is running better.
Không có nhận xét nào:
Đăng nhận xét