Hi. . .
Sorry to hear that your Zepto-fixed system is still BSOD'ing.
I ran the 3 dumps -
0x7f (0x8, 0x80050033, 0x6f8, 0xfffff8000225b10f), probable cause listed as the Vista NT kernel
ntkrnlmp.exe. Process running at the time of crash = hl2.exe
0x7f = UNEXPECTED_KERNEL_MODE_TRAP - Intel CPU generated a trap and the kernel failed to catch it. The first parm = 0x8 = double fault - error occurred while system dealing with previous one. CPU had final say. 2 reasons for 0x7f w/ 0x8 (1) hardware; (2) kernel stack overflow - driver out of control.
0x3b (0xc0000005, 0xfffffa6002619b5d, 0xfffffa600cdc5e30, 0x0), probable cause = NVidia -
nvlddmkm.sys. Process running at the time of crash = hl2.exe
0x3b = SYSTEM_SERVICE_EXCEPTION - an exception happened while app moving from non-privileged code to kernel code. The exception is the first parm - 0xc0000005 - a memory access violation. Video fits here perfectly, specifically NVidia. Roll the drivers back to previous version.
0xf4 (0x3, 0xfffffa80060601d0, 0xfffffa8006060408, 0xfffff80002548e10), probable cause = Microsoft Client Server Runtime Sub System module
csrss.exe. It is also listed as the app running at BSOD time.
0xf4 = CRITICAL_OBJECT_TERMINATION - a system operation has unexpectedly stopped. hl2.exe brings gaming which brings video in here.
Assuming for the moment that your hardware platform is stable, I would look at the following items:
First - what are these?? I could find nothing on them at all. Do a system wide search, registry search & check device manager - enable hidden devices. Use SysInternals
AutoRuns from MS TechNet in the hunt also. Download the exe file to desktop, go to desktop, RIGHT-click on autoruns.exe and select Run as Administrator.
Code:
1: kd> lmvm aw2fxufq
start end module name
fffffa60`0247d000 fffffa60`024c1000 aw2fxufq T (no symbols)
Loaded symbol image file: aw2fxufq.SYS
Image path: \SystemRoot\System32\Drivers\aw2fxufq.SYS
Image name: aw2fxufq.SYS
Timestamp: Sun Jul 20 20:17:14 2008 (4883D58A)
CheckSum: 0004A3EC
ImageSize: 00044000
Translations: 0000.04b0 0000.04e0 0409.04b0 0409.04e0
fffffa60`03567000 fffffa60`035ab000 ab4dw3ix (deferred)
Image path: \SystemRoot\System32\Drivers\ab4dw3ix.SYS
Image name: ab4dw3ix.SYS
Timestamp: Sun Jul 20 20:17:14 2008 (4883D58A)
CheckSum: 0004A3EC
ImageSize: 00044000
Translations: 0000.04b0 0000.04e0 0409.04b0 0409.04e0
.
With a system so new and just back from the manufacturer, I was surprised to find Panda. Did you run it in addition to AVG? Is there any other a/v or firewall ? What is your installed a/v & firewall ?
Panda online scan
Image name:
pavboot64.sys
Thu Jun 19 11:23:50 2008
AVG online scanner
avgmfx64.sys - Thu Jun 26 11:20:11 2008
avgldx64.sys - Mon Jul 14 14:47:25 2008
.
Which NIC do you use = Ethernet or wifi ? Both were found in the loaded driver list and each needs updating:
NETw5v64.sys Wed May 21 07:44:58 2008
Rtlh64.sys Fri May 02 01:59:47 2008
Realtek RTL8168/8111 Family PCI-E Gigabit Ethernet NIC
Realtek had an update last week -
Realtek driver updates
The driver comes back to an Intel 5300 - updated last month -
Intel 5300 driver update.
.
AuthenTec Fingerprint scanner driver - this has caused quite a few problems in Vista x64 - check w/ manufacturer for updates:
Image name:
ATSwpDrv.sys
Timestamp: Mon Feb 05 17:25:24 2007
Check out WERCON (wercon.exe) - go down the list top-left of screen. What is it reporting? How about the Event Viewer (eventvwr.msc)?
As I mentioned, try the previous version of the NVidia drivers - I myself have not updated my GeForce 9600 MGT b/c of the problems (including BSODs) that I have seen. Mine are dated May 13, 2008 - v7.15.11.7553.
A summary of the bugchecks is below; dbug logs attached.
Regards. . .
jcgriff2
.
Code:
BugCheck 7F, {8, 80050033, 6f8, fffff8000225b10f}
Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b8 )
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
BugCheck 3B, {c0000005, fffffa6002619b5d, fffffa600cdc5e30, 0}
Probably caused by : nvlddmkm.sys ( nvlddmkm+cb5d )
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
BugCheck F4, {3, fffffa80060601d0, fffffa8006060408, fffff80002548e10}
Probably caused by : csrss.exe
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
.
Built by: 6001.18145.amd64fre.vistasp1_gdr.080917-1612
Debug session time: Sat Nov 8 17:34:01.656 2008 (GMT-5)
System Uptime: 0 days 6:02:57.824
BugCheck 7F, {8, 80050033, 6f8, fffff8000225b10f}
Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b8 )
PROCESS_NAME: hl2.exe
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Built by: 6001.18145.amd64fre.vistasp1_gdr.080917-1612
Debug session time: Sat Nov 8 17:46:38.430 2008 (GMT-5)
System Uptime: 0 days 0:05:11.563
BugCheck 3B, {c0000005, fffffa6002619b5d, fffffa600cdc5e30, 0}
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+cb5d )
PROCESS_NAME: hl2.exe
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Built by: 6001.18145.amd64fre.vistasp1_gdr.080917-1612
Debug session time: Sat Nov 8 18:19:51.885 2008 (GMT-5)
System Uptime: 0 days 0:01:21.510
BugCheck F4, {3, fffffa80060601d0, fffffa8006060408, fffff80002548e10}
Probably caused by : csrss.exe
PROCESS_NAME: csrss.exe
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=