BSOD issues ntoskrnl.exe

[cabjack]

I have recently been having many BSODs with my computer. The computer is a stock dell xps8700 with an nvidia GTX645. I installed an additional 16GB of RAM and an SSD.

When I use blue screen review most of the time it says caused by ntoskrnl.exe. The BSODs mostly happen when the computer is idle or sleeping and not usually when I am actively working on it. Although occasionally they will happen when it is active.

I have attached a link from my one drive with multiple BSOD minidump files.

https://onedrive.live.com/redir?resid=E64C465D708E4D20!659&authkey=!AND1nlWphgBcK50&ithint=folder%2cdmp

Any help would be greatly appreciated.

Thanks

 

[cabjack]

ma-config was running as this is what was downloaded during scout_03 post which monitored all drivers and provided links to updates from a french site touslesdrivers.com. So that is fairly new. Also the itunes is another program is post dates the beginning of the problem as I have not had itunes on this computer for some time but recently reinstalled it. Would you suggest uninstalling the ma-config.com program?

I will definitely uninstall and reinstall chrome as per your suggestion. Also I will update the atheros driver. and realtek drivers

Thanks again for looking at the dump files.

 

[johnbl]

I just have not seen it before, I would remove it if you are done with it.
I do remember some of the old realtek USB readers driver as a source of memory corruption so be sure to update it.

ma-config was running as this is what was downloaded during scout_03 post which monitored all drivers and provided links to updates from a french site touslesdrivers.com. So that is fairly new. Also the itunes is another program is post dates the beginning of the problem as I have not had itunes on this computer for some time but recently reinstalled it. Would you suggest uninstalling the ma-config.com program?

I will definitely uninstall and reinstall chrome as per your suggestion. Also I will update the atheros driver. and realtek drivers

Thanks again for looking at the dump files.

 

[scout_03]

the 3b error code http://answers.microsoft.com/en-us/windows/forum/windows_7-system/blue-screen-error-0x3b-systemserviceexception/7eeea12d-a97a-477b-b4c3-1fda74a7315e

 

[cabjack]

Since my previous post on 9/28 I have had an additional 5 BSODs the details again are below:

I have as per johnbl's suggestion uninstalled and reinstalled chrome as well as updated the atheros driver. But these did not apparently help.

Anyone with additional suggestions would be greatly appreciated. Thanks again for all your help.


The files can be found here: http://1drv.ms/ZoRIWs

Here is a copy of the who crashed report:

On Fri 10/3/2014 4:11:25 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\100214-21437-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x153CA0)
Bugcheck code: 0x7F (0x8, 0xFFFFD0008A69D230, 0xFFFFD2008A6C6FB0, 0xFFFFF8026CBE0BCF)
Error: UNEXPECTED_KERNEL_MODE_TRAP
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Fri 10/3/2014 4:11:25 AM GMT your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x7F (0x8, 0xFFFFD0008A69D230, 0xFFFFD2008A6C6FB0, 0xFFFFF8026CBE0BCF)
Error: UNEXPECTED_KERNEL_MODE_TRAP
Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Fri 10/3/2014 2:17:07 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\100214-15562-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x153CA0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8025B8510DB, 0xFFFFD0002A3A0E30, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Thu 10/2/2014 10:59:31 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\100214-14859-01.dmp
This was probably caused by the following module: ndis.sys (ndis+0x2474)
Bugcheck code: 0x1000007E (0xFFFFFFFFC000001D, 0xFFFFF800B14CD474, 0xFFFFD000215B0308, 0xFFFFD000215AFB10)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\drivers\ndis.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Network Driver Interface Specification (NDIS)
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Thu 10/2/2014 10:26:25 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\100214-16484-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x153CA0)
Bugcheck code: 0xA (0x218, 0x2, 0x0, 0xFFFFF803483DA40A)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Tue 9/30/2014 3:03:45 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\092914-18671-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x153CA0)
Bugcheck code: 0xA (0xE024B4B6, 0x2, 0x1, 0xFFFFF80191651FDC)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

 

