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

Repeated BSOD errors probably due to display driver


  • Please log in to reply

#1
prince kapoor

prince kapoor

    Member

  • Member
  • PipPip
  • 14 posts
Hi,

I am using windows 7 laptop. Since last few days the system has started giving BSOD error. It shows a blank white or black screen and then blue screen restart occurs. I did crash dump analysis and below are the details.


On Sun 10/6/2013 7:22:39 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\100613-27222-01.dmp
This was probably caused by the following module: hal.sys (hal+0xEF3F)
Bugcheck code: 0x124 (0x0, 0xFFFFFFFF8682D01C, 0xFFFFFFFFBE000000, 0x800400)
Error: WHEA_UNCORRECTABLE_ERROR
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
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: hal.sys .
Google query: hal.sys WHEA_UNCORRECTABLE_ERROR



On Sat 10/5/2013 8:00:52 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\100613-21902-01.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x8CC26)
Bugcheck code: 0x116 (0xFFFFFFFF87D84458, 0xFFFFFFFF9409D86E, 0x0, 0x2)
Error: VIDEO_TDR_ERROR
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.



On Sat 10/5/2013 11:49:21 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\100513-17612-01.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x8CC26)
Bugcheck code: 0x116 (0xFFFFFFFF85C94510, 0xFFFFFFFF94A4386E, 0x0, 0x2)
Error: VIDEO_TDR_ERROR
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.



On Sat 10/5/2013 11:22:31 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\100513-16863-01.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x8CC26)
Bugcheck code: 0x116 (0xFFFFFFFF85B03328, 0xFFFFFFFF938B086E, 0x0, 0x2)
Error: VIDEO_TDR_ERROR
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.


It looks like there is some problem with driver.
Suggestions needed!.


Regards
Prince Kapoor
  • 0

Advertisements


#2
phillpower2

phillpower2

    Mechanised Mod

  • Moderator
  • 23,861 posts
Hello prince kapoor

A thermal issue was the cause of the first crash and driver issues the rest, both could be triggered by the HDD or damaged/corrupt data on it.

Can you tell us the brand and model name or number of the notebook + how much free storage space is available on the HDD.

Have you tried starting in Safe Mode.

Do you have a Windows 7 installation disk in case it is needed to do a repair installion.
  • 0

#3
prince kapoor

prince kapoor

    Member

  • Topic Starter
  • Member
  • PipPip
  • 14 posts
Hey phillpower2, Thanks for responding.

My laptop is HCL Me XITE L 65
C drive has around 8.7 GB free space, Rest all 4 drives have more than 50 GB free space.
I haven't used the system in safe mode, will try using the system with safe mode with networking
I don't have win 7 installation disk.


Thanks :)
  • 0

#4
phillpower2

phillpower2

    Mechanised Mod

  • Moderator
  • 23,861 posts
You are welcome and thanks for the update prince kapoor :thumbsup:

After you have tried Safe Mode (with networking) please see below;

Please note that in order to avoid data corruption and/or mechanical HDD failure for data only HDDs you must always have a minimum of 10% of the HDDs overall storage capacity available as free space and between and 15 and 20% of a HDDs overall storage capacity available as free space if the OS is on it, the free space allows for information to be copied to and from the drive efficiently.

Not having the above can render a computer inoperable if the HDD concerned has the OS on it due to the MBR (Master Boot Record) becoming damaged/corrupt, please see information @ http://pcsupport.abo...sterbootrec.htm


Go to Start then to Search
Type in compmgmt.msc and click Enter
On the left side click on Disk Management
On the right side you will see your hard drive.
Now I need you to take an expanded screenshot and attach it to your next reply. Do the following to take a screenshot while the above is open and showing on your desktop.

To capture and post a screenshot;

Click on the ALT key + PRT SCR key..its on the top row..right hand side..now click on start...all programs...accessories...paint....left click in the white area ...press CTRL + V...click on file...click on save...save it to your desktop...name it something related to the screen your capturing... BE SURE TO SAVE IT AS A .JPG ...otherwise it may be to big to upload... then after typing in any response you have... click on browse...desktop...find the screenshot..select it and click on the upload button...then on the lower left...after it says upload successful...click on add reply like you normally would.

