Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: Freshly Build Win7 -64bit Computer Blue Screens or freezes randomly.

06 Nov 2010   #1

Windows 7 Professional 64bit
 
 
Freshly Build Win7 -64bit Computer Blue Screens or freezes randomly.

I recently build my first computer, using these parts (not sure what you need to know).
Memory -*G.SKILL Ripjaws Series 8GB (2 x 4GB) 240-Pin DDR3 SDRAM DDR3 1333 (PC3 10666) Desktop Memory Model F3-10666CL9D-8GBRL
CPU - Phenom II X6 1090t black edition Thuban 3.2GHz*
PSU - Corsair CMPSU-850TX 850W atx 12v *
Graphics -*XFX HD-587X-ZNFC Radeon HD 5870 1GB 256-bit DDR5 X2 (crossfired)*
MOBO - *MSI 890FXA-GD70 AM3 AMD 890FX SATA 6Gb/s USB 3.0 ATX AMD Motherboard*
My Issue is that my computer BSOD's on a fairly frequent but random basis. Some days I'll have no problems and then other days my computer will crash several times. Most often its happening when I'm watching youtube videos but it does occasionally occur when my computer is just idle or when I'm looking at word documents. In the case of the youtube videos my computer will also sometimes appear to freeze. Sometimes it will recover, (saying that my ATI driver failed but recovered), other times it will stay frozen, and then sometimes it will crash.
I've looked at some other posts relating to things like this and it seems that many people have had problems with either memory or their video card. I've already tried a few things such as running windows 7 memory diagnostic on my computer (it doesn't find any errors in my memory), as well as updating to several versions of my graphics drivers (specifically the newest ones as well as some older more stable versions, 10.5 for example). After changing drivers I'm still not getting any success on my system.
Generally the BSOD's have a bcc code of either 1a, 1e, 3b, or 7e. I've looked at the dump files with BlueScreenView and to be totally honest I don't know what to make of them. I'm hoping someone here can help me out.
I've posted all the minidumps I believe are related to my problem on skydrive at this link
MemoryDumps - Windows Live

I'm not sure if you need any other information to help me out but if I'm missing something please let me know.

Thanks much

My System SpecsSystem Spec
.

06 Nov 2010   #2
Microsoft MVP

 
 

Please post the information from this post: http://www.sevenforums.com/crashes-d...tructions.html

IMO the BSOD errors tend to point at your video card - either the drivers or the video card itself. Have a look at this troubleshooting guide for STOP 0x116 errors: STOP 0x116: VIDEO_TDR_ERROR troubleshooting

I'd also try these free diagnostics in the event it's a memory issue or a video card/memory issue:
Quote:
I suggest starting all troubleshooting with the following diagnostic tests. They'll save you a lot of time and heartache if there is a hardware failure, and you'll have the disks on hand in case you need them in the future:
Quote:
H/W Diagnostics:
Please start by running these bootable hardware diagnostics:
Memory Diagnostics (read the details at the link)
HD Diagnostic (read the details at the link)

Also, please run one of these free, independent online malware scans to ensure that your current protection hasn't been compromised: Malware (read the details at the link)
Then, if the above tests pass, I'd try these free stress tests:
Quote:
FurMark download site: FurMark: VGA Stress Test, Graphics Card and GPU Stability Test, Burn-in Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net
FurMark Setup:
- If you have more than one GPU, select Multi-GPU during setup
- In the Run mode box, select "Stability Test" and "Log GPU Temperature"
Click "Go" to start the test
- Run the test until the GPU temperature maxes out - or until you start having problems (whichever comes first).
- Click "Quit" to exit
Quote:
Prime95 download site: Free Software - GIMPS
Prime95 Setup:
- extract the contents of the zip file to a location of your choice
- double click on the executable file
- select "Just stress testing"
- select the "Blend" test. If you've already run MemTest overnight you may want to run the "Small FFTs" test instead. (run all 3 if you find a problem and note how long it takes to error out with each)
- "Number of torture test threads to run" should equal the number of CPU's times 2 (if you're using hyperthreading).
The easiest way to figure this out is to go to Task Manager...Performance tab - and see the number of boxes under CPU Usage History
Then run the test for 6 to 24 hours - or until you get errors (whichever comes first).
This won't necessarily crash the system - but check the output in the test window for errors.
The Test selection box and the stress.txt file describes what components that the program stresses.
Quote:
Two other video stress tests (may be more stressful than FurMark):
Video Memory stress Test - лœл˜л NVIDIA / лБЛ‚лИл╗лИЛ‚Л‹ / VMT
Artifact Locator - лœл˜л NVIDIA / лБЛ‚лИл╗лИЛ‚Л‹ / Artifact Locator
Sorry, but I don't read the language that this website is made in.
BSOD BUGCHECK SUMMARY
Code:

Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Tue Oct  5 11:33:34.333 2010 (UTC - 4:00)
System Uptime: 0 days 0:06:40.315
Probably caused by : win32k.sys ( win32k!ValidateHwnd+89 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  dwm.exe
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff960`0017ab59 fffff880`05459120 00000000`00000000
ееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееее``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Tue Oct 12 17:35:42.667 2010 (UTC - 4:00)
System Uptime: 0 days 0:03:38.649
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
Probably caused by : atikmdag.sys ( atikmdag+12694 )
DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT
BUGCHECK_STR:  0x116
PROCESS_NAME:  System
Bugcheck code 00000116
Arguments fffffa80`076634e0 fffff880`0481e694 00000000`00000000 00000000`00000002
ееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееее``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Wed Oct 13 09:57:31.209 2010 (UTC - 4:00)
System Uptime: 0 days 15:01:25.551
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::UnmapVideoApertureSegmentInternal+be )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  dwm.exe
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff880`04dc322a fffff880`08328480 00000000`00000000
ееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееее``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Fri Oct 15 01:14:15.485 2010 (UTC - 4:00)
System Uptime: 1 days 13:15:42.467
Probably caused by : ntkrnlmp.exe ( nt!PspReturnQuota+47 )
DEFAULT_BUCKET_ID:  NULL_DEREFERENCE
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
Bugcheck code 1000007E
Arguments ffffffff`c0000005 fffff800`02c86597 fffff880`02fb5958 fffff880`02fb51c0
ееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееее``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Thu Oct 21 11:18:21.861 2010 (UTC - 4:00)
System Uptime: 5 days 8:45:14.203
Probably caused by : memory_corruption ( nt!MiFindNodeOrParent+0 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  svchost.exe
Bugcheck code 0000000A
Arguments 00000000`00000028 00000000`00000002 00000000`00000000 fffff800`02cc1518
ееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееее``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sat Oct 16 02:02:36.109 2010 (UTC - 4:00)
System Uptime: 0 days 0:25:09.436
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::UnmapVideoApertureSegmentInternal+be )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
Bugcheck code 1000007E
Arguments ffffffff`c0000005 fffff880`0462522a fffff880`039e13b8 fffff880`039e0c20
ееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееее``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sat Oct 23 14:55:58.830 2010 (UTC - 4:00)
System Uptime: 2 days 3:37:08.173
Probably caused by : win32k.sys ( win32k!xxxUpdateInputHangInfo+92 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  Steam.exe
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff960`000f4182 fffff880`09246040 00000000`00000000
ееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееее``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Wed Oct 27 00:06:03.929 2010 (UTC - 4:00)
System Uptime: 2 days 8:58:38.271
*** 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+667c )
DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT
BUGCHECK_STR:  0x116
PROCESS_NAME:  System
Bugcheck code 00000116
Arguments fffffa80`08074010 fffff880`0420667c 00000000`00000000 00000000`00000002
ееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееее``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Fri Oct 29 12:39:54.843 2010 (UTC - 4:00)
System Uptime: 0 days 18:41:28.825
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+13bb2 )
BUGCHECK_STR:  0x1a_41201
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  chrome.exe
Bugcheck code 0000001A
Arguments 00000000`00041201 fffff680`0005ee70 eb400001`64fb8867 fffffa80`073ae510
ееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееее``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sat Oct 30 17:23:47.133 2010 (UTC - 4:00)
System Uptime: 1 days 4:43:22.115
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+31ef2 )
BUGCHECK_STR:  0x1a_403
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  chrome.exe
Bugcheck code 0000001A
Arguments 00000000`00000403 fffff680`000e0d18 c7700001`3bc7c867 ff7ff680`000e0d18
ееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееее``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Tue Nov  2 17:13:34.973 2010 (UTC - 4:00)
System Uptime: 2 days 14:08:09.955
*** WARNING: Unable to verify timestamp for Rt64win7.sys
*** ERROR: Module load completed but symbols could not be loaded for Rt64win7.sys
Probably caused by : Rt64win7.sys ( Rt64win7+1667d )
BUGCHECK_STR:  0x1E_0
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
Bugcheck code 0000001E
Arguments 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000
ееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееее``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Fri Nov  5 12:10:58.872 2010 (UTC - 4:00)
System Uptime: 0 days 0:00:13.214
Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )
BUGCHECK_STR:  0x1E_0
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
Bugcheck code 0000001E
Arguments 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000
ееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееее``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Fri Nov  5 11:18:03.638 2010 (UTC - 4:00)
System Uptime: 0 days 17:14:18.604
Probably caused by : ntkrnlmp.exe ( nt!CmpKcbCacheLookup+1dd )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  SoftwareUpdate
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff800`031a474d fffff880`0b85d770 00000000`00000000
ееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееее``
  
  
My System SpecsSystem Spec
06 Nov 2010   #3

Windows 7 Professional 64bit
 
 

Thanks for the info, I've posted the requested files. If you find anything from it just let me know.

Also, as for the 116 error, i believe I only got that when trying to uninstall old graphics card drivers so that I could install new ones.
My System SpecsSystem Spec
.


07 Nov 2010   #4
Microsoft MVP

 
 

Perfmon reports an issue with your ATI sound card (likely to be built into your ATI video card). Please download fresh drivers, remove the current drivers, and install the fresh drivers.
Quote:
A device has reported a "Not OK" status.details:The device, ATI High Definition Audio Device, is reporting a bad status value. This device will not be available until the issue is resolved. The Plug and Play ID for this device is HDAUDIO\FUNC_01&VEN_1002&DEV_AA01&SUBSYS_00AA0100&REV_1002\5&2549FE13&0&0001.resolution:1. Verify the correct driver is installed.
2. Try updating the drivers using Windows Update.
3. Check with the manufacturer for an updated driver.
4. Attempt to uninstall and then reinstall the device using Device Manager.
Did it take approximately 2 weeks to remove the video drivers? Oct 12 and Oct 27 were the dates for the STOP 0x116 errors (there were other errors that involved the ATI video drivers also - 21 Sep and 09 Oct)
And, the BSOD error on 06 Nov was a STOP 0x116 also.

Please uninstall Catalyst Control Center. It has BSOD issues with some Windows 7 installations.

Please download fresh, Windows 7 compatible drivers for your Razer device(s), then remove the old drivers and install the fresh drivers. Some Razer drivers have BSOD issues with Windows 7 systems. If unable to find fresh, Windows 7 compatible drivers, please uninstall the software/drivers until we're finished troubleshooting.

14 memory dumps dated 05 Oct to 06 Nov (a month)
6 different BSOD error codes cited, with 6 different causes blamed.
This is almost certainly a hardware issue, and the most likely suspect is your video card.

Please follow the steps for troubleshooting STOP 0x116 errors here: STOP 0x116: VIDEO_TDR_ERROR troubleshooting
If that doesn't fix it, then you'll have to try another video card. If you don't have a spare, only purchase one that you can return (in case there is another cause - such as a bad video card slot).

Also, there was 1 error that blamed your network driver - so I'd suggest updating that also.
Your FLASHSYS64.sys driver dates from 2008 - it is an MSI driver file, most likely associated w/MSI Live Udpate. Please update it also.

These are all the errors (so some are repeats of those above):
BSOD BUGCHECK SUMMARY
Code:

Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sat Nov  6 18:56:36.022 2010 (UTC - 5:00)
System Uptime: 0 days 0:17:42.364
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
Probably caused by : atikmdag.sys ( atikmdag+12694 )
DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT
BUGCHECK_STR:  0x116
PROCESS_NAME:  System
Bugcheck code 00000116
Arguments fffffa80`077284e0 fffff880`08e7b694 00000000`00000000 00000000`00000002
ееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееее``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Fri Nov  5 11:10:58.872 2010 (UTC - 5:00)
System Uptime: 0 days 0:00:13.214
Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )
BUGCHECK_STR:  0x1E_0
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
Bugcheck code 0000001E
Arguments 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000
ееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееее``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Fri Nov  5 10:18:03.638 2010 (UTC - 5:00)
System Uptime: 0 days 17:14:18.604
Probably caused by : ntkrnlmp.exe ( nt!CmpKcbCacheLookup+1dd )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  SoftwareUpdate
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff800`031a474d fffff880`0b85d770 00000000`00000000
ееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееее``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Tue Nov  2 16:13:34.973 2010 (UTC - 5:00)
System Uptime: 2 days 14:08:09.955
*** WARNING: Unable to verify timestamp for Rt64win7.sys
*** ERROR: Module load completed but symbols could not be loaded for Rt64win7.sys
Probably caused by : Rt64win7.sys ( Rt64win7+1667d )
BUGCHECK_STR:  0x1E_0
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
Bugcheck code 0000001E
Arguments 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000
ееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееее``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sat Oct 30 16:23:47.133 2010 (UTC - 5:00)
System Uptime: 1 days 4:43:22.115
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+31ef2 )
BUGCHECK_STR:  0x1a_403
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  chrome.exe
Bugcheck code 0000001A
Arguments 00000000`00000403 fffff680`000e0d18 c7700001`3bc7c867 ff7ff680`000e0d18
ееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееее``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Fri Oct 29 11:39:54.843 2010 (UTC - 5:00)
System Uptime: 0 days 18:41:28.825
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+13bb2 )
BUGCHECK_STR:  0x1a_41201
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  chrome.exe
Bugcheck code 0000001A
Arguments 00000000`00041201 fffff680`0005ee70 eb400001`64fb8867 fffffa80`073ae510
ееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееее``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Tue Oct 26 23:06:03.929 2010 (UTC - 5:00)
System Uptime: 2 days 8:58:38.271
*** 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+667c )
DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT
BUGCHECK_STR:  0x116
PROCESS_NAME:  System
Bugcheck code 00000116
Arguments fffffa80`08074010 fffff880`0420667c 00000000`00000000 00000000`00000002
ееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееее``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sat Oct 23 13:55:58.830 2010 (UTC - 5:00)
System Uptime: 2 days 3:37:08.173
Probably caused by : win32k.sys ( win32k!xxxUpdateInputHangInfo+92 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  Steam.exe
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff960`000f4182 fffff880`09246040 00000000`00000000
ееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееее``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Thu Oct 21 10:18:21.861 2010 (UTC - 5:00)
System Uptime: 5 days 8:45:14.203
Probably caused by : memory_corruption ( nt!MiFindNodeOrParent+0 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  svchost.exe
Bugcheck code 0000000A
Arguments 00000000`00000028 00000000`00000002 00000000`00000000 fffff800`02cc1518
ееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееее``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sat Oct 16 01:02:36.109 2010 (UTC - 5:00)
System Uptime: 0 days 0:25:09.436
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::UnmapVideoApertureSegmentInternal+be )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
Bugcheck code 1000007E
Arguments ffffffff`c0000005 fffff880`0462522a fffff880`039e13b8 fffff880`039e0c20
ееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееее``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Fri Oct 15 00:14:15.485 2010 (UTC - 5:00)
System Uptime: 1 days 13:15:42.467
Probably caused by : ntkrnlmp.exe ( nt!PspReturnQuota+47 )
DEFAULT_BUCKET_ID:  NULL_DEREFERENCE
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
Bugcheck code 1000007E
Arguments ffffffff`c0000005 fffff800`02c86597 fffff880`02fb5958 fffff880`02fb51c0
ееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееее``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Wed Oct 13 08:57:31.209 2010 (UTC - 5:00)
System Uptime: 0 days 15:01:25.551
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::UnmapVideoApertureSegmentInternal+be )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  dwm.exe
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff880`04dc322a fffff880`08328480 00000000`00000000
ееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееее``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Tue Oct 12 16:35:42.667 2010 (UTC - 5:00)
System Uptime: 0 days 0:03:38.649
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
Probably caused by : atikmdag.sys ( atikmdag+12694 )
DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT
BUGCHECK_STR:  0x116
PROCESS_NAME:  System
Bugcheck code 00000116
Arguments fffffa80`076634e0 fffff880`0481e694 00000000`00000000 00000000`00000002
ееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееее``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Tue Oct  5 10:33:34.333 2010 (UTC - 5:00)
System Uptime: 0 days 0:06:40.315
Probably caused by : win32k.sys ( win32k!ValidateHwnd+89 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  dwm.exe
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff960`0017ab59 fffff880`05459120 00000000`00000000
ееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееееее``
  
  
My System SpecsSystem Spec
08 Nov 2010   #5