[Paul NZ]

athwbx.sys is crashing with a 0x7e stop error your wireless drivers. Directx is crashing with the same stop error

Your video drivers are crashing with a 0x000000a stop error. hal.dll is crashing with the same stop error

ntoskrnl.exe is crashing with a 0x0000004e, 3b and 0x0000007f, 109, and 139 stop error. So is verifierext.exe

Uninstall Norton / Symantec program/s its still on the system. One of its files can cause a 0x7e stop error

 

[scout_03]

did you overclock and if the answer is yes go back to default settings your to high and made a good memtest you could have a cpu ,ram or motherboard that is gone give away .

 

[Dragonburn]

You said that you installed additional ram? did you make sure that it was compatible with the existing ram and have you tried to remove the new ram and see if you are still getting the BSOD?

 

[johnbl]

your drivers list for the dell drivers
http://www.dell.com/support/home/us/en/19/product-support/product/xps-8700/drivers
has a update to the firmware mSATA drives that has fixes for DEVSLP
that is fixes for device sleep low power transitions, could be a root cause of your problem.

---------------
you might disable your NVidia streaming service for your graphics card, it can cause bugs in your wireless Ethernet driver to be exposed. the Nvidia streaming driver is installed and many people never use it to stream their game sessions.
-----------------
looks like you have three virus scanners running
msmpeng.exe (the scanning component of Windows Defender)
\C:\WINDOWS\system32\drivers\mbam.sys Wed Oct 30 09:11:45 2013
\C:\Program Files\SUPERAntiSpyware\SASDIFSV64.SYS Thu Jul 21 16:03:00 2011
\C:\Program Files\SUPERAntiSpyware\SASKUTIL64.SYS Tue Jul 12 14:00:01 2011

remove both or the older one. I am confused why windows defender would be running, I expected it stops when another scanner is installed. three scanners running can cause a kernel stack overflow and lead to this bugcheck. remove your scanners and reboot.
---
ok, just looked at the memory dump again. the bugcheck was in a power function.
I looked at your files and you have the same intelppm.sys file but a older intelpep.sys file
my windows 8.1 intelpep.sys file is dated 8/26/2014
yours is dated Nov 09 00:45:55 2013

you might consider going directly to the intel website directly and installing the cpu chipset drivers from there
https://downloadcenter.intel.com/Detail_Desc.aspx?DwnldID=20775

intelPEP.sys = intel Power Engine Plugin


----------------
I looked at your bugcheck (double fault)
you basically had two things running, wireless network driver and the intel power management driver

it looks like your machine was going through a sleep state change and it caused a double fault.
this could be a BIOS bug or a bug in the intel intelppm.sys (2013) driver. More likely a BIOS problem.

I would, got to BIOS reset the BIOS to defaults and reconfigure the settings. (update the BIOS if there is a new one)
You might look at the BIOS power management features and disable feature, and disable sleep in windows to determine if
you have a sleep problem.
-------------
since you have memory from 2 different manufactures (patriot and Hynix/Hyundai) your bios may have set the memory timings incorrectly. run memtest86 to confirm that RAM timings are set correctly. It will fail if the timings are not set correctly in BIOS
memory installed:

8192MB 1600MHz PSD38G16002

4096MB 1600MHz HMT451U6AFR8C-PB

8192MB 1600MHz PSD38G16002

4096MB 4096MB HMT451U6AFR8C-PB

other machine info:
BIOS Release Date 04/16/2014
BIOS Version A08
Manufacturer Dell Inc.
Product Name XPS 8700
Product 0KWVT8
Version A00
Intel(R) Core(TM) i7-4770 CPU @ 3.40GHz

