[HELP] ntoskrnl.exe & ntkrnlmp.exe & fltmgr.sys BSOD Issue

[Mattrhorn]

[FONT=Segoe UI, Arial]Ive been getting BSOD's recently that i cant quite fix, I have updated A LOT of drivers recently to try to fix it and it has got quiet, but today i had 2 in a the span of 1 hour relating to what I had before. I dont really know what it is but I really want to find out the answer. Just Some information that This started happening after I got
[/FONT]

• [FONT=Segoe UI, Arial]A New Power Supply[/FONT]
• [FONT=Segoe UI, Arial]a Second EVGA GTX 550 Ti GPU[/FONT]
• [FONT=Segoe UI, Arial]and a Khuler Whater Colling CPU System[/FONT]

[FONT=Segoe UI, Arial]One Other Problem i have had is that I can use my OPTICAL DRIVE through the bios but the computer doesnt see or recognise it in the actual accounts. If there is an explaination for that in this please let me know[/FONT][FONT=Segoe UI, Arial]

Files Needed in Description

This is all the Information collected from WhoCrashed (HOME EDITION) v3.06:

On Mon 08/10/2012 2:42:05 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\100712-29265-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x7F1C0)
Bugcheck code: 0xA (0x8, 0x2, 0x0, 0xFFFFF80003583E1B)
Error: [FONT=Segoe UI, Arial]IRQL_NOT_LESS_OR_EQUAL[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/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 which cannot be identified at this time.
[/FONT]

[FONT=Segoe UI, Arial]On Mon 08/10/2012 2:42:05 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntkrnlmp.exe[/FONT] (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xA (0x8, 0x2, 0x0, 0xFFFFF80003583E1B)
Error: [FONT=Segoe UI, Arial]IRQL_NOT_LESS_OR_EQUAL[/FONT]
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 which cannot be identified at this time.
[/FONT]

[FONT=Segoe UI, Arial]On Wed 03/10/2012 9:31:48 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\100312-44491-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x7F1C0)
Bugcheck code: 0xA (0x8, 0x2, 0x0, 0xFFFFF80003587E1B)
Error: [FONT=Segoe UI, Arial]IRQL_NOT_LESS_OR_EQUAL[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/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 which cannot be identified at this time.
[/FONT]

[FONT=Segoe UI, Arial]On Sat 29/09/2012 11:44:49 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\092912-27534-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x7F1C0)
Bugcheck code: 0xA (0x8, 0x2, 0x0, 0xFFFFF8000353BE1B)
Error: [FONT=Segoe UI, Arial]IRQL_NOT_LESS_OR_EQUAL[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/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 which cannot be identified at this time.
[/FONT]

[FONT=Segoe UI, Arial]On Fri 28/09/2012 2:30:34 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\092712-30560-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x7F1C0)
Bugcheck code: 0xA (0x8, 0x2, 0x0, 0xFFFFF80003593E1B)
Error: [FONT=Segoe UI, Arial]IRQL_NOT_LESS_OR_EQUAL[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/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 which cannot be identified at this time.
[/FONT]

[FONT=Segoe UI, Arial]On Wed 26/09/2012 10:46:05 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\092612-32011-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]fltmgr.sys[/FONT] (fltmgr+0x21A0)
Bugcheck code: 0xA (0xFFFFFA80305A1260, 0x2, 0x1, 0xFFFFF80003594366)
Error: [FONT=Segoe UI, Arial]IRQL_NOT_LESS_OR_EQUAL[/FONT]
file path: C:\Windows\system32\drivers\fltmgr.sys
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: Microsoft Filesystem Filter Manager
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 which cannot be identified at this time.
[/FONT]

[FONT=Segoe UI, Arial]On Sat 22/09/2012 6:40:52 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\092212-38859-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]fltmgr.sys[/FONT] (fltmgr+0x21A0)
Bugcheck code: 0xA (0xFFFFFA8031110280, 0x2, 0x1, 0xFFFFF80003533366)
Error: [FONT=Segoe UI, Arial]IRQL_NOT_LESS_OR_EQUAL[/FONT]
file path: C:\Windows\system32\drivers\fltmgr.sys
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: Microsoft Filesystem Filter Manager
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 which cannot be identified at this time.
[/FONT]

