i'm having radnom Bsod have no clue whats causing it crash log inside

[raven235]

[FONT=Segoe UI, Arial]i[FONT=Segoe UI, Arial] ha[FONT=Segoe UI, Arial]ve no clue what is causing this can some 1 please assist me[/FONT][/FONT]

windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir:  C:\Windows
Hardware: MS-7918, MSI, Z97 GAMING 3 (MS-7918)
CPU:  GenuineIntel Intel(R) Core(TM) i5-4670K CPU @ 3.40GHz Intel586, level: 6
4  logical processors, active mask: 15
RAM: 8539398144  total[/COLOR][/SIZE][/FONT]
[FONT=Segoe UI, Arial][SIZE=4][B]  Crash Dump Analysis[/B]  [/SIZE][/FONT]
[FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000]Crash dump  directory: C:\Windows\Minidump[/COLOR][/SIZE][/FONT]

[FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000]Crash dumps are enabled on your  computer.
[/COLOR][/SIZE][/FONT]
[FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][B]On  Tue 2014/12/09 12:49:08 PM GMT your computer crashed[/B]
crash dump file:  C:\Windows\Minidump\120914-13540-01.dmp
This was probably caused by the  following module: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=ntoskrnl.exe"]ntoskrnl.exe[/URL][/COLOR][/SIZE][/FONT] (nt+0x75BC0) 
Bugcheck code: 0xA  (0x1F0, 0x2, 0x0, 0xFFFFF80002ED1325)
Error: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=MSDN+bugcheck+IRQL_NOT_LESS_OR_EQUAL"]IRQL_NOT_LESS_OR_EQUAL[/URL][/COLOR][/SIZE][/FONT]
file path:  C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=Microsoft® Windows® Operating System"]Microsoft® Windows® Operating System[/URL][/COLOR][/SIZE][/FONT]
company: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=Microsoft Corporation"]Microsoft Corporation[/URL][/COLOR][/SIZE][/FONT]
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.  


[/COLOR][/SIZE][/FONT]
[FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][B]On  Tue 2014/12/09 12:49:08 PM GMT your computer crashed[/B]
crash dump file:  C:\Windows\memory.dmp
This was probably caused by the following module: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=mbfilt64.sys"]mbfilt64.sys[/URL][/COLOR][/SIZE][/FONT] (MBfilt64+0x1817) 
Bugcheck code: 0xA  (0x1F0, 0x2, 0x0, 0xFFFFF80002ED1325)
Error: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=MSDN+bugcheck+IRQL_NOT_LESS_OR_EQUAL"]IRQL_NOT_LESS_OR_EQUAL[/URL][/COLOR][/SIZE][/FONT]
file path:  C:\Windows\system32\drivers\mbfilt64.sys
company: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=Creative Technology Ltd."]Creative Technology Ltd.[/URL][/COLOR][/SIZE][/FONT]
description: Creative Audio  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: mbfilt64.sys (Creative Audio Driver, Creative Technology  Ltd.). 
Google query: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=mbfilt64.sys+Creative Technology Ltd.+IRQL_NOT_LESS_OR_EQUAL"]Creative Technology Ltd.  IRQL_NOT_LESS_OR_EQUAL[/URL][/COLOR][/SIZE][/FONT]


[/COLOR][/SIZE][/FONT]
[FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][B]On Tue 2014/12/09 12:49:00 PM GMT your  computer crashed[/B]
crash dump file:  C:\Windows\Minidump\120914-33072-01.dmp
This was probably caused by the  following module: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=Unknown"]Unknown[/URL][/COLOR][/SIZE][/FONT]  () 
Bugcheck code: 0x0 (0x0, 0x0, 0x0, 0x0)
Error: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=MSDN+bugcheck+CUSTOM_ERROR"]CUSTOM_ERROR[/URL][/COLOR][/SIZE][/FONT]
A third party driver was identified as  the probable root cause of this system error. 
Google query: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=CUSTOM_ERROR"]CUSTOM_ERROR[/URL][/COLOR][/SIZE][/FONT]