Screenshot instructions are provided to assist those that may read this topic but are not yet aware of the “how to”.
  • 1

#5
prince kapoor

prince kapoor

    Member

  • Topic Starter
  • Member
  • PipPip
  • 14 posts
Hey Phill,

I am using the system in safe mode, till now its running fine.(Though, it's early to say anything).
I have attached the screenshot,

BSOD.jpg
  • 0

#6
prince kapoor

prince kapoor

    Member

  • Topic Starter
  • Member
  • PipPip
  • 14 posts
UPDATE: The system is running in safe mode for around 1 hour without any error.
  • 0

#7
phillpower2

phillpower2

    Mechanised Mod

  • Moderator
  • 23,861 posts
Apologies for the delay in getting back to you prince kapoor ( work is very demanding at the moment :( )

Thank you for the update which shows that you are low on free disk space on the primary partition which can cause such problems as what you are presently encountering.

Are there any unused programs such as games that you no longer play stored on the C: drive, if there are please uninstall them to free up some space, if you are unsure as to what a program is please leave it and check back here.

NB: The fact that Safe Mode functions ok may only mean that the problem is not occurring because only the bare essential programs and drivers are loading.
  • 0

#8
prince kapoor

prince kapoor

    Member

  • Topic Starter
  • Member
  • PipPip
  • 14 posts
I have cleaned C drive and there is around 21 % space free now.


Do I need to do anything else?
  • 0

#9
phillpower2

phillpower2

    Mechanised Mod

  • Moderator
  • 23,861 posts
Create a new restore point and then check for and install any important Windows updates.

See how the computer behaves in normal mode and then provide an update for us please.
  • 1

#10
prince kapoor

prince kapoor

    Member

  • Topic Starter
  • Member
  • PipPip
  • 14 posts
Just now pc again went weird with blank screen


On Fri 10/11/2013 1:44:55 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\101113-19843-01.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x8CC26)
Bugcheck code: 0x116 (0xFFFFFFFF89339008, 0xFFFFFFFF94E9186E, 0x0, 0x2)
Error: VIDEO_TDR_ERROR
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

#11
prince kapoor

prince kapoor

    Member

  • Topic Starter
  • Member
  • PipPip
  • 14 posts
I believe this is due to some video drivers :(
  • 0

#12
phillpower2

phillpower2

    Mechanised Mod

  • Moderator
  • 23,861 posts
To see if we can identify any driver conflicts please refer to the copy/paste details below provided courtesy of jcgriff2

1. Create a Windows System Restore Point -
Vista - START | type rstrui - create a restore point
Windows 7 - START | type create | select "Create a Restore Point"

2. Run the Driver Verifier -

Go to START | type verifier | make these selections -

1. Select 2nd option - "Create custom settings (for code developers)"
2. Select 2nd option - "Select individual settings from a full list"
3. Check these boxes -▪ Special Pool
▪ Pool Tracking
▪ Force IRQL checking
▪ Deadlock Detection
▪ Security Checks (new as of Windows 7)
▪ Concurrency Stress Test (new as of Windows 8)
▪ DDI compliance checking (new as of Windows 8)
▪ Miscellaneous Checks4. Select last option - "Select driver names from a list"
5. Click on the Provider heading - sorts list by Provider
6. Check ALL boxes where "Microsoft" IS NOT the Provider
7. Click on Finish
8. Re-boot*** IMPORTANT - PLEASE READ:

- If the Driver Verifier (DV) finds a violation, it will result in a BSOD

- After re-start, you may not be able to log on to normal Windows
... • Boot into SAFEMODE - tap the F8 key repeatedly during boot-up
... • Select "System Restore"
... • Choose the restore point that you created in step #1

- For Driver Verifier status
--- select last option, 1st screen -or-
--- type verifier /query (in a cmd/DOS screen)
- To turn Driver Verifier off - verifier /reset then re-boot

- The Driver Verifier needs to run as long as possible - even if the status screen appears clear.
- All future BSOD dumps must be VERIFIER_ENABLED_MINIDUMPs - otherwise the dump(s) are of no use

If your system does BSOD while the Driver Verifier is running, please retrieve the dump file from c:\windows\minidump and attach it to your next reply.
  • 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