help with BSOD please

jonnyshocker · 18 Nov 2013 at 20:29

hi, been having trouble with blue screens for the past couple of nights, pretty sure its down to graphics card driver, is there anybody who could look at these mini dump files for me, thanks

[FONT=Segoe UI, Arial]computer name: JON-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 8546254848 total
VM: 2147352576, free: 1973735424
[/FONT]

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

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

[FONT=Segoe UI, Arial]On Sun 17/11/2013 21:53:59 GMT your computer crashed
crash dump file: C:\Windows\Minidump\111713-46659-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x7F1C0)
Bugcheck code: 0xD1 (0x6C62503, 0x2, 0x1, 0xFFFFFA8008F18B78)
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 which cannot be identified at this time.
[/FONT]

[FONT=Segoe UI, Arial]On Sun 17/11/2013 19:49:02 GMT your computer crashed
crash dump file: C:\Windows\Minidump\111713-44413-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x7F1C0)
Bugcheck code: 0xD1 (0xFFFFFFFFFFFE7960, 0x2, 0x8, 0xFFFFFFFFFFFE7960)
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 which cannot be identified at this time.
[/FONT]

[FONT=Segoe UI, Arial]On Sun 17/11/2013 14:51:48 GMT your computer crashed
crash dump file: C:\Windows\Minidump\111713-36972-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x7F1C0)
Bugcheck code: 0xD1 (0x0, 0x2, 0x1, 0xFFFFFA8009F453E8)
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 which cannot be identified at this time.
[/FONT]

[FONT=Segoe UI, Arial]On Sat 16/11/2013 22:42:00 GMT your computer crashed
crash dump file: C:\Windows\Minidump\111613-39561-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x7F1C0)
Bugcheck code: 0xD1 (0xFFFFFFFFFFFE7960, 0x2, 0x8, 0xFFFFFFFFFFFE7960)
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 which cannot be identified at this time.
[/FONT]

Swarfega · 18 Nov 2013 at 21:38

Were you doing anything at these times?
If it was driver it would normally say. Could be overheating.

jonnyshocker · 18 Nov 2013 at 22:03

playing battlefield 4... everytime, but the thing is it doesnt say amd driver, it says could possibly be driver though, but why do not many other people seem to be having this problem if its battlefield, dont think its overheating, my gpu is at about 70c and cpu about 60c (pretty much at the highest). thanks for reply

bledd · 19 Nov 2013 at 06:43

I'd start by running memtest86
http://www.memtest.org

jonnyshocker · 20 Nov 2013 at 10:42

I've run memtest for a good half an hour or so (to the point where it I 1 pass after 8 tests)
So don't think it's that, don't a disk checker in safe mode and I don't think it found any bad files but it said something about 'ea' files have been repaired I think, does this mean literally 'ea' the game company which could relate I battlefield or is this just abbreviation for something else, I played the game for a good hour or so an no trouble so far, could this be down to some battlefield servers although BSOD is a bit over the top for a game server issue, surely. If it does it again I may revert back I disk driver an try that, thanks for reply though, any more suggestions anyone or is anyone having the same problem?

And jut to let you guys know I have a MSI 280x