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

BSoD w/ Debugger Log


  • Please log in to reply
2 replies to this topic

#1 JRit

JRit

  • Members
  • 1 posts
  • OFFLINE
  •  
  • Local time:12:04 AM

Posted 31 December 2009 - 02:52 PM

Hi there, found this site when trying to google my problem, upon browsing over a few BSoD problems here, i followed the advice of one of your members and installed the debugger and set the symbols url correctly.

Currently my setup is

Motherboard: ASUS P5Q-E
Graphics Card: ATI Radeon 4800 Series
O/S: Windows 7 (64bit)
Drives: 2x 500GB (set under B: & D: - D: is the main windows used drive)
RAM: 4GB Corsair

Problem:

Every so often i happen to receive a BSoD labelled - IRQL_GT_ZERO_AT_SYSTEM_SERVICE.

I set up the event log to try and track it down, but all i would get is events stating logging stopped, something crashed, froze etc the system, and to my knowledge i haven't installed anything recently that would cause this semi intermittant problem, so as stated above i followed a topics advice and installed a debugger and found the following information.

BEGIN_DEBUG:


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


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

Symbol search path is: SRV*d:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02e4c000 PsLoadedModuleList = 0xfffff800`03089e50
Debug session time: Thu Dec 31 19:17:55.388 2009 (GMT+0)
System Uptime: 0 days 1:39:48.448
Loading Kernel Symbols
...............................................................
................................................................
...............................................
Loading User Symbols
PEB is paged out (Peb.Ldr = 00000000`7efdf018). Type ".hh dbgerr001" for details
Loading unloaded module list
........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 4A, {75112dd9, 2, 0, fffff88003dbeca0}

PEB is paged out (Peb.Ldr = 00000000`7efdf018). Type ".hh dbgerr001" for details
PEB is paged out (Peb.Ldr = 00000000`7efdf018). Type ".hh dbgerr001" for details
Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceExit+245 )

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

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

IRQL_GT_ZERO_AT_SYSTEM_SERVICE (4a)
Returning to usermode from a system call at an IRQL > PASSIVE_LEVEL.
Arguments:
Arg1: 0000000075112dd9, Address of system function (system call routine)
Arg2: 0000000000000002, Current IRQL
Arg3: 0000000000000000, 0
Arg4: fffff88003dbeca0, 0

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

PEB is paged out (Peb.Ldr = 00000000`7efdf018). Type ".hh dbgerr001" for details
PEB is paged out (Peb.Ldr = 00000000`7efdf018). Type ".hh dbgerr001" for details

PROCESS_NAME: vsmon.exe

BUGCHECK_STR: RAISED_IRQL_FAULT

FAULTING_IP:
+0
00000000`75112dd9 ?? ???

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

CURRENT_IRQL: 2

LAST_CONTROL_TRANSFER: from fffff80002ebd469 to fffff80002ebdf00

STACK_TEXT:
fffff880`03dbea68 fffff800`02ebd469 : 00000000`0000004a 00000000`75112dd9 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`03dbea70 fffff800`02ebd3a0 : fffff880`03dbeca0 fffffa80`07edb1e0 fffff880`03dbebf8 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`03dbebb0 00000000`75112dd9 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x245
00000000`0399eb48 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x75112dd9


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!KiSystemServiceExit+245
fffff800`02ebd3a0 4883ec50 sub rsp,50h

SYMBOL_STACK_INDEX: 2

SYMBOL_NAME: nt!KiSystemServiceExit+245

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc600

FAILURE_BUCKET_ID: X64_RAISED_IRQL_FAULT_vsmon.exe_nt!KiSystemServiceExit+245

BUCKET_ID: X64_RAISED_IRQL_FAULT_vsmon.exe_nt!KiSystemServiceExit+245

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


Now i am aware vsmon.exe is part of my ZoneAlarm Extreme Security, yet how it is involved confounds me, please help guys!

BC AdBot (Login to Remove)

 


#2 Aus Smithy

Aus Smithy

  • Members
  • 160 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Brisbane QLD Australia
  • Local time:03:04 PM

Posted 01 January 2010 - 10:30 PM

If you have not already done so I'd check supplier sites for your Display card and NIC for Windows 7 drivers as drivers can be one reason for instability after Windows 7 installations.

#3 OldGrumpyBastard

OldGrumpyBastard

  • Members
  • 781 posts
  • OFFLINE
  •  
  • Location:"Way South of 'da Bridge"
  • Local time:12:04 AM

Posted 01 January 2010 - 11:19 PM

I might suggest that you disable your fire wall (Zone Alarm) temporarily and see if the problem persists. If it goes away then that is the cause and you may need to contact Zone Alarms for drivers that are compatible with Windows 7 (Vista drivers should be) maybe yours is just corrupt...
Does this look like an OldGrumpyBastard or what?




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users