Constant random BSOD happening due to video drivers

Since about June a bunch of PCs in our organizations have been crashing. After looking at the dmp files we see that either nVidia, intel, or directx caused the crash. We update the video drivers, but still the PC crashes. The PC would either be a Dell
(e6420, e6520) or Lenovo(T420s, W530). The majority of the dmp's have the words
UNEXPECTED_KERNEL_MODE_TRAP. Any help will be appreciated, this has been plaguing us for months.

Here is the latest crash info:
Kernel Summary Dump File: Only kernel address space is available
************* Symbol Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       SRV*C:\symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*C:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18229.amd64fre.win7sp1_gdr.130801-1533
Machine Name:
Kernel base = 0xfffff800`02e14000 PsLoadedModuleList = 0xfffff800`030576d0
Debug session time: Fri Oct 10 12:20:52.503 2014 (UTC - 4:00)
System Uptime: 0 days 3:08:53.232
Loading Kernel Symbols
Loading User Symbols
Loading unloaded module list
*                        Bugcheck Analysis                                    *
Use !analyze -v to get detailed debugging information.
BugCheck 7F, {8, 80050031, 406f8, fffff8800322efec}
*** ERROR: Module load completed but symbols could not be loaded for nvkflt.sys
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for igdkmd64.sys - 
*** ERROR: Module load completed but symbols could not be loaded for vsdatant.sys
Probably caused by : nvkflt.sys ( nvkflt+18fec )
Followup: MachineOwner
0: kd> !analyze -v
*                        Bugcheck Analysis                                    *
UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault).  The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
        use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
        use .trap on that value
