Sign in with
Sign up | Sign in
Your question

BSOD issues ntoskrnl.exe

Tags:
  • Blue Screen
  • Computers
  • Ntoskrnl.Exe
Last response: in Windows 8
Share
September 16, 2014 4:46:48 PM

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

More about : bsod issues ntoskrnl exe

September 16, 2014 5:50:20 PM

That onedrive link says the file doesnt exist
m
0
l
Related resources
September 16, 2014 7:16:33 PM

Paul, I tried the link and it does seem to not point to the document.

Anyway here is another link to the dump files.

http://1drv.ms/ZoRIWs
m
0
l
September 16, 2014 7:20:46 PM

Scout_03, I have run the software you indicated and have pasted the results here.

On Wed 9/17/2014 2:05:43 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\091614-12390-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x153FA0)
Bugcheck code: 0xA (0x76, 0xD, 0x1, 0xFFFFF8032C53E5F4)
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 Wed 9/17/2014 2:05:43 AM GMT your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: hal.dll (hal!HalPerformEndOfInterrupt+0x6F)
Bugcheck code: 0xA (0x76, 0xD, 0x1, 0xFFFFF8032C53E5F4)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
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 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 Wed 9/17/2014 1:32:49 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\091614-12453-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x153FA0)
Bugcheck code: 0xA (0xFFFFE101C92B31B0, 0x2, 0x0, 0xFFFFF800586CEA3C)
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/16/2014 9:13:07 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\091614-12687-01.dmp
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x217D68)
Bugcheck code: 0xA (0x4C000003, 0xD, 0x1, 0xFFFFF803D6136477)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 340.52
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 340.52
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.
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: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 340.52 , NVIDIA Corporation).
Google query: NVIDIA Corporation IRQL_NOT_LESS_OR_EQUAL



On Mon 9/15/2014 11:22:06 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\091514-12328-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x153FA0)
Bugcheck code: 0xA (0xFFFFFFFFFFFFFFF9, 0xD, 0x0, 0xFFFFF801296B85F6)
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 Mon 9/15/2014 9:24:30 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\091514-12562-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x153FA0)
Bugcheck code: 0xA (0xFFFFF803820FF000, 0x7, 0x0, 0xFFFFF803805D88C5)
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 Mon 9/15/2014 3:30:56 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\091414-12500-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x153FA0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF801C4C0F0BC, 0x1, 0x20)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 kernel-mode program 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 Mon 9/15/2014 1:48:36 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\091414-12609-02.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x153FA0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80149EDF18B, 0xFFFFD00027E59EF0, 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 9/15/2014 1:39:33 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\091414-12609-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x153FA0)
Bugcheck code: 0xA (0xFFFFF8008F7F2190, 0x2, 0x0, 0xFFFFF8010C0D43F8)
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 Sat 9/13/2014 9:57:59 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\091314-12296-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x153FA0)
Bugcheck code: 0xA (0xFFFFA00030E13998, 0x2, 0x0, 0xFFFFF80068ACD18B)
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.




--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

51 crash dumps have been found and analyzed. Only 10 are included in this report. 3 third party drivers have been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

rt630x64.sys (Realtek 8101E/8168/8169 NDIS 6.30 64-bit Driver , Realtek )
nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 340.52 , NVIDIA Corporation)
symnets.sys
m
0
l
September 16, 2014 7:29:58 PM

The Nvidia drivers are causing one of the crashes.

hal.dll is crashing x 3. ntoskrnl.exe is crashing x18. tcpip.sys is crashing x1

I would see if there are any network adapter updates on the dell site
m
0
l
September 17, 2014 2:19:12 PM

you might update your
realtek ethernet driver from realtek or dell website

18.210.127.131/downloads/downloadsView.aspx?Langid=1&PNid=13&PFid=4&Level=5&Conn=4&DownTypeID=3&GetDown=false&Downloads=true

your driver date SystemRoot\system32\DRIVERS\Rt630x64.sys Thu Oct 25 02:14:58 2012
was kind of old.

