Another Blue Screen Error


  1. Posts : 4
    Windows 7 Professional x64
       #1

    Another Blue Screen Error


    Hi guys,

    have you any idea what's the problem with my station?
    I got a blue screen error during the rating process and it appeared after I've updated the video card driver.

    Problem signature:
    Problem Event Name: BlueScreen
    OS Version: 6.1.7601.2.1.0.256.48
    Locale ID: 1033


    Additional information about the problem:
    BCCode: d1
    BCP1: 0000000000000004
    BCP2: 0000000000000002
    BCP3: 0000000000000000
    BCP4: FFFFF8800F4519EC
    OS Version: 6_1_7601
    Service Pack: 1_0
    Product: 256_1

    My configuration is:
    Intel(R) Core(TM) i7 920
    Windows 7 Professional SP1 x64
    GeForce GT220

    Thanks
      My Computer


  2. Posts : 28,845
    Win 8 Release candidate 8400
       #2

    Bucium said:
    Hi guys,

    have you any idea what's the problem with my station?
    I got a blue screen error during the rating process and it appeared after I've updated the video card driver.

    Problem signature:
    Problem Event Name: BlueScreen
    OS Version: 6.1.7601.2.1.0.256.48
    Locale ID: 1033


    Additional information about the problem:
    BCCode: d1
    BCP1: 0000000000000004
    BCP2: 0000000000000002
    BCP3: 0000000000000000
    BCP4: FFFFF8800F4519EC
    OS Version: 6_1_7601
    Service Pack: 1_0
    Product: 256_1

    My configuration is:
    Intel(R) Core(TM) i7 920
    Windows 7 Professional SP1 x64
    GeForce GT220

    Thanks




    To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.

    The procedure:

    * Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
    * Zip up the copy.
    * Attach the ZIP archive to your post using the "paperclip" (file attachments) button.



    To ensure minidumps are enabled:

    Go to Start, in the Search Box type: sysdm.cpl, press Enter.
    Under the Advanced tab, click on the Startup and Recovery Settings... button.
    Ensure that Automatically restart is unchecked.
    Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
    Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
    OK your way out.
    Reboot if changes have been made.
      My Computer


  3. Posts : 4
    Windows 7 Professional x64
    Thread Starter
       #3

    zigzag, please find the attached file.

    Thank you
      My Computer


  4. Posts : 28,845
    Win 8 Release candidate 8400
       #4

    Bucium said:
    zigzag, please find the attached file.

    Thank you
    this one was related to your video driver. Please re-install using this method.

    When upgrading your graphic driver you MUST remove all traces of the current driver. In order to do that we recommend using Guru3D - Driver Sweeper


    Or Phyxion.net - Driver Sweeper

    When it is removed then download and install the fresh copy.


    Code:
    Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Users\K\Desktop\061011-12636-01.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;srv*e:\symbols
    *http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
    Machine Name:
    Kernel base = 0xfffff800`02e66000 PsLoadedModuleList = 0xfffff800`030ab650
    Debug session time: Fri Jun 10 06:01:48.952 2011 (GMT-4)
    System Uptime: 0 days 0:04:34.936
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    .......................
    Loading User Symbols
    Loading unloaded module list
    .....
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck D1, {4, 2, 0, fffff8800f4519ec}
    
    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
    Probably caused by : nvlddmkm.sys ( nvlddmkm+3f19ec )
    
    Followup: MachineOwner
    ---------
    
    7: 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: 0000000000000004, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
    Arg4: fffff8800f4519ec, address which referenced memory
    
    Debugging Details:
    ------------------
    
    
    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80003115100
     0000000000000004 
    
    CURRENT_IRQL:  2
    
    FAULTING_IP: 
    nvlddmkm+3f19ec
    fffff880`0f4519ec 8b4304          mov     eax,dword ptr [rbx+4]
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    BUGCHECK_STR:  0xD1
    
    PROCESS_NAME:  System
    
    TRAP_FRAME:  fffff880031ab4c0 -- (.trap 0xfffff880031ab4c0)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=fffffa8003ce2a80 rbx=0000000000000000 rcx=fffffa8005010d10
    rdx=fffffa8003e23b00 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff8800f4519ec rsp=fffff880031ab650 rbp=0000000000000000
     r8=0000000000000000  r9=fffffa8005010d10 r10=fffff8800f451993
    r11=fffffa8003e23b00 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl zr na po nc
    nvlddmkm+0x3f19ec:
    fffff880`0f4519ec 8b4304          mov     eax,dword ptr [rbx+4] ds:8a3a:00000000`00000004=????????
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from fffff80002ee52a9 to fffff80002ee5d00
    
    STACK_TEXT:  
    fffff880`031ab378 fffff800`02ee52a9 : 00000000`0000000a 00000000`00000004 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
    fffff880`031ab380 fffff800`02ee3f20 : fffff880`0f451993 fffff880`0f2652eb 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
    fffff880`031ab4c0 fffff880`0f4519ec : 00000000`00000000 00000000`4df1eb8c 00000000`00000000 00000000`3fbce078 : nt!KiPageFault+0x260
    fffff880`031ab650 00000000`00000000 : 00000000`4df1eb8c 00000000`00000000 00000000`3fbce078 fffffa80`00000030 : nvlddmkm+0x3f19ec
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    nvlddmkm+3f19ec
    fffff880`0f4519ec 8b4304          mov     eax,dword ptr [rbx+4]
    
    SYMBOL_STACK_INDEX:  3
    
    SYMBOL_NAME:  nvlddmkm+3f19ec
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nvlddmkm
    
    IMAGE_NAME:  nvlddmkm.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4dd73a68
    
    FAILURE_BUCKET_ID:  X64_0xD1_nvlddmkm+3f19ec
    
    BUCKET_ID:  X64_0xD1_nvlddmkm+3f19ec
    
    Followup: MachineOwner
    ---------
      My Computer


  5. Posts : 4
    Windows 7 Professional x64
    Thread Starter
       #5

    Thanks, zigzag

    the problem is solved
      My Computer


  6. Posts : 28,845
    Win 8 Release candidate 8400
       #6

    Bucium said:
    Thanks, zigzag

    the problem is solved
    MP let us know if you need further help

    Ken
      My Computer


  7. Posts : 4
    Windows 7 Professional x64
    Thread Starter
       #7

    Ken,

    sorry to bother you again, but my problem persists.

    So, my system got the same blue screen everytime I play two or three consecutive movies on YouTube - with explorer and firefox as well. I mention that I have not tested it in games.

    Bottom line, I couldn't get rid of the problem after I've reinstalled Windows with all updates, including the latest Nvidia driver(275.33) and K-lite Codec Pack 7.1.0 FULL.

    Please find attached the "Minidump" file.

    Regards
      My Computer


  8. Posts : 28,845
    Win 8 Release candidate 8400
       #8

    Bucium said:
    Ken,

    sorry to bother you again, but my problem persists.

    So, my system got the same blue screen everytime I play two or three consecutive movies on YouTube - with explorer and firefox as well. I mention that I have not tested it in games.

    Bottom line, I couldn't get rid of the problem after I've reinstalled Windows with all updates, including the latest Nvidia driver(275.33) and K-lite Codec Pack 7.1.0 FULL.

    Please find attached the "Minidump" file.

    Regards
    Still your video driver and I would remove the Kodec pack.

    Code:
    Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Users\K\Desktop\061211-14710-01.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;srv*e:\symbols
    *http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
    Machine Name:
    Kernel base = 0xfffff800`02c13000 PsLoadedModuleList = 0xfffff800`02e58650
    Debug session time: Sun Jun 12 04:35:49.874 2011 (GMT-4)
    System Uptime: 0 days 0:25:29.858
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    .....................
    Loading User Symbols
    Loading unloaded module list
    ......
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck D1, {4, 2, 0, fffff8800f4a49ec}
    
    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
    Probably caused by : nvlddmkm.sys ( nvlddmkm+3f19ec )
    
    Followup: MachineOwner
    ---------
    
    7: 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: 0000000000000004, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
    Arg4: fffff8800f4a49ec, address which referenced memory
    
    Debugging Details:
    ------------------
    
    
    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ec2100
     0000000000000004 
    
    CURRENT_IRQL:  2
    
    FAULTING_IP: 
    nvlddmkm+3f19ec
    fffff880`0f4a49ec 8b4304          mov     eax,dword ptr [rbx+4]
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    BUGCHECK_STR:  0xD1
    
    PROCESS_NAME:  Mobile Partner
    
    TRAP_FRAME:  fffff880031b26f0 -- (.trap 0xfffff880031b26f0)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=fffffa8003d45660 rbx=0000000000000000 rcx=fffffa8004f58a90
    rdx=fffffa8005381160 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff8800f4a49ec rsp=fffff880031b2880 rbp=0000000000000000
     r8=0000000000000000  r9=fffffa8004f58a90 r10=fffff8800f4a4993
    r11=fffffa8005381160 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl zr na po nc
    nvlddmkm+0x3f19ec:
    fffff880`0f4a49ec 8b4304          mov     eax,dword ptr [rbx+4] ds:58ca:00000000`00000004=????????
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from fffff80002c922a9 to fffff80002c92d00
    
    STACK_TEXT:  
    fffff880`031b25a8 fffff800`02c922a9 : 00000000`0000000a 00000000`00000004 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
    fffff880`031b25b0 fffff800`02c90f20 : fffff880`0f4a4993 fffff880`0f2b82eb fffffa80`03cf9000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
    fffff880`031b26f0 fffff880`0f4a49ec : 00000000`00000000 00000000`4df47a65 00000000`00000000 00000000`3fbce078 : nt!KiPageFault+0x260
    fffff880`031b2880 00000000`00000000 : 00000000`4df47a65 00000000`00000000 00000000`3fbce078 fffffa80`00000030 : nvlddmkm+0x3f19ec
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    nvlddmkm+3f19ec
    fffff880`0f4a49ec 8b4304          mov     eax,dword ptr [rbx+4]
    
    SYMBOL_STACK_INDEX:  3
    
    SYMBOL_NAME:  nvlddmkm+3f19ec
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nvlddmkm
    
    IMAGE_NAME:  nvlddmkm.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4dd73a68
    
    FAILURE_BUCKET_ID:  X64_0xD1_nvlddmkm+3f19ec
    
    BUCKET_ID:  X64_0xD1_nvlddmkm+3f19ec
    
    Followup: MachineOwner
    ---------
      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 14:45.
Find Us