lisafunkypants
Topic Starter
Hi i recently had help with what we thought was a virus but after my pc started to constantly turn itself on and off and then i got a blue screen saying PAGE_FAULT_IN_NONPAGED_AREA with an array of STOP codes,I thought it best to come to you guys in software
I have recently had a new hard drive and dvd player installed and last year had a new fan and 2 x 512 memory installed,
i did a Who crahed scan and it came up with this:
Crash dump directory: C:\WINDOWS\Minidump
Crash dumps are enabled on your computer.
On Wed 12/10/2011 14:58:54 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini101211-01.dmp
This was probably caused by the following module: atapi.sys (atapi+0x6B0B)
Bugcheck code: 0x10000050 (0xFFFFFFFFF7276BC4, 0x8, 0xFFFFFFFFF7276BC4, 0x0)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\drivers\atapi.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: IDE/ATAPI Port Driver
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.
On Mon 03/10/2011 11:41:11 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini100311-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0x22AF)
Bugcheck code: 0x10000050 (0xFFFFFFFFBA12E6E0, 0x0, 0xFFFFFFFFBF8022AF, 0x0)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
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.
On Sat 17/09/2011 22:10:48 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini091811-01.dmp
This was probably caused by the following module: oadriver.sys (OADriver+0xCF60)
Bugcheck code: 0x1000000A (0x4, 0x2, 0x0, 0xFFFFFFFF804F8FCD)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\drivers\oadriver.sys
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: oadriver.sys .
Google query: oadriver.sys CUSTOM_ERROR
On Sat 17/09/2011 10:01:23 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini091711-01.dmp
This was probably caused by the following module: usbuhci.sys (usbuhci+0x3509)
Bugcheck code: 0x100000D1 (0x40005, 0x2, 0x1, 0xFFFFFFFFF78FE509)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\drivers\usbuhci.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: UHCI USB Miniport Driver
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.
On Mon 30/05/2011 12:26:36 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini053011-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0x6BF2C)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFFBF86BF2C, 0xFFFFFFFFB69FBB70, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
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 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.
On Mon 23/05/2011 15:39:15 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini052311-01.dmp
This was probably caused by the following module: rdbss.sys (rdbss+0x469)
Bugcheck code: 0x100000D1 (0xFFFFFFFFFFFFFF96, 0x2, 0x1, 0xFFFFFFFF801418C7)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\drivers\rdbss.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Redirected Drive Buffering SubSystem Driver
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.
On Thu 03/02/2011 08:07:48 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini020311-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xE1D33)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF805B8D33, 0xFFFFFFFFF36D9A48, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
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 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 which cannot be identified at this time.
On Wed 19/01/2011 16:39:00 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini011911-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x21A51)
Bugcheck code: 0x20 (0xFFFFFFFF85FB887C, 0xFFFFFFFFFFFFFFFA, 0x0, 0x0)
Error: KERNEL_APC_PENDING_DURING_EXIT
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 an asynchronous procedure call (APC) was still pending when a thread exited.
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.
i would appreciate any help offered as i really need pc
thanks in advance Lisa