I think paul is correct, go to the dell website for your machine and you have a few updates to pickup
- BIOS update and chipset updates, and get the network update from there or directly from realtek website.
\SystemRoot\System32\drivers\HECIx64.sys Mon Dec 17 11:32:21 2012 was also old but it should be a chipset update on the dell website.

also see if there is a update to \SystemRoot\System32\drivers\btath_bus.sys Thu Nov 01 22:35:15 2012
Atheros BlueTooth driver from dell (dell has one from 2014 for your system)

the updates from dell website will most likely take care of your problem
m
0
l
September 17, 2014 8:00:00 PM

since you had memory i would memtest each of them one at the time you could also have a defective ram module and did you check the compatibility with your system and if he could handle all that memory .
m
0
l
September 18, 2014 5:18:40 PM

I updated the realtek driver directly from the realtek site and it is now updated with driver date of 6/17/2014. As for the chipset, bios, wireless, bluetooth, and sound drivers, I utilized the downloads from the Dell site and it indicated everything was updated. When checking the drivers on the device manager most indicate release dates in early to mid-2013 (Chipset 1/22/2013, Realtek Sound 8/13/2013, Dell Wireless 7/15/2013, Dell Bluetooth 7/30/2013 , so I don't know if the most updated versions are installed or not.

I am not sure if there is any other items that should be updated, but please let me know if anyone sees anything.

I did have additional BSODs but it was prior to updating the drivers so I will wait and see if anything happens subsequent to these updates.

As to Scout_03's suggestion, I did confirm that the memory installed is compatible with the system and have run some basic diagnostics on the memory with no failure. If there is a more enhanced test that I should run on the modules please point me to that.

Thanks



m
0
l
September 18, 2014 5:34:22 PM

Well 10 min after I updated the drivers, I did have another BSOD. I have copied the report below:

On Fri 9/19/2014 12:26:08 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\091814-12515-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x153CA0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80241CC70DB, 0xFFFFD000222FE750, 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 Fri 9/19/2014 12:26:08 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: 0x3B (0xC0000005, 0xFFFFF80241CC70DB, 0xFFFFD000222FE750, 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.


Any suggestions would be greatly appreciated.
m
0
l
September 18, 2014 5:38:10 PM

Get the dmp files again upload them again..
m
0
l
September 18, 2014 11:14:10 PM

need the two memory .dmp files
C:\WINDOWS\memory.dmp
and C:\WINDOWS\Minidump\091814-12515-01.dmp

if you have not done so already, change your memory dump to a kernel dump
and turn on verifier.exe debugging flags and reboot and provide a link to the next memory .dmp file after the next crash.

http://www.sevenforums.com/crash-lockup-debug-how/65331...

it can be very useful in doing automated debugging to help pinpoint the problem
m
0
l
September 19, 2014 12:09:29 PM

went to dell link for your system and the also have intel wireless driver and bluethooth with also some intel one did you use your service tag to update the driver .
m
0
l
September 23, 2014 10:25:17 AM

I have been away this past weekend and unable to post any results.

As for the minidump files on Onedrive they are all uploaded here: http://1drv.ms/ZoRIWs

I did also update the wireless driver and bluetooth driver from the Dell website so they should be updated.

As per johnbl's suggestion I have also enabled kernel dump and turned on the verifier.






m
0
l
September 24, 2014 1:39:54 PM

I didn't see any dump files after the 18th? looking with one with verifier.exe flags on and kernel dump

cabjack said:
I have been away this past weekend and unable to post any results.

As for the minidump files on Onedrive they are all uploaded here: http://1drv.ms/ZoRIWs

I did also update the wireless driver and bluetooth driver from the Dell website so they should be updated.

As per johnbl's suggestion I have also enabled kernel dump and turned on the verifier.








m
0
l
September 24, 2014 7:44:06 PM

do you still have bsod ?
m
0
l
September 25, 2014 9:03:09 PM

Things have not crashed in a few days, but last night and today I had two more BSODs.

I have uploaded the files to onedrive. They include the two minidump files and a zipped memory dump from the last crash. The link is here:
http://1drv.ms/ZoRIWs

Also I have included the "WhoCrashed" read out below. The first crash (9/25 below) seems somewhat different from the normal crash files, however the 9/26 crash definitely calls out the same ntoskrnl.exe

On Fri 9/26/2014 2:16:34 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\092514-19328-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x153CA0)
Bugcheck code: 0x139 (0x3, 0xFFFFD00121FDC820, 0xFFFFD00121FDC778, 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 9/26/2014 2:16:34 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: 0x139 (0x3, 0xFFFFD00121FDC820, 0xFFFFD00121FDC778, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
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 Thu 9/25/2014 5:23:42 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\092414-18406-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x7E73)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8010AD55E73, 0xFFFFD00020B37758, 0xFFFFD00020B36F60)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
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.


Thanks again for all the help.
m
0
l
September 25, 2014 9:20:48 PM

Directx and your video drivers / nvlddmkm.sys are 2 of the causes. Most of them are crashing ntoskrnl.exe

Is it crashing when you get into windows?? If it is your Nvidia audio drivers maybe the cause

What was installed / installed now that's Norton / Symantec? It looks like a file belonging to it is on the hdd SRTSP64.SYS

Is this still on the hdd / installed? Wouldnt be surprised if this is the cause of the crashes




m
0
l
September 25, 2014 11:16:59 PM

KERNEL_SECURITY_CHECK_FAILURE was a stack overflow.
you have something weird going on with chrome. disable all the add ons you have installed for chrome.

find out why the chrome that is actually running is "chrome.exe.exe" rather than "chrome.exe"

m
0
l
September 26, 2014 11:56:09 AM

Thanks for taking a look at the files.

I did have an additional crash last night and have uploaded the minidump and memory dump files (9^25 memorydump #2).

Here is the link http://1drv.ms/ZoRIWs

The printout from whocrashed is here:

On Fri 9/26/2014 4:49:59 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\092514-32546-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x153CA0)
Bugcheck code: 0xA (0xFFFFFA8309F021B8, 0x2, 0x0, 0xFFFFF800101A9C78)
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 Fri 9/26/2014 4:49:59 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: 0xA (0xFFFFFA8309F021B8, 0x2, 0x0, 0xFFFFF800101A9C78)
Error: IRQL_NOT_LESS_OR_EQUAL
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 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.
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. IRQL_NOT_LESS_OR_EQUAL


To address Paul NZ's post: I had removed the Norton antivirus in August and just turned on Windows defender. This happened after the crashes started to appear and someone indicated it could be a conflict. Anyway no change with the amount or types of crashes since then but the configuration is still Windows Defender and no Norton.

The hdd you are referring to is still installed on the system as a backup drive. During early August in a chat with a Dell tech I explained that I had moved over the OS to the SDD and was experiencing problems. At that time he supposedly wiped the HDD clean but I am not sure whether this could be causing a conflict or not. This drive was the drive originally shipped with the system and originally contained the OS but as I said it was supposed to have been cleaned earlier.

As for when the system crashes, it does not crash going into windows. It "mostly" crashes after it has gone into sleep mode. It will sometimes crash while I am actively using the system, but most of the time it is after I have left the computer for a while and it has gone to sleep and when I wake it up I see it has experienced a BSOD and restarted itself.

As to whether it could be the Nvidia audion drivers, I guess it could be. I really don't know what to make of the problem and what is causing it, however I do realize that the audio is being run by realtek and that Nvidia also has audio so I guess there could be some conflict. I really don't know how to troubleshoot it further.

As to johnbl's comments: I will disable the chrome add ons as you indicate. I do not know why it would be running "chrome.exe.exe". I have noticed recently that the chrome tabs have not been adjusting as well as previously. I have seen some other people reporting this issue although not connected with BSODs.

If the new crash lends any additional information or if there any specific steps that should be taken in order to debug the issue again I really appreciate the help.
m
0
l
September 26, 2014 12:47:25 PM

If Norton/Symantec have been removed use their removal tool to remove the rest of it.

Files belonging to it are still on the hdd. (and services it used may still be on the system)

Update the wireless drivers athwbx.sys is crashing. Thats a wireless adapter driver

m
0
l
September 26, 2014 6:03:22 PM

right click on the file and look at the chrome file properties for the actual .exe name
it should be chrome.exe not chrome.exe.exe the second version would not be correct.

what I looked at was chrome.exe.exe with a process that looked like it was trying to blow up the stack. IE malware, or a really stupid addon
m
0
l
September 28, 2014 8:42:04 AM

To update the situation. I did have an additional BSOD last night details below.

Paul NZ: I did use the norton removal tool that you linked to. I don't know why there would be left over norton files as this is the tool I originally used to remove the software, however I did rerun it just to see if that would remove any additional files.

The chrome application I did remove all of the extensions which were operating and did check the properties on the application. Only saw filename listed as chrome.exe so not sure again why there would be chrome.exe.exe unless there is some hidden malware.

As to the Atheros driver I have not yet found an updated driver other than the one listed on the Dell site. I did notice other individuals indicated some startup issues (ie: long startup/shutdown times) with the dell driver from the site, so I was looking into this issue as maybe a cause of my BSOD.

scout_03: I did run the tool you indicated and have updated most of the drivers, but I wanted to create a restore point before completing some of the driver updates and plan to get to that today. The drivers indicated to still be updated are an Intel storage driver, and realtek audio and PCI driver. The latter seems strange as I just updated from the realtek site but this indicates a newer driver to the 6/17/14 driver that was just loaded.

As to the latest BSOD here are the details:

Onedive link: http://1drv.ms/ZoRIWs (new minidump is 092714-17640-01.dmp, Memory dump is Memory9^27)

Here is the whocrashed information:

On Sun 9/28/2014 5:35:42 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\092714-17640-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x153CA0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80025EC70DB, 0xFFFFD000254BB750, 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 Sun 9/28/2014 5:35:42 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: 0x3B (0xC0000005, 0xFFFFF80025EC70DB, 0xFFFFD000254BB750, 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.
m
0
l
September 28, 2014 9:32:27 AM

why are you running C:\Program Files\ma-config.com\Drivers\ma-config_amd64.sys Wed Oct 23 07:26:33 2013 by Cybelsoft ?
-------------

note: current bugcheck has chrome.exe not chrome.exe.exe

the bugcheck occured while ituneshelper.exe was running
update this file
\SystemRoot\System32\Drivers\RtsUStor.sys Wed Jul 04 18:59:11 2012

from here http://www.realtek.com.tw/downloads/downloadsView.aspx?...
--------------------------

you might update athwbx.sys Mon Jul 15 00:29:50 2013
from https://www.atheros.cz/atheros-wireless-download.php?ch...

----------
chrome.exe.exe listed a network worm, that also monitors keystrokes
http://www.threatexpert.com/report.aspx?md5=c5e119faa88...

I would uninstall your version of chrome and install it again from a trusted source.
m
0
l
September 28, 2014 11:03:16 AM

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.
m
0
l
September 28, 2014 11:18:36 AM

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.

cabjack said:
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.


m
0
l
October 3, 2014 10:59:24 AM

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.
m
0
l
October 3, 2014 12:22:17 PM

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






m
0
l
October 4, 2014 8:29:51 AM

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 .
m
0
l
October 4, 2014 8:42:04 AM

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?
m
0
l
October 4, 2014 9:44:01 AM

your drivers list for the dell drivers
http://www.dell.com/support/home/us/en/19/product-suppo...
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?Dwnld...

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
m
0
l
October 5, 2014 10:34:31 AM

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
m
0
l
October 5, 2014 11:07:07 AM

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?




m
0
l
October 5, 2014 12:10:43 PM

try to update the wireless driver .
m
0
l
October 8, 2014 2:06:34 PM

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.
m
0
l
October 8, 2014 2:15:33 PM

Directx, nvlddmkm.sys / your video drivers, tcpip.sys, the wireless drivers, VerifierExt.sys, ntoskrnl.exe and hal.dll are crashing
m
0
l
October 8, 2014 6:22:58 PM

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?...
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...

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.
m
0
l
October 8, 2014 7:29:44 PM

you could check with hwinfo .
m
0
l
October 18, 2014 3:27:38 PM

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.
m
0
l
October 18, 2014 4:21:42 PM

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)





m
0
l
!