Jump to content

Welcome to Geeks to Go - Register now for FREE

Geeks To Go is a helpful hub, where thousands of volunteer geeks quickly serve friendly answers and support. Check out the forums and get free advice from the experts. Register now to gain access to all of our features, it's FREE and only takes one minute. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more.

Create Account How it Works
Photo

BSOD while playing games


  • Please log in to reply

#1
RedSkye

RedSkye

    New Member

  • Member
  • Pip
  • 1 posts

Hello, Within the last two months I've been having bsod's while playing video games. At first they were few and far between and only multiplayer/online games were doing it. However, since yesterday it's been doing it on all games within an hour of playing them. Sometimes watching youtube will do it and other times it just does it when idle.

 

Most of the time the computer shuts down before it can collect a crashdump. Attached are the minidumps.

 

windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
Hardware: Predator G5910, Acer
CPU: GenuineIntel Intel® Core™ i7-2600 CPU @ 3.40GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 6423543808 total
VM: 2147352576, free: 1935446016

 

On Wed 06/08/2014 20:32:49 GMT your computer crashed
crash dump file: C:\Windows\minidump\080614-20592-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x50 (0xFFFFFFFFFFFFFF8B, 0x0, 0xFFFFF800034F2C33, 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 that cannot be identified at this time.



On Wed 06/08/2014 20:32:49 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x9871F)
Bugcheck code: 0x50 (0xFFFFFFFFFFFFFF8B, 0x0, 0xFFFFF800034F2C33, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
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 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.



On Mon 21/07/2014 12:45:10 GMT your computer crashed
crash dump file: C:\Windows\minidump\072114-16302-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xD1 (0x0, 0x2, 0x8, 0x0)
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 that cannot be identified at this time.



On Sun 06/07/2014 22:39:10 GMT your computer crashed
crash dump file: C:\Windows\minidump\070614-23400-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x1E (0xFFFFFFFFC000001D, 0xFFFFF8000349EF32, 0x2, 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 that cannot be identified at this time

 

I'm not very tech savy so any help would be greatly appreciated!

Attached Files


  • 0

Advertisements


#2
donetao

donetao

    Banned

  • Banned
  • PipPipPip
  • 753 posts

Hello!

Until a GTG member reads your mini dumps, here's some good reading about BSOD!

http://www.resplende...troubleshooting


  • 0






Similar Topics

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP