Solved BSOD during games, "display driver has stopped responding"

cycled

New Member
Messages
2
Hello,

I've come here as a last resort. I've been having issues with my computer which I've recently upgraded to Windows 8.1.

At random times usually during gameplay I will encounter a freeze or major slowdown that leads to the game crashing and seeing an error message that says "display driver NVIDIA windows kernel mode driver, version 344.11, has stopped responding and has successfully recovered".

Sometimes though I will get an entirely different problem, unsure if related. Computer will BSOD and WhoCrashed reports this as the issue:
GnrtFsU.png



What I have tried doing:

1. Reinstalled NVIDIA driver. Did not change anything.

2. Followed up on the crash dump by testing all my non-Microsoft drivers with Driver Verifier and after several BSODs this was the result:
dBCM16H.png


3. Set NVIDIA power management to prefer maximum performance.

4. Changed computer power settings to max performance.

Now I am stuck on what to do. I don't know what to do with the results from Driver Verifier. I'm still getting the driver recovered issue in games.

I've attached my dump files, in some of them you will see an issue caused by DroidCam. I have solved that problem already.

Thank you in advance,
- Cycle
 

My Computer

System One

  • OS
    Windows 8.1
    Computer type
    PC/Desktop
    CPU
    Core i5-4690 3.50GHz
    Motherboard
    Gigabyte Z97X-UD3H
    Memory
    2x 4GB G.SKILL Ripjaws X F3-12800CL9D DDR3-1600
    Graphics Card(s)
    GeForce GTX 660
    Monitor(s) Displays
    2
    PSU
    Corsair TX750W
Hi Cycled & Welcome to the forums ^_^,

I would try my best to help you sort out the issue. I have analysed your dump files and below has been provided an analysis of the same for informative purposes :-
Code:
**************************Sat Oct 11 00:35:30.706 2014 (UTC + 5:30)**************************
Loading Dump File [C:\SysnativeBSODApps\101014-8328-01.dmp]
 
Windows 8 Kernel Version 9600 MP (4 procs) Free x64
 
Built by: 9600.17238.amd64fre.winblue_gdr.140723-2018
 
System Uptime: 0 days 0:00:54.397
 
*** WARNING: Unable to verify timestamp for droidcam.sys
 
*** ERROR: Module load completed but symbols could not be loaded for droidcam.sys
 
Probably caused by : droidcam.sys ( droidcam+1179 )
 
BugCheck D5, {ffffcf80e106ef98, 0, fffff8012363d179, 0}
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x000000D5]DRIVER_PAGE_FAULT_IN_FREED_SPECIAL_POOL (d5)[/url]
 
Arguments: 
Arg1: ffffcf80e106ef98, memory referenced
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation
Arg3: fffff8012363d179, if non-zero, the address which referenced memory.
Arg4: 0000000000000000, (reserved)
BUGCHECK_STR:  0xD5
 
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
 
PROCESS_NAME:  System
 
FAILURE_BUCKET_ID:  0xD5_VRF_droidcam+1179
 
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sat Oct 11 00:34:16.265 2014 (UTC + 5:30)**************************
Loading Dump File [C:\SysnativeBSODApps\101014-8859-01.dmp]
 
Windows 8 Kernel Version 9600 MP (4 procs) Free x64
 
Built by: 9600.17238.amd64fre.winblue_gdr.140723-2018
 
System Uptime: 0 days 0:00:53.957
 
*** WARNING: Unable to verify timestamp for droidcam.sys
 
*** ERROR: Module load completed but symbols could not be loaded for droidcam.sys
 
Probably caused by : droidcam.sys ( droidcam+1179 )
 
BugCheck 50, {ffffcf80769bef98, 0, fffff80151de5179, 2}
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x00000050]PAGE_FAULT_IN_NONPAGED_AREA (50)[/url]
 
Arguments: 
Arg1: ffffcf80769bef98, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff80151de5179, If non-zero, the instruction address which referenced the bad memory
 address.
Arg4: 0000000000000002, (reserved)
BUGCHECK_STR:  AV
 
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
 
PROCESS_NAME:  System
 
FAILURE_BUCKET_ID:  AV_VRF_droidcam+1179
 
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sat Oct 11 00:33:02.261 2014 (UTC + 5:30)**************************
Loading Dump File [C:\SysnativeBSODApps\101014-8390-01.dmp]
 
Windows 8 Kernel Version 9600 MP (4 procs) Free x64
 
