BSOD Windows 7 new install, reboot for unknown reason


  1. Posts : 1
    Windows 7 SP1 x86
       #1

    BSOD Windows 7 new install, reboot for unknown reason


    Hello guys,

    I would appreciate if you could help me, my problem is the following,


    The computer has windows xp sp3 installed, I has tons of bloatware and then I decided to reinstalled and upgraded with windows 7sp1, the thing is that it continues to reboot every time I saw a video or tray to open a high def video, I'm not sure if this is related to the video card, but I installed the proper driver via windows update.

    I attached the two windows minidump (dmp) file that it generates and my computer info on a .nfo file,
    would be really helpful if someone can help me through the resolution of this problema

    FROM THE WINDOWS EVENT VIEWER:

    CRITICAL
    The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.


    ERROR
    The computer has rebooted from a bugcheck. The bugcheck was: 0x000000d1 (0x00000736, 0x0000000a, 0x00000000, 0x8ed5b944). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 101814-22869-01.
      My Computer


  2. Posts : 15,026
    Windows 10 Home 64Bit
       #2

    Welcome to the forum.

    Vtgkmodedx32.sys with description S3GIGP is a driver file from company S3 Graphics Co., Ltd. belonging to product S3 Graphics UMA-series Miniport.

    Please uninstall this software and observe if the BSOD problem persists.

    Use Revo Uninstaller to uninstall stubborn software. Opt for Advance Mode while uninstalling which allows you to remove leftover registry:-



    Sometimes drivers remain, not completely uninstalled. Follow this tutorial for complete removal of drivers of the particular program: How to Clean Left Over Driver Files with Driver Sweeper
    Code:
    Microsoft (R) Windows Debugger Version 6.2.9200.20512 X86
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Downloads\dudo28_dmp_files\101814-24164-01.user_dudu28.dmp]
    Mini Kernel Dump File: Only registers and stack trace are 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 (2 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7601.18247.x86fre.win7sp1_gdr.130828-1532
    Machine Name:
    Kernel base = 0x82846000 PsLoadedModuleList = 0x8298f4d0
    Debug session time: Sun Oct 19 00:27:41.797 2014 (UTC + 6:00)
    System Uptime: 0 days 0:35:40.904
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ....................
    Loading User Symbols
    Loading unloaded module list
    .......
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck D1, {18e3319c, a, 0, 8d512603}
    
    Unable to load image \SystemRoot\system32\DRIVERS\VTGKModeDX32.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for VTGKModeDX32.sys
    *** ERROR: Module load completed but symbols could not be loaded for VTGKModeDX32.sys
    Probably caused by : VTGKModeDX32.sys ( VTGKModeDX32+3a603 )
    
    Followup: MachineOwner
    ---------
    
    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
    An attempt was made to access a pageable (or completely invalid) address at an
    interrupt request level (IRQL) that is too high.  This is usually
    caused by drivers using improper addresses.
    If kernel debugger is available get stack backtrace.
    Arguments:
    Arg1: 18e3319c, memory referenced
    Arg2: 0000000a, IRQL
    Arg3: 00000000, value 0 = read operation, 1 = write operation
    Arg4: 8d512603, address which referenced memory
    
    Debugging Details:
    ------------------
    
    
    READ_ADDRESS: GetPointerFromAddress: unable to read from 829af84c
    Unable to read MiSystemVaType memory at 8298ee20
     18e3319c 
    
    CURRENT_IRQL:  a
    
    FAULTING_IP: 
    VTGKModeDX32+3a603
    8d512603 8bec            mov     ebp,esp
    
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    
    BUGCHECK_STR:  0xD1
    
    PROCESS_NAME:  WinSAT.exe
    
    TRAP_FRAME:  9e9e4c04 -- (.trap 0xffffffff9e9e4c04)
    ErrCode = 00000000
    eax=85755000 ebx=030df1b0 ecx=00000001 edx=00000001 esi=855a29d8 edi=85bb4780
    eip=8d512603 esp=9e9e4c78 ebp=9e9e4ca4 iopl=0         nv up ei pl nz na po nc
    cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010202
    VTGKModeDX32+0x3a603:
    8d512603 8bec            mov     ebp,esp
    Resetting default scope
    
    EXCEPTION_RECORD:  85bb4780 -- (.exr 0xffffffff85bb4780)
    Cannot read Exception record @ 85bb4780
    
    LAST_CONTROL_TRANSFER:  from 8d512603 to 82886b7f
    
    STACK_TEXT:  
    9e9e4c04 8d512603 badb0d00 00000001 85755ca0 nt!KiTrap0E+0x1b3
    WARNING: Stack unwind information not available. Following frames may be wrong.
    9e9e4c78 8d527f4f 85755000 00000000 00000000 VTGKModeDX32+0x3a603
    9e9e4ca4 8d52845b 85755000 00000000 00420000 VTGKModeDX32+0x4ff4f
    9e9e4ce4 8de3eb14 85755000 00000000 9e9e4d08 VTGKModeDX32+0x5045b
    9e9e4cf4 8de4ed59 85bb4780 85757920 00000000 dxgkrnl!DpiFdoMessageInterruptRoutine+0x17
    9e9e4d08 8287fe1d 85bb4780 85757920 00000000 dxgkrnl!DpiFdoLineInterruptRoutine+0x12
    9e9e4d08 6cae4172 85bb4780 85757920 00000000 nt!KiInterruptDispatch+0x6d
    030df1b0 00000000 00000000 00000000 00000000 0x6cae4172
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    VTGKModeDX32+3a603
    8d512603 8bec            mov     ebp,esp
    
    SYMBOL_STACK_INDEX:  1
    
    SYMBOL_NAME:  VTGKModeDX32+3a603
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: VTGKModeDX32
    
    IMAGE_NAME:  VTGKModeDX32.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  48f7f1f4
    
    FAILURE_BUCKET_ID:  0xD1_VTGKModeDX32+3a603
    
    BUCKET_ID:  0xD1_VTGKModeDX32+3a603
    
    Followup: MachineOwner
    ---------
    
    0: kd> lmvm VTGKModeDX32
    start    end        module name
    8d4d8000 8d5a9000   VTGKModeDX32 T (no symbols)           
        Loaded symbol image file: VTGKModeDX32.sys
        Image path: \SystemRoot\system32\DRIVERS\VTGKModeDX32.sys
        Image name: VTGKModeDX32.sys
        Timestamp:        Fri Oct 17 08:01:24 2008 (48F7F1F4)
        CheckSum:         000C93CB
        ImageSize:        000D1000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 08:12.
Find Us