[FONT=Segoe UI, Arial]On Sat 22/09/2012 5:00:36 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\092212-29031-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]fltmgr.sys[/FONT] (fltmgr+0x21A0)
Bugcheck code: 0xA (0xFFFFFA80313CC1B8, 0x2, 0x1, 0xFFFFF80003541366)
Error: [FONT=Segoe UI, Arial]IRQL_NOT_LESS_OR_EQUAL[/FONT]
file path: C:\Windows\system32\drivers\fltmgr.sys
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: Microsoft Filesystem Filter Manager
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 which cannot be identified at this time.
[/FONT]

[FONT=Segoe UI, Arial]On Thu 20/09/2012 9:04:29 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\092012-25256-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]fltmgr.sys[/FONT] (fltmgr+0x21A0)
Bugcheck code: 0xA (0xFFFFFA80311E01C8, 0x2, 0x1, 0xFFFFF80003586366)
Error: [FONT=Segoe UI, Arial]IRQL_NOT_LESS_OR_EQUAL[/FONT]
file path: C:\Windows\system32\drivers\fltmgr.sys
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: Microsoft Filesystem Filter Manager
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 which cannot be identified at this time.
[/FONT]

[FONT=Segoe UI, Arial]On Thu 20/09/2012 4:05:02 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\092012-27596-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]fltmgr.sys[/FONT] (fltmgr+0x21A0)
Bugcheck code: 0xA (0xFFFFFA80312101C0, 0x2, 0x1, 0xFFFFF80003549366)
Error: [FONT=Segoe UI, Arial]IRQL_NOT_LESS_OR_EQUAL[/FONT]
file path: C:\Windows\system32\drivers\fltmgr.sys
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: Microsoft Filesystem Filter Manager
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 which cannot be identified at this time.
[/FONT]

[FONT=Segoe UI, Arial]On Thu 20/09/2012 8:32:11 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\092012-24913-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]fltmgr.sys[/FONT] (fltmgr+0x21A0)
Bugcheck code: 0xA (0xFFFFFA8030B24290, 0x2, 0x1, 0xFFFFF80003538366)
Error: [FONT=Segoe UI, Arial]IRQL_NOT_LESS_OR_EQUAL[/FONT]
file path: C:\Windows\system32\drivers\fltmgr.sys
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: Microsoft Filesystem Filter Manager
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 which cannot be identified at this time.
[/FONT]

[FONT=Segoe UI, Arial]On Mon 17/09/2012 9:24:26 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\091712-28828-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]fltmgr.sys[/FONT] (fltmgr+0x21A0)
Bugcheck code: 0xA (0xFFFFFA8030E0D2C8, 0x2, 0x1, 0xFFFFF80003543366)
Error: [FONT=Segoe UI, Arial]IRQL_NOT_LESS_OR_EQUAL[/FONT]
file path: C:\Windows\system32\drivers\fltmgr.sys
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: Microsoft Filesystem Filter Manager
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 which cannot be identified at this time.
[/FONT]

[FONT=Segoe UI, Arial]On Fri 14/09/2012 10:55:06 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\091412-28017-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]fltmgr.sys[/FONT] (fltmgr+0x21A0)
Bugcheck code: 0xA (0xFFFFFA8030CBC218, 0x2, 0x1, 0xFFFFF80003588366)
Error: [FONT=Segoe UI, Arial]IRQL_NOT_LESS_OR_EQUAL[/FONT]
file path: C:\Windows\system32\drivers\fltmgr.sys
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: Microsoft Filesystem Filter Manager
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 which cannot be identified at this time.
[/FONT]

[FONT=Segoe UI, Arial]On Fri 14/09/2012 11:16:29 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\091412-26379-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]fltmgr.sys[/FONT] (fltmgr+0x21A0)
Bugcheck code: 0xA (0xFFFFFA8030A12258, 0x2, 0x1, 0xFFFFF80003587366)
Error: [FONT=Segoe UI, Arial]IRQL_NOT_LESS_OR_EQUAL[/FONT]
file path: C:\Windows\system32\drivers\fltmgr.sys
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: Microsoft Filesystem Filter Manager
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 which cannot be identified at this time.
[/FONT]

