BSOD issues ntoskrnl.exe

cabjack

Reputable
Sep 16, 2014
15
0
4,510
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

Reputable
Sep 16, 2014
15
0
4,510
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
 
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
 

cabjack

Reputable
Sep 16, 2014
15
0
4,510
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



 

cabjack

Reputable
Sep 16, 2014
15
0
4,510
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.
 

cabjack

Reputable
Sep 16, 2014
15
0
4,510
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.






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



 

cabjack

Reputable
Sep 16, 2014
15
0
4,510
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.
 
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




 

cabjack

Reputable
Sep 16, 2014
15
0
4,510
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.
 
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
 

cabjack

Reputable
Sep 16, 2014
15
0
4,510
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.
 
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?Langid=1&PNid=15&PFid=25&Level=4&Conn=3&DownTypeID=3&GetDown=false
--------------------------

you might update athwbx.sys Mon Jul 15 00:29:50 2013
from https://www.atheros.cz/atheros-wireless-download.php?chipset=61&system=7

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

I would uninstall your version of chrome and install it again from a trusted source.