BSOD while playing games

[dannyguitar]

Hi there,

i have some serious problems with my pc and i hope you guys can help me out.
but before i start i have to apologize for my bad english cause i´m german.

i experienced a few bsods since i started gaming on my pc a few weeks ago. i bought a new graphicscard and a new power supply. when i start the game it lasts a few minutes sometimes an hour until i got the bsod.
i checked bluescreenview and in 5 from 6 cases it blames ntoskrnl.exe as the problem. the other cause would be nvlddmkm.sys.

i updated all nvidia drivers for the graphics and the win 7 directx. since then it seems getting better, because bsods don´t happen that fast anymore.
sfc /scannow does not report anything bad.
i dont´t think its an overheating issue, cause my gpu does not get over 76 degrees.
i just played two games since i started gaming, both over steam. metro 2033 and half life 2. i wondered if it might be a prob with steam???

i attached the health report and the dumpfiles, i hope i did not forget anything.
any help would be appreciated.

my system specs:

Windows 7 Home Premium 64bit (OEM disk from retailer that i installed myself/system was originally vista 64bit)
Intel Core 2 Quad Q6600 @ 2,4GHZ
mainboard: ECS GF7100PVT-M3
graphic: Palit GeForce GTX-460 Sonic (OC)
sound: onBoard
psu: Corsair 550W

i bought the pc in august 2008

 

[usasma]

Issues with your Bluetooth:

Bluetooth-Peripheriegerät    BTHENUM\{00000002-0000-1000-8000-0002EE000002}_VID&00010001_PID&006E\7&181F6A28&0&EC9B5BE74F2E_C00000000    Die Treiber für dieses Gerät wurden nicht installiert.

Bluetooth-Peripheriegerät    BTHENUM\{00005557-0000-1000-8000-0002EE000001}_VID&00010001_PID&006E\7&181F6A28&0&EC9B5BE74F2E_C00000000    Die Treiber für dieses Gerät wurden nicht installiert.

Bluetooth-Peripheriegerät    BTHENUM\{00005601-0000-1000-8000-0002EE000001}_VID&00010001_PID&006E\7&181F6A28&0&EC9B5BE74F2E_C00000000    Die Treiber für dieses Gerät wurden nicht installiert.

Bluetooth-Peripheriegerät    BTHENUM\{0000111B-0000-1000-8000-00805F9B34FB}_VID&00010001_PID&006E\7&181F6A28&0&EC9B5BE74F2E_C00000000    Die Treiber für dieses Gerät wurden nicht installiert.

Bluetooth-Peripheriegerät    BTHENUM\{00005005-0000-1000-8000-0002EE000001}_VID&00010001_PID&006E\7&181F6A28&0&EC9B5BE74F2E_C00000000    Die Treiber für dieses Gerät wurden nicht installiert.

Please install these drivers immediately.

Please stop the MacDrive stuff from starting when the system starts (just a hunch on my part).

Please update your nVidia chipset drivers (nForce) - http://www.nvidia.com/object/nforce_vista_win7_64bit_15.49.html

All but one of the memory dumps are attributed to the OS kernel (not a likely cause). As such, please run Driver Verifier according to these directions:

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
NOTE: You can use Low Resource Simulation if you'd like. From my limited experimentation it makes the BSOD's come faster.
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

If that doesn't work, post back and we'll have to see about fixing the registry entry off-line:

Delete these registry keys (works in XP, Vista, Win7):
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDrivers
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDriverLevel

More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users

BSOD BUGCHECK SUMMARY

