PC Crashing due to drivers?

[bennyessex]

Evening all.
A complete newb to the forum.
Need some advice - My PC running windows 7 has been crashing regularly when running games, videos or even when downloading large files. Ive used a program called "whocrashed" to run a report as follows:

[FONT=Segoe UI, Arial]System Information (local) [/FONT]
[FONT=Segoe UI, Arial]computer name: BEN-PC
windows version: Windows 7 , 6.1, build: 7600
windows dir: C:\Windows
Hardware: Aspire X3950, Acer
CPU: GenuineIntel Intel(R) Core(TM) i3 CPU 550 @ 3.20GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 3211902976 total
VM: 2147352576, free: 1947439104


[/FONT]
[FONT=Segoe UI, Arial] Crash Dump Analysis [/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 Sat 23/11/2013 16:35:16 GMT your computer crashed
crash dump file: C:\Windows\Minidump\112313-21496-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]nwifi.sys[/FONT] (0xFFFFF88006DB5FCD)
Bugcheck code: 0xD1 (0xA, 0x2, 0x0, 0xFFFFF88006DB5FCD)
Error: [FONT=Segoe UI, Arial]DRIVER_IRQL_NOT_LESS_OR_EQUAL[/FONT]
file path: C:\Windows\system32\drivers\nwifi.sys
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NativeWiFi Miniport 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.
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 Sat 23/11/2013 16:35:16 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]nwifi.sys[/FONT] (nwifi+0xAFCD)
Bugcheck code: 0xD1 (0xA, 0x2, 0x0, 0xFFFFF88006DB5FCD)
Error: [FONT=Segoe UI, Arial]DRIVER_IRQL_NOT_LESS_OR_EQUAL[/FONT]
file path: C:\Windows\system32\drivers\nwifi.sys
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NativeWiFi Miniport 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.
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 Sun 10/11/2013 15:58:39 GMT your computer crashed
crash dump file: C:\Windows\Minidump\111013-17284-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]mrvw24c.sys[/FONT] (0xFFFFF88006B2073F)
Bugcheck code: 0xD1 (0x76, 0x2, 0x0, 0xFFFFF88006B2073F)
Error: [FONT=Segoe UI, Arial]DRIVER_IRQL_NOT_LESS_OR_EQUAL[/FONT]
file path: C:\Windows\system32\drivers\mrvw24c.sys
product: [FONT=Segoe UI, Arial]Device driver for Marvell 802.11n NIC[/FONT]
company: [FONT=Segoe UI, Arial]Marvell Semiconductor, Inc[/FONT]
description: ExtSta NDIS 6.0 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: mrvw24c.sys (ExtSta NDIS 6.0 driver, Marvell Semiconductor, Inc).
Google query: [FONT=Segoe UI, Arial]Marvell Semiconductor, Inc DRIVER_IRQL_NOT_LESS_OR_EQUAL[/FONT]


[/FONT]
[FONT=Segoe UI, Arial]On Tue 01/10/2013 17:37:47 GMT your computer crashed
crash dump file: C:\Windows\Minidump\100113-14742-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x6F880)
Bugcheck code: 0x9F (0x3, 0xFFFFFA8005888050, 0xFFFFF80001FBA518, 0xFFFFFA8006C0FB10)
Error: [FONT=Segoe UI, Arial]DRIVER_POWER_STATE_FAILURE[/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 bug check indicates that the driver is in an inconsistent or invalid power state.
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 Sun 18/08/2013 17:39:34 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081813-16926-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]mrvw24c.sys[/FONT] (MRVW24C+0x27309)
Bugcheck code: 0xC2 (0x7, 0x1097, 0xE0000, 0xFFFFFA800686D010)
Error: [FONT=Segoe UI, Arial]BAD_POOL_CALLER[/FONT]
file path: C:\Windows\system32\drivers\mrvw24c.sys
product: [FONT=Segoe UI, Arial]Device driver for Marvell 802.11n NIC[/FONT]
company: [FONT=Segoe UI, Arial]Marvell Semiconductor, Inc[/FONT]
description: ExtSta NDIS 6.0 driver
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: mrvw24c.sys (ExtSta NDIS 6.0 driver, Marvell Semiconductor, Inc).
Google query: [FONT=Segoe UI, Arial]Marvell Semiconductor, Inc BAD_POOL_CALLER[/FONT]


[/FONT]
[FONT=Segoe UI, Arial]On Sat 10/08/2013 20:00:01 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081013-15615-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x6F850)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: [FONT=Segoe UI, Arial]KMODE_EXCEPTION_NOT_HANDLED[/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 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.


[/FONT]
[FONT=Segoe UI, Arial]On Tue 06/08/2013 19:23:59 GMT your computer crashed
crash dump file: C:\Windows\Minidump\080713-25178-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]nwifi.sys[/FONT] (0xFFFFF88008794FCD)
Bugcheck code: 0xD1 (0xA, 0x2, 0x0, 0xFFFFF88008794FCD)
Error: [FONT=Segoe UI, Arial]DRIVER_IRQL_NOT_LESS_OR_EQUAL[/FONT]
file path: C:\Windows\system32\drivers\nwifi.sys
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NativeWiFi Miniport 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.
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 Sat 13/07/2013 19:54:09 GMT your computer crashed
crash dump file: C:\Windows\Minidump\071313-20997-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x6F880)
Bugcheck code: 0xC2 (0x7, 0x1097, 0xE0005, 0xFFFFFA8002966160)
Error: [FONT=Segoe UI, Arial]BAD_POOL_CALLER[/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 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.
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 Sat 13/07/2013 19:38:05 GMT your computer crashed
crash dump file: C:\Windows\Minidump\071313-14430-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x6F880)
Bugcheck code: 0xC2 (0x7, 0x1097, 0x40D000C, 0xFFFFFA80075C8830)
Error: [FONT=Segoe UI, Arial]BAD_POOL_CALLER[/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 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.
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 Sat 13/07/2013 19:19:24 GMT your computer crashed
crash dump file: C:\Windows\Minidump\071313-15849-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]mrvw24c.sys[/FONT] (0xFFFFF880084DDDC4)
Bugcheck code: 0xD1 (0x2, 0x2, 0x0, 0xFFFFF880084DDDC4)
Error: [FONT=Segoe UI, Arial]DRIVER_IRQL_NOT_LESS_OR_EQUAL[/FONT]
file path: C:\Windows\system32\drivers\mrvw24c.sys
product: [FONT=Segoe UI, Arial]Device driver for Marvell 802.11n NIC[/FONT]
company: [FONT=Segoe UI, Arial]Marvell Semiconductor, Inc[/FONT]
description: ExtSta NDIS 6.0 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: mrvw24c.sys (ExtSta NDIS 6.0 driver, Marvell Semiconductor, Inc).
Google query: [FONT=Segoe UI, Arial]Marvell Semiconductor, Inc DRIVER_IRQL_NOT_LESS_OR_EQUAL[/FONT]


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

Any advice would be appreciated!
[/FONT]

 

[matts6887]

it appears there are 3 different problems. Looks like there is a issue with power management, wifi driver(s), and one other one. I would try and see if you can update the drivers from your motherboard manufacturer for the power management; and see if you can find out what brand your wireless card or access is and go to the site for that and see if you can get some updated drivers for it.