Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: many BSOD only in 3D gaming


16 Nov 2010   #1

windows 7 home premium 64bit
 
 
many BSOD only in 3D gaming

hi
i run windows 7 home premium 64bit full retail
on a gigabyte GA-MA790FX-DS5 mainboard / AMD Phenom II X4 955 3,2 GHz / 4 gigabyte Ram


2moths ago i changed my GFXcard into a ATI 5870 / but BSOD was there before
last thing i tryed was to raise my Dram voltage but still BSOD

it comes one oder two times a day only in several Games like MW2 WOW F1 2010. then it comes the sound hangs up into a loop.

two times i remember it was at the windowsstartup after a crash then comes this atikmdag.sys bluescreen otherwise only in 3D

i have no idea / sorry for bad english

My System SpecsSystem Spec
.

16 Nov 2010   #2

ultimate 64 sp1
 
 

it only happens when you are playing games?

maybe your computer is getting too hot. try taking one side of your case off, and play a game.

if it stops crashing, then your problem is heat - buy more fans or make your fans run faster.

if it crashes with the case open, then you have a different problem.
My System SpecsSystem Spec
16 Nov 2010   #3

windows 7 home premium 64bit
 
 

hehe this was fast
i got a new bsod 5 minutes ago with open case and last seen temps gfx 62░C CPU 50░C =(
now i took out my dram modules one by one till next crash
My System SpecsSystem Spec
.


16 Nov 2010   #4

ultimate 64 sp1
 
 

ok - it isn't a heat problem.

i'm sorry, but i cannot help you any more.

hopefully, somebody else will have some more ideas.
My System SpecsSystem Spec
16 Nov 2010   #5

Windows 7 Ultimate 32 bit
 
 

I looked at your three most recent dumps. One of them directly blames Kaspersky. Kaspersky is known to cause BSOD's on some Win 7 systems. I recommend that you install Kaspersky using this removal tool: Tool. Download and install Microsoft Security Essentials in its place. Make sure windows firewall is turned on.
Quote:
Probably caused by : klim6.sys
Quote:
Error code 1E (2X), KMODE_EXCEPTION_NOT_HANDLED. Usual causes: Device driver, hardware, System service, compatibility, Remote control programs, memory, BIOS.

Error code 3D, INTERRUPT_EXCEPTION_NOT_HANDLED. BSOD Index.
Code:
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02e4f000 PsLoadedModuleList = 0xfffff800`0308ce50
Debug session time: Tue Nov 16 01:25:32.766 2010 (GMT-5)
System Uptime: 0 days 1:21:02.481
Loading Kernel Symbols
...............................................................
................................................................
.................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {ffffffffc0000094, fffff88008105ab0, 0, 0}

Unable to load image \SystemRoot\system32\DRIVERS\klim6.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for klim6.sys
*** ERROR: Module load completed but symbols could not be loaded for klim6.sys
Probably caused by : klim6.sys ( klim6+284b )

Followup: MachineOwner
---------

2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000094, The exception code that was not handled
Arg2: fffff88008105ab0, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception

Debugging Details:
------------------


EXCEPTION_CODE: (NTSTATUS) 0xc0000094 - {EXCEPTION}  Integer division by zero.

FAULTING_IP: 
+5929952f01a4d7fc
fffff880`08105ab0 c8691008        enter   1069h,8

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000000

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x1E

PROCESS_NAME:  System

CURRENT_IRQL:  2

EXCEPTION_RECORD:  fffff880081069c8 -- (.exr 0xfffff880081069c8)
ExceptionAddress: fffff8800167346e (tcpip!TcpUpdateMicrosecondCount+0x000000000000008e)
   ExceptionCode: c0000094 (Integer divide-by-zero)
  ExceptionFlags: 00000000
NumberParameters: 0

TRAP_FRAME:  fffff88008106a70 -- (.trap 0xfffff88008106a70)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000000002dc6c0 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8800167346e rsp=fffff88008106c00 rbp=0000000000000002
 r8=0000000000000001  r9=0000000000000000 r10=fffff88008107098
r11=000000038dfd070b r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz ac po nc
tcpip!TcpUpdateMicrosecondCount+0x8e:
fffff880`0167346e 48f7f1          div     rax,rcx
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002f51bdb to fffff80002ebf740

STACK_TEXT:  
fffff880`08106c00 fffff880`0170b689 : fffffa80`045e7000 fffffa80`04479080 00000000`00000000 fffffa80`045e1e30 : tcpip!TcpUpdateMicrosecondCount+0x8e
fffff880`08106c40 fffff880`0167b277 : fffff880`047f2c00 fffff880`0176b9a0 fffffa80`05048e20 fffff880`0165e649 : tcpip!TcpEnterReceiveDpc+0x99
fffff880`08106c70 fffff880`0165d6c7 : fffffa80`045e7000 fffffa80`045e1e30 fffffa80`044b78a0 00000000`00000000 : tcpip!TcpPreValidatedReceive+0x37
fffff880`08106d20 fffff880`0165d799 : fffff880`08106ea0 fffff880`0176b9a0 fffff880`08106eb0 fffff880`01634bab : tcpip!IppDeliverListToProtocol+0x97
fffff880`08106de0 fffff880`0165dc90 : fffffa80`045e7000 fffffa80`05011100 fffffa80`05024000 fffff880`08106ea0 : tcpip!IppProcessDeliverList+0x59
fffff880`08106e50 fffff880`0165cb21 : 00000000`00000000 fffffa80`045e7000 fffff880`0176b9a0 00000000`05106401 : tcpip!IppReceiveHeaderBatch+0x231
fffff880`08106f30 fffff880`0165b592 : fffffa80`0511aad0 00000000`00000000 fffffa80`05106401 00000000`00000001 : tcpip!IpFlcReceivePackets+0x651
fffff880`08107130 fffff880`01674e5a : fffffa80`05106410 fffff880`08107260 fffffa80`05106410 00000000`00000000 : tcpip!FlpReceiveNonPreValidatedNetBufferListChain+0x2b2
fffff880`08107210 fffff800`02ecee5a : fffffa80`05048cf0 fffff880`08102000 00000000`00004800 00000000`00000000 : tcpip!FlReceiveNetBufferListChainCalloutRoutine+0xda
fffff880`08107260 fffff880`01674882 : fffff880`01674d80 fffff880`08107370 00000001`00000002 00000003`00000030 : nt!KeExpandKernelStackAndCalloutEx+0xda
fffff880`08107340 fffff880`0153b0eb : fffffa80`051078d0 00000000`00000000 fffffa80`04efe1a0 f805e628`00000000 : tcpip!FlReceiveNetBufferListChain+0xb2
fffff880`081073b0 fffff880`01504fc6 : fffffa80`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ndis!ndisMIndicateNetBufferListsToOpen+0xdb
fffff880`08107420 fffff880`01487a24 : fffffa80`04efe1a0 00000000`00000002 00000000`00000001 fffff880`0453b339 : ndis!ndisMDispatchReceiveNetBufferLists+0x1d6
fffff880`081078a0 fffff880`014879e9 : fffffa80`04e99090 fffff880`08107938 fffff880`08107908 fffff880`0453b227 : ndis!ndisMTopReceiveNetBufferLists+0x24
fffff880`081078e0 fffff880`01487980 : fffffa80`04efe102 fffff880`0453d0d0 fffff880`081078e0 fffff880`08107938 : ndis!ndisFilterIndicateReceiveNetBufferLists+0x29
fffff880`08107920 fffff880`0453a84b : fffffa80`05223dc0 00000000`00000000 00000000`00000002 fffffa80`050ffa30 : ndis!NdisFIndicateReceiveNetBufferLists+0x50
fffff880`08107960 fffffa80`05223dc0 : 00000000`00000000 00000000`00000002 fffffa80`050ffa30 fffff880`00000001 : klim6+0x284b
fffff880`08107968 00000000`00000000 : 00000000`00000002 fffffa80`050ffa30 fffff880`00000001 fffffa80`05223dc0 : 0xfffffa80`05223dc0


STACK_COMMAND:  .trap 0xfffff88008106a70 ; kb

FOLLOWUP_IP: 
klim6+284b
fffff880`0453a84b ??              ???

SYMBOL_STACK_INDEX:  10

SYMBOL_NAME:  klim6+284b

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: klim6

IMAGE_NAME:  klim6.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4bd0662c

FAILURE_BUCKET_ID:  X64_0x1E_klim6+284b

BUCKET_ID:  X64_0x1E_klim6+284b

Followup: MachineOwner
---------

2: kd> lmtsmn
start             end                 module name
fffff880`04ac0000 fffff880`04afe000   1394ohci 1394ohci.sys Mon Jul 13 20:07:12 2009 (4A5BCC30)
fffff880`00e50000 fffff880`00ea7000   ACPI     ACPI.sys     Mon Jul 13 19:19:34 2009 (4A5BC106)
fffff880`03232000 fffff880`032bc000   afd      afd.sys      Mon Jul 13 19:21:40 2009 (4A5BC184)
fffff880`04b71000 fffff880`04b87000   AgileVpn AgileVpn.sys Mon Jul 13 20:10:24 2009 (4A5BCCF0)
fffff880`0446f000 fffff880`04484000   amdppm   amdppm.sys   Mon Jul 13 19:19:25 2009 (4A5BC0FD)
fffff880`00e3e000 fffff880`00e49000   amdxata  amdxata.sys  Tue May 19 13:56:59 2009 (4A12F2EB)
fffff880`07f49000 fffff880`07f54000   asyncmac asyncmac.sys Mon Jul 13 20:10:13 2009 (4A5BCCE5)
fffff880`00e00000 fffff880`00e09000   atapi    atapi.sys    Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`00e09000 fffff880`00e33000   ataport  ataport.SYS  Mon Jul 13 19:19:52 2009 (4A5BC118)
fffff880`0591b000 fffff880`0593b000   AtihdW76 AtihdW76.sys Mon Aug 16 06:41:02 2010 (4C6915BE)
fffff880`04e2c000 fffff880`055e7000   atikmdag atikmdag.sys Tue Sep 07 21:41:17 2010 (4C86E9BD)
fffff880`0481d000 fffff880`04867000   atikmpag atikmpag.sys Tue Sep 07 21:15:05 2010 (4C86E399)
fffff960`00800000 fffff960`00861000   ATMFD    ATMFD.DLL    unavailable (00000000)
fffff880`0337a000 fffff880`03381000   Beep     Beep.SYS     Mon Jul 13 20:00:13 2009 (4A5BCA8D)
fffff880`04438000 fffff880`04449000   blbdrive blbdrive.sys Mon Jul 13 19:35:59 2009 (4A5BC4DF)
fffff880`03ee2000 fffff880`03f00000   bowser   bowser.sys   Mon Jul 13 19:23:50 2009 (4A5BC206)
fffff960`00620000 fffff960`00647000   cdd      cdd.dll      unavailable (00000000)
fffff880`0103a000 fffff880`01064000   cdrom    cdrom.sys    Mon Jul 13 19:19:54 2009 (4A5BC11A)
fffff880`00c94000 fffff880`00d54000   CI       CI.dll       Mon Jul 13 21:32:13 2009 (4A5BE01D)
fffff880`0144a000 fffff880`0147a000   CLASSPNP CLASSPNP.SYS Mon Jul 13 19:19:58 2009 (4A5BC11E)
fffff880`00c36000 fffff880`00c94000   CLFS     CLFS.SYS     Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`01147000 fffff880`011ba000   cng      cng.sys      Mon Jul 13 19:49:40 2009 (4A5BC814)
fffff880`04b61000 fffff880`04b71000   CompositeBus CompositeBus.sys Mon Jul 13 20:00:33 2009 (4A5BCAA1)
fffff880`06da2000 fffff880`06db0000   crashdmp crashdmp.sys Mon Jul 13 20:01:01 2009 (4A5BCABD)
fffff880`06cb6000 fffff880`06cc2000   dc3d     dc3d.sys     Wed May 20 22:58:41 2009 (4A14C361)
fffff880`0441a000 fffff880`04438000   dfsc     dfsc.sys     Mon Jul 13 19:23:44 2009 (4A5BC200)
fffff880`0440b000 fffff880`0441a000   discache discache.sys Mon Jul 13 19:37:18 2009 (4A5BC52E)
fffff880`01fe6000 fffff880`01ffc000   disk     disk.sys     Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`05978000 fffff880`0599a000   drmk     drmk.sys     Mon Jul 13 21:01:25 2009 (4A5BD8E5)
fffff880`06dbc000 fffff880`06dc5000   dump_atapi dump_atapi.sys Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`06db0000 fffff880`06dbc000   dump_dumpata dump_dumpata.sys Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`06dc5000 fffff880`06dd8000   dump_dumpfve dump_dumpfve.sys Mon Jul 13 19:21:51 2009 (4A5BC18F)
fffff880`06c8b000 fffff880`06c97000   Dxapi    Dxapi.sys    Mon Jul 13 19:38:28 2009 (4A5BC574)
fffff880`04867000 fffff880`0495b000   dxgkrnl  dxgkrnl.sys  Thu Oct 01 21:00:14 2009 (4AC5509E)
fffff880`0495b000 fffff880`049a1000   dxgmms1  dxgmms1.sys  Mon Jul 13 19:38:32 2009 (4A5BC578)
fffff880`04afe000 fffff880`04b0b000   fdc      fdc.sys      Mon Jul 13 20:00:54 2009 (4A5BCAB6)
fffff880`010d5000 fffff880`010e9000   fileinfo fileinfo.sys Mon Jul 13 19:34:25 2009 (4A5BC481)
fffff880`058fb000 fffff880`05906000   flpydisk flpydisk.sys Mon Jul 13 20:00:54 2009 (4A5BCAB6)
fffff880`01089000 fffff880`010d5000   fltmgr   fltmgr.sys   Mon Jul 13 19:19:59 2009 (4A5BC11F)
fffff880`013d0000 fffff880`013da000   Fs_Rec   Fs_Rec.sys   Mon Jul 13 19:19:45 2009 (4A5BC111)
fffff880`01000000 fffff880`0103a000   fvevol   fvevol.sys   Mon Jul 13 19:22:15 2009 (4A5BC1A7)
fffff880`01400000 fffff880`0144a000   fwpkclnt fwpkclnt.sys Mon Jul 13 19:21:08 2009 (4A5BC164)
fffff880`055e7000 fffff880`055f4000   GEARAspiWDM GEARAspiWDM.sys Mon May 18 08:17:04 2009 (4A1151C0)
fffff800`02e06000 fffff800`02e4f000   hal      hal.dll      Mon Jul 13 21:27:36 2009 (4A5BDF08)
fffff880`04e00000 fffff880`04e24000   HDAudBus HDAudBus.sys Mon Jul 13 20:06:13 2009 (4A5BCBF5)
fffff880`06cd9000 fffff880`06cf2000   HIDCLASS HIDCLASS.SYS Mon Jul 13 20:06:21 2009 (4A5BCBFD)
fffff880`06cc2000 fffff880`06cca080   HIDPARSE HIDPARSE.SYS Mon Jul 13 20:06:17 2009 (4A5BCBF9)
fffff880`06ccb000 fffff880`06cd9000   hidusb   hidusb.sys   Mon Jul 13 20:06:22 2009 (4A5BCBFE)
fffff880`03e1a000 fffff880`03ee2000   HTTP     HTTP.sys     Mon Jul 13 19:22:16 2009 (4A5BC1A8)
fffff880`01fdd000 fffff880`01fe6000   hwpolicy hwpolicy.sys Mon Jul 13 19:19:22 2009 (4A5BC0FA)
fffff880`04b34000 fffff880`04b52000   i8042prt i8042prt.sys Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`00f97000 fffff880`00fb7000   jraid    jraid.sys    Thu Oct 29 04:14:20 2009 (4AE94EDC)
fffff880`04b52000 fffff880`04b61000   kbdclass kbdclass.sys Mon Jul 13 19:19:50 2009 (4A5BC116)
fffff880`06cf2000 fffff880`06d00000   kbdhid   kbdhid.sys   Mon Jul 13 20:00:20 2009 (4A5BCA94)
fffff800`00bb1000 fffff800`00bbb000   kdcom    kdcom.dll    Mon Jul 13 21:31:07 2009 (4A5BDFDB)
fffff880`01818000 fffff880`01f77000   kl1      kl1.sys      Wed Jun 09 09:34:19 2010 (4C0F985B)
fffff880`0322b000 fffff880`03232000   kl2      kl2.sys      Wed Jun 09 09:24:47 2010 (4C0F961F)
fffff880`032db000 fffff880`03371000   klif     klif.sys     Fri Aug 06 13:14:46 2010 (4C5C4306)
fffff880`04538000 fffff880`04541000   klim6    klim6.sys    Thu Apr 22 11:07:24 2010 (4BD0662C)
fffff880`06d1b000 fffff880`06d25000   klmouflt klmouflt.sys Mon Nov 02 11:26:06 2009 (4AEF081E)
fffff880`05835000 fffff880`05878000   ks       ks.sys       Mon Jul 13 20:00:31 2009 (4A5BCA9F)
fffff880`013a5000 fffff880`013bf000   ksecdd   ksecdd.sys   Mon Jul 13 19:20:54 2009 (4A5BC156)
fffff880`015cf000 fffff880`015fa000   ksecpkg  ksecpkg.sys  Fri Dec 11 01:03:32 2009 (4B21E0B4)
fffff880`0599a000 fffff880`0599f200   ksthunk  ksthunk.sys  Mon Jul 13 20:00:19 2009 (4A5BCA93)
fffff880`059a0000 fffff880`059b5000   lltdio   lltdio.sys   Mon Jul 13 20:08:50 2009 (4A5BCC92)
fffff880`06dd8000 fffff880`06dfb000   luafv    luafv.sys    Mon Jul 13 19:26:13 2009 (4A5BC295)
fffff880`00c15000 fffff880`00c22000   mcupdate_AuthenticAMD mcupdate_AuthenticAMD.dll Mon Jul 13 21:29:09 2009 (4A5BDF65)
fffff880`06d40000 fffff880`06d4e000   monitor  monitor.sys  Mon Jul 13 19:38:52 2009 (4A5BC58C)
fffff880`04be6000 fffff880`04bf5000   mouclass mouclass.sys Mon Jul 13 19:19:50 2009 (4A5BC116)
fffff880`06d00000 fffff880`06d0d000   mouhid   mouhid.sys   Mon Jul 13 20:00:20 2009 (4A5BCA94)
fffff880`00fe6000 fffff880`01000000   mountmgr mountmgr.sys Mon Jul 13 19:19:54 2009 (4A5BC11A)
fffff880`03f00000 fffff880`03f18000   mpsdrv   mpsdrv.sys   Mon Jul 13 20:08:25 2009 (4A5BCC79)
fffff880`03f18000 fffff880`03f45000   mrxsmb   mrxsmb.sys   Sat Feb 27 02:52:19 2010 (4B88CF33)
fffff880`03f45000 fffff880`03f93000   mrxsmb10 mrxsmb10.sys Sat Feb 27 02:52:28 2010 (4B88CF3C)
fffff880`03f93000 fffff880`03fb6000   mrxsmb20 mrxsmb20.sys Sat Feb 27 02:52:26 2010 (4B88CF3A)
fffff880`00e33000 fffff880`00e3e000   msahci   msahci.sys   Mon Jul 13 20:01:01 2009 (4A5BCABD)
fffff880`033df000 fffff880`033ea000   Msfs     Msfs.SYS     Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`00eb0000 fffff880`00eba000   msisadrv msisadrv.sys Mon Jul 13 19:19:26 2009 (4A5BC0FE)
fffff880`010e9000 fffff880`01147000   msrpc    msrpc.sys    Mon Jul 13 19:21:32 2009 (4A5BC17C)
fffff880`04400000 fffff880`0440b000   mssmbios mssmbios.sys Mon Jul 13 19:31:10 2009 (4A5BC3BE)
fffff880`01fcb000 fffff880`01fdd000   mup      mup.sys      Mon Jul 13 19:23:45 2009 (4A5BC201)
fffff880`0147d000 fffff880`0156f000   ndis     ndis.sys     Mon Jul 13 19:21:40 2009 (4A5BC184)
fffff880`04bab000 fffff880`04bb7000   ndistapi ndistapi.sys Mon Jul 13 20:10:00 2009 (4A5BCCD8)
fffff880`04bb7000 fffff880`04be6000   ndiswan  ndiswan.sys  Mon Jul 13 20:10:11 2009 (4A5BCCE3)
fffff880`05906000 fffff880`0591b000   NDProxy  NDProxy.SYS  Mon Jul 13 20:10:05 2009 (4A5BCCDD)
fffff880`04541000 fffff880`04550000   netbios  netbios.sys  Mon Jul 13 20:09:26 2009 (4A5BCCB6)
fffff880`044c4000 fffff880`04509000   netbt    netbt.sys    Mon Jul 13 19:21:28 2009 (4A5BC178)
fffff880`0156f000 fffff880`015cf000   NETIO    NETIO.SYS    Mon Jul 13 19:21:46 2009 (4A5BC18A)
fffff880`033ea000 fffff880`033fb000   Npfs     Npfs.SYS     Mon Jul 13 19:19:48 2009 (4A5BC114)
fffff880`045ed000 fffff880`045f9000   nsiproxy nsiproxy.sys Mon Jul 13 19:21:02 2009 (4A5BC15E)
fffff800`02e4f000 fffff800`0342b000   nt       ntkrnlmp.exe Sat Jun 19 00:16:41 2010 (4C1C44A9)
fffff880`01202000 fffff880`013a5000   Ntfs     Ntfs.sys     Mon Jul 13 19:20:47 2009 (4A5BC14F)
fffff880`03371000 fffff880`0337a000   Null     Null.SYS     Mon Jul 13 19:19:37 2009 (4A5BC109)
fffff880`04512000 fffff880`04538000   pacer    pacer.sys    Mon Jul 13 20:09:41 2009 (4A5BCCC5)
fffff880`04b17000 fffff880`04b34000   parport  parport.sys  Mon Jul 13 20:00:40 2009 (4A5BCAA8)
fffff880`00efa000 fffff880`00f0f000   partmgr  partmgr.sys  Mon Jul 13 19:19:58 2009 (4A5BC11E)
fffff880`00eba000 fffff880`00eed000   pci      pci.sys      Mon Jul 13 19:19:51 2009 (4A5BC117)
fffff880`00f80000 fffff880`00f87000   pciide   pciide.sys   Mon Jul 13 19:19:49 2009 (4A5BC115)
fffff880`00f87000 fffff880`00f97000   PCIIDEX  PCIIDEX.SYS  Mon Jul 13 19:19:48 2009 (4A5BC114)
fffff880`013bf000 fffff880`013d0000   pcw      pcw.sys      Mon Jul 13 19:19:27 2009 (4A5BC0FF)
fffff880`07a40000 fffff880`07ae6000   peauth   peauth.sys   Mon Jul 13 21:01:19 2009 (4A5BD8DF)
fffff880`06d0d000 fffff880`06d1b000   point64k point64k.sys Fri May 08 04:53:29 2009 (4A03F309)
fffff880`0593b000 fffff880`05978000   portcls  portcls.sys  Mon Jul 13 20:06:27 2009 (4A5BCC03)
fffff880`00c22000 fffff880`00c36000   PSHED    PSHED.dll    Mon Jul 13 21:32:23 2009 (4A5BE027)
fffff880`04b87000 fffff880`04bab000   rasl2tp  rasl2tp.sys  Mon Jul 13 20:10:11 2009 (4A5BCCE3)
fffff880`04a00000 fffff880`04a1b000   raspppoe raspppoe.sys Mon Jul 13 20:10:17 2009 (4A5BCCE9)
fffff880`04a1b000 fffff880`04a3c000   raspptp  raspptp.sys  Mon Jul 13 20:10:18 2009 (4A5BCCEA)
fffff880`04a3c000 fffff880`04a56000   rassstp  rassstp.sys  Mon Jul 13 20:10:25 2009 (4A5BCCF1)
fffff880`0459c000 fffff880`045ed000   rdbss    rdbss.sys    Mon Jul 13 19:24:09 2009 (4A5BC219)
fffff880`033c4000 fffff880`033cd000   RDPCDD   RDPCDD.sys   Mon Jul 13 20:16:34 2009 (4A5BCE62)
fffff880`033cd000 fffff880`033d6000   rdpencdd rdpencdd.sys Mon Jul 13 20:16:34 2009 (4A5BCE62)
fffff880`033d6000 fffff880`033df000   rdprefmp rdprefmp.sys Mon Jul 13 20:16:35 2009 (4A5BCE63)
fffff880`011ba000 fffff880`011f4000   rdyboost rdyboost.sys Mon Jul 13 19:34:34 2009 (4A5BC48A)
fffff880`059b5000 fffff880`059cd000   rspndr   rspndr.sys   Mon Jul 13 20:08:50 2009 (4A5BCC92)
fffff880`049a1000 fffff880`049d3000   Rt64win7 Rt64win7.sys Thu Feb 26 04:04:13 2009 (49A65B0D)
fffff880`06a24000 fffff880`06c77700   RTKVHD64 RTKVHD64.sys Wed Jul 28 06:01:36 2010 (4C500000)
fffff880`00fb7000 fffff880`00fe6000   SCSIPORT SCSIPORT.SYS Mon Jul 13 20:01:04 2009 (4A5BCAC0)
fffff880`07ae6000 fffff880`07af1000   secdrv   secdrv.SYS   Wed Sep 13 09:18:38 2006 (4508052E)
fffff880`04b0b000 fffff880`04b17000   serenum  serenum.sys  Mon Jul 13 20:00:33 2009 (4A5BCAA1)
fffff880`04550000 fffff880`0456d000   serial   serial.sys   Mon Jul 13 20:00:40 2009 (4A5BCAA8)
fffff880`01fc3000 fffff880`01fcb000   spldr    spldr.sys    Mon May 11 12:56:27 2009 (4A0858BB)
fffff880`07e11000 fffff880`07ea7000   srv      srv.sys      Thu Aug 26 23:38:00 2010 (4C773318)
fffff880`07b38000 fffff880`07b9f000   srv2     srv2.sys     Thu Aug 26 23:37:46 2010 (4C77330A)
fffff880`07af1000 fffff880`07b1e000   srvnet   srvnet.sys   Thu Aug 26 23:37:24 2010 (4C7732F4)
fffff880`07b1e000 fffff880`07b26000   SSPORT   SSPORT.sys   Thu Aug 11 19:07:32 2005 (42FBDA34)
fffff880`04bf5000 fffff880`04bf6480   swenum   swenum.sys   Mon Jul 13 20:00:18 2009 (4A5BCA92)
fffff880`01600000 fffff880`017fd000   tcpip    tcpip.sys    Sun Jun 13 23:39:04 2010 (4C15A458)
fffff880`07b26000 fffff880`07b38000   tcpipreg tcpipreg.sys Mon Jul 13 20:09:49 2009 (4A5BCCCD)
fffff880`0321e000 fffff880`0322b000   TDI      TDI.SYS      Mon Jul 13 19:21:18 2009 (4A5BC16E)
fffff880`03200000 fffff880`0321e000   tdx      tdx.sys      Mon Jul 13 19:21:15 2009 (4A5BC16B)
fffff880`04588000 fffff880`0459c000   termdd   termdd.sys   Mon Jul 13 20:16:36 2009 (4A5BCE64)
fffff960`005b0000 fffff960`005ba000   TSDDD    TSDDD.dll    unavailable (00000000)
fffff880`04449000 fffff880`0446f000   tunnel   tunnel.sys   Mon Jul 13 20:09:37 2009 (4A5BCCC1)
fffff880`06d4e000 fffff880`06da2000   udfs     udfs.sys     Mon Jul 13 19:23:37 2009 (4A5BC1F9)
fffff880`0588f000 fffff880`058a1000   umbus    umbus.sys    Mon Jul 13 20:06:56 2009 (4A5BCC20)
fffff880`06c97000 fffff880`06cb4000   usbccgp  usbccgp.sys  Mon Jul 13 20:06:45 2009 (4A5BCC15)
fffff880`06cb4000 fffff880`06cb5f00   USBD     USBD.SYS     Mon Jul 13 20:06:23 2009 (4A5BCBFF)
fffff880`04aaf000 fffff880`04ac0000   usbehci  usbehci.sys  Mon Jul 13 20:06:30 2009 (4A5BCC06)
fffff880`058a1000 fffff880`058fb000   usbhub   usbhub.sys   Mon Jul 13 20:07:09 2009 (4A5BCC2D)
fffff880`055f4000 fffff880`055ff000   usbohci  usbohci.sys  Mon Jul 13 20:06:30 2009 (4A5BCC06)
fffff880`04a59000 fffff880`04aaf000   USBPORT  USBPORT.SYS  Mon Jul 13 20:06:31 2009 (4A5BCC07)
fffff880`06d25000 fffff880`06d40000   USBSTOR  USBSTOR.SYS  Mon Jul 13 20:06:34 2009 (4A5BCC0A)
fffff880`00eed000 fffff880`00efa000   vdrvroot vdrvroot.sys Mon Jul 13 20:01:31 2009 (4A5BCADB)
fffff880`03381000 fffff880`0338f000   vga      vga.sys      Mon Jul 13 19:38:47 2009 (4A5BC587)
fffff880`0338f000 fffff880`033b4000   VIDEOPRT VIDEOPRT.SYS Mon Jul 13 19:38:51 2009 (4A5BC58B)
fffff880`00f0f000 fffff880`00f24000   volmgr   volmgr.sys   Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`00f24000 fffff880`00f80000   volmgrx  volmgrx.sys  Mon Jul 13 19:20:33 2009 (4A5BC141)
fffff880`01f77000 fffff880`01fc3000   volsnap  volsnap.sys  Mon Jul 13 19:20:08 2009 (4A5BC128)
fffff880`0456d000 fffff880`04588000   wanarp   wanarp.sys   Mon Jul 13 20:10:21 2009 (4A5BCCED)
fffff880`033b4000 fffff880`033c4000   watchdog watchdog.sys Mon Jul 13 19:37:35 2009 (4A5BC53F)
fffff880`00d54000 fffff880`00df8000   Wdf01000 Wdf01000.sys Mon Jul 13 19:22:07 2009 (4A5BC19F)
fffff880`00c00000 fffff880`00c0f000   WDFLDR   WDFLDR.SYS   Mon Jul 13 19:19:54 2009 (4A5BC11A)
fffff880`04509000 fffff880`04512000   wfplwf   wfplwf.sys   Mon Jul 13 20:09:26 2009 (4A5BCCB6)
fffff960`00080000 fffff960`0038f000   win32k   win32k.sys   unavailable (00000000)
fffff880`05878000 fffff880`0587cd00   WmBEnum  WmBEnum.sys  Tue Apr 27 16:10:19 2010 (4BD744AB)
fffff880`04484000 fffff880`0448d000   wmiacpi  wmiacpi.sys  Mon Jul 13 19:31:02 2009 (4A5BC3B6)
fffff880`00ea7000 fffff880`00eb0000   WMILIB   WMILIB.SYS   Mon Jul 13 19:19:51 2009 (4A5BC117)
fffff880`0587d000 fffff880`0588e480   WmXlCore WmXlCore.sys Tue Apr 27 16:09:26 2010 (4BD74476)
fffff880`06a00000 fffff880`06a21000   WudfPf   WudfPf.sys   Mon Jul 13 20:05:37 2009 (4A5BCBD1)
fffff880`07ea7000 fffff880`07ed8000   WUDFRd   WUDFRd.sys   Mon Jul 13 20:06:06 2009 (4A5BCBEE)
fffff880`06c78000 fffff880`06c8a100   xusb21   xusb21.sys   Thu Aug 13 18:10:17 2009 (4A848F49)

Unloaded modules:
fffff880`07ed8000 fffff880`07f49000   spsys.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`01800000 fffff880`0180e000   crashdmp.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`013da000 fffff880`013e6000   dump_ataport
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`0180e000 fffff880`01817000   dump_atapi.s
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`013e6000 fffff880`013f9000   dump_dumpfve
    Timestamp: unavailable (00000000)
    Checksum:  00000000

Debug session time: Tue Nov 16 00:02:36.440 2010 (GMT-5)
System Uptime: 0 days 12:48:09.155
Loading Kernel Symbols
...............................................................
................................................................
.................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3D, {fffff8800358a980, 0, 0, fffff88004b210a8}

Probably caused by : ntkrnlmp.exe ( nt!KiInterruptHandler+29 )

Followup: MachineOwner
---------

2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

INTERRUPT_EXCEPTION_NOT_HANDLED (3d)
Arguments:
Arg1: fffff8800358a980
Arg2: 0000000000000000
Arg3: 0000000000000000
Arg4: fffff88004b210a8

Debugging Details:
------------------


CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x3D

PROCESS_NAME:  System

CURRENT_IRQL:  b

EXCEPTION_RECORD:  fffff8800358b118 -- (.exr 0xfffff8800358b118)
Cannot read Exception record @ fffff8800358b118

TRAP_FRAME:  fffff8800358b1c0 -- (.trap 0xfffff8800358b1c0)
Unable to read trap frame at fffff880`0358b1c0

LAST_CONTROL_TRANSFER:  from fffff80002e8eca9 to fffff80002e8f740

STACK_TEXT:  
fffff880`0358a0c8 fffff800`02e8eca9 : 00000000`0000003d fffff880`0358a980 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
fffff880`0358a0d0 fffff800`02e8afe9 : fffffa80`05166a00 fffffa80`05169170 fffff880`0358a980 fffff800`02ebc668 : nt!KiBugCheckDispatch+0x69
fffff880`0358a210 fffff800`02eb540d : fffff880`04920150 fffff880`04902018 fffff880`048dd000 fffff880`0358b118 : nt!KiInterruptHandler+0x29
fffff880`0358a240 fffff800`02ebca90 : fffff800`02fde91c fffff880`0358a2b8 fffff880`0358b118 fffff800`02e1f000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`0358a270 fffff800`02ec99ef : fffff880`0358b118 fffff880`0358a980 fffff880`00000000 fffffa80`05735d50 : nt!RtlDispatchException+0x410
fffff880`0358a950 fffff800`02e8ed82 : fffff880`0358b118 fffffa80`05757000 fffff880`0358b1c0 fffffa80`05757000 : nt!KiDispatchException+0x16f
fffff880`0358afe0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatch+0xc2


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiInterruptHandler+29
fffff800`02e8afe9 90              nop

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  nt!KiInterruptHandler+29

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9

FAILURE_BUCKET_ID:  X64_0x3D_nt!KiInterruptHandler+29

BUCKET_ID:  X64_0x3D_nt!KiInterruptHandler+29

Followup: MachineOwner
---------

Debug session time: Tue Nov 16 09:10:07.983 2010 (GMT-5)
System Uptime: 0 days 1:59:39.698
Loading Kernel Symbols
...............................................................
................................................................
.................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {0, 0, 0, 0}

Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )

Followup: MachineOwner
---------

3: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception

Debugging Details:
------------------


EXCEPTION_CODE: (Win32) 0 (0) - The operation completed successfully.

FAULTING_IP: 
+5929952f01addc74
00000000`00000000 ??              ???

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000000

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x1E

PROCESS_NAME:  Wow.exe

CURRENT_IRQL:  2

EXCEPTION_RECORD:  fffff880009b0c28 -- (.exr 0xfffff880009b0c28)
ExceptionAddress: fffff80002ed53a1 (nt!KiTimerExpiration+0x00000000000000a1)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

TRAP_FRAME:  fffff880009b0cd0 -- (.trap 0xfffff880009b0cd0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000000000000ca rbx=0000000000000000 rcx=00000000000705ca
rdx=0000000000003a10 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002ed53a1 rsp=fffff880009b0e60 rbp=00000000000705ca
 r8=0000000000000000  r9=00000000000000c0 r10=00000000000000ca
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
nt!KiTimerExpiration+0xa1:
fffff800`02ed53a1 483b36          cmp     rsi,qword ptr [rsi] ds:00000000`00000000=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002ec146e to fffff80002ec9710

STACK_TEXT:  
fffff880`009afd18 fffff800`02ec146e : 00000000`00000000 00000000`00000000 fffff880`009b0490 fffff800`02ef6668 : nt!KeBugCheck
fffff880`009afd20 fffff800`02eef40d : fffff800`030d7b7c fffff800`03011e84 fffff800`02e59000 fffff880`009b0c28 : nt!KiKernelCalloutExceptionHandler+0xe
fffff880`009afd50 fffff800`02ef6a90 : fffff800`03018a40 fffff880`009afdc8 fffff880`009b0c28 fffff800`02e59000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`009afd80 fffff800`02f039ef : fffff880`009b0c28 fffff880`009b0490 fffff880`00000000 fffff880`035d3180 : nt!RtlDispatchException+0x410
fffff880`009b0460 fffff800`02ec8d82 : fffff880`009b0c28 00000010`b76f0865 fffff880`009b0cd0 ffff1000`6baa70e2 : nt!KiDispatchException+0x16f
fffff880`009b0af0 fffff800`02ec768a : 00000000`00000286 fffff880`04e789e1 00000000`75722450 00000000`75722450 : nt!KiExceptionDispatch+0xc2
fffff880`009b0cd0 fffff800`02ed53a1 : 00000010`b76eba44 fffff880`009b0e88 00000000`000705c9 fffff880`035d6ea8 : nt!KiGeneralProtectionFault+0x10a
fffff880`009b0e60 fffff800`02ed4cb7 : fffff880`035d31c0 fffffa80`000705ca 00000000`00000000 00000000`000000c9 : nt!KiTimerExpiration+0xa1
fffff880`009b0f00 fffff800`02ecf865 : 000004d8`00000000 fffffa80`03f66b60 00000000`00000000 fffff800`02fe9da0 : nt!KiRetireDpcList+0x277
fffff880`009b0fb0 fffff800`02ecf67c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxRetireDpcList+0x5
fffff880`02f8abe0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchInterruptContinue


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiKernelCalloutExceptionHandler+e
fffff800`02ec146e 90              nop

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!KiKernelCalloutExceptionHandler+e

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9

FAILURE_BUCKET_ID:  X64_0x1E_nt!KiKernelCalloutExceptionHandler+e

BUCKET_ID:  X64_0x1E_nt!KiKernelCalloutExceptionHandler+e

Followup: MachineOwner
---------


Debug session time: Tue Nov 16 09:10:07.983 2010 (GMT-5)
System Uptime: 0 days 1:59:39.698
Loading Kernel Symbols
...............................................................
................................................................
.................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {0, 0, 0, 0}

Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )

Followup: MachineOwner
---------

3: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception

Debugging Details:
------------------


EXCEPTION_CODE: (Win32) 0 (0) - The operation completed successfully.

FAULTING_IP: 
+5929952f01addc74
00000000`00000000 ??              ???

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000000

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x1E

PROCESS_NAME:  Wow.exe

CURRENT_IRQL:  2

EXCEPTION_RECORD:  fffff880009b0c28 -- (.exr 0xfffff880009b0c28)
ExceptionAddress: fffff80002ed53a1 (nt!KiTimerExpiration+0x00000000000000a1)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

TRAP_FRAME:  fffff880009b0cd0 -- (.trap 0xfffff880009b0cd0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000000000000ca rbx=0000000000000000 rcx=00000000000705ca
rdx=0000000000003a10 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002ed53a1 rsp=fffff880009b0e60 rbp=00000000000705ca
 r8=0000000000000000  r9=00000000000000c0 r10=00000000000000ca
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
nt!KiTimerExpiration+0xa1:
fffff800`02ed53a1 483b36          cmp     rsi,qword ptr [rsi] ds:00000000`00000000=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002ec146e to fffff80002ec9710

STACK_TEXT:  
fffff880`009afd18 fffff800`02ec146e : 00000000`00000000 00000000`00000000 fffff880`009b0490 fffff800`02ef6668 : nt!KeBugCheck
fffff880`009afd20 fffff800`02eef40d : fffff800`030d7b7c fffff800`03011e84 fffff800`02e59000 fffff880`009b0c28 : nt!KiKernelCalloutExceptionHandler+0xe
fffff880`009afd50 fffff800`02ef6a90 : fffff800`03018a40 fffff880`009afdc8 fffff880`009b0c28 fffff800`02e59000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`009afd80 fffff800`02f039ef : fffff880`009b0c28 fffff880`009b0490 fffff880`00000000 fffff880`035d3180 : nt!RtlDispatchException+0x410
fffff880`009b0460 fffff800`02ec8d82 : fffff880`009b0c28 00000010`b76f0865 fffff880`009b0cd0 ffff1000`6baa70e2 : nt!KiDispatchException+0x16f
fffff880`009b0af0 fffff800`02ec768a : 00000000`00000286 fffff880`04e789e1 00000000`75722450 00000000`75722450 : nt!KiExceptionDispatch+0xc2
fffff880`009b0cd0 fffff800`02ed53a1 : 00000010`b76eba44 fffff880`009b0e88 00000000`000705c9 fffff880`035d6ea8 : nt!KiGeneralProtectionFault+0x10a
fffff880`009b0e60 fffff800`02ed4cb7 : fffff880`035d31c0 fffffa80`000705ca 00000000`00000000 00000000`000000c9 : nt!KiTimerExpiration+0xa1
fffff880`009b0f00 fffff800`02ecf865 : 000004d8`00000000 fffffa80`03f66b60 00000000`00000000 fffff800`02fe9da0 : nt!KiRetireDpcList+0x277
fffff880`009b0fb0 fffff800`02ecf67c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxRetireDpcList+0x5
fffff880`02f8abe0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchInterruptContinue


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiKernelCalloutExceptionHandler+e
fffff800`02ec146e 90              nop

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!KiKernelCalloutExceptionHandler+e

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9

FAILURE_BUCKET_ID:  X64_0x1E_nt!KiKernelCalloutExceptionHandler+e

BUCKET_ID:  X64_0x1E_nt!KiKernelCalloutExceptionHandler+e

Followup: MachineOwner
---------


You have two out of date drivers loading on your system. Outdated drivers can and do cause memory corruption and crashes. The driver in bold font is an XP driver. Update or eliminate these drivers.

Rt64win7.sys Thu Feb 26 04:04:13 2009 -Latest PCIe GBE (GigaBit Ethernet) drivers here:
Realtek

SSPORT.sys Thu Aug 11 19:07:32 2005 -
Samsung printer driver Samsung. If there is no update for this driver, navigate to C:\Windows\System32\Drivers, locate ssport.sys and rename it to ssport.bak. Reboot and it will not load. I believe it is associated with a Samsung utility. This will break the utility.

Uninstall Kaspersky, take care of the two drivers and run your system. Lets see how it does. Post back and let us know. If you get another BSOD, upload it and we will take the next steps.


My System SpecsSystem Spec
16 Nov 2010   #6

Windows 7 x64, Windows XP SP3, Fedora
 
 

Hi,

Remove Kaspersky - KIS Removal -- jcgriff2.com

Turn the Driver Verifier on - Driver Verifier - Enable and Disable

Run some hardware tests:

http://www.sevenforums.com/tutorials...t-prime95.html (run the Blend test as well as the Small FFT test)

RAM - Test with Memtest86+

Regards,
Reventon

BUGCHECK SUMMARY
Code:

Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Wed Nov 17 03:10:07.983 2010 (GMT+13)
System Uptime: 0 days 1:59:39.698
Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x1E
PROCESS_NAME:  Wow.exe
Bugcheck code 0000001E
Arguments 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Tue Nov 16 19:25:32.766 2010 (GMT+13)
System Uptime: 0 days 1:21:02.481
*** WARNING: Unable to verify timestamp for klim6.sys
*** ERROR: Module load completed but symbols could not be loaded for klim6.sys
Probably caused by : klim6.sys ( klim6+284b )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x1E
PROCESS_NAME:  System
Bugcheck code 0000001E
Arguments ffffffff`c0000094 fffff880`08105ab0 00000000`00000000 00000000`00000000
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Tue Nov 16 18:02:36.440 2010 (GMT+13)
System Uptime: 0 days 12:48:09.155
Probably caused by : ntkrnlmp.exe ( nt!KiInterruptHandler+29 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3D
PROCESS_NAME:  System
Bugcheck code 0000003D
Arguments fffff880`0358a980 00000000`00000000 00000000`00000000 fffff880`04b210a8
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Tue Nov 16 04:10:21.340 2010 (GMT+13)
System Uptime: 0 days 3:11:38.573
Probably caused by : dxgmms1.sys ( dxgmms1!VidSchiUpdateContextRunningTimeAtISR+58 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x7E
PROCESS_NAME:  System
Bugcheck code 1000007E
Arguments ffffffff`c0000094 fffff880`049ba0a8 fffff880`0275d7d8 fffff880`0275d040
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sun Nov 14 10:09:22.810 2010 (GMT+13)
System Uptime: 0 days 0:46:54.525
Probably caused by : dxgmms1.sys ( dxgmms1!VidSchiWaitForSchedulerEvents+1bc )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
Bugcheck code 0000000A
Arguments fffff800`010f4910 00000000`00000002 00000000`00000000 fffff800`02ec3a39
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sun Nov 14 09:21:42.362 2010 (GMT+13)
System Uptime: 0 days 0:54:26.077
Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x1E
PROCESS_NAME:  HAWX2.exe
Bugcheck code 0000001E
Arguments 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sun Nov 14 08:26:01.241 2010 (GMT+13)
System Uptime: 0 days 7:56:48.346
Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x1E
PROCESS_NAME:  HAWX2.exe
Bugcheck code 0000001E
Arguments 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Fri Nov 12 07:17:02.148 2010 (GMT+13)
System Uptime: 0 days 1:56:36.863
Probably caused by : amdppm.sys ( amdppm!C1Halt+2 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x1E
PROCESS_NAME:  System
Bugcheck code 0000001E
Arguments 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Thu Nov 11 00:59:11.926 2010 (GMT+13)
System Uptime: 0 days 1:32:42.641
Probably caused by : ntkrnlmp.exe ( nt!KiTimerExpiration+171 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
Bugcheck code 0000000A
Arguments 00000000`00057105 00000000`00000002 00000000`00000000 fffff800`02ec9471
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Tue Nov  9 06:22:00.950 2010 (GMT+13)
System Uptime: 0 days 0:00:24.665
Probably caused by : atikmdag.sys ( atikmdag+117b7b )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  atieclxx.exe
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff880`04f26b7b fffff880`041b3710 00000000`00000000
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Tue Nov  9 05:54:45.120 2010 (GMT+13)
System Uptime: 0 days 0:00:25.225
Probably caused by : atikmdag.sys ( atikmdag+117b7b )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  atieclxx.exe
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff880`0513fb7b fffff880`043cd710 00000000`00000000
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Nov  8 01:03:50.146 2010 (GMT+13)
System Uptime: 0 days 2:19:21.217
Probably caused by : tcpip.sys ( tcpip!TcpUpdateMicrosecondCount+8e )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x7E
PROCESS_NAME:  System
Bugcheck code 1000007E
Arguments ffffffff`c0000094 fffff880`0167446e fffff880`037a86d8 fffff880`037a7f40
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sun Nov  7 04:41:54.770 2010 (GMT+13)
System Uptime: 0 days 4:38:12.875
Probably caused by : amdppm.sys ( amdppm!C1Halt+2 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x1E
PROCESS_NAME:  System
Bugcheck code 0000001E
Arguments 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sun Oct 31 22:57:48.530 2010 (GMT+13)
System Uptime: 0 days 0:42:28.635
Probably caused by : amdppm.sys ( amdppm!C1Halt+2 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x1E
PROCESS_NAME:  System
Bugcheck code 0000001E
Arguments 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Fri Oct 22 07:59:58.260 2010 (GMT+13)
System Uptime: 0 days 2:25:42.366
Probably caused by : ntkrnlmp.exe ( nt!KiProcessExpiredTimerList+72 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
Bugcheck code 0000000A
Arguments 00000000`00200000 00000000`00000002 00000000`00000000 fffff800`02c96d82
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Fri Oct 22 05:31:59.812 2010 (GMT+13)
System Uptime: 0 days 8:57:16.918
Probably caused by : hardware ( nt!KiTimerWaitTest+244 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
Bugcheck code 0000000A
Arguments 00000000`00000003 00000000`00000002 00000000`00000001 fffff800`02ccb364
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Thu Oct 21 08:10:27.091 2010 (GMT+13)
System Uptime: 0 days 7:55:15.196
Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x1E
PROCESS_NAME:  System
Bugcheck code 0000001E
Arguments 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Wed Oct 20 09:17:38.011 2010 (GMT+13)
System Uptime: 0 days 1:19:57.116
Probably caused by : amdppm.sys ( amdppm!C1Halt+2 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x1E
PROCESS_NAME:  System
Bugcheck code 0000001E
Arguments 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Wed Oct 20 07:56:18.253 2010 (GMT+13)
System Uptime: 0 days 1:17:39.968
Probably caused by : amdppm.sys ( amdppm!C1Halt+2 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x1E
PROCESS_NAME:  System
Bugcheck code 0000001E
Arguments 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Tue Oct 19 12:39:02.285 2010 (GMT+13)
System Uptime: 0 days 8:24:25.000
Probably caused by : hardware ( nt!KiKernelCalloutExceptionHandler+e )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x1E
PROCESS_NAME:  Wow.exe
Bugcheck code 0000001E
Arguments 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Tue Oct 12 04:49:10.121 2010 (GMT+13)
System Uptime: 0 days 0:35:46.836
Probably caused by : amdppm.sys ( amdppm!C1Halt+2 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x1E
PROCESS_NAME:  System
Bugcheck code 0000001E
Arguments 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Tue Oct 12 04:11:53.233 2010 (GMT+13)
System Uptime: 0 days 0:35:17.948
Probably caused by : amdppm.sys ( amdppm!C1Halt+2 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x1E
PROCESS_NAME:  System
Bugcheck code 0000001E
Arguments 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Oct 11 06:02:53.886 2010 (GMT+13)
System Uptime: 0 days 9:16:39.038
Probably caused by : ntkrnlmp.exe ( nt!KiTimerExpiration+118 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  iw4mp.exe
Bugcheck code 0000000A
Arguments 00000000`00188f6e 00000000`00000002 00000000`00000000 fffff800`02c85418
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sun Oct 10 19:04:46.663 2010 (GMT+13)
System Uptime: 0 days 5:54:38.768
Probably caused by : ntkrnlmp.exe ( nt!KiDeferredReadyThread+cc )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
Bugcheck code 0000000A
Arguments 00000000`00000000 00000000`00000002 00000000`00000001 fffff800`02cd7fac
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Fri Oct  8 10:32:20.853 2010 (GMT+13)
System Uptime: 0 days 6:00:00.989
Probably caused by : amdppm.sys ( amdppm!C1Halt+2 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x1E
PROCESS_NAME:  System
Bugcheck code 0000001E
Arguments 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Sep 27 08:43:02.586 2010 (GMT+13)
System Uptime: 0 days 2:49:13.692
Probably caused by : amdppm.sys ( amdppm!C1Halt+2 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x1E
PROCESS_NAME:  System
Bugcheck code 0000001E
Arguments 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Sep 27 05:46:01.195 2010 (GMT+13)
System Uptime: 0 days 1:26:51.911
BugCheck F7, {200065e86c0, 439e3e897368, ffffbc61c1768c97, 0}
Probably caused by : ntkrnlmp.exe ( nt!_report_gsfailure+25 )
DEFAULT_BUCKET_ID:  GS_FALSE_POSITIVE_MISSING_GSFRAME
BUGCHECK_STR:  0xF7
PROCESS_NAME:  System
Bugcheck code 000000F7
Arguments 00000200`065e86c0 0000439e`3e897368 ffffbc61`c1768c97 00000000`00000000
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Thu Sep 23 09:00:00.879 2010 (GMT+13)
System Uptime: 0 days 2:24:56.016
Probably caused by : amdppm.sys ( amdppm!C1Halt+2 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x1E
PROCESS_NAME:  System
Bugcheck code 0000001E
Arguments 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Thu Sep 23 06:33:33.988 2010 (GMT+13)
System Uptime: 0 days 1:46:59.703
Probably caused by : ntkrnlmp.exe ( nt!RtlpOwnerAcesPresent+78 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  F1_2010_game.e
Bugcheck code 0000000A
Arguments 00000000`000001ab 00000000`00000002 00000000`00000000 fffff800`02ca9d38
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Tue Sep 21 05:55:35.084 2010 (GMT+13)
System Uptime: 0 days 0:46:57.189
Probably caused by : ntkrnlmp.exe ( nt!KiTimerWaitTest+222 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  iw4mp.exe
Bugcheck code 0000000A
Arguments fffff880`03607610 00000000`00000002 00000000`00000001 fffff800`02c7f342
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Tue Sep 14 10:38:30.233 2010 (GMT+13)
System Uptime: 0 days 1:53:24.951
Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x1E
PROCESS_NAME:  iw4mp.exe
Bugcheck code 0000001E
Arguments 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Thu Sep  2 03:24:41.160 2010 (GMT+13)
System Uptime: 0 days 1:02:18.265
Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x1E
PROCESS_NAME:  dirt2_game.exe
Bugcheck code 0000001E
Arguments 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sun Aug 22 02:26:08.295 2010 (GMT+13)
System Uptime: 0 days 0:32:06.400
Probably caused by : amdppm.sys ( amdppm!C1Halt+2 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x1E
PROCESS_NAME:  System
Bugcheck code 0000001E
Arguments 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Wed Aug 18 02:24:09.090 2010 (GMT+13)
System Uptime: 0 days 2:59:26.211
Probably caused by : hardware ( nt!SwapContext+7d )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  darkfall.exe
Bugcheck code 0000000A
Arguments ffffffff`ffffff96 00000000`00000002 00000000`00000001 fffff800`02a7f8fd
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Tue Aug 10 09:35:39.194 2010 (GMT+13)
System Uptime: 0 days 10:29:02.316
Probably caused by : hidusb.sys
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x9F
PROCESS_NAME:  System
Bugcheck code 0000009F
Arguments 00000000`00000003 fffffa80`05c5d060 fffff800`00b9c518 fffffa80`041e7360
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
My System SpecsSystem Spec
17 Nov 2010   #7

windows 7 home premium 64bit
 
 

hi again
thx for assistance at all
now i got new infos
most of them tips u told me i have done

prime95 test - no errors max cpu temp was 54░C
driver verifier activated
kaspersky in safe mode uninstalled microsoft security installed
ram test will follow tonight
some drivers updated (not the samsung because printer is relative new and bsod was there before)

now today i got 2 new bluescreens 1. was usual while playing worldof warcraft
but the latest was a new one at startup from windows

can u take a look ?

thanks in afvance
My System SpecsSystem Spec
17 Nov 2010   #8

64-bit Windows 8.1 Pro
 
 

Your .dmp file points to jraid.sys (JMicron RAID Driver) as the cause of your crash... Download the latest version at Driver Support

Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {fffffa8005668eca, a, 0, fffff88000e77356}

Unable to load image \SystemRoot\system32\DRIVERS\jraid.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for jraid.sys
*** ERROR: Module load completed but symbols could not be loaded for jraid.sys
Probably caused by : jraid.sys ( jraid+4356 )

Followup: MachineOwner
---------
This driver is out of date and either needs to be updated, or the associated program uninstalled..
Code:
SSPORT.sys   Thu Aug 11 19:07:32 2005 ... Samsung printer driver ... Samsung
My System SpecsSystem Spec
17 Nov 2010   #9

windows 7 home premium 64bit
 
 

me again
ok i dunno what this JMicron RAID Driver thing is but i updated the sata controllerdriver from the page

i tried to do the samsung update via driveragent but now i get a bluescreen everytime if i start driveragent and its load at 10%. can this be somthing to do with the microsoft driver verifier? its still activated!

i uninstalled the samsung printer driver for the moment

attached the new bsod files

i think its something with my hardware dram motherboard cpu but if i only knew what exactly i would be happy

greetings
My System SpecsSystem Spec
17 Nov 2010   #10

64-bit Windows 8.1 Pro
 
 

The jraid.sys file is still loading and is still being blamed as the cause of your crash... rename the driver to jraid.BAK, then reboot and test...

Code:

Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Tom\Desktop\111710-45801-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02e59000 PsLoadedModuleList = 0xfffff800`03096e50
Debug session time: Wed Nov 17 11:59:50.387 2010 (UTC - 5:00)
System Uptime: 0 days 0:02:59.539
Loading Kernel Symbols
...............................................................
................................................................
...............................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {fffffa8005668eca, a, 0, fffff88000e77356}

Unable to load image \SystemRoot\system32\DRIVERS\jraid.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for jraid.sys
*** ERROR: Module load completed but symbols could not be loaded for jraid.sys
Probably caused by : jraid.sys ( jraid+4356 )

Followup: MachineOwner
---------
My System SpecsSystem Spec
Reply

 many BSOD only in 3D gaming




Thread Tools



Similar help and support threads for2: many BSOD only in 3D gaming
Thread Forum
Gaming on a Desktop Computer VERSUS Gaming on a laptop Gaming
Solved BSOD Occurring Randomly while gaming and when i am not gaming??? BSOD Help and Support
BSOD During Gaming - BSOD's include dxgmms.sys, win32k.sys BSOD Help and Support
BSOD 116 while gaming BSOD Help and Support
BSOD while gaming BSOD Help and Support
BSOD while gaming & corrupted sound before BSOD BSOD Help and Support
Daily BSOD's, some random, some during gaming (Prime95 Insta-BSOD) BSOD Help and Support

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

й Designer Media Ltd

All times are GMT -5. The time now is 08:13 PM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33