Blue Screen of Death

Page 1 of 2 12 LastLast

  1. Posts : 27
    7
       #1

    Blue Screen of Death


    Hi everybody,

    Please take a look at my BSOD's!

    Windows 7 32 bit did not came preinstalled on my system. It was original Windows Vista and I used an upgrade disk to Windows 7. Age about 1-2 years. Age of the OS I guess 6-12 months.

    Tnx guys I really appreciate your help!
      My Computer


  2. Posts : 4,772
    Windows 7 Ultimate - 64-bit | Windows 8 Pro - 64-bit
       #2

    Hello and Welcome !

    First of all i would recommend to Run a Hardware Diagnostic (Memory and Hard Drive) follow this link for instructions Hardware Diagnostic !! « Captain Debugger

    Go to C:\Windows\Drivers and rename giveio.sys to giveio.old and reboot the System.

    Report us back the results.

    Bugcheck:

    Code:
    PAGE_FAULT_IN_NONPAGED_AREA (50)
    Invalid system memory was referenced.  This cannot be protected by try-except,
    it must be protected by a Probe.  Typically the address is just plain bad or it
    is pointing at freed memory.
    Arguments:
    Arg1: ffff0050, memory referenced.
    Arg2: 00000000, value 0 = read operation, 1 = write operation.
    Arg3: 8b83c4d3, If non-zero, the instruction address which referenced the bad memory
        address.
    Arg4: 00000000, (reserved)
    
    Debugging Details:
    ------------------
    
    
    Could not read faulting driver name
    
    READ_ADDRESS: GetPointerFromAddress: unable to read from 82f6d718
    Unable to read MiSystemVaType memory at 82f4d160
     ffff0050 
    
    FAULTING_IP: 
    Ntfs!NtfsSnapshotScbInternal+194
    8b83c4d3 394f50          cmp     dword ptr [edi+50h],ecx
    
    MM_INTERNAL_CODE:  0
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    BUGCHECK_STR:  0x50
    
    PROCESS_NAME:  svchost.exe
    
    CURRENT_IRQL:  0
    
    TRAP_FRAME:  b17278a0 -- (.trap 0xffffffffb17278a0)
    ErrCode = 00000000
    eax=8586d6a0 ebx=00000727 ecx=8586d6a0 edx=b6172c88 esi=b6172d78 edi=ffff0000
    eip=8b83c4d3 esp=b1727914 ebp=b1727920 iopl=0         nv up ei ng nz na pe nc
    cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010286
    Ntfs!NtfsSnapshotScbInternal+0x194:
    8b83c4d3 394f50          cmp     dword ptr [edi+50h],ecx ds:0023:ffff0050=????????
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from 82e4b638 to 82e8a903
    
    STACK_TEXT:  
    b1727888 82e4b638 00000000 ffff0050 00000000 nt!MmAccessFault+0x106
    b1727888 8b83c4d3 00000000 ffff0050 00000000 nt!KiTrap0E+0xdc
    b1727920 8b83c7a2 8586d6a0 b6172d78 00000000 Ntfs!NtfsSnapshotScbInternal+0x194
    b1727934 8b8bba18 8586d6a0 b6172d78 3af492b7 Ntfs!NtfsSnapshotScb+0x12
    b172799c 8b8d73de 8586d6a0 b6172c88 00000080 Ntfs!NtfsCreateScb+0x110
    b17279d4 8b8c9eeb 8586d6a0 85e6be00 85e6bfb4 Ntfs!NtfsBreakBatchOplock+0x7e
    b1727a0c 8b8c1217 8586d6a0 85e6be00 b6172f20 Ntfs!NtfsOpenExistingAttr+0xa9
    b1727af4 8b8c1677 8586d6a0 85e6be00 b6172f20 Ntfs!NtfsOpenAttributeInExistingFile+0x7a4
    b1727ba0 8b8c0a2d 8586d6a0 85e6be00 b6172f20 Ntfs!NtfsOpenExistingPrefixFcb+0x26e
    b1727c00 8b8c2c5c 8586d6a0 85e6be00 8c7ced08 Ntfs!NtfsFindStartingNode+0xb88
    b1727cdc 8b849210 8586d6a0 85e6be00 9ed99344 Ntfs!NtfsCommonCreate+0x65f
    b1727d1c 82e7511e 9ed992dc 00000000 ffffffff Ntfs!NtfsCommonCreateCallout+0x20
    b1727d1c 82e75215 9ed992dc 00000000 ffffffff nt!KiSwapKernelStackAndExit+0x15a
    9ed99240 00000000 00000000 00000000 00000000 nt!KiSwitchKernelStackAndCallout+0x31
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    Ntfs!NtfsSnapshotScbInternal+194
    8b83c4d3 394f50          cmp     dword ptr [edi+50h],ecx
    
    SYMBOL_STACK_INDEX:  2
    
    SYMBOL_NAME:  Ntfs!NtfsSnapshotScbInternal+194
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: Ntfs
    
    IMAGE_NAME:  Ntfs.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bbf45
    
    FAILURE_BUCKET_ID:  0x50_Ntfs!NtfsSnapshotScbInternal+194
    
    BUCKET_ID:  0x50_Ntfs!NtfsSnapshotScbInternal+194
    
    Followup: MachineOwner
    ---------
    
    3: kd> lmvm Ntfs
    start    end        module name
    8b830000 8b95f000   Ntfs       (pdb symbols)          c:\symcache\ntfs.pdb\513BBB60430D411DBE02DF92418A2B272\ntfs.pdb
        Loaded symbol image file: Ntfs.sys
        Mapped memory image file: C:\SymCache\Ntfs.sys\4A5BBF4512f000\Ntfs.sys
        Image path: \SystemRoot\System32\Drivers\Ntfs.sys
        Image name: Ntfs.sys
        Timestamp:        Tue Jul 14 04:42:05 2009 (4A5BBF45)
        CheckSum:         00127FFB
        ImageSize:        0012F000
        File version:     6.1.7600.16385
        Product version:  6.1.7600.16385
        File flags:       0 (Mask 3F)
        File OS:          40004 NT Win32
        File type:        3.7 Driver
        File date:        00000000.00000000
        Translations:     0409.04b0
        CompanyName:      Microsoft Corporation
        ProductName:      Microsoft® Windows® Operating System
        InternalName:     ntfs.sys
        OriginalFilename: ntfs.sys
        ProductVersion:   6.1.7600.16385
        FileVersion:      6.1.7600.16385 (win7_rtm.090713-1255)
        FileDescription:  NT File System Driver
        LegalCopyright:   © Microsoft Corporation. All rights reserved.
    Hope this helps,
    Captain
      My Computer


  3. Posts : 27
    7
    Thread Starter
       #3

    Changed the file u asked.
    Did a harddisk check. What should I look for in event viewer? I see alot of errors and a few critical errors (Kernel power 41)

    Memtest was ok.
    Still BSOD.
      My Computer


  4. Posts : 27
    7
    Thread Starter
       #4

    BSOD are back again...

    Also lagging before BSOD appears.

    What can I try?
      My Computer


  5. Posts : 4,772
    Windows 7 Ultimate - 64-bit | Windows 8 Pro - 64-bit
       #5

    Please post the new files
      My Computer


  6. Posts : 27
    7
    Thread Starter
       #6

    here it is
      My Computer


  7. Posts : 27
    7
    Thread Starter
       #7

    you have a clue?
      My Computer


  8. Posts : 4,772
    Windows 7 Ultimate - 64-bit | Windows 8 Pro - 64-bit
       #8

    Hello,

    Apologize for the delayed response !

    Most of the Bugchecks PAGE_FAULT_IN_NONPAGED_AREA (50) but different reason. Let enable the Driver Verifier follow this article Using Driver Verifier to identify issues with Drivers

    Follow this post and run the Video Test https://www.sevenforums.com/748030-post2.html

    Bugcheck:

    Code:
    VIDEO_TDR_FAILURE (116)
    Attempt to reset the display driver and recover from timeout failed.
    Arguments:
    Arg1: 8865f428, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
    Arg2: 91ce2326, The pointer into responsible device driver module (e.g. owner tag).
    Arg3: 00000000, Optional error code (NTSTATUS) of the last failed operation.
    Arg4: 00000002, Optional internal context dependent data.
    
    Debugging Details:
    ------------------
    
    Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for nvlddmkm.sys
    *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
    
    FAULTING_IP: 
    nvlddmkm+de326
    91ce2326 55              push    ebp
    
    DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT
    
    CUSTOMER_CRASH_COUNT:  1
    
    BUGCHECK_STR:  0x116
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  0
    
    STACK_TEXT:  
    8d89eb74 9273aadb 00000116 8865f428 91ce2326 nt!KeBugCheckEx+0x1e
    WARNING: Stack unwind information not available. Following frames may be wrong.
    8d89eb98 9273b8fa 91ce2326 00000000 00000002 dxgkrnl+0x8cadb
    8d89ebbc 9276b92c 00000000 00000102 8843f260 dxgkrnl+0x8d8fa
    8d89ec34 92795a32 fffffcfb 0000080a 00000000 dxgmms1!VidSchiReportHwHang+0x3c0
    8d89ec5c 92796153 00000000 00000000 00000000 dxgmms1!VidSchiCheckHwProgress+0x68
    8d89ec98 927728f0 8d89ec90 82e8b3f1 8843f260 dxgmms1!VidSchiWaitForSchedulerEvents+0x1b1
    8d89ed28 927974b7 8843f260 82e8b3f1 8843f260 dxgmms1!VidSchiScheduleCommandToRun+0xaa
    8d89ed3c 92797573 8843f260 00000000 867b7610 dxgmms1!VidSchiRun_PriorityTable+0xf
    8d89ed50 8305d6d3 8843f260 a6ed3784 00000000 dxgmms1!VidSchiWorkerThread+0x7f
    8d89ed90 82f0f0f9 927974f4 8843f260 00000000 nt!PspSystemThreadStartup+0x9e
    00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19
    
    
    STACK_COMMAND:  .bugcheck ; kb
    
    FOLLOWUP_IP: 
    nvlddmkm+de326
    91ce2326 55              push    ebp
    
    SYMBOL_NAME:  nvlddmkm+de326
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nvlddmkm
    
    IMAGE_NAME:  nvlddmkm.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4c379162
    
    FAILURE_BUCKET_ID:  0x116_IMAGE_nvlddmkm.sys
    
    BUCKET_ID:  0x116_IMAGE_nvlddmkm.sys
    
    Followup: MachineOwner
    Report us back the results.
    Captain
      My Computer


  9. Posts : 27
    7
    Thread Starter
       #9

    Video test was ok. Harddrive scan also. Did the driver verifier thing a few months ago and posted results.
    Strangly, I did not have a BSOD for a week so I was happy.

    BUT Today my problems got extremely worse al of sudden! Now I have BSOD every 2 minutes.
    What I did is i used TuneUp Utilities did a scan, register cleaning etc and now its all BSOD!

    Also a few weeks ago my keyboard stopped working. Now I use a different one, don't know if this means something but I thought it was strange keyboard is 1 year old.
      My Computer


  10. Posts : 27
    7
    Thread Starter
       #10

    here are the files
      My Computer


 
Page 1 of 2 12 LastLast

  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 20:03.
Find Us