Built by: 9600.17238.amd64fre.winblue_gdr.140723-2018
 
System Uptime: 0 days 1:43:38.953
 
*** WARNING: Unable to verify timestamp for tcpip.sys
 
*** ERROR: Module load completed but symbols could not be loaded for tcpip.sys
 
Probably caused by : wfplwfs.sys ( wfplwfs!LwfLowerOidRequest+6e )
 
BugCheck C4, {91001, fffff800884ebe40, ffffe000a3dcb5a0, ffffe000a3dcb628}
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x000000C4]DRIVER_VERIFIER_DETECTED_VIOLATION (c4)[/url]
 
DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
 
Arguments: 
Arg1: 0000000000091001, ID of the 'NdisOidComplete' rule that was violated.
Arg2: fffff800884ebe40, A pointer to the string describing the violated rule condition.
Arg3: ffffe000a3dcb5a0, Address of internal rule state (second argument to !ruleinfo).
Arg4: ffffe000a3dcb628, Address of supplemental states (third argument to !ruleinfo).
BUGCHECK_STR:  0xc4_NdisOidComplete_XDV
 
PROCESS_NAME:  System
 
FAILURE_BUCKET_ID:  0xc4_NdisOidComplete_XDV_VRF_wfplwfs!LwfLowerOidRequest
 
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Fri Oct 10 22:49:04.450 2014 (UTC + 5:30)**************************
Loading Dump File [C:\SysnativeBSODApps\101014-7109-01.dmp]
 
Windows 8 Kernel Version 9600 MP (4 procs) Free x64
 
Built by: 9600.17238.amd64fre.winblue_gdr.140723-2018
 
System Uptime: 0 days 12:00:10.141
 
*** WARNING: Unable to verify timestamp for tcpip.sys
 
*** ERROR: Module load completed but symbols could not be loaded for tcpip.sys
 
Probably caused by : wfplwfs.sys ( wfplwfs!LwfLowerOidRequest+6e )
 
BugCheck C4, {91001, fffff80121170e40, ffffe000c1f3a3c0, ffffe000c1f3a448}
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x000000C4]DRIVER_VERIFIER_DETECTED_VIOLATION (c4)[/url]
 
DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
 
Arguments: 
Arg1: 0000000000091001, ID of the 'NdisOidComplete' rule that was violated.
Arg2: fffff80121170e40, A pointer to the string describing the violated rule condition.
Arg3: ffffe000c1f3a3c0, Address of internal rule state (second argument to !ruleinfo).
Arg4: ffffe000c1f3a448, Address of supplemental states (third argument to !ruleinfo).
BUGCHECK_STR:  0xc4_NdisOidComplete_XDV
 
PROCESS_NAME:  System
 
FAILURE_BUCKET_ID:  0xc4_NdisOidComplete_XDV_VRF_wfplwfs!LwfLowerOidRequest
 
CPUID:        "Intel(R) Core(TM) i5-4690 CPU @ 3.50GHz"
 
MaxSpeed:     3500
 
CurrentSpeed: 3500
 
  BIOS Version                  F7
 
  BIOS Release Date             06/17/2014
 
  Manufacturer                  Gigabyte Technology Co., Ltd.
 
  Product Name                  Z97X-UD3H
 
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Fri Oct 10 06:57:13.688 2014 (UTC + 5:30)**************************
Loading Dump File [C:\SysnativeBSODApps\100914-5812-01.dmp]
 
Windows 8 Kernel Version 9600 MP (4 procs) Free x64
 
Built by: 9600.17238.amd64fre.winblue_gdr.140723-2018
 
System Uptime: 5 days 2:04:41.140
 
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
 
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
 
Probably caused by : nvlddmkm.sys ( nvlddmkm+1c806d )
 
BugCheck 133, {0, 501, 500, 0}
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x00000133]DPC_WATCHDOG_VIOLATION (133)[/url]
 
Arguments: 
Arg1: 0000000000000000, A single DPC or ISR exceeded its time allotment. The offending
 component can usually be identified with a stack trace.
Arg2: 0000000000000501, The DPC time count (in ticks).
Arg3: 0000000000000500, The DPC time allotment (in ticks).
Arg4: 0000000000000000
BUGCHECK_STR:  0x133
 
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
 
PROCESS_NAME:  System
 
FAILURE_BUCKET_ID:  0x133_DPC_nvlddmkm+1c806d
 
CPUID:        "Intel(R) Core(TM) i5-4690 CPU @ 3.50GHz"
 
MaxSpeed:     3500
 
CurrentSpeed: 3500
 
  BIOS Version                  F7
 
  BIOS Release Date             06/17/2014
 
  Manufacturer                  Gigabyte Technology Co., Ltd.
 
  Product Name                  Z97X-UD3H
 
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Thu Oct  2 09:28:39.214 2014 (UTC + 5:30)**************************
Loading Dump File [C:\SysnativeBSODApps\100114-6875-01.dmp]
 
Windows 8 Kernel Version 9600 MP (4 procs) Free x64
 
Built by: 9600.17238.amd64fre.winblue_gdr.140723-2018
 
System Uptime: 0 days 20:57:59.882
 
Probably caused by : droidcamvide ( droidcamvide>+2a8d )
 
BugCheck CE, {fffff801a037ca8d, 8, fffff801a037ca8d, 0}
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x000000CE]DRIVER_UNLOADED_WITHOUT_CANCELLING_PENDING_OPERATIONS (ce)[/url]
 
Arguments: 
Arg1: fffff801a037ca8d, memory referenced
Arg2: 0000000000000008, value 0 = read operation, 1 = write operation
Arg3: fffff801a037ca8d, If non-zero, the instruction address which referenced the bad memory
 address.
Arg4: 0000000000000000, Mm internal code.
BUGCHECK_STR:  0xCE
 
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
 
PROCESS_NAME:  System
 
FAILURE_BUCKET_ID:  0xCE_droidcamvide_+2a8d
 
CPUID:        "Intel(R) Core(TM) i5-4690 CPU @ 3.50GHz"
 
MaxSpeed:     3500
 
CurrentSpeed: 3500
 
  BIOS Version                  F7
 
  BIOS Release Date             06/17/2014
 
  Manufacturer                  Gigabyte Technology Co., Ltd.
 
  Product Name                  Z97X-UD3H
 
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sun Sep 28 03:51:19.002 2014 (UTC + 5:30)**************************
Loading Dump File [C:\SysnativeBSODApps\092714-7250-01.dmp]
 
Windows 8 Kernel Version 9600 MP (4 procs) Free x64
 
Built by: 9600.17238.amd64fre.winblue_gdr.140723-2018
 
System Uptime: 0 days 4:03:43.668
 
*** WARNING: Unable to verify timestamp for e1i63x64.sys
 
*** ERROR: Module load completed but symbols could not be loaded for e1i63x64.sys
 
Probably caused by : e1i63x64.sys ( e1i63x64+4fc1a )
 
BugCheck 1E, {ffffffffc0000005, fffff80172c81c1a, ffffd0016e9a6748, ffffd0016e9a5f50}
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x0000001E]KMODE_EXCEPTION_NOT_HANDLED (1e)[/url]
 
Arguments: 
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80172c81c1a, The address that the exception occurred at
Arg3: ffffd0016e9a6748, Parameter 0 of the exception
Arg4: ffffd0016e9a5f50, Parameter 1 of the exception
BUGCHECK_STR:  0x1E_c0000005
 
PROCESS_NAME:  System
 
FAILURE_BUCKET_ID:  0x1E_c0000005_e1i63x64+4fc1a
 
CPUID:        "Intel(R) Core(TM) i5-4690 CPU @ 3.50GHz"
 
MaxSpeed:     3500
 
CurrentSpeed: 3500
 
  BIOS Version                  F7
 
  BIOS Release Date             06/17/2014
 
  Manufacturer                  Gigabyte Technology Co., Ltd.
 
  Product Name                  Z97X-UD3H
 
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sat Sep 27 23:47:26.814 2014 (UTC + 5:30)**************************
Loading Dump File [C:\SysnativeBSODApps\092714-7937-01.dmp]
 
Windows 8 Kernel Version 9600 MP (4 procs) Free x64
 
Built by: 9600.17238.amd64fre.winblue_gdr.140723-2018
 
System Uptime: 4 days 19:09:13.719
 
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
 
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
 
Probably caused by : nvlddmkm.sys ( nvlddmkm+2003ee )
 
BugCheck 133, {0, 501, 500, 0}
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x00000133]DPC_WATCHDOG_VIOLATION (133)[/url]
 
Arguments: 
Arg1: 0000000000000000, A single DPC or ISR exceeded its time allotment. The offending
 component can usually be identified with a stack trace.
