Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Windows 7 64 home premium blue screen


  • Please log in to reply
3 replies to this topic

#1 phil0sophy

phil0sophy

  • Members
  • 46 posts
  • OFFLINE
  •  
  • Local time:01:29 PM

Posted 14 October 2011 - 09:48 AM

Hi all first time posting here and was hoping for some help with an issue im having on my MSI GX740 laptop my specs are as follows:

Intel Core I5 450M dual core at 2.40 GHz

4.00 gb ram

ATI Radeon HD 5870

Fully updated drivers for everything.

Now my issue is twice today my screen has blue screened as im watching a movie in windows media player, I get a prewarning stutter and the sound freezes and then it blue screens out of nowhere I have also been having stuttering issues in games but no blue screens as of yet.

I followed the instructions in anothe thread on this site and got the Memory.dmp file out of my windows directory and dubugged it as follows...













Microsoft ® Windows Debugger Version 6.12.0002.633 AMD64
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`03660000 PsLoadedModuleList = 0xfffff800`038a5670
Debug session time: Mon Sep 19 01:37:15.707 2011 (UTC + 1:00)
System Uptime: 0 days 22:49:47.886
Loading Kernel Symbols
...............................................................
................................................................
..............................
Loading User Symbols

Loading unloaded module list
..............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 119, {1, 562ba, 562bd, 562bc}

*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
Probably caused by : dxgmms1.sys ( dxgmms1!VidSchiVerifyDriverReportedFenceId+ad )

Followup: MachineOwner
---------

2: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

VIDEO_SCHEDULER_INTERNAL_ERROR (119)
The video scheduler has detected that fatal violation has occurred. This resulted
in a condition that video scheduler can no longer progress. Any other values after
parameter 1 must be individually examined according to the subtype.
Arguments:
Arg1: 0000000000000001, The driver has reported an invalid fence ID.
Arg2: 00000000000562ba
Arg3: 00000000000562bd
Arg4: 00000000000562bc

Debugging Details:
------------------


DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x119

PROCESS_NAME: System

CURRENT_IRQL: a

LAST_CONTROL_TRANSFER: from fffff8800472822f to fffff800036dcc40

STACK_TEXT:
fffff880`0338c4a8 fffff880`0472822f : 00000000`00000119 00000000`00000001 00000000`000562ba 00000000`000562bd : nt!KeBugCheckEx
fffff880`0338c4b0 fffff880`04807eb9 : 00000000`00000000 00000000`000562ba 00000000`00000000 00000000`000562bd : watchdog!WdLogEvent5+0x11b
fffff880`0338c500 fffff880`04808125 : fffffa80`086a8000 fffff880`0338c630 fffffa80`000011ac 00000000`00000001 : dxgmms1!VidSchiVerifyDriverReportedFenceId+0xad
fffff880`0338c530 fffff880`04807f76 : 00000000`000562ba fffffa80`04804818 fffffa80`0869e000 00000000`00000001 : dxgmms1!VidSchDdiNotifyInterruptWorker+0x19d
fffff880`0338c580 fffff880`048d713f : fffffa80`078c0040 fffff880`01cd6405 fffffa80`0696bd90 fffffa80`041e1bd0 : dxgmms1!VidSchDdiNotifyInterrupt+0x9e
fffff880`0338c5b0 fffff880`04405162 : fffffa80`0a1e2000 fffffa80`078f0700 00000000`00000000 fffffa80`0a73d430 : dxgkrnl!DxgNotifyInterruptCB+0x83
fffff880`0338c5e0 fffff880`04c4e4c6 : fffffa80`07127000 00000000`00000000 00000000`000562ba fffffa80`06ac1000 : atikmpag+0x5162
fffff880`0338c6a0 fffff880`04c4ca17 : 00000000`00000000 00000000`00000000 fffffa80`085cf000 fffffa80`085f1c70 : atikmdag+0x4e4c6
fffff880`0338c770 fffff880`04c5f110 : 00000000`00000000 fffffa80`0aaca1d0 fffffa80`06ac1000 fffffa80`0aaca1d0 : atikmdag+0x4ca17
fffff880`0338c7a0 fffff880`04cecb70 : 00000000`00000000 fffffa80`06ac6010 00003012`00267adc 00002ff2`00267adc : atikmdag+0x5f110
fffff880`0338c7d0 fffff880`04cf2d45 : fffffa80`06ac6010 fffff880`01d7cc27 fffffa80`0aaf7aa0 00000000`00000000 : atikmdag+0xecb70
fffff880`0338c850 fffff880`04cf2f5b : fffffa80`085f1c70 fffffa80`085e49d0 fffffa80`085cf000 00000000`00000000 : atikmdag+0xf2d45
fffff880`0338c940 fffff880`04cf34f8 : fffffa80`00000000 fffff880`0338c9f4 00000000`00000004 fffffa80`085e49d0 : atikmdag+0xf2f5b
fffff880`0338c9c0 fffff880`04cf36ee : 00000000`00000000 fffffa80`085e49d0 fffff880`0338cb10 fffff880`04cf2e14 : atikmdag+0xf34f8
fffff880`0338ca50 fffff880`04cf942d : fffffa80`085cfe20 fffffa80`085e49d0 00000000`00000001 fffffa80`085cf000 : atikmdag+0xf36ee
fffff880`0338cae0 fffff880`04ceb994 : fffffa80`00000000 fffffa80`085cf000 fffff880`0338cc70 00000000`00000001 : atikmdag+0xf942d
fffff880`0338cb60 fffff880`04c4c8c7 : fffff880`03364180 fffffa80`04a07300 00000000`005063c4 00000000`00000000 : atikmdag+0xeb994
fffff880`0338cb90 fffff880`04405cfd : fffff880`03364180 fffff880`0338cc70 0000b107`423501f5 fffff880`0336efc0 : atikmdag+0x4c8c7
fffff880`0338cbc0 fffff800`036d8a7c : fffff880`03364180 fffff880`0338cc70 fffffa80`04a07300 0000b107`423501f5 : atikmpag+0x5cfd
fffff880`0338cbf0 fffff800`036d4942 : fffff880`03364180 fffff880`00000002 00000000`00000002 fffffa80`00000000 : nt!KiInterruptDispatch+0x16c
fffff880`0338cd80 00000000`00000000 : fffff880`0338d000 fffff880`03387000 fffff880`0338cd40 00000000`00000000 : nt!KiIdleLoop+0x32


