New
#1
BSOD - Windows 7 64bit
Hi Guys,
My computer keeps on getting BSOD's every so often and I haven't been able to fix it.
Is there anything you could see that might be the cause?
I've attached the reports.
Thanks!
Hi Guys,
My computer keeps on getting BSOD's every so often and I haven't been able to fix it.
Is there anything you could see that might be the cause?
I've attached the reports.
Thanks!
Code:BugCheck C5, {22fd391, 2, 0, fffff80002bbf123} Probably caused by : tcpip.sys ( tcpip!TcpRestructureHashTable+53 )Run Driver Verifier to scan for any corrupted drivers which may be causing problems, this program works by running various stress tests on drivers, in order to produce a BSOD which will locate the driver; run for least 24 hours:Code:Usual causes: Device driver, Memory
Additional Help - Using Driver Verifier to identify issues with Drivers
Upload a .NFO file:
Start > Type: msinfo32 > File, Save
I've enabled driver verifier, will check to see what happens.
Cheers!
Please also upload a .NFO file, this is a System Information file, which give details about drivers, services and programs which you have installed on your system. It will not contain any Product Keys or personal information.
Hi guys,
I had another BSOD but for some reason it did not go into C:/Windows/Minidump so I can't show it.
I've also uploaded the .nfo file, thanks!
Make sure it a Minidump has been configured:
Reduce the number of programs at startup, to avoid any driver or program conflicts:
Update BIOS (if possible):
Update your System Specifications with Speccy, and then copy this information into your System Specifications: Go to your UserCP, and then select Edit System Spec in the left pane. Copy the information from Speccy into the required fields. These System Specifications will then follow your every post.Code:American Megatrends Inc. 0802, 24/08/2010
Hi, The BIOS is at the latest version already (that one).
Got another BSOD/dump as well.
Cheers for the help :)
Code:BugCheck 50, {ffffffff82e802cf, 1, fffff8800496ee95, 5} *** WARNING: Unable to verify timestamp for atikmdag.sys *** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys Could not read faulting driver name Probably caused by : atikmdag.sys ( atikmdag+158e95 )Your graphics driver seems to be causing some problems, roll back to the WHQL driver, by using these instructions:Code:2: kd> lmvm atikmdag start end module name fffff880`04816000 fffff880`05381000 atikmdag T (no symbols) Loaded symbol image file: atikmdag.sys Image path: \SystemRoot\system32\DRIVERS\atikmdag.sys Image name: atikmdag.sys Timestamp: Sat Feb 16 03:47:02 2013 (511F0136) CheckSum: 00B1F650 ImageSize: 00B6B000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
- Download Driver
- Start Type: Device Manager
- Expand Display Adapters
- Right-Click Driver Name, Uninstall
- Reboot
- Run Driver Sweeper
- Reboot
- Install Downloaded Driver
Driver Sweeper will scan for any left over files from the old driver, old driver files can cause conflicts with new driver installations. Create a System Restore point beforehand, in case any problems or issues arise.
Driver Sweeper:
I've installed the WHQL driver, will let you know if the issue is resolved!
Thanks :)
In theory, the latest WHQL driver, should be the most stable driver since it has been tested by Microsoft, but let's hope it's resolved the problem.