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

BSOD has started repeatedly.

  • Please log in to reply




  • Member
  • PipPipPip
  • 139 posts
Hi there,

It looks like something has happened on my PC which is causing the BSOD to reoccur repeatedly. The first time happened when I was playing a media file which caused the screen to start flashing and freeze before going to the BSOD. It's happened several times since when I've tried to restart the Laptop. It might just be that my display driver is actually damaged. I've attached WhoCrashed logs as they seem to be asked for on other similar threads. Thanks for any help.

computer name: OWNER-PC
windows version: Windows Vista Service Pack 2, 6.0, build: 6002
windows dir: C:\Windows
CPU: GenuineIntel Intel® Core™2 Duo CPU T7300 @ 2.00GHz Intel586, level: 6
2 logical processors, active mask: 3
RAM: 2144591872 total
VM: 2147352576, free: 1980026880

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Tue 11/06/2013 19:45:46 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini061113-01.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x7C07C)
Bugcheck code: 0x116 (0xFFFFFFFF87D8A008, 0xFFFFFFFF8CA11170, 0x0, 0x2)
file path: C:\Windows\system32\drivers\dxgkrnl.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics Kernel
Bug check description: This indicates that an attempt to reset the display driver and recover from a timeout failed.
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.
  • 0





  • Moderator
  • 34,114 posts
This crashed happened on the 6th which was 7 days ago. Is there or has there been another occurrence since then?
  • 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