Solved bsod on new system lots of whocrashed reports at a brickwall now

bsod on new system included reports

hi, for the past month i have been having crashes and i thought due to it being a new build it may be due to needing windows updates. it is still happening and i thought i may have fixed it yesterday by using a previous nvidia graphics driver as i managed to game for over 2 hours without a bsod but today within 20 mins while downloading i got a crash. i have included the zip file with system info as requested by site and some whocrashed reports if anyone can deciver this and aid me to a fix i would be very happy. thanks.

i have took ram out and put back in. deleted corsair link software and avast. tried several nvidia gpu drivers and used driver sweeper to remove old. i have re installed windows but i cant figure this out.

windows 7 home premium 64bit
nvidia gtx660 ftw 2gb
amd fx9590 (not over clocked)
asus m5a99fx 2.0
corsair h100i
1x scan disck ssd for windows
2x hdd for games
windows security center
novatech 750 psu
novatech 16gb ram

[FONT=Segoe UI, Arial]View attachment 308026[/FONT]




[FONT=Segoe UI, Arial]System Information (local) [/FONT]
[FONT=Segoe UI, Arial]</B>[/FONT]
[FONT=Segoe UI, Arial][FONT=Segoe UI, Arial]computer name: PETE-PC[/FONT]
[FONT=Segoe UI, Arial]windows version: Windows 7 Service Pack 1, 6.1, build: 7601[/FONT]
[FONT=Segoe UI, Arial]windows dir: C:\Windows[/FONT]
[FONT=Segoe UI, Arial]Hardware: BB-895908G, NOVATECH LTD, ASUSTeK COMPUTER INC., M5A99FX PRO R2.0[/FONT]
[FONT=Segoe UI, Arial]CPU: AuthenticAMD AMD FX(tm)-9590 Eight-Core Processor AMD586, level: 21[/FONT]
[FONT=Segoe UI, Arial]8 logical processors, active mask: 255[/FONT]
[FONT=Segoe UI, Arial]RAM: 17075523584 total[/FONT]
[FONT=Segoe UI, Arial]VM: 2147352576, free: 1936429056[/FONT]




[FONT=Segoe UI, Arial]Crash Dump Analysis[/FONT]
[FONT=Segoe UI, Arial]</B>[/FONT]
[FONT=Segoe UI, Arial]Crash dump directory: C:\Windows\Minidump[/FONT]

[FONT=Segoe UI, Arial]Crash dumps are enabled on your computer.[/FONT]

[FONT=Segoe UI, Arial]On Tue 2/25/2014 3:12:43 PM GMT your computer crashed[/FONT]
[FONT=Segoe UI, Arial]crash dump file: C:\Windows\Minidump\022514-13119-01.dmp[/FONT]
[FONT=Segoe UI, Arial]This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x75BC0)
Bugcheck code: 0xD1 (0x0, 0x2, 0x8, 0x0)
Error: [FONT=Segoe UI, Arial]DRIVER_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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


[/FONT]
[FONT=Segoe UI, Arial]On Tue 2/25/2014 3:12:43 PM GMT your computer crashed[/FONT]
[FONT=Segoe UI, Arial]crash dump file: C:\Windows\memory.dmp[/FONT]
[FONT=Segoe UI, Arial]This was probably caused by the following module: [FONT=Segoe UI, Arial]ntkrnlmp.exe[/FONT] (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xD1 (0x0, 0x2, 0x8, 0x0)
Error: [FONT=Segoe UI, Arial]DRIVER_IRQL_NOT_LESS_OR_EQUAL[/FONT]
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


[/FONT]
[FONT=Segoe UI, Arial]On Mon 2/24/2014 2:12:24 PM GMT your computer crashed[/FONT]
[FONT=Segoe UI, Arial]crash dump file: C:\Windows\Minidump\022414-12885-01.dmp[/FONT]
[FONT=Segoe UI, Arial]This was probably caused by the following module: [FONT=Segoe UI, Arial]msfs.sys[/FONT] (Msfs+0x49F4)
Bugcheck code: 0xFC (0xFFFFF880010E19F4, 0x800000040047D121, 0xFFFFF8800AC92530, 0x2)
Error: [FONT=Segoe UI, Arial]ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY[/FONT]
file path: C:\Windows\system32\drivers\msfs.sys
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: Mailslot driver
Bug check description: This indicates that an attempt was made to execute non-executable memory.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. There is a possibility this problem was caused by a virus or other malware.
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.


[/FONT]
[FONT=Segoe UI, Arial]On Mon 2/24/2014 12:23:00 PM GMT your computer crashed[/FONT]
[FONT=Segoe UI, Arial]crash dump file: C:\Windows\Minidump\022414-12901-01.dmp[/FONT]
[FONT=Segoe UI, Arial]This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x75B80)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800031FC147, 0xFFFFF88003832C50, 0x0)
Error: [FONT=Segoe UI, Arial]SYSTEM_SERVICE_EXCEPTION[/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 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.


[/FONT]

[FONT=Segoe UI, Arial]Conclusion[/FONT]
[FONT=Segoe UI, Arial]</B>[/FONT]
[FONT=Segoe UI, Arial]4 crash dumps have been found and analyzed. No offending third party drivers have been found. Consider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you. [/FONT][/FONT]

have had more bsod. one within 20 mins of pc being turned on and was only downloading from net lol. driving me crazy. have tried moving ram to other slots as i am no way able to make sense of all these codes but bluescreen view pointed towards ram/graphic/driver issue so worth a shot i guess. in my original post i did uplad a zip with all system info and minidumps using this sites download. would be much appreciated if anyone can understrand that as its all new to me, thanks

There are three crash dumps in the uploaded zip. BSODs are caused by multiple versions of the display driver.

With 334.89 WHQL:
With 332.21 WHQL:
Different bugcheck codes with different version, but the victim is common.

In this situation, the first obvious step should be to try the last stable version which never failed on itself. Install the NVIDIA DRIVERS 314.22WHQL only.

• Uninstall All nvidia items in Control Panel > Programs and features
  • 3D Vision Control Driver
  • 3D Vision Driver
  • Graphics Driver
  • HD Audio Driver
  • PhysX
  • nvidia Update
  (Are you using nvidia chipset drivers? If so, dont uninstall anything other than those are listed).
• Now follow Drivers - Clean Left over Files after Uninstalling
• Download 314.22 WHQL. While installing, Select Custom (Advanced) install. In the next page, follow this settings:
  
  

If still the situation is the same, we have to think about it otherwise, beyond a driver failure. So let us know the results.

thank you for your reply. i was reading forum and thought i would give removing a stick of ram a try first. i had a bsod within an hour so swapped the current ram with other and so far 3 hours without a bsod on bf4 and assassins creed 4! these are the 2 games that if any give me bsod the most. i am still not confident this has fixed it but i will continue gaming thursday in the hope i can extend those 3 hours of no bsod. i just wanted to rule out faulty ram while everything is still under warrently.

Well done!

After trying pc with one ram stick at a time, i had bsod on one but after trying other stick on its own i have now had no bsod for 7 hrs on games maxed out, No freezing or anything so i am going to shop to get a replacement on the bad stick and hope that is the end of my problem. Fingers crossed this is now solved and i dont post here again for help. Thank you for help and the useful info available on site

Also microsoft security found a malware and i have had around 13gb extra space given back on os drive? As the above crash reports mentioned a possible virus in one crash. I have had avast and avg and norton and they never detected this but credit due microsoft detected it and got rid of this one malware after being installed for only a few days. The file malware came from was the crysis 3 game that has been on system for a while so a bit annoyed that no other security programs detected it.