New
#21
The crash your looking for is a actual BSOD.
The crash your looking for is a actual BSOD.
Code:BugCheck 3B, {c0000005, fffff8000394f51b, fffff88007aabe40, 0} Probably caused by : ntkrnlmp.exe ( nt!ViZwCheckObjectAttributes+b )Your graphics driver seem to likely to be contributing to the crashes, and may explain the white lines on the screen when running Driver Verifier:Code:Usual causes: System service, Device driver, graphics driver, memory
Update with the latest WHQL driver which is available to download from here - Latest AMD Catalyst Video Driver for Windows 7Code:0: kd> lmvm atikmdag start end module name fffff880`05652000 fffff880`06168000 atikmdag T (no symbols) Loaded symbol image file: atikmdag.sys Image path: \SystemRoot\system32\DRIVERS\atikmdag.sys Image name: atikmdag.sys Timestamp: Wed Dec 19 20:38:55 2012 (50D225DF) CheckSum: 00AC6529 ImageSize: 00B16000 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:
Okay I uninstalled via device manager, rebooted, ran driver sweeper, clicked on AMD Display and clicked clean, rebooted and ran the installer for the driver 13.5 beta, rebooted and it took effect.
I do have a few concerns/things worth noting though:
-When I ran driver sweeper, it showed nvidea drivers (chipset, display, and Physx) which I thought was weird as I have no Nvidea hardware
-I quickly checked driver sweeper after reboot and it still showed two drivers under AMD-Display. I didn't touch them, wasn't sure if they needed to be cleaned as well
-After the driver installer installed it said warnings occurred during installation, however it also said it was successful.
The other entries are just default, and could you post a screenshot of your Device Manager with the Display section expanded:
Okay I am pretty sure I did something wrong as I got another BSOD. I included the screenshot and the SF tool file just in case.
There's only one entry for your graphics card which is normal and no warning triangles next to any of the drivers which is another good point.
Code:BugCheck 109, {a3a039d899271816, b3b7465eeba3e76c, fffff800034cb3fc, 1} *** WARNING: Unable to verify timestamp for win32k.sys *** ERROR: Module load completed but symbols could not be loaded for win32k.sys Probably caused by : memory_corruptionmemory_corruption doesn't necessary mean that a RAM module is faulty, it can also point to a object which corrupted the RAM at the time of the crash, for instance a corrupted driver or program. Paging files and the CPU caches can also be causes.Code:Usual causes: Device driver, Breakpoint set with no debugger attached, Hardware (Memory in particular)
It's best to install the WHQL driver not the Beta driver for the graphics card.
-----------------------------------------------------
Run some hard-drive diagnostics and follow these steps:
Find your hard-drive manufacturer and run their tests.
Additional Tests:
Post a screenshot of Crystal Disk Info summary:
Check for any file system errors and bad sectors using Option #2 of:writhziden said:
Use this command with Disk Check:
Code:chkdsk C: /f /r
Here's a Windows version of Seagate Tools - SeaTools for Windows | Seagate
For the chkdsk results, you can check here and then upload the file - Check Disk (chkdsk) - Read Event Viewer Log
The Crystal Disk Info screenshot seems to be fine, however, this only gives the S.M.A.R.T values, but is a positive sign so far.
Could you also upload the new BSOD?