Else
        .trap on the appropriate frame will show where the trap was taken
        (on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
Arg2: 0000000080050031
Arg3: 00000000000406f8
Arg4: fffff8800322efec
Debugging Details:
BUGCHECK_STR:  0x7f_8
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  System
CURRENT_IRQL:  a
ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre
EXCEPTION_RECORD:  fffff80002e67e04 -- (.exr 0xfffff80002e67e04)
ExceptionAddress: 00076675870f40fe
   ExceptionCode: 74ff8548
  ExceptionFlags: 74f68556
NumberParameters: 1064629893
   Parameter[0]: 001f0fce8b440000
   Parameter[1]: 0f10c783480f8b48
   Parameter[2]: 048154b60f0141b6
   Parameter[3]: 094c0fe083c28b48
   Parameter[4]: c148c28b4810c344
   Parameter[5]: 0090c384094c04e8
   Parameter[6]: e98349c0d1490000
   Parameter[7]: 3824748b48cd7501
   Parameter[8]: 7c8b4830245c8b48
   Parameter[9]: 28c48348c0332024
   Parameter[10]: 90909090909090c3
   Parameter[11]: 244c894c90909090
   Parameter[12]: 8948102454894820
   Parameter[13]: 485741564108244c
   Parameter[14]: 9824b48b4c58ec83
LAST_CONTROL_TRANSFER:  from fffff80002e89129 to fffff80002e89b80
STACK_TEXT:  
fffff800`00ba4d28 fffff800`02e89129 : 00000000`0000007f 00000000`00000008 00000000`80050031 00000000`000406f8 : nt!KeBugCheckEx
fffff800`00ba4d30 fffff800`02e875f2 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff800`00ba4e70 fffff880`0322efec : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb2
fffff880`0e1eefd0 fffff880`0322ef1d : fffffa80`103f1570 fffffa80`103f1570 fffffa80`113cc040 00000000`00000000 : nvkflt+0x18fec
fffff880`0e1ef070 fffff880`0322ef1d : fffff880`0322ee87 fffffa80`103f1970 fffff880`0e1ef280 fffffa80`113cc040 : nvkflt+0x18f1d
fffff880`0e1ef110 fffff880`0322ed6f : fffff880`0322ee87 fffffa80`113cc040 fffff880`0e1ef8b0 00000000`00000000 : nvkflt+0x18f1d
fffff880`0e1ef1b0 fffff880`1058baf2 : fffff880`0322ecdd 00000000`00000000 00000000`00000000 00000000`00000000 : nvkflt+0x18d6f
fffff880`0e1ef250 fffff880`10516a4b : 00000000`00000000 fffff880`00000000 fffff880`0e1ef890 00000000`00000000 : igdkmd64!hybDriverEntry+0x10dcc2
fffff880`0e1ef7f0 fffff880`104a7133 : fffffa80`11502000 fffffa80`103f8010 00000000`00000000 fffffa80`1512354c : igdkmd64!hybDriverEntry+0x98c1b
fffff880`0e1ef870 fffff880`03228d11 : 00000000`00000000 fffffa80`11502000 00000000`00000000 fffffa80`1caaf7b0 : igdkmd64!hybDriverEntry+0x29303
fffff880`0e1ef8e0 fffff880`03228ed7 : fffff880`03228c7f fffffa80`10401c10 fffffa80`11502000 fffffa80`103f1570 : nvkflt+0x12d11
fffff880`0e1ef980 fffff880`0322905a : fffff880`03228e3e 00000000`00000000 fffffa80`103f1420 00000000`00000001 : nvkflt+0x12ed7
fffff880`0e1efa30 fffff800`02e859dc : fffff880`03228fc7 fffff880`0e1efe30 fffff880`0e1efb50 fffffa80`0ffe3f00 : nvkflt+0x1305a
fffff880`0e1efad0 fffff800`02e8be23 : fffff800`02e67e04 fffff880`0e1f0930 fffff880`0e1f0400 fffff880`0e1f0408 : nt!KiInterruptDispatch+0x16c
fffff880`0e1efc68 fffff800`02e67e04 : fffff880`0e1f0930 fffff880`0e1f0400 fffff880`0e1f0408 00000000`00000000 : nt!memset+0x93
fffff880`0e1efc70 fffff800`02e57cbc : fffff880`0e1efd50 fffffa80`139667c8 fffffa80`15113148 00000000`00000000 : nt!RtlSidHashInitialize+0x34
fffff880`0e1efca0 fffff800`02e57dff : fffffa80`139667c8 00000000`00000001 fffffa80`15123000 fffff880`0e1f0408 : nt!SepTokenFromAccessInformation+0xbc
fffff880`0e1efcd0 fffff880`01cfda3a : fffff880`0e1f03e0 fffff880`01cfd501 fffff880`0e1f0408 fffff880`0e1f0400 : nt!SeAccessCheckFromState+0x9f
fffff880`0e1f03c0 fffff880`01cfd29f : fffffa80`1515cf48 00000000`00000000 00000000`00000001 fffff880`01cfd434 : NETIO!CompareSecurityContexts+0x6a
fffff880`0e1f0430 fffff880`01cfd434 : 00000000`00000000 00000000`00000000 fffffa80`13c57be0 fffff880`01cfd753 : NETIO!MatchValues+0xef
fffff880`0e1f0480 fffff880`01cfd8e2 : 00000000`00000000 fffffa80`1119aa70 fffff880`0e1f06a8 fffffa80`0fa25ca0 : NETIO!FilterMatch+0x94
fffff880`0e1f04d0 fffff880`01cfe6ec : 00000000`00000000 00000000`00000010 fffffa80`0fa25ca0 fffff880`0e1f0690 : NETIO!IndexListClassify+0x69
fffff880`0e1f0550 fffff880`01e811c7 : fffffa80`0fa25ca0 fffff880`0e1f0930 00000000`00000000 fffffa80`20ee5e20 : NETIO!KfdClassify+0xa4e
fffff880`0e1f08c0 fffff880`01e82d94 : fffffa80`0fa25ca0 fffffa80`14b2a800 fffff880`0e1f1348 fffffa80`111c70e0 : tcpip!WfpAleClassify+0x57
fffff880`0e1f0900 fffff880`01e83125 : 00000000`00000000 fffff880`00000000 00000000`00000000 00000000`00000002 : tcpip!WfpAlepReauthorizeInboundConnection+0x5f4
fffff880`0e1f0c00 fffff880`01e5a1cd : fffffa80`14b2a800 fffff880`0e1f0d7c 00000001`00000011 fffffa80`111c70e0 : tcpip!WfpAleReauthorizeInboundConnection+0x1f5
fffff880`0e1f0d60 fffff880`01e556da : 00000000`00000797 fffffa80`111c71d0 fffffa80`13c44ec0 fffff880`0e1f1200 : tcpip!WfpAleReauthorizeConnection+0x63d
fffff880`0e1f0ec0 fffff880`01e80bfa : fffffa80`14b2a800 00000000`00000002 00000000`00000000 00000000`00000100 : tcpip!TlShimOptionalReauthorizeConnection+0x2ca
fffff880`0e1f1000 fffff880`01e8deed : fffff880`00000003 fffff880`00000000 fffff880`00000003 fffffa80`20ee5e20 : tcpip!ProcessALEForTransportPacket+0x3ea
fffff880`0e1f1270 fffff880`01e81e48 : fffffa80`14b2a800 fffffa80`00000000 00000000`00000000 fffffa80`0fa2eb14 : tcpip!ProcessAleForNonTcpIn+0x1ad
fffff880`0e1f1390 fffff880`01e598b8 : fffffa80`00000011 fffff880`0e1f0002 fffffa80`14b2eb14 00000000`0000fccc : tcpip!WfpProcessInTransportStackIndication+0xb98
fffff880`0e1f1520 fffff880`01e85fb9 : 00000000`00000018 fffffa80`0fa5b820 00000000`00000000 fffff880`01e865b4 : tcpip!InetInspectReceiveDatagram+0x1d8
fffff880`0e1f15c0 fffff880`01e85b34 : fffffa80`14bcbb60 fffffa80`1398d160 fffffa80`13f88080 00000000`00000000 : tcpip!UdpBeginMessageIndication+0x89
fffff880`0e1f16e0 fffff880`01e800de : fffffa80`0ccc7000 00000000`00000018 fffffa80`00000000 fffff880`0e1f1810 : tcpip!UdpDeliverDatagrams+0x2f4
fffff880`0e1f17c0 fffff880`01e55197 : 00000000`00000000 fffff800`03401a01 00000000`00000001 fffffa80`00000005 : tcpip!UdpReceiveDatagrams+0x18f
fffff880`0e1f18a0 fffff880`01e54caa : 00000000`00000000 fffff880`01f6ba10 fffff880`0e1f1a60 00000000`00000000 : tcpip!IppDeliverListToProtocol+0xf7
fffff880`0e1f1960 fffff880`01e54261 : fffff880`01f6ba10 fffffa80`214afa30 00000000`00000011 fffff880`0e1f1a50 : tcpip!IppProcessDeliverList+0x5a
fffff880`0e1f1a00 fffff880`01e51eef : 00000000`fc0000e0 fffff880`01f6ba10 00000000`00000000 00000000`00000000 : tcpip!IppReceiveHeaderBatch+0x232
fffff880`0e1f1b00 fffff880`01f36022 : fffffa80`13439590 00000000`00000000 fffffa80`103c9501 00000000`00000001 : tcpip!IpFlcReceivePackets+0x64f
fffff880`0e1f1d00 fffff880`01d8db16 : fffffa80`210bb002 fffffa80`210bb010 00000000`00000002 00000000`00000000 : tcpip!IppInspectInjectReceive+0xf2
fffff880`0e1f1d40 fffff880`04aba7cc : fffffa80`0ccf8570 fffffa80`103c9540 fffffa80`103c9600 fffffa80`214af900 : fwpkclnt!FwpsInjectTransportReceiveAsync0+0x256
fffff880`0e1f1df0 fffff880`04aba8e5 : fffffa80`103c9540 fffff880`0e1f2700 fffffa80`103c9600 00000000`00000000 : vsdatant+0x137cc
fffff880`0e1f1e80 fffff880`04ab9c07 : fffffa80`1d645010 fffff880`0e1f2700 fffffa80`1d645010 fffffa80`103c9600 : vsdatant+0x138e5
fffff880`0e1f1ec0 fffff880`04ab53b4 : fffffa80`103c9540 fffffa80`103c9500 fffff880`0e1f2700 fffffa80`00000000 : vsdatant+0x12c07
fffff880`0e1f1fd0 fffff880`01d15aaf : fffff880`0e1f26c8 fffff880`0e1f2280 fffffa80`24383ae0 fffffa80`0cceb040 : vsdatant+0xe3b4
fffff880`0e1f2110 fffff880`01cfcf58 : 00000000`00000018 fffff880`0e1f26c8 fffffa80`111c7138 fffffa80`24383ae0 : NETIO! ?? ::FNODOBFM::`string'+0x7277
fffff880`0e1f2230 fffff880`01cfe5d2 : 00000000`00000018 fffff880`0e1f26c8 fffff880`0e1f27e0 fffff880`00000000 : NETIO!ArbitrateAndEnforce+0x238
fffff880`0e1f2300 fffff880`01f006cb : fffff880`0e1f2d18 fffff880`0e1f26c8 fffff880`00000000 fffffa80`24383ae0 : NETIO!KfdClassify+0x934
fffff880`0e1f2670 fffff880`01eb8102 : 00000000`00000000 fffffa80`14b2a800 fffffa80`111c7240 00000000`00000100 : tcpip!WFPDatagramDataShimV4+0x49b
fffff880`0e1f29d0 fffff880`01e8deed : fffff880`00000003 fffff880`00000000 fffff880`00000003 fffffa80`24383ae0 : tcpip! ?? ::FNODOBFM::`string'+0x26aa2
fffff880`0e1f2c40 fffff880`01e81e48 : fffffa80`14b2a800 fffffa80`00000000 00000000`00000000 fffffa80`0fa2eb14 : tcpip!ProcessAleForNonTcpIn+0x1ad
fffff880`0e1f2d60 fffff880`01e598b8 : fffffa80`00000011 fffff880`0e1f0002 fffffa80`14b2eb14 00000000`0000fccc : tcpip!WfpProcessInTransportStackIndication+0xb98
fffff880`0e1f2ef0 fffff880`01e85fb9 : 00000000`00000018 fffffa80`0fa5b820 00000000`00000000 fffff880`01e865b4 : tcpip!InetInspectReceiveDatagram+0x1d8
fffff880`0e1f2f90 fffff880`01e85b34 : fffffa80`14bcbb60 fffffa80`1398d160 fffffa80`13f88080 00000000`00000000 : tcpip!UdpBeginMessageIndication+0x89
fffff880`0e1f30b0 fffff880`01e800de : fffffa80`0ccc7000 00000000`00000018 fffffa80`00000000 fffff880`0e1f31e0 : tcpip!UdpDeliverDatagrams+0x2f4
fffff880`0e1f3190 fffff880`01e55197 : fffffa80`138f0007 fffff880`0e1f3301 00000000`00000002 fffff880`00000005 : tcpip!UdpReceiveDatagrams+0x18f
fffff880`0e1f3270 fffff880`01e54caa : 00000000`00000000 fffff880`01f6ba10 fffff880`0e1f3430 00000000`00000000 : tcpip!IppDeliverListToProtocol+0xf7
fffff880`0e1f3330 fffff880`01e54261 : fffff880`01f6ba10 fffffa80`21196e80 00000000`00000011 fffff880`0e1f3420 : tcpip!IppProcessDeliverList+0x5a
fffff880`0e1f33d0 fffff880`01e51eef : 00000000`fc0000e0 fffff880`01f6ba10 00000000`00000000 00000000`00000000 : tcpip!IppReceiveHeaderBatch+0x232
fffff880`0e1f34d0 fffff880`01e514c2 : fffffa80`13439590 00000000`00000000 fffffa80`13884b01 00000000`00000001 : tcpip!IpFlcReceivePackets+0x64f
fffff880`0e1f36d0 fffff880`01e508ea : fffffa80`13884ba0 fffff880`0e1f3800 fffffa80`13884ba0 00000000`00000000 : tcpip!FlpReceiveNonPreValidatedNetBufferListChain+0x2b2
fffff880`0e1f37b0 fffff800`02e95878 : fffffa80`20190030 00000000`00004800 fffffa80`2429eab0 00000000`00000000 : tcpip!FlReceiveNetBufferListChainCalloutRoutine+0xda
fffff880`0e1f3800 fffff880`01e50fe2 : fffff880`01e50810 fffff880`0e1f3c00 fffff880`0e1f3c02 00000000`00000000 : nt!KeExpandKernelStackAndCalloutEx+0xd8
fffff880`0e1f38e0 fffff880`01cc40eb : fffffa80`138b98d0 00000000`00000000 fffffa80`115af1a0 fffffa80`115af1a0 : tcpip!FlReceiveNetBufferListChain+0xb2
fffff880`0e1f3950 fffff880`01c8dad6 : fffffa80`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ndis!ndisMIndicateNetBufferListsToOpen+0xdb
fffff880`0e1f39c0 fffff880`01c105d4 : fffffa80`115af1a0 00000000`00000002 00000000`00000001 fffff880`091b300f : ndis!ndisMDispatchReceiveNetBufferLists+0x1d6
fffff880`0e1f3e40 fffff880`01c10549 : fffffa80`13884050 fffff880`091b5630 00000000`00000008 fffff880`01c07d9f : ndis!ndisMTopReceiveNetBufferLists+0x24
fffff880`0e1f3e80 fffff880`01c104e0 : ffff0000`0aaf8d9e 00000000`00000000 00000000`00000000 fffffa80`138b8930 : ndis!ndisFilterIndicateReceiveNetBufferLists+0x29
fffff880`0e1f3ec0 fffff880`04abd9f4 : 00000000`00000000 fffffa80`20190030 00000000`00000000 fffffa80`138b8930 : ndis!NdisFIndicateReceiveNetBufferLists+0x50
fffff880`0e1f3f00 fffff880`04abdb20 : 00000000`0000ff00 fffffa80`00000000 00000001`00000000 fffffa80`138a8670 : vsdatant+0x169f4
fffff880`0e1f3f70 fffff880`01c10549 : 00000000`00000000 00000000`00000000 fffffa80`138ae020 00000000`00000001 : vsdatant+0x16b20
fffff880`0e1f3fb0 fffff880`01c104e0 : fffff880`091ed5c0 fffffa80`138b1010 fffffa80`138ae020 00000000`00000001 : ndis!ndisFilterIndicateReceiveNetBufferLists+0x29
fffff880`0e1f3ff0 fffff880`091b67ee : fffffa80`138b1010 00000000`00000000 fffffa80`20190030 fffff880`091ed5c0 : ndis!NdisFIndicateReceiveNetBufferLists+0x50
fffff880`0e1f4030 fffff880`01c10549 : fffffa80`11c57260 00000000`00000000 00000000`00000001 00000000`00000001 : nwifi!Pt6Receive+0x296
fffff880`0e1f4090 fffff880`01c104e0 : fffffa80`1220f028 fffff880`0320a0c7 fffff880`0320b340 00000000`00000010 : ndis!ndisFilterIndicateReceiveNetBufferLists+0x29
STACK_COMMAND:  kb
FOLLOWUP_IP: 
nvkflt+18fec
fffff880`0322efec e85b90feff      call    nvkflt+0x204c (fffff880`0321804c)
SYMBOL_STACK_INDEX:  3
SYMBOL_NAME:  nvkflt+18fec
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: nvkflt
IMAGE_NAME:  nvkflt.sys
DEBUG_FLR_IMAGE_TIMESTAMP:  534455e8
FAILURE_BUCKET_ID:  X64_0x7f_8_nvkflt+18fec
BUCKET_ID:  X64_0x7f_8_nvkflt+18fec
ANALYSIS_SOURCE:  KM
FAILURE_ID_HASH_STRING:  km:x64_0x7f_8_nvkflt+18fec
FAILURE_ID_HASH:  {852d6a08-1c03-cc24-3abf-2b8e31df551a}
Followup: MachineOwner
---------

Similar Messages

  • Random BSOD after installing port replicator drivers.

    Hi, my boss just got a new laptop (TP T400s running Windows 7) and after configuring it, it was working fine. But then I installed the drivers for the USB port replicator with digital video and after rebooting, right after the login screen, it BSOD, complaining about igdkmd64.sys. Rebooted again, it didn't crashed upon login this time, just a little while later when clicking on the start menu. After more test, the replicator seemed to work, but not the digital video port. The DVI connector didn't worked correctly, just the mouse pointer was being displayed. Trying to set resolution didn't do anything and switching output source via Win-P provoked a strange flickering for a minute or so and then the machine automatically rebooted. Tried the driver found on the CD (1.0) and also those available through Lenovo website (1.5.6.8), always the same thing. Now I've uninstalled the drivers and the random BSOD keep reappearing.
    Is this issue common? Is the port replicator faulty or is it the ThinkPad? Is the windows installation screwed, can it be repaired? What is Lenovo return policy?
    I've also seen lots of complaints on this forum about random shutdown, this would be as unacceptable for us than the current BSOD we're experiencing. Is that situation widespread?
    P.S.: We're trying to get work done, not beta test Lenovo products!
    Thanks
    Solved!
    Go to Solution.

    nbuduroi wrote:
    Hi, my boss just got a new laptop (TP T400s running Windows 7) and after configuring it, it was working fine. But then I installed the drivers for the USB port replicator with digital video and after rebooting, right after the login screen, it BSOD, complaining about igdkmd64.sys. Rebooted again, it didn't crashed upon login this time, just a little while later when clicking on the start menu. After more test, the replicator seemed to work, but not the digital video port. The DVI connector didn't worked correctly, just the mouse pointer was being displayed. Trying to set resolution didn't do anything and switching output source via Win-P provoked a strange flickering for a minute or so and then the machine automatically rebooted. Tried the driver found on the CD (1.0) and also those available through Lenovo website (1.5.6.8), always the same thing. Now I've uninstalled the drivers and the random BSOD keep reappearing.
    Is this issue common? Is the port replicator faulty or is it the ThinkPad? Is the windows installation screwed, can it be repaired? What is Lenovo return policy?
    I've also seen lots of complaints on this forum about random shutdown, this would be as unacceptable for us than the current BSOD we're experiencing. Is that situation widespread?
    P.S.: We're trying to get work done, not beta test Lenovo products!
    Thanks
    The win7 driver for the usb port replicator with digital output is not out yet. So, you cannot get it work under win7. I recall seeing an official flyer of the product, in which there is a line stating that a win7 driver will be out in December.

  • Disgusted with HP Elite m9280a constant/random freezes, lock ups, BSOD, black screen

    constant/random freezes, lock ups, BSOD, black screen.
    I have been trying to trouble shoot this PC for almost a day now. weird problems like when 3 sticks of memory is present it wil not boot but it will boot on 1 and on 2 sticks will have hangs?
    disappointed tot the max... u think HP TOTAL CARE  - u pay extra thinking u are going to get a decent system...
    i have run diagnostics on all major components... still no luck
    someone please help - i have never spent sooo much time trying to repair a pc

    Try this bootable memory diagnostic tool: 
    Download memtest86 iso file and burn it to disk using Imgburn.
    HP DV9700, t9300, Nvidia 8600, 4GB, Crucial C300 128GB SSD
    HP Photosmart Premium C309G, HP Photosmart 6520
    HP Touchpad, HP Chromebook 11
    Custom i7-4770k,Z-87, 8GB, Vertex 3 SSD, Samsung EVO SSD, Corsair HX650,GTX 760
    Custom i7-4790k,Z-97, 16GB, Vertex 3 SSD, Plextor M.2 SSD, Samsung EVO SSD, Corsair HX650, GTX 660TI
    Windows 7/8 UEFI/Legacy mode, MBR/GPT

  • After applying update my apple tv2 will randomly go to a black screen that lasts for a few seconds. When it gets back to normal after a few seconds it acts like the video never stopped since its farther along in the timeline. This happens with all video c

    After applying update my apple tv2 will randomly go to a black screen that lasts for a few seconds. When it gets back to normal after a few seconds it acts like the video never stopped since its farther along in the timeline. This happens with all video content wether its from Netflix or streaming from my iTunes library

    You might try restarting the Apple TV by removing ALL the cables for a 30 seconds. If that doesn't help try using another HDMI cable.

  • Error launching Premiere Pro CS6 due to non-capable video drivers

    Premiere Pro not finding any capable video drivers.   I am newly subscribed to the CS6 Creative Cloud and using a brand new Toshiba i7 windows laptop. When I try to launch Premiere Pro, I get the error message -" could not find any capable video display modules. Please update your video display drivers and start again."   This is the only/first Adobe program that I have installed so far besides the Adobe Application Manager on this machine. I believe the i7 controller should be able to handle this.  What next?

    More hardware information needed... ESPECIALLY the brand/model graphics adapter in that laptop, and the driver version
    Read http://forums.adobe.com/message/4200840
    Also, some laptop information...
    For effective HD video editing, a laptop with the following
    -at least the Intel sandy bridge 2720 or 2820 quad processor
    -1280x900 display with OpenGL 2.0-compatible graphics card
    -and 8 or 16 gig ram and Win7 64bit Pro
    -and 2 internal 7200 HDDs minimum
    Does your graphics adapter "card or motherboard chip" and display match what I bolded?
    Dual laptop video http://forums.adobe.com/thread/1001579
    -Use BIOS http://forums.adobe.com/thread/1019004?tstart=0

  • Boot Camp Video Drivers

    Where can I find updated Boot Camp Video drivers? I want to update my video drivers on my MacBook running Boot Camp w/ Windows XP. Can I download XP video drivers from nVidia and install?

    Hi there,
    I recently had XP on my Macbook pro (Late 08) and wanted to update the nvidia GPU drivers. So all I had to do was get the "Correct" ones from the nvidia website and just installed them like normal.
    That being said, I ran into some problems with Windows Vista 64. Constant crashing when booting into the desktop due to incompatible graphics drivers. So what I had to do there was enter the device manager and "Roll back" the graphics driver. THEN restart in safemode and install the updated graphics driver.
    Maybe give that a try and see what happens? Hope we could help you...
    Tony

  • MSI Z97 MPOWER MAX AC, getting Random Bsod

    I installed my new msi z97 mpower and i7 4790k and iv gotten random bsod, mostly when running youtube videos in fullscreen 1080p and when i tried to defrag my hdd i always got bsod. I formated everything and only installed the LAN driver from my dvd so i could get internet going and then i updated all up to windows 8.1, wich i then proceded to download the drivers from MSI Updater Live.
    Main Board: MSI Z97 MPOWER MAX AC
    Bios Version: 1.60
    Video Card: Gigabyte GeForce GTX 980 4GB G1 Gaming
    PSU:   Corsair AX 850W 80+ Gold
    12v rail Rating of listed PSU:
    CPU: Intel Core i7 4790K 4GHz, 8MB
    Memory:Corsair 16GB (4x4GB) CL9 1600Mhz VENGEANCE Quad Channel
    SSD/ HDD: Corsair SSD Force 3 Series 180GB + 2TB WD Black 7200rpm 64MB
    CPU COOLER: Corsair Hydro H100
    Raid Card: None
    Sound Card: None
    Any Additional hardware plugged into your system: Gigabyte GTX 980
    OC: No
    Operating System: Windows 8.1 64bit
    Drivers i have installed:
    The bsod I'v gotten since i formated my harddrives, using WhoCrashed:
    (This happen when i was typing this thread and it also knocked my mouse and keyboard out so i had to change their usb slots to make them work again)
    I'v watched some other threads who had similar problems but i couldnt come to a conculsion on what problem i had, so any help would be very appriecated.

    I have not tried the clear cmos guide and I will try it.
    I have tried memtest, and passed. But iv only let it pass once after closing it because I didnt know how it worked.
    Its 4x4gb singlekit. I will try the 'Exclude method' next
    Here is the messages i got after clearing cmos
    Edit: Clearing CMOS did not solve my problem.

  • BSOD when on Skype Video call

    So I just recently started to get frequent BSODs when on a video call. I believe it has to do with my Logitech webcam, because I can Audio call (No video at all) with no problem, but if I turn on the camera, a few minutes later, i just randomly get the BSOD.
    I do have this file from the last BSOD. I got it when in a game while video calling, but the error is the same, so I know it's not the games or anything. 
    =================================================================
    Problem signature:
      Problem Event Name: BlueScreen
      OS Version: 6.1.7600.2.0.0.768.3
      Locale ID: 1033
    Additional information about the problem:
      BCCode: 1000007e
      BCP1: FFFFFFFFC0000005
      BCP2: FFFFF88004BE561A
      BCP3: FFFFF880033C4658
      BCP4: FFFFF880033C3EC0
      OS Version: 6_1_7600
      Service Pack: 0_0
      Product: 768_1
    Files that help describe the problem:
      C:\Windows\Minidump\010714-31855-01.dmp
      C:\Users\Matt\AppData\Local\Temp\WER-86050-0.sysdata.xml
    Read our privacy statement online:
      http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409
    If the online privacy statement is not available, please read our privacy statement offline:
      C:\Windows\system32\en-US\erofflps.txt
    ==================================================================
    The .dmp file is here: https://skydrive.live.com/redir?resid=3533AA13C3B40212!107&authkey=!AJH3kGYMbTnw1jM&ithint=file%2c.dmp
    I couldn't get it to open or anything, so I figured someone else could. I really need help here. I usually know my way around these issues but this one's got me stumped..
    Thanks for any help possible. Really appreciate it.

    Matthew
    This one crash was Related to
    stdriver64.sys stdriver.sys from NCH Software  I would remove it at least to test. 
    You also have other drivers needing updating because you have not installed SP-1.  You need to asap
    Service pack 1 Update.
    http://windows.microsoft.com/installwindows7sp1
    Learn how to install Windows 7 Service Pack 1 (SP1)
    http://windows.microsoft.com/en-US/windows7/learn-how-to-install-windows-7-service-pack-1-sp1
    Additional Resources:
    http://windows.microsoft.com/en-US/windows7/uninstall-sp1
    http://windows.microsoft.com/troubleshootwindows7sp1
    Microsoft (R) Windows Debugger Version 6.3.9600.16384 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    Loading Dump File [C:\Users\Ken\Desktop\010714-31855-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    ************* Symbol Path validation summary **************
    Response Time (ms) Location
    Deferred SRV*H:\symbols*http://msdl.microsoft.com/download/symbols
    Symbol search path is: SRV*H:\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.17118.amd64fre.win7_gdr.120830-0334
    Machine Name:
    Kernel base = 0xfffff800`0360b000 PsLoadedModuleList = 0xfffff800`03847e70
    Debug session time: Tue Jan 7 17:10:45.288 2014 (UTC - 5:00)
    System Uptime: 0 days 0:31:08.334
    Loading Kernel Symbols
    *** WARNING: Unable to verify timestamp for stdriver64.sys
    *** ERROR: Module load completed but symbols could not be loaded for stdriver64.sys
    BugCheck 1000007E, {ffffffffc0000005, fffff88004be561a, fffff880033c4658, fffff880033c3ec0}
    Probably caused by : stdriver64.sys ( stdriver64+261a )
    Wanikiya and Dyami--Team Zigzag

  • Youtube is causing my video drivers to crash

    I have a 21.5-inch Imac that I purchased mid 2012. I have created a windows 7 partintion on my computer using Bootcamp. Occasionally, Youtube will cause my video drivers to crash, which also causes my computer to crash. I have updated as much as I could with flash, windows, and my bootcamp drivers, but it still happens. I believe this is due to outdated video drivers, I happen to know that there has not been an update to the bootcamp video drivers since 2011, while AMD has a far more recent driver update. If anyone knows another solution to this problem please let me know; however, I believe the problem is the outdated video drivers. Apple very much needs to remedy this situation, even if it is nt causing my specific issue.

    OK we all have acknowledged the problem, now are there any solutions out there besides switching to firefox? Does Safari have a Flashblock extension, are there any at the ap store, is there a work around or any other ideas? I do have one, if there are no other fix,then we must boycott youtube for the summer and try youtubes compitition. I know of three, never really gave them much of my time though. But seeing as how I'm being forced to by YouTube, I'm sure their compitition would appreciate their, umm, sporting gesture in forcing us to switch

  • Random BSOD/Crackle Pop in BF2/BSOD in BF2142 on X-FI Fatality FPS Champ

    Using latest drivers from Creative v2.9.7 not the June/July update through windows update because it kills the DTS and makes the sound sound all monolike. Ok so here it goes, the driver support says that the latest should've fixed the BF2 crack/snap/pop sounds but I just reinstalled the game recently and I still hear it even with the current version I use so I guess it isn't fixed. 2nd issue is when setting it audio to x-fi with Ultra High, it BSOD's after awhile or so of playing with ha20x2k.sys. Also I get random BSOD's from doing various things such as I could be watching a movie then wanted to play a game or something then a BSOD occurs thereafter with ha20x2k.sys issue again. No this doesn't happen all the time just after my computer has been used for a few days and when I have been listening to various audio's from being a movie or music. On some games it just gives BSOD as if it were random. After a quick reboot I can play the game fine so I just know it's random to the point where it can happen if maybe multiple files with audio are initiated either it being a game and/or movie. And last issue is BF242. I find it funny how it says certified for 242 and/or best heard with on X-fi and yet it gives these casual BSOD after playing for an hour or so using X-FI ultra high settings. I was wondering what can be done to fix any of the 3 possible issues already said on the topic. Yes I've reinstalled them again and still no go. I only have the drivers instealled, EAX, audio console, volume properties, DTS NEO:6, and GO launcher v5.0. Everything else I got rid of... so if anyone knows of a solution or suggestion please let me know. Thanks. P.S. Was looking around but I don't see a Fatality FPS Champion edition no more. Only Xtremegamer Fatality... discontinued? Problem related issues?

    Using latest drivers from Creative v2.9.7 not the June/July update through windows update because it kills the DTS and makes the sound sound all monolike. Ok so here it goes, the driver support says that the latest should've fixed the BF2 crack/snap/pop sounds but I just reinstalled the game recently and I still hear it even with the current version I use so I guess it isn't fixed. 2nd issue is when setting it audio to x-fi with Ultra High, it BSOD's after awhile or so of playing with ha20x2k.sys. Also I get random BSOD's from doing various things such as I could be watching a movie then wanted to play a game or something then a BSOD occurs thereafter with ha20x2k.sys issue again. No this doesn't happen all the time just after my computer has been used for a few days and when I have been listening to various audio's from being a movie or music. On some games it just gives BSOD as if it were random. After a quick reboot I can play the game fine so I just know it's random to the point where it can happen if maybe multiple files with audio are initiated either it being a game and/or movie. And last issue is BF242. I find it funny how it says certified for 242 and/or best heard with on X-fi and yet it gives these casual BSOD after playing for an hour or so using X-FI ultra high settings. I was wondering what can be done to fix any of the 3 possible issues already said on the topic. Yes I've reinstalled them again and still no go. I only have the drivers instealled, EAX, audio console, volume properties, DTS NEO:6, and GO launcher v5.0. Everything else I got rid of... so if anyone knows of a solution or suggestion please let me know. Thanks. P.S. Was looking around but I don't see a Fatality FPS Champion edition no more. Only Xtremegamer Fatality... discontinued? Problem related issues?

  • Randomly BSODs caused by ntoskrnl.exe

    I have random BSODs, this is the dump file... any ideas? I tried to update all drivers, but I solved nothing.
    Microsoft (R) Windows Debugger Version 6.3.9600.17029 X86
    Copyright (c) Microsoft Corporation. All rights reserved.
    Loading Dump File [C:\Program Files (x86)\Windows Kits\8.1\Debuggers\x86\061114-29937-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    Error: Attempts to access '061114-29937-01.dmp' failed: 0x0 - The operation completed successfully.
    ************* Symbol Path validation summary **************
    Response                         Time (ms)     Location
    Error                                          061114-29937-01.dmp
    Symbol search path is: 061114-29937-01.dmp
    Executable search path is:
    Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
    Windows 8 Kernel Version 9600 MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 9600.17085.amd64fre.winblue_gdr.140330-1035
    Machine Name:
    Kernel base = 0xfffff800`6e28e000 PsLoadedModuleList = 0xfffff800`6e5582d0
    Debug session time: Wed Jun 11 20:29:12.062 2014 (UTC + 2:00)
    System Uptime: 0 days 0:22:21.219
    Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
    Loading Kernel Symbols
    Loading User Symbols
    Loading unloaded module list
    ************* Symbol Loading Error Summary **************
    Module name            Error
    ntoskrnl               The system cannot find the file specified
    You can troubleshoot most symbol related issues by turning on symbol loading diagnostics (!sym noisy) and repeating the command that caused symbols to be loaded.
    You should also verify that your symbol search path (.sympath) is correct.
    *                        Bugcheck Analysis                                   
    Use !analyze -v to get detailed debugging information.
    BugCheck 133, {1, 1e00, 0, 0}
    ***** Kernel symbols are WRONG. Please fix symbols to do analysis.
    ***    Either you specified an unqualified symbol, or your debugger   ***
    ***    doesn't have full symbol information.  Unqualified symbol      ***
    ***    resolution is turned off by default. Please either specify a   ***
    ***    fully qualified symbol module!symbolname, or enable resolution ***
    ***    of unqualified symbols by typing ".symopt- 100". Note that   ***
    ***    enabling unqualified symbol resolution with network symbol     ***
    ***    server shares in the symbol path may cause the debugger to     ***
    ***    appear to hang for long periods of time when an incorrect      ***
    ***    symbol name is typed or the network symbol server is down.     ***
    ***    For some commands to work properly, your symbol path           ***
    ***    must point to .pdb files that have full type information.      ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                         
    ***    Type referenced: nt!_KPRCB                                    
    5 times more...
    ***    Either you specified an unqualified symbol, or your debugger   ***
    ***    doesn't have full symbol information.  Unqualified symbol      ***
    ***    resolution is turned off by default. Please either specify a   ***
    ***    fully qualified symbol module!symbolname, or enable resolution ***
    ***    of unqualified symbols by typing ".symopt- 100". Note that   ***
    ***    enabling unqualified symbol resolution with network symbol     ***
    ***    server shares in the symbol path may cause the debugger to     ***
    ***    appear to hang for long periods of time when an incorrect      ***
    ***    symbol name is typed or the network symbol server is down.     ***
    ***    For some commands to work properly, your symbol path           ***
    ***    must point to .pdb files that have full type information.      ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                         
    ***    Type referenced: nt!_KPRCB                                    
    Probably caused by : ntoskrnl.exe ( nt+153fa0 )
    Followup: MachineOwner
    Systeminfo:
    OS Name:                   Microsoft Windows 8.1 Pro
    OS Version:                6.3.9600 N/A Build 9600
    OS Manufacturer:           Microsoft Corporation
    OS Configuration:          Standalone Workstation
    OS Build Type:             Multiprocessor Free
    Original Install Date:     30/10/2013, 13:43:05
    System Boot Time:          11/06/2014, 20:29:52
    System Manufacturer:       TOSHIBA
    System Model:              Satellite L500
    System Type:               x64-based PC
    Processor(s):              1 Processor(s) Installed.
                               [01]: Intel64 Family 6 Model 37 Stepping 2 GenuineIntel ~2261 Mhz
    BIOS Version:              TOSHIBA 2.10, 17/05/2011
    Windows Directory:         C:\WINDOWS
    System Directory:          C:\WINDOWS\system32
    Boot Device:               \Device\HarddiskVolume2
    Total Physical Memory:     3.958 MB
    Available Physical Memory: 1.792 MB
    Virtual Memory: Max Size:  7.926 MB
    Virtual Memory: Available: 5.492 MB
    Virtual Memory: In Use:    2.434 MB
    Page File Location(s):     C:\pagefile.sys
    Domain:                    WORKGROUP
    Logon Server:             
    \\MicrosoftAccount
    Hotfix(s):                 56 Hotfix(s) Installed.
                               [01]: KB2899189_Microsoft-Windows-CameraCodec-Package
                               [02]: KB2843630
                               [03]: KB2868626
                               [04]: KB2883200
                               [05]: KB2887595
                               [06]: KB2889543
                               [07]: KB2891214
                               [08]: KB2893294
                               [09]: KB2894029
                               [10]: KB2894179
                               [11]: KB2898868
                               [12]: KB2900986
                               [13]: KB2901125
                               [14]: KB2901128
                               [15]: KB2903939
                               [16]: KB2904440
                               [17]: KB2911106
                               [18]: KB2912390
                               [19]: KB2913152
                               [20]: KB2916036
                               [21]: KB2919355
                               [22]: KB2919394
                               [23]: KB2919442
                               [24]: KB2920189
                               [25]: KB2923528
                               [26]: KB2923768
                               [27]: KB2926765
                               [28]: KB2928680
                               [29]: KB2931358
                               [30]: KB2931366
                               [31]: KB2939153
                               [32]: KB2939576
                               [33]: KB2950153
                               [34]: KB2953522
                               [35]: KB2954879
                               [36]: KB2955164
                               [37]: KB2956575
                               [38]: KB2957151
                               [39]: KB2957189
                               [40]: KB2957689
                               [41]: KB2958262
                               [42]: KB2959977
                               [43]: KB2961908
                               [44]: KB2962140
                               [45]: KB2964718
                               [46]: KB2964736
                               [47]: KB2965065
                               [48]: KB2965142
                               [49]: KB2965500
                               [50]: KB2965699
                               [51]: KB2965788
                               [52]: KB2966072
                               [53]: KB2966407
                               [54]: KB2966804
                               [55]: KB2969817
                               [56]: KB976002
    Network Card(s):           10 NIC(s) Installed.
                               [01]: Realtek PCIe FE Family Controller
                                     Connection Name: Ethernet
                                     DHCP Enabled:    Yes
                                     DHCP Server:     N/A
                                     IP address(es)
                               [02]: Realtek RTL8191SE Wireless LAN 802.11n PCI-E NIC
                                     Connection Name: Wi-Fi
                                     Status:          Hardware
    not present
                               [03]: Hyper-V Virtual Ethernet Adapter
                                     Connection Name: Ethernet 6
                                     Status:          Media
    disconnected
                               [04]: Hyper-V Virtual Ethernet Adapter
                                     Connection Name: Ethernet 3
                                     Status:          Media
    disconnected
                               [05]: Hyper-V Virtual Ethernet Adapter
                                     Connection Name: Ethernet 5
                                     DHCP Enabled:    Yes
                                     DHCP Server:     192.168.1.1
                                     IP address(es)
                                     [01]: 192.168.1.129
                                     [02]: fe80::1513:f368:3c1e:c173
                               [06]: Hyper-V Virtual Ethernet Adapter
                                     Connection Name: Ethernet 4
                                     DHCP Enabled:    No
                                     IP address(es)
                                     [01]: 169.254.80.80
                                     [02]: fe80::4892:9cb3:7a80:2057
                               [07]: VMware Virtual Ethernet Adapter for VMnet1
                                     Connection Name: VMware Network Adapter VMnet1
                                     DHCP Enabled:    No
                                     IP address(es)
                                     [01]: 192.168.223.1
                                     [02]: fe80::a11c:f4d5:c02f:9fcf
                               [08]: VMware Virtual Ethernet Adapter for VMnet8
                                     Connection Name: VMware Network Adapter VMnet8
                                     DHCP Enabled:    No
                                     IP address(es)
                                     [01]: 192.168.132.1
                                     [02]: fe80::fc9a:9075:a71e:776c
                               [09]: TAP-Windows Adapter V9
                                     Connection Name: Local Area Connection 3
                                     Status:          Media
    disconnected
                               [10]: Hyper-V Virtual Ethernet Adapter
                                     Connection Name: vEthernet (TAP-Windows Adapter V9 Virtual Switch)
                                     Status:          Media
    disconnected
    Hyper-V Requirements:      A hypervisor has been detected. Features required for Hyper-V will not be displayed.

    Hi,
    In order to assist you, we will need the .DMP files to analyze what exactly occurred at the time of the crash, etc.
    If you don't know where .DMP files are located, here's how to get to them:
    1. Navigate to the %systemroot%\Minidump folder.
    2. Copy any and all DMP files in the Minidump folder to your Desktop and then zip up these files.
    3. Upload the zip containing the .DMP files to Onedrive or a hosting site of your choice and paste in your reply. Preferred sites: Onedrive, Mediafire, Dropbox, etc. Nothing with wait-timers, download managers, etc.
    4 (optional): The type of .DMP files located in the Minidump folder are known as Small Memory Dumps. In %systemroot% there will be what is known as a Kernel-Dump (if your system is set to generate). It is labeled MEMORY.DMP. The difference
    between Small Memory Dumps and Kernel-Dumps in the simplest definition is a Kernel-Dump contains
    much more information at the time of the crash, therefore allowing further debugging of your issue. If your upload speed permits it, and you aren't going against any strict bandwidth and/or usage caps, etc, the Kernel-Dump is the best
    choice. Do note that Kernel-Dumps are much larger in size due to containing much more info, which is why I mentioned upload speed, etc.
    If you are going to use Onedrive but don't know how to upload to it, please visit the following:
    Upload photos and files to Onedrive.
    After doing that, to learn how to share the link to the file if you are unaware, please visit the following link -
    Share files and folders and change permissions and view 'Get a link'.
    Please note that any "cleaner" programs such as TuneUpUtilities, CCleaner, etc, by default will delete .DMP files upon use. With this said, if you've run such software, you will need to allow the system to crash once again to generate a crash dump.
    If your computer is not generating .DMP files, please do the following:
    1. Start > type %systemroot% which should show the Windows folder, click on it. Once inside that folder, ensure there is a Minidump folder created. If not, CTRL-SHIFT-N to make a New Folder and name it Minidump.
    2. Windows key + Pause key. This should bring up System. Click Advanced System Settings on the left > Advanced > Performance > Settings > Advanced > Ensure there's a check-mark for 'Automatically manage paging file size for all
    drives'.
    3. Windows key + Pause key. This should bring up System. Click Advanced System Settings on the left > Advanced > Startup and Recovery > Settings > System Failure > ensure there is a check mark next to 'Write an event to the system
    log'.
    Ensure Small Memory Dump is selected and ensure the path is %systemroot%\Minidump.
    4. Double check that the WERS is ENABLED:
    Start > Search > type services.msc > Under the name tab, find Windows Error Reporting Service > If the status of the service is not Started then right click it and select Start. Also ensure that under Startup Type it is set to Automatic rather than
    Manual. You can do this by right clicking it, selecting properties, and under General selecting startup type to 'Automatic', and then click Apply.
    If you cannot get into normal mode to do any of this, please do this via Safe Mode.
    Regards,
    Patrick
    “Be kind whenever possible. It is always possible.” - Dalai Lama

  • Gt70 dragon edition 2 random bsod

    hello everyone ,, 4 days ago i bought a new msi gt70 dragon edition 2 with these system specs
    i7-4700mq processor
    nividia geforce gtx780m
    750gb +128g ssd(super raid)
    ram 32gb
    os: windows 8
    and i got random BSOD's a lot until now i got like 8 BSOD's and it just happens randomly .. i tried a lot of thing ,, changing drivers , deleting programs and even the (Killer's network drivers only [without software suite])
    driver ... please tell me what to do .. this is the dump file to read the error or something like that
    although i tried attaching the file on the post but i couldn't so i guess i'll have to upload it to mediafire
    www(.)mediafire(.)com/download/d82175lxyof34zd/SF_04-01-2014.zip   <<< please remove the () between the .
    guys please tell me if it's something related to the hardware so i could replace the laptop itself within the given days because i bought it couple days ago

    Okay. I see the confusion. He is using the drivers that Svet recommended. Which are slightly newer than your own, but are also without the Killer Network Manager and must be installed manually. (10.0.1.263 for the Wireless and 8.0.2.42 for the e2200)
    My issues with the wireless seemed to go away with Svet's drivers - which was essentially a newer download pinned to the forums of what Warner gave to you. He could give Warner's a try but they basically are the same. I assumed my issue didn't go away as I was having another BSOD issue that didn't exactly specify which device was causing the BSOD.
    As for my issue - I have uninstalled the Logitech software and haven't had a crash within the past day and a half. I noticed the longer I have the laptop on, the more likely the BSOD. So, I am leaving it on all day playing games off and on.
    I did notice that SetPoint does install software that is meant for keyboards. Simply because Logitech has a unified driver suite between their mice and keyboards able to use a single wireless dongle, eliminating the need to use one for each device. This could, in theory, be causing an issue with the MSI SCM. Most people think of the SCM as a control app, but it also installs a service (called Micro Star SCM) which handles event communication between several different driver packages/software. This is why when the SCM is uninstalled, the keyboard light manager fails to start up as well as Hybrid Power and a few other MSI apps. If uninstalling the Logitech software does work, then it could be that the keyboard manager in SetPoint is intercepting events that should be going to the SCM service.
    If it crashes again, I will swap out the mouse itself. I'll update my thread on this issue on the next crash or in a few days if I have no further issues. I'm crossing my fingers and thanks for the tips.

  • P67A-GD55 - Random BSODs with varying codes

    Hey guys,
    I'm sort of reaching the end of the line with my troubleshooting resources, so I'm hoping someone here can possibly provide me a little assistance.  As the title indicates, I'm experiencing random BSODs on a newly built system.  Below is what I have done to troubleshoot, as well as the specs.
    MOBO - MSI P67A-GD55 (B3)
    CPU - Intel Core i5 - PN BX80623I52500K
    PSU - CORSAIR HX Series CMPSU-850HX 850W
    Memory - Corsair XMS3 DDR3 1333 (2x4GB) - PN CMX8GX3M2A1333C9
    HD - OCZ Vertex Series OCZSSD2-1VTX30GXXX SSD
    HD - Seagate Barracuda 7200.12 ST31000528AS x2 (Raid 0)
    Video - EVGA 01G-P3-1373-AR GeForce GTX 460
    Updated all drivers to current revisions
    Updated BIOS to latest revision
    memtest86 - Over 24 hours of testing, all testing options, 10x passes - No errors
    Windows Memory Tester - Over 24 hours of testing, full options - No errors
    PSU Test - Checked every connection coming off of the PSU and all voltages are appropriate
    Just for fun I've run the system with memory in varying slots and with varying sticks.  No dice.
    superpi - I've run this up to 32m on all cores on the CPU multiple times just to see if this causes any crashes despite the CPU being at stock config.  - No errors
    BSODs I have seen:
    APC_INDEX_MISMATCH
    MEMORY_MANAGEMENT
    SYSTEM_SERVICE_EXCEPTION
    dxgmms1.sys
    And about 12 others that I didn't note at the time for some reason.
    Other odd behavior:
    After some BSODs, the system rediscovers all my USB devices that I have attached.
    I've done research on the individual codes, but the solutions are like throwing darts at a dart board.  I'm suspecting at this point that I either have a bad CPU or Mobo.
    Also note that nothing is overclocked.
    Any thoughts or ideas?
    TYVM in advance.
    -JT

    Quote from: Somewords on 07-May-11, 06:47:01
    PSU - CORSAIR HX Series CMPSU-850HX 850W
    is your psu over powered?
    mine is 500w silverstone.
    running i5 2400
    gskill 4gbx2 10666cl7
    palit 550 ti sonic
    wd cavier blue 320gb 6gb/s and seagate 320gb 3gb/s
    sony dvd-rw lightscribe

  • Tecra M3 video drivers causing crashes

    My Toshiba Tecra M3 is crashing (freezing or blue screen of death) with drivers 71.14, 71.36, and 76.44. It uses an NVIDIA GeForce Go 6600 TE 128M. When I uninstall all video drivers (or boot into safe mode), the laptop runs fine, although of course scrolling is deadly slow and I can't suspend or hibernate. But when I install either of the two WHQL certified drivers from Toshiba's site, 71.44 or 71.36, I can consistently create a crash just by running a 3D screensaver for more than 3 minutes. The same thing happens with the 76.44 non-WHQL driver from laptopvideo2go.com.
    Sorry if this is not the best thread to post on, but I would desperately appreciate any help you can offer on what driver might work reliably. At this point, I'm not at all interested in great graphics performance; I just want a stable laptop to do some work on. Is there perhaps some setting within the driver to turn off whatever fancy features are causing the crash?
    The laptop has a 2.13 GHz Pentium M and 2 GB of RAM. It's running WinXP SP2 with all updates and is using BIOS 1.20, the latest. And I doubt it's a related, but here's a different problem I ran into with the VPN, Wi-Fi, and Matlab.
    Thanks in advance for any help you can provide.
    [Edited by: admin]

    Hi danhkon
    I suppose that your notebook worked properly at the beginning. Can you maybe remember since when the unit started to make these troubles to you? It is not easy to give you a proper opinion or any kind of solution because every problem is caused by some reason.
    First of all I want to say that you should use just display driver given by Toshiba and not some driver that you found on the net. The drivers that you got on Tools & utilities CD or drivers that you can find on Toshiba site are all tested and they should work properly. As far as I know Tecra M3 is a new model and also delivered with SP2. That means that all drivers are also tested to work properly with SP2.
    Before you spend lot of times searching the right solution you should, in my opinion, save your data and reinstall OS using Recovery CD. On this way you will have a stable laptop to do some work on it. If there is no second partition you can make it for data saving using expert mode installation.

  • Windows server 2012 R2 randomly BSOD's

    Dear all,
    Since recently we suffering from random BSOD's on a Windows 2012 R2 terminal server. We already checked if there has been any changes, updates, new drivers installed, etc. around the time we receive the first one, but we cannot find anything. The server
    is a virtual server on Hyper-V but the Hyper-V host doesn't suffer from BSOD's and is working properly. We updated the servers with newest windows updates. Could someone please help me debugging this minidump:
    Loading Dump File [C:\Users\admtem\Desktop\031915-48906-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    ************* Symbol Path validation summary **************
    Response Time (ms) Location
    Deferred srv*c:\cache*http://msdl.microsoft.com/download/symbols
    Symbol search path is: srv*c:\cache*http://msdl.microsoft.com/download/symbols
    Executable search path is:
    Windows 8 Kernel Version 9600 MP (16 procs) Free x64
    Product: Server, suite: TerminalServer
    Built by: 9600.17668.amd64fre.winblue_r8.150127-1500
    Machine Name:
    Kernel base = 0xfffff801`f4489000 PsLoadedModuleList = 0xfffff801`f4762250
    Debug session time: Thu Mar 19 01:55:51.856 2015 (UTC + 1:00)
    System Uptime: 0 days 2:21:59.525
    Loading Kernel Symbols
    Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
    Run !sym noisy before .reload to track down problems loading symbols.
    Loading User Symbols
    Loading unloaded module list
    * Bugcheck Analysis *
    Use !analyze -v to get detailed debugging information.
    BugCheck A, {fffff90140599000, 2, 0, fffff801f45280ab}
    Probably caused by : ntkrnlmp.exe ( nt!KeSetEvent+3fb )
    Followup: MachineOwner
    6: kd> !analyze -v
    * Bugcheck Analysis *
    IRQL_NOT_LESS_OR_EQUAL (a)
    An attempt was made to access a pageable (or completely invalid) address at an
    interrupt request level (IRQL) that is too high. This is usually
    caused by drivers using improper addresses.
    If a kernel debugger is available get the stack backtrace.
    Arguments:
    Arg1: fffff90140599000, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000000, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
    Arg4: fffff801f45280ab, address which referenced memory
    Debugging Details:
    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff801f47ec138
    unable to get nt!MmNonPagedPoolStart
    unable to get nt!MmSizeOfNonPagedPoolInBytes
    fffff90140599000
    CURRENT_IRQL: 2
    FAULTING_IP:
    nt!KeSetEvent+3fb
    fffff801`f45280ab 488b09 mov rcx,qword ptr [rcx]
    CUSTOMER_CRASH_COUNT: 1
    DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP
    BUGCHECK_STR: AV
    PROCESS_NAME: System
    ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre
    TRAP_FRAME: ffffd00142686900 -- (.trap 0xffffd00142686900)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=ffffd001475bc4e8 rbx=0000000000000000 rcx=fffff90140599000
    rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff801f45280ab rsp=ffffd00142686a90 rbp=0000000000000000
    r8=0000000000000000 r9=fffff801f492c628 r10=fffff90140599000
    r11=ffffd00142686b00 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0 nv up ei pl nz ac po nc
    nt!KeSetEvent+0x3fb:
    fffff801`f45280ab 488b09 mov rcx,qword ptr [rcx] ds:fffff901`40599000=????????????????
    Resetting default scope
    LAST_CONTROL_TRANSFER: from fffff801f45e54e9 to fffff801f45d99a0
    STACK_TEXT:
    ffffd001`426867b8 fffff801`f45e54e9 : 00000000`0000000a fffff901`40599000 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
    ffffd001`426867c0 fffff801`f45e3d3a : 00000000`00000000 ffffd001`475bc4e0 ffffe001`26538900 ffffcf81`0df3afa0 : nt!KiBugCheckDispatch+0x69
    ffffd001`42686900 fffff801`f45280ab : 00000000`00002608 00000000`00000000 00000000`00000030 00000000`00000000 : nt!KiPageFault+0x23a
    ffffd001`42686a90 fffff801`f45343ac : fffff901`40599000 ffffe001`00000000 ffffe001`25f34800 fffff801`00000000 : nt!KeSetEvent+0x3fb
    ffffd001`42686b50 fffff801`f4561280 : 13131313`13131313 ffffe001`25f34880 00000000`00000080 ffffe001`25f34880 : nt!ExpWorkerThread+0x28c
    ffffd001`42686c00 fffff801`f45dffc6 : ffffd001`42040180 ffffe001`25f34880 ffffd001`4204c5c0 13131313`13131313 : nt!PspSystemThreadStartup+0x58
    ffffd001`42686c60 00000000`00000000 : ffffd001`42687000 ffffd001`42681000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16
    STACK_COMMAND: kb
    FOLLOWUP_IP:
    nt!KeSetEvent+3fb
    fffff801`f45280ab 488b09 mov rcx,qword ptr [rcx]
    SYMBOL_STACK_INDEX: 3
    SYMBOL_NAME: nt!KeSetEvent+3fb
    FOLLOWUP_NAME: MachineOwner
    MODULE_NAME: nt
    IMAGE_NAME: ntkrnlmp.exe
    DEBUG_FLR_IMAGE_TIMESTAMP: 54c832b2
    IMAGE_VERSION: 6.3.9600.17668
    BUCKET_ID_FUNC_OFFSET: 3fb
    FAILURE_BUCKET_ID: AV_VRF_nt!KeSetEvent
    BUCKET_ID: AV_VRF_nt!KeSetEvent
    ANALYSIS_SOURCE: KM
    FAILURE_ID_HASH_STRING: km:av_vrf_nt!kesetevent
    FAILURE_ID_HASH: {3ff99d47-0a85-0b19-f59a-c152651b9c12}
    Followup: MachineOwner
    Any help would be much appriciated!
    Kind Regards,
    Thijs

    Hi Thijs,
    Just addition, please also check if all necessary windows updates were installed in this problematic server. Please check if drivers need to be updated.
    Please also refer to following thread and check if can help you.
    Blue Screen Error (Probably caused by : ntkrnlmp.exe)
    If this issues is a state of emergency for you. Please contact Microsoft Customer Service and Support (CSS) via telephone so that a dedicated Support Professional can assist with your request.
    To obtain the phone numbers for specific technology request, please refer to the web site listed below:
    http://support.microsoft.com/default.aspx?scid=fh;EN-US;OfferProPhone#faq607
    Best regards,
    Justin Gu
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Maybe you are looking for

  • Select query help for Sales order

    Hi Experts, I have to write a select query to fetch sales orders which are open along with the quantities which are open ( not delivered). What would the best approach for this? Any help is appreciated. Expecting code samples....Thanks Thanks Ricky

  • MacBook Pro Late 2013 retina randomly freezing

    Hi there, I recently purchased a pretty tricked out MacBook Pro 15" Retina from the refurbished store. Totally stoked to have it, and I was really enjoying the machine. However, I've been having these random lockups about once a day which is the only

  • Urgent : store and retrieve image to oracle database thru applet

    hi all i want the code sample for storing the image to oracle database development enviornment: server : oracle 9i , apache web server client : ie6 browser i am connecting to oracle database thru applet using oracle jdbc thin driver can anyone give m

  • HT1657 wont download error code .50

    any thoughts?

  • What is a flat file ?

    Hello sap experts Could you please explain me the concept of creating flat files ? what is the use and where do we use those? thankyou very much full points will be awarded bj