[FONT=lucida console]
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Sep 20 18:20:06.395 2010 (UTC - 4:00)
System Uptime: 0 days 0:55:08.330
BugCheck D1, {0, 2, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )
PROCESS_NAME:  hl2.exe
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
Bugcheck code 000000D1
Arguments 00000000`00000000 00000000`00000002 00000000`00000000 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Sep 20 07:04:53.659 2010 (UTC - 4:00)
System Uptime: 0 days 0:16:42.984
BugCheck D1, {0, 2, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )
PROCESS_NAME:  hl2.exe
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
Bugcheck code 000000D1
Arguments 00000000`00000000 00000000`00000002 00000000`00000000 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sun Sep 19 12:32:19.071 2010 (UTC - 4:00)
System Uptime: 0 days 0:50:47.397
BugCheck D1, {c0000102, 2, 1, fffff8a00af58017}
Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME:  hl2.exe
Bugcheck code 000000D1
Arguments 00000000`c0000102 00000000`00000002 00000000`00000001 fffff8a0`0af58017
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sat Sep 18 07:34:10.654 2010 (UTC - 4:00)
System Uptime: 0 days 0:46:33.589
BugCheck D1, {0, 2, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )
PROCESS_NAME:  audiodg.exe
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
Bugcheck code 000000D1
Arguments 00000000`00000000 00000000`00000002 00000000`00000000 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Wed Sep 15 18:55:27.470 2010 (UTC - 4:00)
System Uptime: 0 days 0:49:48.405
BugCheck D1, {0, 2, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )
PROCESS_NAME:  metro2033.exe
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
Bugcheck code 000000D1
Arguments 00000000`00000000 00000000`00000002 00000000`00000000 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Wed Sep 15 18:05:00.258 2010 (UTC - 4:00)
System Uptime: 0 days 0:04:50.583
Probably caused by : ntkrnlmp.exe ( nt!KiSwapContext+7a )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  metro2033.exe
Bugcheck code 0000003B
Arguments 00000000`c000001d fffff880`04744000 fffff880`04743630 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Wed Sep 15 17:59:16.998 2010 (UTC - 4:00)
System Uptime: 0 days 4:52:58.323
BugCheck D1, {200, 2, 0, 200}
Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )
PROCESS_NAME:  svchost.exe
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
Bugcheck code 000000D1
Arguments 00000000`00000200 00000000`00000002 00000000`00000000 00000000`00000200
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Tue Sep 14 20:56:48.416 2010 (UTC - 4:00)
System Uptime: 0 days 0:18:59.741
BugCheck D1, {c0000102, 2, 1, fffff8a00ba98017}
Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME:  metro2033.exe
Bugcheck code 000000D1
Arguments 00000000`c0000102 00000000`00000002 00000000`00000001 fffff8a0`0ba98017
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Tue Sep 14 20:37:11.319 2010 (UTC - 4:00)
System Uptime: 0 days 0:12:29.644
BugCheck D1, {0, 2, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )
PROCESS_NAME:  audiodg.exe
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
Bugcheck code 000000D1
Arguments 00000000`00000000 00000000`00000002 00000000`00000000 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Tue Sep 14 18:06:51.995 2010 (UTC - 4:00)
System Uptime: 0 days 2:52:47.320
Probably caused by : ntkrnlmp.exe ( nt!KiInitialPCR+18e )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  metro2033.exe
Bugcheck code 0000003B
Arguments 00000000`c000001d fffff800`031fce8e fffff880`04d77630 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Tue Sep 14 15:04:53.059 2010 (UTC - 4:00)
System Uptime: 0 days 0:57:47.385
BugCheck D1, {0, 2, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )
PROCESS_NAME:  metro2033.exe
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
Bugcheck code 000000D1
Arguments 00000000`00000000 00000000`00000002 00000000`00000000 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Tue Sep 14 11:31:26.640 2010 (UTC - 4:00)
System Uptime: 0 days 2:17:59.966
BugCheck D1, {0, 2, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )
PROCESS_NAME:  Steam.exe
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
Bugcheck code 000000D1
Arguments 00000000`00000000 00000000`00000002 00000000`00000000 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Tue Sep 14 08:16:17.888 2010 (UTC - 4:00)
System Uptime: 0 days 0:14:24.214
Probably caused by : ntkrnlmp.exe ( nt!KiSwapContext+7a )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  metro2033.exe
Bugcheck code 0000003B
Arguments 00000000`c000001d fffff880`07718000 fffff880`07717630 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Tue Sep 14 07:01:50.710 2010 (UTC - 4:00)
System Uptime: 0 days 0:15:32.035
BugCheck D1, {c0000102, 2, 1, fffff8a009940017}
Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME:  metro2033.exe
Bugcheck code 000000D1
Arguments 00000000`c0000102 00000000`00000002 00000000`00000001 fffff8a0`09940017
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Sep 13 19:12:00.458 2010 (UTC - 4:00)
System Uptime: 0 days 0:27:48.393
BugCheck D1, {c0000102, 2, 1, fffff8a00cbcb017}
Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME:  hl2.exe
Bugcheck code 000000D1
Arguments 00000000`c0000102 00000000`00000002 00000000`00000001 fffff8a0`0cbcb017
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Sep 13 16:46:03.131 2010 (UTC - 4:00)
System Uptime: 0 days 0:44:18.456
BugCheck D1, {0, 2, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )
PROCESS_NAME:  Steam.exe
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
Bugcheck code 000000D1
Arguments 00000000`00000000 00000000`00000002 00000000`00000000 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Sep 13 09:32:26.605 2010 (UTC - 4:00)
System Uptime: 0 days 0:16:37.930
Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceHandler+7c )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  metro2033.exe
Bugcheck code 0000003B
Arguments 00000000`c000001d fffffa80`03b1470a fffff880`07e45620 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Sep 13 08:24:46.677 2010 (UTC - 4:00)
System Uptime: 0 days 0:33:07.003
BugCheck D1, {0, 2, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )
PROCESS_NAME:  metro2033.exe
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
Bugcheck code 000000D1
Arguments 00000000`00000000 00000000`00000002 00000000`00000000 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sun Sep 12 18:45:04.574 2010 (UTC - 4:00)
System Uptime: 0 days 0:43:01.900
BugCheck D1, {0, 2, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )
PROCESS_NAME:  Steam.exe
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
Bugcheck code 000000D1
Arguments 00000000`00000000 00000000`00000002 00000000`00000000 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sun Sep 12 07:14:42.679 2010 (UTC - 4:00)
System Uptime: 0 days 0:31:35.614
BugCheck D1, {0, 2, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )
PROCESS_NAME:  metro2033.exe
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
Bugcheck code 000000D1
Arguments 00000000`00000000 00000000`00000002 00000000`00000000 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sat Sep 11 18:53:36.839 2010 (UTC - 4:00)
System Uptime: 0 days 0:10:59.165
BugCheck D1, {0, 2, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )
PROCESS_NAME:  metro2033.exe
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
Bugcheck code 000000D1
Arguments 00000000`00000000 00000000`00000002 00000000`00000000 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sat Sep 11 18:41:32.570 2010 (UTC - 4:00)
System Uptime: 0 days 0:13:37.226
BugCheck D1, {28f012b700, 2, 0, 28f012b700}
Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )
PROCESS_NAME:  metro2033.exe
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
Bugcheck code 000000D1
Arguments 00000028`f012b700 00000000`00000002 00000000`00000000 00000028`f012b700
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sat Sep 11 10:52:44.135 2010 (UTC - 4:00)
System Uptime: 0 days 0:28:44.461
BugCheck D1, {0, 2, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )
PROCESS_NAME:  metro2033.exe
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
Bugcheck code 000000D1
Arguments 00000000`00000000 00000000`00000002 00000000`00000000 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sat Sep 11 10:17:57.055 2010 (UTC - 4:00)
System Uptime: 0 days 0:36:18.380
BugCheck D1, {0, 2, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )
PROCESS_NAME:  audiodg.exe
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
Bugcheck code 000000D1
Arguments 00000000`00000000 00000000`00000002 00000000`00000000 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sat Sep 11 09:41:01.750 2010 (UTC - 4:00)
System Uptime: 0 days 0:26:42.076
Probably caused by : ntkrnlmp.exe ( nt!KiSwapContext+7a )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  metro2033.exe
Bugcheck code 0000003B
Arguments 00000000`c000001d fffff880`047b8000 fffff880`047b7630 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sat Sep 11 09:13:12.012 2010 (UTC - 4:00)
System Uptime: 0 days 3:13:06.338
BugCheck D1, {0, 2, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )
PROCESS_NAME:  metro2033.exe
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
Bugcheck code 000000D1
Arguments 00000000`00000000 00000000`00000002 00000000`00000000 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Fri Sep 10 13:33:46.008 2010 (UTC - 4:00)
System Uptime: 0 days 0:09:39.334
Probably caused by : ntkrnlmp.exe ( nt!KiSwapContext+7a )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  metro2033.exe
Bugcheck code 0000003B
Arguments 00000000`c000001d fffff880`08504000 fffff880`08503630 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Fri Sep 10 13:23:29.282 2010 (UTC - 4:00)
System Uptime: 0 days 0:08:31.607
BugCheck D1, {c0000102, 2, 1, fffff8a00411e017}
Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME:  metro2033.exe
Bugcheck code 000000D1
Arguments 00000000`c0000102 00000000`00000002 00000000`00000001 fffff8a0`0411e017
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Thu Sep  9 18:35:30.090 2010 (UTC - 4:00)
System Uptime: 0 days 0:19:30.416
BugCheck D1, {0, 2, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )
PROCESS_NAME:  metro2033.exe
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
Bugcheck code 000000D1
Arguments 00000000`00000000 00000000`00000002 00000000`00000000 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Thu Sep  9 18:15:22.442 2010 (UTC - 4:00)
System Uptime: 0 days 0:43:51.377
BugCheck D1, {c0000102, 2, 1, fffff8800531c108}
Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME:  SteamService.e
Bugcheck code 000000D1
Arguments 00000000`c0000102 00000000`00000002 00000000`00000001 fffff880`0531c108
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Wed Sep  8 10:42:41.556 2010 (UTC - 4:00)
System Uptime: 0 days 0:34:07.881
BugCheck D1, {0, 2, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )
PROCESS_NAME:  metro2033.exe
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
Bugcheck code 000000D1
Arguments 00000000`00000000 00000000`00000002 00000000`00000000 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Wed Sep  8 09:54:22.651 2010 (UTC - 4:00)
System Uptime: 0 days 0:47:11.586
BugCheck D1, {0, 2, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )
PROCESS_NAME:  Steam.exe
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
Bugcheck code 000000D1
Arguments 00000000`00000000 00000000`00000002 00000000`00000000 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Wed Sep  8 09:06:30.194 2010 (UTC - 4:00)
System Uptime: 0 days 0:20:35.129
BugCheck D1, {0, 2, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )
PROCESS_NAME:  metro2033.exe
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
Bugcheck code 000000D1
Arguments 00000000`00000000 00000000`00000002 00000000`00000000 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Wed Sep  8 08:31:35.424 2010 (UTC - 4:00)
System Uptime: 0 days 0:10:28.359
BugCheck D1, {c0000102, 2, 1, fffff8a00b526017}
Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME:  metro2033.exe
Bugcheck code 000000D1
Arguments 00000000`c0000102 00000000`00000002 00000000`00000001 fffff8a0`0b526017
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Wed Sep  8 08:20:12.128 2010 (UTC - 4:00)
System Uptime: 0 days 0:35:05.453
BugCheck D1, {0, 2, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )
PROCESS_NAME:  Steam.exe
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
Bugcheck code 000000D1
Arguments 00000000`00000000 00000000`00000002 00000000`00000000 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sat Aug  7 14:28:00.572 2010 (UTC - 4:00)
System Uptime: 0 days 0:42:14.881
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
BugCheck D1, {0, 2, 0, 0}
Probably caused by : ntoskrnl.exe ( nt+70600 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
Bugcheck code 000000D1
Arguments 00000000`00000000 00000000`00000002 00000000`00000000 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sun Jul 25 08:05:35.797 2010 (UTC - 4:00)
System Uptime: 0 days 0:31:18.475
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
BugCheck D1, {0, 2, 0, 0}
Probably caused by : ntoskrnl.exe ( nt+70600 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
Bugcheck code 000000D1
Arguments 00000000`00000000 00000000`00000002 00000000`00000000 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Mon Jul 19 11:25:58.528 2010 (UTC - 4:00)
System Uptime: 0 days 0:16:15.837
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
BugCheck D1, {0, 2, 0, 0}
Probably caused by : ntoskrnl.exe ( nt+70600 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
Bugcheck code 000000D1
Arguments 00000000`00000000 00000000`00000002 00000000`00000000 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Mon Jul 19 11:09:09.296 2010 (UTC - 4:00)
System Uptime: 0 days 0:21:15.215
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
BugCheck D1, {0, 2, 0, 0}
Probably caused by : ntoskrnl.exe ( nt+70600 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
Bugcheck code 000000D1
Arguments 00000000`00000000 00000000`00000002 00000000`00000000 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Thu Jun 17 15:28:54.842 2010 (UTC - 4:00)
System Uptime: 0 days 0:22:57.152
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Probably caused by : ntoskrnl.exe ( nt+764da )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
Bugcheck code 0000003B
Arguments 00000000`c000001d fffff880`0503c000 fffff880`0503b630 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sun Jun  6 17:37:01.710 2010 (UTC - 4:00)
System Uptime: 0 days 4:51:47.184
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Probably caused by : ntoskrnl.exe ( nt+70600 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
Bugcheck code 0000003B
Arguments 00000000`c000001d fffffa80`0677c00e fffff880`06d59620 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sat Jun  5 19:18:18.523 2010 (UTC - 4:00)
System Uptime: 0 days 1:03:29.274
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Probably caused by : ntoskrnl.exe ( nt+764da )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
Bugcheck code 0000003B
Arguments 00000000`c000001d fffff880`06c3a000 fffff880`06c39630 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Mon May 24 10:50:29.953 2010 (UTC - 4:00)
System Uptime: 0 days 0:57:56.263
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
BugCheck D1, {0, 2, 0, 0}
Probably caused by : ntoskrnl.exe ( nt+70600 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
Bugcheck code 000000D1
Arguments 00000000`00000000 00000000`00000002 00000000`00000000 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Wed May 19 14:48:29.207 2010 (UTC - 4:00)
System Uptime: 0 days 1:11:18.517
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Probably caused by : ntoskrnl.exe ( nt+b2410 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
Bugcheck code 0000000A
Arguments 00000000`00000028 00000000`00000002 00000000`00000000 fffff800`02abf410
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Tue Dec 22 16:10:03.317 2009 (UTC - 4:00)
System Uptime: 0 days 0:00:08.626
Probably caused by : hardware
BUGCHECK_STR:  0x124_GenuineIntel
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
Bugcheck code 00000124
Arguments 00000000`00000000 fffffa80`0493a8f8 00000000`00000000 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Tue Nov 17 13:28:06.677 2009 (UTC - 4:00)
System Uptime: 0 days 3:52:17.986
BugCheck D1, {0, 2, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )
PROCESS_NAME:  dwm.exe
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
Bugcheck code 000000D1
Arguments 00000000`00000000 00000000`00000002 00000000`00000000 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
 
  
  [/FONT]

 

[dannyguitar]

Hi again

thank you for your help !!

i removed macdrive from my pc, i did not need it anyway. the bluetooth cause was a bit complicated, i connected my mobile per bt with the pc and so win demanded the drivers for the phone to work as an modem. i removed the bluetooth usb stick so the device manager did not list up those missing drivers anymore, i hope that will fix it, too.

the nforce driver:
i had installed it before, so i wondered why it was not the current one. but i installed it again.

then i activated driver verifier like you said and played for 3 hours without crash.
next day i had a crash (bsod) and win couldn´t boot. so i did a reset and a system start repair. that did not work either. after turning power on again it started normally.
then i played further in order to provoke more crashes.
onetime it crashed and directly crashed again while booting. this time i did not choose system start repair but normal start. it worked.
bad thing is, after this win created only one dumpfile, i assume its the one from the crash while gaming as normally. the start-up-bsod is not listed, but i remember it was a DRIVER_IRQL_NOT_LESS_OR_EQUAL (0x000000d1)



i attached the new dumpfiles. the oldest two of them report about bsods before driver verifier. the rest happened with activated driver verifier.
during driver verifier i had problems with email. my antivirus software avg is connected to that, because it scans incoming mails. this happened far slower then normal until winmail said it could not connect to gmx.
i just thought i better mention it here.



thanks in advance
danny

 

[usasma]

The Verifier Enabled memory dumps point to Windows components. Since you set Driver Verifier to test 3rd party drivers we can assume that there weren't any problems with the 3rd party drivers. But we still don't know if this is a hardware issue, a compatibility issue or a Windows issue.

So, let's try these free diagnostics:

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:

FurMark download site: FurMark: VGA Stress Test, Graphics Card and GPU Stability 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

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.

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.

If all the diagnostics pass, then we're left with compatibility or Windows issues.

You can check compatibility at this website: Windows 7 Compatibility: Software Programs & Hardware Devices: Find Updates, Drivers, & Downloads

You can check Windows by using SFC.EXE /SCANNOW from an elevated (Run as administrator) Command Prompt.

BSOD BUGCHECK SUMMARY

[font=lucida console]
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Fri Sep 24 17:58:30.306 2010 (UTC - 4:00)
System Uptime: 0 days 0:00:16.210
Probably caused by : ataport.SYS ( ataport!GenPnpPdoQueryDeviceRelations+3b )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
Bugcheck code 0000000A
Arguments 00000000`6f726463 00000000`00000002 00000000`00000000 fffff800`030a5436
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Fri Sep 24 08:30:39.069 2010 (UTC - 4:00)
System Uptime: 0 days 0:15:27.363
Probably caused by : memory_corruption ( nt!MiStoreSetEvictPageFile+b )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0xA
PROCESS_NAME:  Crysis64.exe
Bugcheck code 0000000A
Arguments 00000000`00000008 00000000`00000002 00000000`00000000 fffff800`0314a56b
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Fri Sep 24 07:55:26.640 2010 (UTC - 4:00)
System Uptime: 0 days 0:39:14.544
Probably caused by : memory_corruption ( nt!MiStoreSetEvictPageFile+b )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0xA
PROCESS_NAME:  Crysis64.exe
Bugcheck code 0000000A
Arguments 00000000`00000008 00000000`00000002 00000000`00000000 fffff800`0314a56b
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Thu Sep 23 19:03:00.106 2010 (UTC - 4:00)
System Uptime: 0 days 8:26:29.041
BugCheck D1, {0, 2, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )
PROCESS_NAME:  Crysis64.exe
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
Bugcheck code 000000D1
Arguments 00000000`00000000 00000000`00000002 00000000`00000000 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Thu Sep 23 10:35:46.788 2010 (UTC - 4:00)
System Uptime: 0 days 1:28:48.114
BugCheck D1, {0, 2, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )
PROCESS_NAME:  Crysis64.exe
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
Bugcheck code 000000D1
Arguments 00000000`00000000 00000000`00000002 00000000`00000000 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
  [/font]

 

[dannyguitar]

Update

Ok, I was a little busy last week, so it took longer to do all the stress tests and staff.

I did furmark, memtest86+ and the hdd test from hitachi.
all passed.
I still have to do the prime95.

by the way, today i exchanged my gtx 460 with the same model from my retailer in order to exclude a hardware defect. with the new card the same problem still occurs. he said that maybe, if the problem still exists i could try a second exchange e.g. for an ati radeon.

then i forgot to say that i did not update my bios so far because i do not have the experience. should i catch up on this first? if so, could you please give me an detailed description of what to do?

after memtest i had another bluescreen that pointed to hal.dll.
could it be a new hint? i attached the latest dumps.

i will be in barcelona for a week now, so i will keep on with that when i come back.
i hope you´re still patient with me.

 

[usasma]

Involvement of hal.dll can mean that there are compatibility issues. I'd suggest checking both your hardware and your software here: Windows 7 Compatibility: Software Programs & Hardware Devices: Find Updates, Drivers, & Downloads

Here's an older post with some suggestions on how to troubleshoot by stripping the system down: Hardware Troubleshooting Via System Stripdown