Arg2: 0000000000000501, The DPC time count (in ticks).
Arg3: 0000000000000500, The DPC time allotment (in ticks).
Arg4: 0000000000000000
BUGCHECK_STR:  0x133
 
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
 
PROCESS_NAME:  System
 
FAILURE_BUCKET_ID:  0x133_DPC_nvlddmkm+2003ee
 
CPUID:        "Intel(R) Core(TM) i5-4690 CPU @ 3.50GHz"
 
MaxSpeed:     3500
 
CurrentSpeed: 3500
 
  BIOS Version                  F7
 
  BIOS Release Date             06/17/2014
 
  Manufacturer                  Gigabyte Technology Co., Ltd.
 
  Product Name                  Z97X-UD3H
 
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Below is a list of 3rd party drivers present on the system :-
Code:
**************************Sat Oct 11 00:35:30.706 2014 (UTC + 5:30)**************************
[COLOR=#0000FF][U][B]MO3v2Driver.sys             Mon Nov 22 07:50:58 2010 (4CE9D38A)
[/B][/U][/COLOR]speedfan.sys                Sun Dec 30 02:29:35 2012 (50DF59B7)
e1i63x64.sys                Wed Mar 20 13:07:29 2013 (51496739)
intelppm.sys                Thu Aug 22 14:16:35 2013 (5215CFEB)
dump_storahci.sys           Thu Aug 22 17:10:39 2013 (5215F8B7)
TeeDriverx64.sys            Thu Mar 13 23:51:52 2014 (5321F740)
[COLOR=#FF0000][B][U]droidcam.sys                Fri May  9 08:19:18 2014 (536C422E)
droidcamvideo.sys           Fri May 16 08:47:21 2014 (53758341)
[/U][/B][/COLOR]RTKVHD64.sys                Wed May 28 17:47:12 2014 (5385D3C8)
iwdbus.sys                  Wed Jun 18 03:24:22 2014 (53A0B90E)
aswHwid.sys                 Thu Jun 26 17:01:26 2014 (53AC048E)
aswMonFlt.sys               Thu Jun 26 17:02:51 2014 (53AC04E3)
aswRdr2.sys                 Thu Jun 26 17:03:28 2014 (53AC0508)
aswSnx.sys                  Thu Jun 26 17:04:44 2014 (53AC0554)
aswRvrt.sys                 Thu Jun 26 17:05:39 2014 (53AC058B)
aswVmm.sys                  Thu Jun 26 17:05:49 2014 (53AC0595)
aswStm.sys                  Thu Jun 26 17:17:09 2014 (53AC083D)
aswSP.sys                   Wed Jul  2 23:08:12 2014 (53B44384)
nvhda64v.sys                Mon Jul 21 19:47:53 2014 (53CD2111)
igdkmd64.sys                Tue Aug  5 21:17:18 2014 (53E0FC86)
rzendpt.sys                 Thu Aug 21 08:28:43 2014 (53F56063)
rzudd.sys                   Thu Aug 21 08:28:48 2014 (53F56068)
nvlddmkm.sys                Sun Sep 14 01:29:50 2014 (5414A236)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Fri Oct 10 06:57:13.688 2014 (UTC + 5:30)**************************
nvvad64v.sys                Thu Sep  4 22:40:48 2014 (54089D18)
NvStreamKms.sys             Fri Oct  3 07:09:09 2014 (542DFE3D)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Thu Oct  2 09:28:39.214 2014 (UTC + 5:30)**************************
ssudbus.sys                 Thu Jan  2 15:21:22 2014 (52C5369A)
ssudmdm.sys                 Thu Jan  2 15:21:26 2014 (52C5369E)
NvStreamKms.sys             Sat Sep  6 10:07:11 2014 (540A8F77)
http://www.carrona.org/drivers/driver.php?id=MO3v2Driver.sys
http://www.carrona.org/drivers/driver.php?id=speedfan.sys
http://www.carrona.org/drivers/driver.php?id=e1i63x64.sys
http://www.carrona.org/drivers/driver.php?id=intelppm.sys
http://www.carrona.org/drivers/driver.php?id=dump_storahci.sys
http://www.carrona.org/drivers/driver.php?id=TeeDriverx64.sys
droidcam.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
droidcamvideo.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
http://www.carrona.org/drivers/driver.php?id=RTKVHD64.sys
http://www.carrona.org/drivers/driver.php?id=iwdbus.sys
http://www.carrona.org/drivers/driver.php?id=aswHwid.sys
http://www.carrona.org/drivers/driver.php?id=aswMonFlt.sys
http://www.carrona.org/drivers/driver.php?id=aswRdr2.sys
http://www.carrona.org/drivers/driver.php?id=aswSnx.sys
http://www.carrona.org/drivers/driver.php?id=aswRvrt.sys
http://www.carrona.org/drivers/driver.php?id=aswVmm.sys
http://www.carrona.org/drivers/driver.php?id=aswStm.sys
http://www.carrona.org/drivers/driver.php?id=aswSP.sys
http://www.carrona.org/drivers/driver.php?id=nvhda64v.sys
http://www.carrona.org/drivers/driver.php?id=igdkmd64.sys
http://www.carrona.org/drivers/driver.php?id=rzendpt.sys
http://www.carrona.org/drivers/driver.php?id=rzudd.sys
http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
http://www.carrona.org/drivers/driver.php?id=nvvad64v.sys
http://www.carrona.org/drivers/driver.php?id=NvStreamKms.sys
http://www.carrona.org/drivers/driver.php?id=ssudbus.sys
http://www.carrona.org/drivers/driver.php?id=ssudmdm.sys
http://www.carrona.org/drivers/driver.php?id=NvStreamKms.sys

It appears that the DroidCam is still loading up. Atleast the drivers are present in the Loaded Modules list which means you would have to manually rename those driver files and stop any services related to the DroidCam. I have highlighted the DroidCam Drivers in RED so that it would be easy for you to find them throughout the system.

Furthermore, you have a SteelSeries WOW Mouse which has very old drivers, so update them. Till the time we are troubleshooting, kindly remove any Razer Devices from the system.

You must note that the System would BSOD only once there are 5 attempts of recovering the Display Driver. Remove the present version of the NVIDIA Drivers using the Display Driver Uninstaller over **HERE** and then install the drivers provided to you by the GPU Manufacturer in a driver media. See if it still results in a BSOD or not.

Furthermore, there are in many dump files, the Networking Drivers present on the system. I would suggest you to remove Avast using this **TOOL** till the time we are troubleshooting.

Let me know how it goes ^_^
 

My Computer

System One

  • OS
    Windows 8.1 Industry Pro B-)
    Computer type
    Laptop
    System Manufacturer/Model
    Toshiba
    CPU
    Core I5 2430M @ 2.4GHz
    Memory
    8 GB DDR3 @ 1600MHz Dual Channel ^_^
    Graphics Card(s)
    Intel HD 3000 B-)
    Screen Resolution
    1366x768
    Hard Drives
    Toshiba 500 GB
    Browser
    Google Chrome
    Antivirus
    Windows Defender & Common Sense!
