bluescreen "6.1.7600.2.0.0.256.1" Prevents Booting

Page 2 of 2 FirstFirst 12

  1. Posts : 13,354
    Windows 7 Professional x64
       #11

    I still suspect your graphics card.
    Code:
    Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Users\Jonathan\AppData\Local\Temp\Temp1_052110-19203-01.zip\052110-19203-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
    Executable search path is: 
    Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7600.16539.x86fre.win7_gdr.100226-1909
    Machine Name:
    Kernel base = 0x82c3c000 PsLoadedModuleList = 0x82d84810
    Debug session time: Fri May 21 06:48:11.591 2010 (GMT-4)
    System Uptime: 0 days 0:00:12.932
    Loading Kernel Symbols
    ...............................................................
    ..
    Loading User Symbols
    Loading unloaded module list
    ....
    1: kd> !analyze -v ;lmtsmn
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    THREAD_STUCK_IN_DEVICE_DRIVER_M (100000ea)
    The device driver is spinning in an infinite loop, most likely waiting for
    hardware to become idle. This usually indicates problem with the hardware
    itself or with the device driver programming the hardware incorrectly.
    If the kernel debugger is connected and running when watchdog detects a
    timeout condition then DbgBreakPoint() will be called instead of KeBugCheckEx()
    and detailed message including bugcheck arguments will be printed to the
    debugger. This way we can identify an offending thread, set breakpoints in it,
    and hit go to return to the spinning code to debug it further. Because
    KeBugCheckEx() is not called the .bugcheck directive will not return bugcheck
    information in this case. The arguments are already printed out to the kernel
    debugger. You can also retrieve them from a global variable via
    "dd watchdog!g_WdBugCheckData l5" (use dq on NT64).
    On MP machines it is possible to hit a timeout when the spinning thread is
    interrupted by hardware interrupt and ISR or DPC routine is running at the time
    of the bugcheck (this is because the timeout's work item can be delivered and
    handled on the second CPU and the same time). If this is the case you will have
    to look deeper at the offending thread's stack (e.g. using dds) to determine
    spinning code which caused the timeout to occur.
    Arguments:
    Arg1: 87128d48, Pointer to a stuck thread object.  Do .thread then kb on it to find
        the hung location.
    Arg2: 00000000, Pointer to a DEFERRED_WATCHDOG object.
    Arg3: 00000000, Pointer to offending driver name.
    Arg4: 00000000, Number of times "intercepted" bugcheck 0xEA was hit (see notes).
    
    Debugging Details:
    ------------------
    
    
    FAULTING_THREAD:  87128d48
    
    DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_FAULT
    
    CUSTOMER_CRASH_COUNT:  1
    
    BUGCHECK_STR:  0xEA
    
    PROCESS_NAME:  csrss.exe
    
    CURRENT_IRQL:  0
    
    LAST_CONTROL_TRANSFER:  from 918d1bbc to 82d18d10
    
    STACK_TEXT:  
    807ad7d4 918d1bbc 000000ea 87128d48 00000000 nt!KeBugCheckEx+0x1e
    WARNING: Frame IP not in any known module. Following frames may be wrong.
    807ad818 918ca34d 807ad864 00000000 918c4673 0x918d1bbc
    807ad840 914565ce 807ad864 00000000 00000000 0x918ca34d
    807ad890 91450a54 9156297a 807ad928 000001f4 0x914565ce
    807ad8ac 9156c12e 866ed000 807ad8c4 853b3a98 0x91450a54
    807ad904 9156fb2b 853b3498 9156297a 807ad928 0x9156c12e
    807ad944 9157047d e0000000 853b3498 853b3b28 0x9156fb2b
    807ad960 91563a07 00000003 00000000 853b3498 0x9157047d
    807ad974 91564368 853b3498 95f58040 853b35d0 0x91563a07
    807ad98c 9155f10a 853b3498 87285010 87285000 0x91564368
    807ad9a0 91436038 853b3498 8d07c000 807ada20 0x9155f10a
    807adb3c 82e5d960 807adb68 82e5d9c2 00000000 0x91436038
    807adb44 82e5d9c2 00000000 00000020 918d71c8 nt!ObpFreeObject+0x213
    807adbe0 82ca35e4 87128d48 0000031c 00000000 nt!ObpFreeObject+0x275
    00000000 00000000 00000000 00000000 00000000 nt!KiExitThreadWait+0x89
    
    
    STACK_COMMAND:  .thread 0xffffffff87128d48 ; kb
    
    FOLLOWUP_IP: 
    nt!ObpFreeObject+213
    82e5d960 83661000        and     dword ptr [esi+10h],0
    
    SYMBOL_STACK_INDEX:  c
    
    SYMBOL_NAME:  nt!ObpFreeObject+213
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nt
    
    IMAGE_NAME:  ntkrpamp.exe
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4b88cacf
    
    FAILURE_BUCKET_ID:  0xEA_nt!ObpFreeObject+213
    
    BUCKET_ID:  0xEA_nt!ObpFreeObject+213
    
    Followup: MachineOwner
    ---------
    
    start    end        module name
    8339b000 833e3000   ACPI     ACPI.sys     Mon Jul 13 19:11:11 2009 (4A5BBF0F)
    90063000 900bd000   afd      afd.sys      Mon Jul 13 19:12:34 2009 (4A5BBF62)
    8af98000 8afa1000   amdxata  amdxata.sys  Tue May 19 13:57:35 2009 (4A12F30F)
    90059000 90062c00   aswTdi   aswTdi.SYS   Wed Apr 14 12:35:46 2010 (4BC5EEE2)
    8af00000 8af09000   atapi    atapi.sys    Mon Jul 13 19:11:15 2009 (4A5BBF13)
    8af09000 8af2c000   ataport  ataport.SYS  Mon Jul 13 19:11:18 2009 (4A5BBF16)
    8aedf000 8aeea000   BATTC    BATTC.SYS    Mon Jul 13 19:19:15 2009 (4A5BC0F3)
    8b3f7000 8b3fe000   Beep     Beep.SYS     Mon Jul 13 19:45:00 2009 (4A5BC6FC)
    83227000 8322f000   BOOTVID  BOOTVID.dll  Mon Jul 13 21:04:34 2009 (4A5BD9A2)
    8b011000 8b030000   cdrom    cdrom.sys    Mon Jul 13 19:11:24 2009 (4A5BBF1C)
    83271000 8331c000   CI       CI.dll       Mon Jul 13 21:09:28 2009 (4A5BDAC8)
    8b3d2000 8b3f7000   CLASSPNP CLASSPNP.SYS Mon Jul 13 19:11:20 2009 (4A5BBF18)
    8322f000 83271000   CLFS     CLFS.SYS     Mon Jul 13 19:11:10 2009 (4A5BBF0E)
    8b217000 8b274000   cng      cng.sys      Mon Jul 13 19:32:55 2009 (4A5BC427)
    8aed7000 8aedf000   compbatt compbatt.sys Mon Jul 13 19:19:18 2009 (4A5BC0F6)
    8b400000 8b411000   disk     disk.sys     Mon Jul 13 19:11:28 2009 (4A5BBF20)
    8afd5000 8afe6000   fileinfo fileinfo.sys Mon Jul 13 19:21:51 2009 (4A5BC18F)
    8afa1000 8afd5000   fltmgr   fltmgr.sys   Mon Jul 13 19:11:13 2009 (4A5BBF11)
    8b282000 8b28b000   Fs_Rec   Fs_Rec.sys   Mon Jul 13 19:11:14 2009 (4A5BBF12)
    8b1a4000 8b1d6000   fvevol   fvevol.sys   Fri Sep 25 22:24:21 2009 (4ABD7B55)
    8b55d000 8b58e000   fwpkclnt fwpkclnt.sys Mon Jul 13 19:12:03 2009 (4A5BBF43)
    82c05000 82c3c000   hal      halmacpi.dll Mon Jul 13 19:11:03 2009 (4A5BBF07)
    8b5ee000 8b5f6000   hwpolicy hwpolicy.sys Mon Jul 13 19:11:01 2009 (4A5BBF05)
    80b97000 80b9f000   kdcom    kdcom.dll    Mon Jul 13 21:08:58 2009 (4A5BDAAA)
    8b191000 8b1a4000   ksecdd   ksecdd.sys   Mon Jul 13 19:11:56 2009 (4A5BBF3C)
    8b380000 8b3a5000   ksecpkg  ksecpkg.sys  Thu Dec 10 23:04:22 2009 (4B21C4C6)
    8320b000 83216000   mcupdate_AuthenticAMD mcupdate_AuthenticAMD.dll Mon Jul 13 19:13:13 2009 (4A5BBF89)
    8aeea000 8af00000   mountmgr mountmgr.sys Mon Jul 13 19:11:27 2009 (4A5BBF1F)
    9001e000 90029000   Msfs     Msfs.SYS     Mon Jul 13 19:11:26 2009 (4A5BBF1E)
    833ec000 833f4000   msisadrv msisadrv.sys Mon Jul 13 19:11:09 2009 (4A5BBF0D)
    8b166000 8b191000   msrpc    msrpc.sys    Mon Jul 13 19:11:59 2009 (4A5BBF3F)
    8b5de000 8b5ee000   mup      mup.sys      Mon Jul 13 19:14:14 2009 (4A5BBFC6)
    8b28b000 8b342000   ndis     ndis.sys     Mon Jul 13 19:12:24 2009 (4A5BBF58)
    8b342000 8b380000   NETIO    NETIO.SYS    Mon Jul 13 19:12:35 2009 (4A5BBF63)
    90029000 90037000   Npfs     Npfs.SYS     Mon Jul 13 19:11:31 2009 (4A5BBF23)
    82c3c000 8304c000   nt       ntkrpamp.exe Sat Feb 27 02:33:35 2010 (4B88CACF)
    8b037000 8b166000   Ntfs     Ntfs.sys     Mon Jul 13 19:12:05 2009 (4A5BBF45)
    8b20d000 8b214000   Null     Null.SYS     Mon Jul 13 19:11:12 2009 (4A5BBF10)
    8af2c000 8af51000   nvstor   nvstor.sys   Wed May 20 02:44:09 2009 (4A13A6B9)
    8ae56000 8ae67000   partmgr  partmgr.sys  Mon Jul 13 19:11:35 2009 (4A5BBF27)
    8ae21000 8ae4b000   pci      pci.sys      Mon Jul 13 19:11:16 2009 (4A5BBF14)
    8ae67000 8ae6e000   pciide   pciide.sys   Mon Jul 13 19:11:19 2009 (4A5BBF17)
    8ae6e000 8ae7c000   PCIIDEX  PCIIDEX.SYS  Mon Jul 13 19:11:15 2009 (4A5BBF13)
    8b274000 8b282000   pcw      pcw.sys      Mon Jul 13 19:11:10 2009 (4A5BBF0E)
    83216000 83227000   PSHED    PSHED.dll    Mon Jul 13 21:09:36 2009 (4A5BDAD0)
    833f4000 833fc000   RDPCDD   RDPCDD.sys   Mon Jul 13 20:01:40 2009 (4A5BCAE4)
    83200000 83208000   rdpencdd rdpencdd.sys Mon Jul 13 20:01:39 2009 (4A5BCAE3)
    90016000 9001e000   rdprefmp rdprefmp.sys Mon Jul 13 20:01:41 2009 (4A5BCAE5)
    8b3a5000 8b3d2000   rdyboost rdyboost.sys Mon Jul 13 19:22:02 2009 (4A5BC19A)
    8b5d6000 8b5de000   spldr    spldr.sys    Mon May 11 12:13:47 2009 (4A084EBB)
    8af51000 8af98000   storport storport.sys Mon Jul 13 19:45:58 2009 (4A5BC736)
    8b414000 8b55d000   tcpip    tcpip.sys    Mon Jul 13 19:13:18 2009 (4A5BBF8E)
    9004e000 90059000   TDI      TDI.SYS      Mon Jul 13 19:12:12 2009 (4A5BBF4C)
    90037000 9004e000   tdx      tdx.sys      Mon Jul 13 19:12:10 2009 (4A5BBF4A)
    00000001 963452b5   Unknown_Module_00000001 Unknown_Module_00000001 unavailable (00000000)
    8ae4b000 8ae56000   vdrvroot vdrvroot.sys Mon Jul 13 19:46:19 2009 (4A5BC74B)
    8afe6000 8aff2000   vga      vga.sys      Mon Jul 13 19:25:50 2009 (4A5BC27E)
    8ae00000 8ae21000   VIDEOPRT VIDEOPRT.SYS Mon Jul 13 19:25:49 2009 (4A5BC27D)
    8b58e000 8b596380   vmstorfl vmstorfl.sys Mon Jul 13 19:28:44 2009 (4A5BC32C)
    8ae7c000 8ae8c000   volmgr   volmgr.sys   Mon Jul 13 19:11:25 2009 (4A5BBF1D)
    8ae8c000 8aed7000   volmgrx  volmgrx.sys  Mon Jul 13 19:11:41 2009 (4A5BBF2D)
    8b597000 8b5d6000   volsnap  volsnap.sys  Mon Jul 13 19:11:34 2009 (4A5BBF26)
    8aff2000 8afff000   watchdog watchdog.sys Mon Jul 13 19:24:10 2009 (4A5BC21A)
    8331c000 8338d000   Wdf01000 Wdf01000.sys Mon Jul 13 19:11:36 2009 (4A5BBF28)
    8338d000 8339b000   WDFLDR   WDFLDR.SYS   Mon Jul 13 19:11:25 2009 (4A5BBF1D)
    833e3000 833ec000   WMILIB   WMILIB.SYS   Mon Jul 13 19:11:22 2009 (4A5BBF1A)
    
    Unloaded modules:
    8b200000 8b20d000   crashdmp.sys
        Timestamp: unavailable (00000000)
        Checksum:  00000000
    8b5f6000 8b600000   dump_storpor
        Timestamp: unavailable (00000000)
        Checksum:  00000000
    8b1d6000 8b1fb000   dump_nvstor.
        Timestamp: unavailable (00000000)
        Checksum:  00000000
    8b000000 8b011000   dump_dumpfve
        Timestamp: unavailable (00000000)
        Checksum:  00000000
    Download a copy of Ubuntu and burn the ISO to a CD using ISO Recorder or the built-in Windows Image Burning utility: Download Ubuntu | Ubuntu

    Boot from the CD, and select "Try Ubuntu without any changes to my computer". Play around for a little while. See if you can get it to crash. If it does crash, I'm going to guess the card itself is fried. If it doesn't crash, let's hope it's a driver issue, and continue playing around with different drivers.
      My Computer


  2. Posts : 55
    Windows 7
    Thread Starter
       #12

    booted from Ubuntu CD - but v. confused - no "Try -- without changes"... I started but then aborted installation before it got to partitioning drive - lots of alternatives there but no "...without changes" - wh. one should I try?

    [Ubuntu 10.04 - i386.iso]
      My Computer


  3. Posts : 55
    Windows 7
    Thread Starter
       #13

    Lots of trouble restarting again - several goes/mins - looks like you may be right re graphics card. Any way to know? If I should get new one, any idea which is compatible?

    [I saw these on ebuyer/other in sub-£30 -
    PNY Technologies PNY 8400GS 256MB DDR2 VGA DVI out PCI-E Graphics Card
    HIS Radeon HD 4350 512MB GDDR2 PCI-E 2.0x16 Graphics Card ]
      My Computer


  4. Posts : 13,354
    Windows 7 Professional x64
       #14

    The second card should be compatible with your system.
      My Computer


  5. Posts : 55
    Windows 7
    Thread Starter
       #15

    Thx - if that'll work, that seems easiest. Just double-checking - there is still an Nvidia Nforce PCI System Management driver listed for update by Driver Checker - wh. I d/l and didn't install - it lists 3 drivers - Away Mode & Ethernet & Storage Drivers. Is it worth trying that?

    Or will a new card automatically clear up all these probs?
      My Computer


  6. Posts : 13,354
    Windows 7 Professional x64
       #16

    Hopefully the new card will clear up the problems. We can't really tell anything for sure.

    Sure, go ahead and update the drivers. It won't hurt anything. I also don't think it will help your problem, but you never know.
      My Computer


  7. Posts : 55
    Windows 7
    Thread Starter
       #17

    Just to say - put in the recommended card - & everything seems fine on 2nd day - so many thanks for all your patience and help
      My Computer


  8. Posts : 13,354
    Windows 7 Professional x64
       #18

    You're very welcome. I just hope it stays that way.

    Be sure to let is know if you need anything else.
      My Computer


 
Page 2 of 2 FirstFirst 12

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