Help BSOD to do with kernal ,Not sure of problem

[shappywoo]

Hello

i bought a computer for my relative about a year ago it was going okay then all of a sudden BSOD , so he reinstalled the OS (XP) still same BSOD then he tried with Win 7 same thing there has been a couple of things going wrong am not quite sure what it is whether its the motherboard or the OS

here are the what the dumps say:


On Wed 13/06/2012 14:16:00 GMT your computer crashed
crash dump file: C:\Windows\Minidump\061312-31278-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x7F (0x8, 0x80050031, 0x6F8, 0xFFFFF80002AE8392)
Error: UNEXPECTED_KERNEL_MODE_TRAP
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
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 13/06/2012 14:16:00 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x7F (0x8, 0x80050031, 0x6F8, 0xFFFFF80002AE8392)
Error: UNEXPECTED_KERNEL_MODE_TRAP
Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
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 13/06/2012 13:06:16 GMT your computer crashed
crash dump file: C:\Windows\Minidump\061312-20560-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x50 (0xFFFFFFFFFFFFFF80, 0x1, 0xFFFFF80002A8C54B, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 invalid system memory has been referenced.
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 Tue 12/06/2012 19:44:37 GMT your computer crashed
crash dump file: C:\Windows\Minidump\061212-25740-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F190)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 Tue 12/06/2012 18:41:20 GMT your computer crashed
crash dump file: C:\Windows\Minidump\061212-17893-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x50 (0xFFFFFA800DA73BC8, 0x1, 0xFFFFF8800113B62C, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 invalid system memory has been referenced.
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 Tue 12/06/2012 18:21:14 GMT your computer crashed
crash dump file: C:\Windows\Minidump\061212-30154-01.dmp
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x17EA68)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0x10000, 0x8, 0x10000)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 190.38
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 190.38
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.
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 190.38 , NVIDIA Corporation).
Google query: nvlddmkm.sys NVIDIA Corporation KMODE_EXCEPTION_NOT_HANDLED

Am not sure if i ahve fixed any my self but as you can see the latest one has no clue on me
the specs for the computer are:


Language: English (Regional Setting: English)
System Manufacturer: Gigabyte Technology Co., Ltd.
System Model: M68MT-S2P
BIOS: Award Modular BIOS v6.00PG
Processor: AMD Phenom(tm) II X4 840 Processor (4 CPUs), ~3.2GHz
Memory: 4096MB RAM
Available OS Memory: 3838MB RAM
Page File: 1479MB used, 6195MB available
Windows Dir: C:\Windows
DirectX Version: DirectX 11
DX Setup Parameters: Not found
User DPI Setting: Using System DPI
System DPI Setting: 96 DPI (100 percent)
DWM DPI Scaling: Disabled
DxDiag Version: 6.01.7601.17514 32bit Unicode


any help or if am asking in the wrong place any direction would be greatful thanks

 

[djscribbles]

Try running MemTest86 on it, the variety of the errors makes me think it's likely RAM. You've already reinstalled the OS (not to mention XP and Win7) unless you have some unconventional hardware (if you've got TV capture cards, scanners, printers etc, try unplugging them and disabling their drivers) the error is probably not going to be a driver issue.

Once you've done a memtest, if it doesn't find any errors, try Prime95 to vet the processor as well.