Windows 7 Professional 64bit
 
 

No, it didn't take two weeks to uninstall the drivers. Those were separate instances. Normally I'd get the 116 when I tried to uninstall the drivers, however the uninstall would go through clean but then, when the screen was flickering and cycling through resolutions it would die. I would restart my computer and find that the drivers had uninstalled successfully. It was as if the card was trying to reset itself and was unable to do so.

Are the sound drivers (since I don't have a sound card) simply updated when I update the drivers for my graphics card, Or do I need to do that separately.

If I uninstall catalyst is there any way to get the same functionality and data that CCC provided me with through another means.

Also, something of note. I had this problem

http://forums.amd.com/game/messagevi...VIEWTMP=Linear

with my grapics card after I had just bought it. I followed the instructions in the last post and it fixed my error. Not sure if that could be part of the problem.
My System SpecsSystem Spec
08 Nov 2010   #6

Windows 7 Professional 64bit
 
 

Also, I've run furmark for half an hour (temp maxed at 84c about half way through and didn't go above), and memtest for several passes and neither came up with any problems.
My System SpecsSystem Spec
08 Nov 2010   #7
Microsoft MVP

 
 

Just posted suggestions in this thread: Newly Built Win7 -64bit Computer Blue Screens or freezes randomly. - Tech Support Forum