[FONT=Segoe UI, Arial]On Thu 13/09/2012 8:44:03 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\091312-29140-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x7F1C0)
Bugcheck code: 0xA (0x8, 0x2, 0x0, 0xFFFFF8000354BE1B)
Error: [FONT=Segoe UI, Arial]IRQL_NOT_LESS_OR_EQUAL[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/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 which cannot be identified at this time. [/FONT]

 

[Arc]

First of all, you need to update your Realtek RTL8168D/8111D Family PCI-E Gigabit Ethernet NIC.

► update the network driver.
First, download the network card driver from manufactuer's website, Realtek
Then reinstall the driver:

1. Click the Start Button, type "devmgmt.msc" (without quotation marks) in the Start Menu Search box and press Enter.
2. Double click to expand "Network adaptors".
3. Right click your network card and click Uninstall.
4. Check "Delete driver software for this device" check box, click OK.
5. Restart the computer
6. If windows does not auto configure the appropriate drivers at startup, install the downloaded one manually.

► This error is often caused by Notron, and Mcafee.

fffff880`0354d568  fffff880`01005132 [COLOR=Red]fltmgr![/COLOR]GetContextFromStreamList+0x192

My suggestion, you uninstall those both for the time being (McAfee permanently) and use Microsoft Security Essentials - Free Antivirus for Windows.

► Free up the startup.

1. Click on the Start button
2. Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
3. Select the “Startup” tab.
4. Deselect all items other than the antivirus.
5. Apply > OK
6. Accept the restart.

Let us know the results.

 

[Mattrhorn]

Hey Arc,
Thanks for all the help, I have not done anything yet, but i am going to get to that right now. My one question is for the security software, is it because of mcafee and norton's conflicting with eachother, or are both of those just a source of the problem. The reason is ive been using Nortons for around 2 years now and I accidentally download McAfee while getting a new flashplayer and havent gotten around to uninstalling it cause i dont need it. So will removing McAfee be alright or is it Important that I remove both...

Thanks for the reply by the way, I REALLY appreciate it. Ill do what you said and give feedback at the end of the day (10:00pm EST).

as well as look for things relating to:

[FONT=Segoe UI, Arial]One Other Problem i have had is that I can use my OPTICAL DRIVE through the bios but the computer doesnt see or recognize it in the actual accounts. If there is an explanation for that in this please let me know[/FONT]

Thanks for everything arc

EDIT 1: Hey Arc, Uninstalled McAfee, as well as I realized that most of my blue screens are caused while playing games in extreme graphics, and one of the times it said something like dxsmmg1.sys or something like that, so see if this could be a DirctX thing. I let Steam handle downloading directx for me, so should look into actually downloading it from microsoft site to get a clean install?

One other thing is that everytime i start up i get a permession thing asking if its ok to run "jucheck.exe" or something really similar to that, it says its from orical and it has flash so i assumed that it was flash player related. but i never got this before, just recently like 1-2 months ago when this started happening

 

[Arc]

Mat, McAfee is the worst program ever coded, perhaps. It causes a huge lot of troubles, we see every day. You MUST to remove it.

About norton, that is good, no doubt. but if you use it tactfully. Norton, if used normally, also cause a lot of troubles.

On the other hand, MSE is the best security, and never causes a problem. It does not cost anything, just needs WGA to pass before installation.

That is why, if there is a security software related issue, we suggest to use MSE.

And, NEVER use multiple security software at once.

 

[Mattrhorn]

Alright, well I removed McAfee aswell as i uptaded the driver you told me to which was sthe Realtek one, I was on an old one, and when I uninstalled it, it went back and downloaded the old one again so i went in and manually downloaded it, Hope that helps. So ya, looks like its a waiting game now. Thanks for all the help Arc.

As well as Norton's is only used to check downloads for viruses as well as scans 1 every other week so its not heavily used, but i guess ill see if anything comes up.

 

[Arc]

Let us know the results

 

[Mattrhorn]

Did you read my edit on post #3?

 

[Arc]

Sorry I havent seen it.

That jucheck.exe is Java automatic update utility. If you dont need Java, you may uninstall it.

Otherwise Free up the startup.

1. Click on the Start button
2. Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
3. Select the “Startup” tab.
4. Deselect all items other than the antivirus.
5. Apply > OK
6. Accept the restart.

I guess the jucheck.exe will not prompt up at startup anymore.


For the games, your thought are almost right. In such a situation, you may set the games preference settings to minimum, hopefully it will work there.

 

[Mattrhorn]

Alright, So i freed up the startup with some exceptions:

• USB 3.0 Monitor
• Microsoft(R) Windows(R) Operating System
• And a few Logitech controllers for my keyboard, so that my keyboard works properly

Other than that everything is off. My computer has the power to run games at extreme graphics, but i think that the problem meybe with a corrupt DirectX install, so i am going to try a fresh install with that and see how that works.

Thanks again for the Assistance !!!

 

[Arc]

You are welcome. Let us know the results when you are done

 

[Mattrhorn]

Well around an hour and a half has gone by without any isues, Ive been putting gaming stress tests on my computer because that was usually when it happened soo i did that, Nothing soo far. I am a Small Youtube Gamer Commentator, so i was using Fraps as well as Vegas Pro to test the stress of everything, and everything worked out great, so im crossing my fingers with this one hoping its solved. Ill update again every few hours. You dont need to reply to this if you dont want to because it is unnecessary. Ill keep Updating on a regular basis and if anything happens ill let you know. Thanks again

 

[Mattrhorn]

I just got my blue screen like 5 minutes ago I opened up and ran that SF tool thing and got the files for you, Let me know what you think. This happened while editing a video in Vegas Pro. There isnt allot of edits and i didnt use up more than 45% of my cpu power. Im very concerned now about anything i do and to make sure i save EVERYTHING. so yea, let me know what you think

EDIT 1: Well I opened up WhoCrashed.exe and it came up with this:
EDIT 2: Im starting to notice that most of the BSOD's prop up 2 Files at the same time, Could this be because of Conflicting Drivers?

[FONT=Segoe UI, Arial]On Mon 08/10/2012 10:52:53 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\100812-32541-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]fltmgr.sys[/FONT] (fltmgr+0x21A0)
Bugcheck code: 0xA (0xFFFFFA803117D2C0, 0x2, 0x1, 0xFFFFF80003539366)
Error: [FONT=Segoe UI, Arial]IRQL_NOT_LESS_OR_EQUAL[/FONT]
file path: C:\Windows\system32\drivers\fltmgr.sys
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: Microsoft Filesystem Filter Manager
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 which cannot be identified at this time.
[/FONT]