[/COLOR][/SIZE][/FONT]
[FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][B]On Tue 2014/12/09 12:29:43 PM GMT your  computer crashed[/B]
crash dump file:  C:\Windows\Minidump\120914-24726-01.dmp
This was probably caused by the  following module: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=nvlddmkm.sys"]nvlddmkm.sys[/URL][/COLOR][/SIZE][/FONT] (nvlddmkm+0xCEEF9) 
Bugcheck code: 0xC2  (0x7, 0x109B, 0xC0821F8, 0xFFFFFA800C082210)
Error: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=MSDN+bugcheck+BAD_POOL_CALLER"]BAD_POOL_CALLER[/URL][/COLOR][/SIZE][/FONT]
file path:  C:\Windows\system32\drivers\nvlddmkm.sys
product: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=NVIDIA Windows Kernel Mode Driver, Version 340.52"]NVIDIA Windows Kernel Mode Driver, Version 340.52  [/URL][/COLOR][/SIZE][/FONT]
company: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=NVIDIA Corporation"]NVIDIA  Corporation[/URL][/COLOR][/SIZE][/FONT]
description: NVIDIA Windows Kernel Mode Driver,  Version 340.52 
Bug check description: This indicates that the current thread  is making a bad pool request.
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: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=nvlddmkm.sys+NVIDIA Corporation+BAD_POOL_CALLER"]NVIDIA Corporation  BAD_POOL_CALLER[/URL][/COLOR][/SIZE][/FONT]


[/COLOR][/SIZE][/FONT]
[FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][B]On Sun 2014/12/07 12:33:35 AM GMT your computer  crashed[/B]
crash dump file: C:\Windows\Minidump\120714-21902-01.dmp
This  was probably caused by the following module: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=ntoskrnl.exe"]ntoskrnl.exe[/URL][/COLOR][/SIZE][/FONT] (nt+0x75BC0) 
Bugcheck code: 0x3B  (0xC0000005, 0xFFFFF800031EFCE8, 0xFFFFF8800A2C9C10, 0x0)
Error: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=MSDN+bugcheck+SYSTEM_SERVICE_EXCEPTION"]SYSTEM_SERVICE_EXCEPTION[/URL][/COLOR][/SIZE][/FONT]
file path:  C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=Microsoft® Windows® Operating System"]Microsoft® Windows® Operating System[/URL][/COLOR][/SIZE][/FONT]
company: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=Microsoft Corporation"]Microsoft Corporation[/URL][/COLOR][/SIZE][/FONT]
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. 


[/COLOR][/SIZE][/FONT]
[FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][B]On Tue 2014/12/02 07:44:06 PM GMT your computer  crashed[/B]
crash dump file: C:\Windows\Minidump\120214-20108-01.dmp
This  was probably caused by the following module: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=dxgmms1.sys"]dxgmms1.sys[/URL][/COLOR][/SIZE][/FONT] (0xFFFFF88003A1D40C) 
Bugcheck code:  0x50 (0xFFFFFA80F58B13E0, 0x0, 0xFFFFF88003A1D40C, 0x5)
Error: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=MSDN+bugcheck+PAGE_FAULT_IN_NONPAGED_AREA"]PAGE_FAULT_IN_NONPAGED_AREA[/URL][/COLOR][/SIZE][/FONT]
file path:  C:\Windows\system32\drivers\dxgmms1.sys
product: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=Microsoft® Windows® Operating System"]Microsoft® Windows® Operating System[/URL][/COLOR][/SIZE][/FONT]
company: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=Microsoft Corporation"]Microsoft Corporation[/URL][/COLOR][/SIZE][/FONT]
description: DirectX Graphics  MMS
Bug check description: This indicates that invalid system memory has been  referenced.
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. 