you have a old 2011 version of SUPERAntiSpyware installed.
SASKUTIL64 SASKUTIL64.SYS Tue Jul 12 14:00:01 2011
SASDIFSV64 SASDIFSV64.SYS Thu Jul 21 16:03:00 2011


driver:
RtsUStor.sys Wed Jul 04 18:59:11 2012 is old
athwbx.sys Mon Jul 15 00:29:50 2013 should be ok

- got to go, will take another look at the memory dump when I get back

 

[cabjack]

Thanks to everyone for the suggestions. As to the comments received here is some additional information:

PaulNZ: I did use the norton removal tool, so I am not sure why norton/symantec is still showing up. It does not show in the program list so I am at a loss as to how to remove whatever additional programs that are being shown.

Scout_03: The system is not overclocked, it is literally a standard dell machine which I added an additional 16GB of RAM and an SSD to.

Dragonburn: I did check the RAM for compatibility and it is compatible, I have not removed the additional RAM yet. I will try to do that tomorrow as I will be away from the system today.

johnbl: the new superantispy was something I recently downloaded. This occured well after all of the problems started and I did it as it was pointed out that maybe chrome was infected with some malware. I will remove this program.

I will also disable the Nvidia streaming driver and try to download the chipset drivers from Intel.

You also pointed out that the crash occurred in the sleep state and 90% of the BSODs are occurring when the computer is in a sleep state. Once in a while they occur while actively working but not usually. Also another interesting thing is that this particular computer is not connected wirelessly to the internet and it has a hardwired ethernet connection so I am somewhat confused what would be calling the wireless driver. I did just disable the wireless function and will see if that helps.

Also I will look into the BIOS issue you have stated and run memory test.

Finally there was an additional BSOD on the system. I have included the dump files in the onedrive located here: http://1drv.ms/ZoRIWs

The signature seems to be the same as most of the previous occurred while sleeping indicating ntoskrnl.exe and athwbx.sys. Below is a link to the Whocrashed readout.

On Sun 10/5/2014 11:25:17 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\100514-20359-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1DA40A)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF800EADDE40A, 0xFFFFD000205F1868, 0xFFFFD000205F1070)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sun 10/5/2014 11:25:17 AM GMT your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: athwbx.sys (athwbx+0x27073F)
Bugcheck code: 0x7E (0xFFFFFFFFC0000005, 0xFFFFF800EADDE40A, 0xFFFFD000205F1868, 0xFFFFD000205F1070)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\drivers\athwbx.sys
product: Driver for Qualcomm Atheros CB42/CB43/MB42/MB43 Network Adapter
company: Qualcomm Atheros Communications, Inc.
description: Qualcomm Atheros Extensible Wireless LAN device driver
Bug check description: This bug check indicates that a system thread generated an exception that the error handler did not catch.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: athwbx.sys (Qualcomm Atheros Extensible Wireless LAN device driver, Qualcomm Atheros Communications, Inc.).
Google query: Qualcomm Atheros Communications, Inc. SYSTEM_THREAD_EXCEPTION_NOT_HANDLED

 

[Paul NZ]

Looks like the wireless drivers are still crashing. See if theres an update for these

If you've uninstalled Norton / whatever then used their tool. Find these files then delete them

ENG64.SYS, EX64.SYS, IDSvia64.sys this belongs to Intrusion detection by the looks of it

SRTSP64.SYS, SRTSPX64.SYS, SYMDS64.SYS, SYMEFA64.SYS, SYMEVENT64x86.SYS, SYMNETS.SYS

Is Symantec Eraser still installed?

 

[scout_03]

try to update the wireless driver .

 

[cabjack]

Thanks again for all the suggestions. Here is the latest update.

johnbl: I disabled the Nvidia streaming service and removed the superantispy software from the machine. I also ran memtest and that completed without any errors. I checked the bios and it is the most up to date as listed on the Dell site. I still need to look into the intel driver downloads which you mentioned.

PaulNZ: I deleted everyfile that I could find related to norton or symantec. I even went into the registry and deleted any that I could find. Could not find any of the above files you indicate, so don't know what else to do to remove any additional norton remnants.

scout_03: The wireless driver is the latest version.

Finally two additional BSODs have occured since last post. They both occurred on 10/06. I have again included the dump files in one drive located here:

http://1drv.ms/ZoRIWs

Also here is the whocrashed printout:

On Mon 10/6/2014 10:15:06 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\100614-18062-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x153CA0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8009D8413CB, 0xFFFFD00025078C30, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Mon 10/6/2014 10:15:06 PM GMT your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8009D8413CB, 0xFFFFD00025078C30, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Mon 10/6/2014 8:19:42 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\100614-14828-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x153CA0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800A0A4F0DB, 0xFFFFD0002BFD3EF0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

 

[Paul NZ]

Directx, nvlddmkm.sys / your video drivers, tcpip.sys, the wireless drivers, VerifierExt.sys, ntoskrnl.exe and hal.dll are crashing

 

[johnbl]

I am looking at a bugcheck, it looks like a failed call to a disk quota api.


do what you can to get rid of this driver. bad driver, corrupts memory.
\SystemRoot\System32\Drivers\RtsUStor.sys Wed Jul 04 18:59:11 2012
is still loaded. install the driver from
http://www.realtek.com.tw/downloads/downloadsView.aspx?Langid=1&PNid=15&PFid=25&Level=4&Conn=3&DownTypeID=3&GetDown=false
date is 2014/1/22
or uninstall and disable the device.

you are running Iastora.sys Jan 14 10:00:27 2013
are you running a raid array?
if you are get the current version from intel
https://downloadcenter.intel.com/SearchResult.aspx?lang=eng&keyword=%22iaStor.sys%22

you still have a mix of Hynix / Hyundai RAM mixed with patriot RAM
on a Dell BIOS. You need to look of the technical specs for both RAM types and find the primary and all the secondary timings
and confirm that the Dell BIOS has set them correctly. Maybe someone can suggest a good free program to display your current memory timings on each bank while running winodows.

 

[scout_03]

you could check with hwinfo .

 

[cabjack]

I have tried a couple of items since my last post. Mainly disable the rtsustor driver which johnbl suggested. I also turned of the fast startup setting from the power options. Somewhere I read that people have experienced issues with that setting.

Anyway, the system has produced three more BSODs since the last post. The first and last one were more "typical" for the system, they would crash while the computer is sleeping. The 2nd one was somewhat different as the screen just froze after waking the computer up. Anyway after the 1st two BSODs I did not experience one for 5 days until today. I did get a microsoft update earlier today and went forward and restarted the system. Then a few hours later again after the computer was sleeping the BSOD occured.

Anyway I do appreciate all of the help and have posted the memorydump and minidump files to the onedrive located here: http://1drv.ms/ZoRIWs

Also here is the whocrashed readout:

On Sat 10/18/2014 8:53:56 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\101814-15375-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x153CA0)
Bugcheck code: 0x3B (0x80000004, 0xFFFFF8013985E13F, 0xFFFFD00026BFCEF0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sat 10/18/2014 8:53:56 PM GMT your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x3B (0x80000004, 0xFFFFF8013985E13F, 0xFFFFD00026BFCEF0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Mon 10/13/2014 2:55:50 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\101314-15984-01.dmp
This was probably caused by the following module: tcpip.sys (0xFFFFF80062D177B2)
Bugcheck code: 0xD1 (0xFFFFF8006AE55570, 0x2, 0x0, 0xFFFFF80062D177B2)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\tcpip.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: TCP/IP Driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Sat 10/11/2014 4:33:56 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\101114-15609-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x153CA0)
Bugcheck code: 0x139 (0x3, 0xFFFFD001EA046820, 0xFFFFD001EA046778, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The kernel has detected the corruption of a critical data structure.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Fri 10/10/2014 11:31:38 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\101014-17859-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x153CA0)
Bugcheck code: 0x133 (0x0, 0x501, 0x500, 0x0)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

 

[johnbl]

Twp things, You must confirm:
that running memtest86 works as expected with no errors.
(because you have mixed types of memory modules on machine)

- you have verifier enabled but you must provide a full or kernel memory dump or the verifier information is not saved to the memory dump for debugging.

With the mini dump I can tell you what the problem is but not what caused the problem.
With the kernel dump I can look at the internal logs and the tracking that verifier puts in.
with the full memory dump I can look at the orginal program that called the driver that made the call to the OS that caused the bugcheck. Sometimes you can actually see where the problem occurs at.

otherwise all I can say is "chrome made a call and got a error 4 " look up error 4 and see that it is
a IO error (input/output)" I think chrome or a chrome addon tried to use a interface that did not exist and got a error.

only think I would think to do would be to disable chrome add ons.

And this would not normally cause a bugcheck, whith maybe the exectpion of if chrome was set to use hardware acceleration and you had a issue with that hardware. (ie turn of chrome browser hardware acceleration and see if it helps)

 

[cabjack]

Thanks again for the response. I have been providing two types of dumps to the onedrive. One is definitely the minidump file size of 291KB, the other is a zipped file of memory.dmp which is a file of around 1GB. I don't know if the larger file represents the full dump you are referring to or not. If not please let me know how to obtain it and I will begin posting them.

As for memtest, it did run for 10 hours with no errors. I don't know if there is an additional setting to use or not but it completed whatever was the default test.

As for the Chrome extensions I have them all disabled.

So if you can let me know how to get you the data that would better identify the problem please let me know.

Also I did get one more BSOD today.

Files were uploaded to onedrive: http://1drv.ms/ZoRIWs

Also the whos crashed printout is below:

On Sun 10/19/2014 6:27:43 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\101914-18281-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x153CA0)
Bugcheck code: 0xA (0xFFFFE200D01EA198, 0x2, 0x0, 0xFFFFF802782B20DB)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sun 10/19/2014 6:27:43 PM GMT your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xA (0xFFFFE200D01EA198, 0x2, 0x0, 0xFFFFF802782B20DB)
Error: IRQL_NOT_LESS_OR_EQUAL
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

 

[johnbl]

I just started looking at the first bugcheck.
I have not found the problem but I think the function is being called by the Ethernet driver
\SystemRoot\system32\DRIVERS\Rt630x64.sys Tue Jun 17 04:56:46 2014
your driver is pretty current but they made a update sept 24 2014.
install this driver from here:
http://www.realtek.com.tw/downloads/downloadsView.aspx?Langid=1&PNid=13&PFid=5&Level=5&Conn=4&DownTypeID=3&GetDown=false


also you seem to have a google extension loaded: chrome-extension_pafkbggdmjlpgkdkcbjmhmfcdpncadgh
I don't know what it does.

anyway try the network driver update and I will see if I can figure out what went wrong in the memory dump


http://www.realtek.com.tw/downloads/downloadsView.aspx?Langid=1&PNid=13&PFid=5&Level=5&Conn=4&DownTypeID=3&GetDown=false

note: the process that started the calls that bugchecked are the NVidia streaming software.
if you are not using that software to stream your game video sessions to a server you might want to stop the service in control panel. I think the streaming software is exposing some bug in your network driver, so be sure to update the network driver.

you also have a process called hpnetworkcommunicator.exe
running it might be doing bad calls to your Ethernet driver. I would uninstall if don't use it.

I just realize your Bluetooth driver is actually a Bluetooth and wifi Ethernet driver from 2012
Dell Wireless1703 802.11 b/g/n, Bluetooth4.0 + HS Driver

go to http://www.dell.com/support/home/us/en/19/product-support/product/xps-8700/drivers
and get the june 2014 version for window 8.x