So turns out I found the solution to my problem. My default ram timings were overclocked on my motherboard. They were 11-11-11-28 when the manufacturer's default is 8-8-8-24. Manually adjusting ram timings fixed all the problems for me.

Thank you for your time though, blueelvis!
 

My Computer

System One

  • OS
    Windows 8.1
    Computer type
    PC/Desktop
    CPU
    Core i5-4690 3.50GHz
    Motherboard
    Gigabyte Z97X-UD3H
    Memory
    2x 4GB G.SKILL Ripjaws X F3-12800CL9D DDR3-1600
    Graphics Card(s)
    GeForce GTX 660
    Monitor(s) Displays
    2
    PSU
    Corsair TX750W
So turns out I found the solution to my problem. My default ram timings were overclocked on my motherboard. They were 11-11-11-28 when the manufacturer's default is 8-8-8-24. Manually adjusting ram timings fixed all the problems for me.

Thank you for your time though, blueelvis!

Overclocking is never recommended :(

But, glad to hear that you have solved your issue yourself ^_^
 

My Computer

System One

  • OS
    Windows 8.1 Industry Pro B-)
    Computer type
    Laptop
    System Manufacturer/Model
    Toshiba
    CPU
    Core I5 2430M @ 2.4GHz
    Memory
    8 GB DDR3 @ 1600MHz Dual Channel ^_^
    Graphics Card(s)
    Intel HD 3000 B-)
    Screen Resolution
    1366x768
    Hard Drives
    Toshiba 500 GB
    Browser
    Google Chrome
    Antivirus
    Windows Defender & Common Sense!
Back
Top