Quote:
Yes, if you uninstall CCC you can install the most recent version available AFTER we finish troubleshooting.

If you are overclocking, remove all overclocks while we're testing.
If the green pixels come back, I'd suggest putting up with them until we're finished troubleshooting.

Our troubleshooting procedures rely on stock system values in order to provide reliable results - overclocks tend to mess up those results, so a stock system is essential for troubleshooting.

After we've got everything running well at stock values, then resume the overclock and see if there's any further issues. If so, we'll figure out something for them.
I'd imagine that updating the video drivers would update the sound function of the card. But the only way to tell is to update the video drivers and see what happens. Please check in Device Manager to see if the sound device is listed there. That way when you update the drivers you'll have a place to check it. If not, check in the Problem Devices section of MSINFO32.
My System SpecsSystem Spec
11 Nov 2010   #8

Windows 7 Professional 64bit
 
 

Posted in the other thread:

Quote:
Ok, I'm running prime 95 right now, so far no errors. I had another blue screen today (It was before I had uninstalled ccc). I posted the dump here (Do I need to resubmit all of the required files again?). http://cid-886d8b61508d8613.office.l...0-19500-01.dmp

I've just unistalled CCC, and removed the adjustments to the video cards.
I was browsing the internet when this occured btw
EDIT: ran prime95 all last night, it ran for over 6 hours, no problems
My System SpecsSystem Spec
Reply

 Freshly Build Win7 -64bit Computer Blue Screens or freezes randomly.




Thread Tools



Similar help and support threads for2: Freshly Build Win7 -64bit Computer Blue Screens or freezes randomly.
Thread Forum
Computer randomly blue screens BSOD Help and Support
Freshly installed OS win7 64bit taking 30 seconds at Welcome screen General Discussion
Blue Screens and Freezes still going on randomly BSOD Help and Support
Computer Randomly Freezes New Build - Ongoing Problem BSOD Help and Support
Random Blue Screens on fresh(er) Computer Build BSOD Help and Support
Blue Screens happening randomly BSOD Help and Support
Daily Daily Blue Screens on win7 64bit BSOD Help and Support

Our Sites

Site Links

About Us

Find 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 07:55 PM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33