[/COLOR][/SIZE][/FONT]
[FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][B]On Thu 2014/11/27 09:58:22 AM GMT your computer  crashed[/B]
crash dump file: C:\Windows\Minidump\112714-28984-01.dmp
This  was probably caused by the following module: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=ntoskrnl.exe"]ntoskrnl.exe[/URL][/COLOR][/SIZE][/FONT] (nt+0x75BC0) 
Bugcheck code: 0x50  (0xFFFFF6FB480AAC28, 0x0, 0xFFFFF80002E1B41F, 0x2)
Error: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=MSDN+bugcheck+PAGE_FAULT_IN_NONPAGED_AREA"]PAGE_FAULT_IN_NONPAGED_AREA[/URL][/COLOR][/SIZE][/FONT]
file path:  C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=Microsoft® Windows® Operating System"]Microsoft® Windows® Operating System[/URL][/COLOR][/SIZE][/FONT]
company: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=Microsoft Corporation"]Microsoft Corporation[/URL][/COLOR][/SIZE][/FONT]
description: NT Kernel &  System
Bug check description: This indicates that invalid system memory has  been referenced.
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. 


[/COLOR][/SIZE][/FONT]
[FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][B]On Thu 2014/11/27 07:46:57 AM GMT your computer  crashed[/B]
crash dump file: C:\Windows\Minidump\112714-24039-01.dmp
This  was probably caused by the following module: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=ntoskrnl.exe"]ntoskrnl.exe[/URL][/COLOR][/SIZE][/FONT] (nt+0x75BC0) 
Bugcheck code: 0x1E  (0xFFFFFFFFC0000005, 0xFFFFF8800A4D39D0, 0x0, 0x0)
Error: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=MSDN+bugcheck+KMODE_EXCEPTION_NOT_HANDLED"]KMODE_EXCEPTION_NOT_HANDLED[/URL][/COLOR][/SIZE][/FONT]
file path:  C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=Microsoft® Windows® Operating System"]Microsoft® Windows® Operating System[/URL][/COLOR][/SIZE][/FONT]
company: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=Microsoft Corporation"]Microsoft Corporation[/URL][/COLOR][/SIZE][/FONT]
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.  


[/COLOR][/SIZE][/FONT]
[FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][B]On  Thu 2014/11/27 06:53:04 AM GMT your computer crashed[/B]
crash dump file:  C:\Windows\Minidump\112714-27830-01.dmp
This was probably caused by the  following module: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=ntfs.sys"]ntfs.sys[/URL][/COLOR][/SIZE][/FONT]  (Ntfs+0x4211) 
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF8800318C2C8,  0xFFFFF8800318BB20, 0xFFFFF800032CDCCA)
Error: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=MSDN+bugcheck+NTFS_FILE_SYSTEM"]NTFS_FILE_SYSTEM[/URL][/COLOR][/SIZE][/FONT]
file path:  C:\Windows\system32\drivers\ntfs.sys
product: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=Microsoft® Windows® Operating System"]Microsoft® Windows® Operating System[/URL][/COLOR][/SIZE][/FONT]
company: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=Microsoft Corporation"]Microsoft Corporation[/URL][/COLOR][/SIZE][/FONT]
description: NT File System  Driver
Bug check description: This indicates a problem occurred in the NTFS  file system. 
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.  


