Random BSOD happening.

First of all, I would like to say my english isnt good =/. However, I decided ask you guys because I know you are the best in it. I got a new notebook and it starts to have BSOD in random situations. At least, I guess so, because I cant see any logic behind these crashes.
So, I brought this case to this forum, following the rules of this post: [INFO] How to ask for help with a BSOD problem

All the archives the post said I need to bring are here. And also the diagnosis of the WhoCrashed. If you guys need more information, I will get it.

And again, sorry the bad english (I am still learning it)

=============================================================

WhoCrashed's Diagnosis


System Information (local)
--------------------------------------------------------------------------------

computer name: JOÃOVITOR-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Core(TM) i5-2450M CPU @ 2.50GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 4198383616 total
VM: 2147352576, free: 1936441344



--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Tue 21/08/2012 01:54:55 GMT your computer crashed
crash dump file: C:\Windows\Minidump\082012-16754-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0xD1 (0x28, 0x2, 0x0, 0xFFFFF8800170EB2D)
Error: DRIVER_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 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 which cannot be identified at this time.


On Sat 18/08/2012 02:07:08 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081712-21075-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0xD1 (0x28, 0x2, 0x0, 0xFFFFF880017ABB2D)
Error: DRIVER_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 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 which cannot be identified at this time.


On Fri 17/08/2012 22:59:40 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081712-21684-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0xD1 (0x28, 0x2, 0x0, 0xFFFFF88001706B2D)
Error: DRIVER_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 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 which cannot be identified at this time.


On Wed 15/08/2012 20:30:24 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081512-18408-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0xD1 (0x28, 0x2, 0x0, 0xFFFFF880017B1B2D)
Error: DRIVER_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 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 which cannot be identified at this time.


On Wed 15/08/2012 20:30:24 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: mfenlfk.sys (mfenlfk+0x133E)
Bugcheck code: 0xD1 (0x28, 0x2, 0x0, 0xFFFFF880017B1B2D)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\mfenlfk.sys
product: SYSCORE
company: McAfee, Inc.
description: McAfee NDIS Light Filter 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.
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: mfenlfk.sys (McAfee NDIS Light Filter Driver, McAfee, Inc.).
Google query: mfenlfk.sys McAfee, Inc. DRIVER_IRQL_NOT_LESS_OR_EQUAL




On Tue 14/08/2012 03:55:13 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081412-17128-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0xD1 (0x28, 0x2, 0x0, 0xFFFFF88001611B2D)
Error: DRIVER_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 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 which cannot be identified at this time.


On Sun 12/08/2012 00:53:44 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081112-22105-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0xD1 (0x28, 0x2, 0x0, 0xFFFFF8800174FB2D)
Error: DRIVER_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 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 which cannot be identified at this time.


On Sat 11/08/2012 21:15:11 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081112-16270-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0xD1 (0x28, 0x2, 0x0, 0xFFFFF88001740B2D)
Error: DRIVER_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 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 which cannot be identified at this time.



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

8 crash dumps have been found and analyzed. A third party driver has 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:

mfenlfk.sys (McAfee NDIS Light Filter Driver, McAfee, Inc.)


P.S> I've already uninstalled, reinstalled, and uninstalled McAfee and the problem is still happening

Uninstall Mcafee. Download and use Microsoft Security Essentials.

AFter you install, Essentials and you get a BSOD post. I want to see if the offending driver has been removed.

I still want to see the report, but you can find out now
Go to search by the start button and type cmd
in cmd type driverquery

And so what? Sorry, I am kinda newbie on these issues.

EDIT: Here is the cmd result for the command

Chevk said:

And so what? Sorry, I am kinda newbie on these issues.

EDIT: Here is the cmd result for the command

All I did was to look at the driver list and saw the driver that caused the first BSOD was still in your system.
If you uninstalled Mcafee, you may want to go to the Mcafee site and use the uninstall tool. Any new BSODs after that, send the file, dont send your text of the file.