[FONT=Segoe UI, Arial]On Mon 08/10/2012 10:52:53 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntkrnlmp.exe[/FONT] (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xA (0xFFFFFA803117D2C0, 0x2, 0x1, 0xFFFFF80003539366)
Error: [FONT=Segoe UI, Arial]IRQL_NOT_LESS_OR_EQUAL[/FONT]
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 which cannot be identified at this time.

[/FONT]

[FONT=Segoe UI, Arial]On Mon 08/10/2012 2:42:05 AM GMT your computer crashed
[/FONT][FONT=Segoe UI, Arial]On Mon 08/10/2012 2:42:05 AM GMT your computer crashed[/FONT]

 

[Arc]

First, run a disc check.

1. Reseat the sata and power.
2. Run chkdsk /f/r, following the option two of the tutorial Disk Check
3. Seatool for dos: SeaTools | Seagate download
   Burn it in a blank cd. boot from the CD, click on "Accept", wait for it to finish detecting the drives, then in the upper left corner select "Basic Tests", then select "Long Test" and let it run.

Second, uninstall Norton for the time being, use Microsoft Security Essentials - Free Antivirus for Windows. The fltmgr.sys error causes by the antivirus programs, too.

And, run memtest for at least 8 passes, preferably overnight, for each module placed in each slot, one by one.
http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

Let us know the results.

 

[Mattrhorn]

First, run a disc check.

1. Reseat the sata and power.
2. Run chkdsk /f/r, following the option two of the tutorial Disk Check
3. Seatool for dos: SeaTools | Seagate download
   Burn it in a blank cd. boot from the CD, click on "Accept", wait for it to finish detecting the drives, then in the upper left corner select "Basic Tests", then select "Long Test" and let it run.

Well this is sort of a problem due to the fact that i cant burn to a cd/dvd/bluray because my computer for some reason cant see my optical drive inside windows. Only in the bios. I will uninstall norton's though tomorrow. Aswell as sorry for the late response my school went on 11 hours today :S

Is there any other ways of doing this?

 

[Arc]

You can do it by making a bootable USB, too.

But, before that, you can follow step 1 and 2 easily.

 

[Mattrhorn]

Alright man, Is it possible to start conversations through skype just for easier conversations cause even though these forums are pretty amazing, communication is just a bit harder through here?.

Aswell as i uninstalled nortons and got a BSOD like 10 minutes before that.

This is what came up and ill send the SF Files

[FONT=Segoe UI, Arial]On Wed 10/10/2012 2:49:26 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\100912-39889-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x7F1C0)
Bugcheck code: 0xA (0x8, 0x2, 0x0, 0xFFFFF80003594E1B)
Error: [FONT=Segoe UI, Arial]IRQL_NOT_LESS_OR_EQUAL[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/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 which cannot be identified at this time.
[/FONT]

[FONT=Segoe UI, Arial]On Wed 10/10/2012 2:49:26 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntkrnlmp.exe[/FONT] (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xA (0x8, 0x2, 0x0, 0xFFFFF80003594E1B)
Error: [FONT=Segoe UI, Arial]IRQL_NOT_LESS_OR_EQUAL[/FONT]
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 which cannot be identified at this time. [/FONT]

 

[Arc]

OK, here is it. Apparently your crash is network caused.

► You have a Realtek PCI GBE Family Controller, the driver is somehow old.

 Driver     c:\windows\system32\drivers\rt64win7.sys (7.46.610.2011, 526.60 KB (539,240 bytes), [COLOR=red]10/06/2011[/COLOR] 6:34 AM)

► You also have a Hamachi Network Interface, that one is even old.

 Driver     c:\windows\system32\drivers\hamachi.sys (7.0.1.1, 33.06 KB (33,856 bytes), [COLOR=red]18/03/2009[/COLOR] 5:35 PM)

Update both the network drivers.

► Norton is a known cause of crash. It blocks some network elements off and on. As a test, uninstall Norton and use Free Microsoft Scurity Essentials.

► Free up the startup.

1. Click on the Start button
2. Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
3. Select the “Startup” tab.
4. Deselect all items other than the antivirus.
5. Apply > OK
6. Accept the restart.

Let us know the results.

 

[Mattrhorn]

Nortons Gone for the time being, Startup is free'd. I dont know how to get an updated realtek driver caused i used the one i got from the link you sent me w while back. Ill try again. Adn for Hamachi, ill have to look around for that. But thanks. Ill look into everything you have said

EDIT 1: No Drivers are available for Hamachi, This is the Most recent one. The Realtek driver however was updated to the current version as it wasn't before
EDIT 2: Running Hard Processes on My computer and everything... So far no issues, so i have my fingers crossed. Hope its fixed

 

[Arc]

I also hope it fixed, but if it still crashes, and pointed the cause to network, we may need to think for log me in hamachi, unfortunately.

Best of luck.

 

[Mattrhorn]

Bad News... After all this time:

[FONT=Segoe UI, Arial]On Thu 01/11/2012 1:10:52 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\103112-49561-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]nvlddmkm.sys[/FONT] (nvlddmkm+0xF5985)
Bugcheck code: 0xA (0xFFFFFA8030846290, 0x2, 0x1, 0xFFFFF8000353B376)
Error: [FONT=Segoe UI, Arial]IRQL_NOT_LESS_OR_EQUAL[/FONT]
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: [FONT=Segoe UI, Arial]NVIDIA Windows Kernel Mode Driver, Version 306.23 [/FONT]
company: [FONT=Segoe UI, Arial]NVIDIA Corporation[/FONT]
description: NVIDIA Windows Kernel Mode Driver, Version 306.23
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 306.23 , NVIDIA Corporation).
Google query: [FONT=Segoe UI, Arial]nvlddmkm.sys NVIDIA Corporation IRQL_NOT_LESS_OR_EQUAL[/FONT]


[/FONT]

[FONT=Segoe UI, Arial]On Thu 01/11/2012 1:10:52 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntkrnlmp.exe[/FONT] (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xA (0xFFFFFA8030846290, 0x2, 0x1, 0xFFFFF8000353B376)
Error: [FONT=Segoe UI, Arial]IRQL_NOT_LESS_OR_EQUAL[/FONT]
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 which cannot be identified at this time. [/FONT]

--------------------------------------------------------------------------------------------------------------

It said that windows removed a malicious item of the computer after it restarted soo I tthink that has something to do with it and it may just be nothing but please take a look if you have time...

EDIT1: I went ahead and updated my NVIDIA Driver because it was out of date by like 2 months soo...

Thanks,
Mattrhorn