[/COLOR][/SIZE][/FONT]
[FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][B]On  Wed 2014/11/26 09:23:32 AM GMT your computer crashed[/B]
crash dump file:  C:\Windows\Minidump\112614-25131-01.dmp
This was probably caused by the  following module: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=ntoskrnl.exe"]ntoskrnl.exe[/URL][/COLOR][/SIZE][/FONT] (nt+0x75B90) 
Bugcheck code: 0x1E (0x0,  0x0, 0x0, 0x0)
Error: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=MSDN+bugcheck+KMODE_EXCEPTION_NOT_HANDLED"]KMODE_EXCEPTION_NOT_HANDLED[/URL][/COLOR][/SIZE][/FONT]
file path:  C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=Microsoft® Windows® Operating System"]Microsoft® Windows® Operating System[/URL][/COLOR][/SIZE][/FONT]
company: [FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=Microsoft Corporation"]Microsoft Corporation[/URL][/COLOR][/SIZE][/FONT]
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.  


[/COLOR][/SIZE][/FONT]
[FONT=Segoe UI, Arial][SIZE=4][B]  Conclusion[/B]  [/SIZE][/FONT]
[FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000]11 crash dumps  have been found and analyzed. Only 10 are included in this report. 2 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: 

[FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=nvlddmkm.sys+NVIDIA Corporation+NVIDIA Windows Kernel Mode Driver, Version 340.52"]nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 340.52 ,  NVIDIA Corporation)[/URL][/COLOR][/SIZE][/FONT]
[FONT=Segoe UI,  Arial][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=mbfilt64.sys+Creative Technology Ltd."]mbfilt64.sys (Creative Audio Driver, Creative Technology  Ltd.)[/URL][/COLOR][/SIZE][/FONT]

If no updates for these drivers are available, try  searching with Google on the names of these drivers in combination the errors  that have been reported for these drivers and include the brand and model name  of your computer as well in the query. This often yields interesting results  from discussions from users who have been experiencing similar  problems.[/COLOR][/SIZE][/FONT]

[FONT=Segoe UI, Arial]

[/FONT]

 

[raven235]

just a humping bumping

 

[raven235]

bump

 

[essenbe]

Hello raven235, I'll see if I can help with your problem. First, just a little general information. It is generally not a good idea to bump your own posts. I is generally frowned on here, but the biggest reason is it can hurt you. Most regulars here look for posts with no responses. When you bump your own post, it says there are responses, yours. So, you are generally better off not to do it. Having said that, I do understand it can be frustrating not to get a response quickly, so no big deal, just something to consider. On another note, just so you know, I will be notified if you make a new post in this thread. If you edit a previous post, I will not be notified, so you will be better off to always make a new post in this thread.

Now, I need you to fill out your system specs as detailed as possible. We like them to be available in every post and detailed enough so we can look each component up. Please put them in the lower part of your last post.

Please fill out your System Specs​

   Information

Your System Specs will help us to help you, and doing it in this manner will make them available to all helpers in every post and keep us from hunting for them. We ask that you fill them out in as much detail as possible including Desktop or Laptop, Model number if it is an OEM computer and all components with the Manufacturer and Model number if possible.

If you will go to your last post and click the 'System Specs' in the bottom left of the post, you will find a link to update your system specs. Please fill those out in as much detail as possible, making sure to click save at the bottom of the page. If you would like to know what we would like, you can click 'My System Specs' at the bottom left of this post to see mine. If you do not know what your components are, this will help you accomplish this task. http://www.sevenforums.com/tutorials/180324-system-info-see-your-system-specs.html​

I looked at your last several dump files. Each one is a different cause and a different stop code.

nvlddmkm
start             end                 module name
fffff880`0f04c000 fffff880`0fcda000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: [COLOR=red]\SystemRoot\system32\DRIVERS\nvlddmkm.sys
[/COLOR]    Image name: nvlddmkm.sys
    Timestamp:        Wed Jul 02 12:42:02 2014 (53B4446A)
    CheckSum:         00C4C7C9
    ImageSize:        00C8E000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

That is your graphics driver and showed up in about 3 of the dump files. I would like you to try and update your drivers in the following way http://www.sevenforums.com/tutorials/327414-nvidia-drivers-avoid-problems.html

Likewise the Direct X was noted a couple of times.

dxgmms1
start             end                 module name
fffff880`0f000000 fffff880`0f046000   dxgmms1    (pdb symbols)          c:\symcache\dxgmms1.pdb\93AB163000A844D5BF442A979FB6FF991\dxgmms1.pdb
    Loaded symbol image file: dxgmms1.sys
    Mapped memory image file: c:\symcache\dxgmms1.sys\5164DC1346000\dxgmms1.sys
    Image path: \SystemRoot\System32\drivers\dxgmms1.sys
    Image name: dxgmms1.sys
    Timestamp:        Tue Apr 09 22:27:15 2013 (5164DC13)
    CheckSum:         00043C9B
    ImageSize:        00046000
    File version:     6.1.7601.18126
    Product version:  6.1.7601.18126
    File flags:       0 (Mask 3F)
    File OS:          40004 NT Win32
    File type:        3.7 Driver
    File date:        00000000.00000000
    Translations:     0409.04b0
    CompanyName:      Microsoft Corporation
    ProductName:      Microsoft® Windows® Operating System
    InternalName:     dxgmms1.sys
    OriginalFilename: dxgmms1.sys
    ProductVersion:   6.1.7601.18126
    FileVersion:      6.1.7601.18126 (win7sp1_gdr.130409-1534)
    FileDescription:  DirectX Graphics MMS
    LegalCopyright:   © Microsoft Corporation. All rights reserved.

Please go to this link and download the latest version. It will tell you if you have the latest version or not How to install the latest version of DirectX

Also blamed was

MBfilt64
start             end                 module name
fffff880`059e7000 fffff880`059f5000   MBfilt64 T (no symbols)           
    Loaded symbol image file: MBfilt64.sys
    Image path: \SystemRoot\system32\drivers\MBfilt64.sys
    Image name: MBfilt64.sys
    Timestamp:        Thu Jul 30 22:40:32 2009 (4A7267B0)
    CheckSum:         0000FF02
    ImageSize:        0000E000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Kaspersky Virus Removal Tool - Klif Mini-Filter (variant of klif.sys)

and

xusb21
start             end                 module name
fffff880`04dbe000 fffff880`04dd0100   xusb21   T (no symbols)           
    Loaded symbol image file: xusb21.sys
    Image path: \SystemRoot\system32\DRIVERS\xusb21.sys
    Image name: xusb21.sys
    Timestamp:        Thu Aug 13 17:10:17 2009 (4A848F49)
    CheckSum:         00020048
    ImageSize:        00012100
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4]

XBox USB wireless controller
BSOD issues in Win7 with 2009 driver (found in mid-2012 You should be able to uopdate it at http://www.microsoft.com/hardware/download/download.aspx?category=Gaming&type=Gaming&sku=JR9-00001

After doing the above please open an elevated command prompt ( click start, type cmd in the search box, right click on the cmd entry and select run as administrator) in the black box that opens, copy/paste sfc /scannow. If you decide to type it, notice the space between the sfc and the /. It is a system file checker which will scan your system files and attempt to correct any missing or corrupt files. What we want are the results to say windows found no integrity violations. If it says files were found but could not be repaired, close the box, reboot and run it again, after opening the administrative command prompt. You may have to reboot and run it three times for it to repair all system files. If it can't repair them after 3 reboots, let us know.

Please also run Seatools on every mechanical hard drive you have http://www.sevenforums.com/tutorials/313457-seatools-dos-windows-how-use.html#Part3

If you have an SSD, please insure your Firmware is up to date. Please let us know the results of these tests

 

[raven235]

um thanks for this but it turns out it was a stick of ram causing the issue , i cycled through my ram pulling 1 at a time till the crash's stopped , have not had a crash in 17 hours where as befor is was almost hourly also i have run the sfc scannow no issue's found and done all update a few mins ago just to be safe will leave this post unsolved for a lil while longer just in-case

 

[essenbe]

Great, I'm glad you have it running right and hope your good luck continues. Good job. Please let us know how it goes for you.