Hi Djlaquest
I'm sorry to let you know that this might be a hardware problem. Based on the information collected from the dmp files, hardware was blamed though I didnt see specific piece of hardware blamed. Right now, I'm doubting the graphic card and the RAM
As you mentioned, you already done re-installing the graphic card driver, therefore we will go straight to graphic card stress test
Try this free video stress test:
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
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.
The following drivers are out of date and need to be updated right away:
Code:
L1C62x64 L1C62x64.sys Tue Mar 31 23:09:17 2009 (49D2F6FD)
This is Atheros NIC driver
If you are using laptop, perhaps you can go to the laptop vendor to update this driver. Otherwise, you can use some program such as Everest to identify what specific model of what Atheros NIC driver is (perhaps is ethernet or wireless card)
BUGCHECK SUMMARY:
Code:
BugCheck 3B, {c0000005, fffff960000a493b, fffff88005fc30b0, 0}
Probably caused by : win32k.sys ( win32k!InternalRebuildHwndListForIMEClass+9b )
Followup: MachineOwner
---------
BugCheck D1, {fffffa800ef5bbf8, 2, 1, fffff8800494f32e}
Unable to load image \SystemRoot\system32\DRIVERS\atikmdag.sys, Win32 error 0n2
*** 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+ac32e )
Followup: MachineOwner
---------
BugCheck 124, {0, fffffa80034b08f8, 0, 0}
Probably caused by : hardware
Followup: MachineOwner
---------
BugCheck 1000007E, {ffffffffc0000005, fffff80002cf04c5, fffff88002f856e8, fffff88002f84f50}
Probably caused by : ntkrnlmp.exe ( nt!FsRtlLookupPerFileObjectContext+a5 )
Followup: MachineOwner
---------
This can be a overheating problem, so please keep an eye on your system temps using speedfan
SpeedFan - Access temperature sensor in your computer
or using HWmonitor
CPUID - System & hardware benchmark, monitoring, reporting
Best regard,
Tuan