STACK_COMMAND: kb

FOLLOWUP_IP:
dxgmms1!VidSchiVerifyDriverReportedFenceId+ad
fffff880`04807eb9 c744244053eeffff mov dword ptr [rsp+40h],0FFFFEE53h

SYMBOL_STACK_INDEX: 2

SYMBOL_NAME: dxgmms1!VidSchiVerifyDriverReportedFenceId+ad

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME: dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4ce799c1

FAILURE_BUCKET_ID: X64_0x119_dxgmms1!VidSchiVerifyDriverReportedFenceId+ad

BUCKET_ID: X64_0x119_dxgmms1!VidSchiVerifyDriverReportedFenceId+ad

Followup: MachineOwner
---------

I remember when it bluescreened something about kernel_data_inpage_error but it was so quick that I could not write it down.

Im hoping someone can help with this issue and maybe let me know what the problem is and how I can fix it, im worried it may be my hard drive? but have run all hard drive checking tools and even ran memtest on my ram and everything is fine?

Anyway thanks again all.


BC AdBot (Login to Remove)

 


#2 Allan

Allan

  • BC Advisor
  • 8,602 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:02:29 PM

Posted 14 October 2011 - 10:00 AM

Download BlueScreenView:
http://www.nirsoft.net/utils/blue_screen_view.html
unzip downloaded file and double click on BlueScreenView.exe to run the program.
when scanning is done, go to EDIT - Select All
Go to FILE - SAVE Selected Items, and save the report as BSOD.txt
Open BSOD.txt in Notepad, copy all of the content, and paste it into your next reply

#3 phil0sophy

phil0sophy
  • Topic Starter

  • Members
  • 46 posts
  • OFFLINE
  •  
  • Local time:01:29 PM

Posted 14 October 2011 - 10:09 AM

Download BlueScreenView:
http://www.nirsoft.net/utils/blue_screen_view.html
unzip downloaded file and double click on BlueScreenView.exe to run the program.
when scanning is done, go to EDIT - Select All
Go to FILE - SAVE Selected Items, and save the report as BSOD.txt
Open BSOD.txt in Notepad, copy all of the content, and paste it into your next reply



Ok I have done so but it seems to have only picked up the blue screen I got last month? Not the two that I happened today for some reason? here are the results anyway.

==================================================
Dump File : 091911-18969-01.dmp
Crash Time : 19/09/2011 09:44:50
Bug Check String :
Bug Check Code : 0x00000119
Parameter 1 : 00000000`00000001
Parameter 2 : 00000000`000562ba
Parameter 3 : 00000000`000562bd
Parameter 4 : 00000000`000562bc
Caused By Driver : watchdog.sys
Caused By Address : watchdog.sys+122f
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+7cc40
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\windows\Minidump\091911-18969-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 275,968
==================================================

#4 phil0sophy

phil0sophy
  • Topic Starter

  • Members
  • 46 posts
  • OFFLINE
  •  
  • Local time:01:29 PM

Posted 14 October 2011 - 10:40 AM

I just realised also the original dump I posted was also from that date which leads me to say that windows has not stored my most recent bluescreen? Why would that be? And how do I remedy it?




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users