BSOD problems


  1. Posts : 6
    Windows 7
       #1

    BSOD problems


    I built a brand new computer with 2.93 GHz processor, and 4 GB ram. Upon installing windows 7 not 10 minutes in and a blue screen pops up with the following message:

    Problem signature:
    Problem Event Name: BlueScreen
    OS Version: 6.1.7600.2.0.0.256.48
    Locale ID: 4105

    Additional information about the problem:
    BCCode: 34
    BCP1: 0000000000001838
    BCP2: FFFFFFFFC0000420
    BCP3: 0000000000000000
    BCP4: 0000000000000000
    OS Version: 6_1_7600
    Service Pack: 0_0
    Product: 256_1

    Files that help describe the problem:
    C:\Windows\Minidump\022010-16593-01.dmp
    C:\Users\Matthew Kent\AppData\Local\Temp\WER-27328-0.sysdata.xml

    Read our privacy statement online:
    Windows 7 Privacy Statement - Microsoft Windows

    If the online privacy statement is not available, please read our privacy statement offline:
    C:\Windows\system32\en-US\erofflps.txt

    This blue screen has happened more than a dozen times on the same day of installation.

    Please help I'm a freelance artist and can't have my computer crashing in the middle of a large photoshop project. I have installed a printer, a wacom Bamboo Fun tablet and mozilla firefox and that's it.

    I have included the most recent DMP in a zip file (see Attachment)
      My Computer


  2. Posts : 324
    Windows 7 and MAC
       #2

    Have you tried to start the installation of Windows 7 in safe mode
      My Computer


  3. Posts : 13,354
    Windows 7 Professional x64
       #3

    Try following the generic tips here, like memory test: https://www.sevenforums.com/crashes-d...tml#post572070
      My Computer


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

    Deadcool said:
    I built a brand new computer with 2.93 GHz processor, and 4 GB ram. Upon installing windows 7 not 10 minutes in and a blue screen pops up with the following message:

    Problem signature:
    Problem Event Name: BlueScreen
    OS Version: 6.1.7600.2.0.0.256.48
    Locale ID: 4105

    Additional information about the problem:
    BCCode: 34
    BCP1: 0000000000001838
    BCP2: FFFFFFFFC0000420
    BCP3: 0000000000000000
    BCP4: 0000000000000000
    OS Version: 6_1_7600
    Service Pack: 0_0
    Product: 256_1

    Files that help describe the problem:
    C:\Windows\Minidump\022010-16593-01.dmp
    C:\Users\Matthew Kent\AppData\Local\Temp\WER-27328-0.sysdata.xml

    Read our privacy statement online:
    Windows 7 Privacy Statement - Microsoft Windows

    If the online privacy statement is not available, please read our privacy statement offline:
    C:\Windows\system32\en-US\erofflps.txt

    This blue screen has happened more than a dozen times on the same day of installation.

    Please help I'm a freelance artist and can't have my computer crashing in the middle of a large photoshop project. I have installed a printer, a wacom Bamboo Fun tablet and mozilla firefox and that's it.

    I have included the most recent DMP in a zip file (see Attachment)

    Hey
    This crash was caused by cache manager.
    Usual causes: Insufficient physical memory, Indexing, Device driver. I noticed you have four Gigs of ram and if you are running 64bit it might be insufficient.

    To cover the possibility of corrupt system files I would
    run a system file check.
    type cmd in search>right click and run as admin>SFC /SCANNOW

    Let us know the results.

    Good luck

    Ken




    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\022010-16593-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    Symbol search path is: SRV*d:\symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 7 Kernel Version 7600 MP (2 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
    Machine Name:
    Kernel base = 0xfffff800`02806000 PsLoadedModuleList = 0xfffff800`02a43e50
    Debug session time: Fri Feb 19 23:59:25.956 2010 (GMT-5)
    System Uptime: 0 days 0:20:30.627
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ...............
    Loading User Symbols
    Loading unloaded module list
    ....
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 34, {1838, ffffffffc0000420, 0, 0}
    
    Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+2ed4 )
    
    Followup: MachineOwner
    ---------
    
    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    CACHE_MANAGER (34)
        See the comment for FAT_FILE_SYSTEM (0x23)
    Arguments:
    Arg1: 0000000000001838
    Arg2: ffffffffc0000420
    Arg3: 0000000000000000
    Arg4: 0000000000000000
    
    Debugging Details:
    ------------------
    
    
    EXCEPTION_RECORD:  ffffffffc0000420 -- (.exr 0xffffffffc0000420)
    Cannot read Exception record @ ffffffffc0000420
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    BUGCHECK_STR:  0x34
    
    PROCESS_NAME:  svchost.exe
    
    CURRENT_IRQL:  0
    
    LAST_CONTROL_TRANSFER:  from fffff8000280fb8c to fffff80002877f00
    
    STACK_TEXT:  
    fffff880`06c4a948 fffff800`0280fb8c : 00000000`00000034 00000000`00001838 ffffffff`c0000420 00000000`00000000 : nt!KeBugCheckEx
    fffff880`06c4a950 fffff880`012be67c : 00000000`00000000 00000000`00000000 fffffa80`04a2e858 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x2ed4
    fffff880`06c4a990 fffff880`01298019 : fffff8a0`071c7010 00000000`00000000 fffffa80`041dcc10 00000000`00000001 : Ntfs!NtfsLookupInFileRecord+0x20c
    fffff880`06c4aa20 fffff880`012b3b43 : fffffa80`039909c0 fffff880`06c27450 fffffa80`039909c0 fffffa80`039909c0 : Ntfs!NtfsUpdateNormalizedName+0x99
    fffff880`06c4ab10 fffff880`0121cc0d : fffffa80`039909c0 fffffa80`041dcc10 fffff880`06c27450 fffffa80`04d20b00 : Ntfs!NtfsCommonCreate+0xc93
    fffff880`06c4acf0 fffff800`0286fd87 : fffff880`06c273c0 00000000`00000000 00000000`7ef68000 00000000`07abfbc0 : Ntfs!NtfsCommonCreateCallout+0x1d
    fffff880`06c4ad20 fffff800`0286fd41 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KySwitchKernelStackCallout+0x27
    fffff880`06c27290 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSwitchKernelStackContinue
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    nt! ?? ::FNODOBFM::`string'+2ed4
    fffff800`0280fb8c cc              int     3
    
    SYMBOL_STACK_INDEX:  1
    
    SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+2ed4
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nt
    
    IMAGE_NAME:  ntkrnlmp.exe
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc600
    
    FAILURE_BUCKET_ID:  X64_0x34_nt!_??_::FNODOBFM::_string_+2ed4
    
    BUCKET_ID:  X64_0x34_nt!_??_::FNODOBFM::_string_+2ed4
    
    Followup: MachineOwner
    ---------
    Code:
    022010-16593-01.dmp    2/20/2010 12:00:24 AM    CACHE_MANAGER    0x00000034    00000000`00001838    ffffffff`c0000420    00000000`00000000    00000000`00000000    Ntfs.sys    Ntfs.sys+b8aa7        x64
    OLD DRIVERS THAT NEED UPDATING
    Code:
    secdrv.SYS        fffff880`02b2d000    fffff880`02b38000    0x0000b000    0x4508052e    9/13/2006 8:18:38 AM                        
    WacomVKHid.sys        fffff880`04399000    fffff880`0439ac80    0x00001c80    0x45d4e87e    2/15/2007 6:10:54 PM                        
    wacomvhid.sys        fffff880`04374000    fffff880`04376300    0x00002300    0x45d5e9f8    2/16/2007 12:29:28 PM                        
    wacommousefilter.sys        fffff880`045a8000    fffff880`045b0000    0x00008000    0x45d5f401    2/16/2007 1:12:17 PM
      My Computer


  5. Posts : 6
    Windows 7
    Thread Starter
       #5

    Alright i ran the admin Scannow and here what came up.

    Microsoft Windows [Version 6.1.7600]
    Copyright (c) 2009 Microsoft Corporation. All rights reserved.

    C:\Windows\system32>SFC/SCANNOW

    Beginning system scan. This process will take some time.

    Beginning verification phase of system scan.
    Verification 100% complete.
    Windows Resource Protection found corrupt files but was unable to fix some of th
    em.
    Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For example
    C:\Windows\Logs\CBS\CBS.log

    Now what do i do to fix the corrupt files that where unable to be fixed. you will have to excuse my ignorance I maybe a lot of things in this world but computer sauvy is not one of them. Your patience and help are greatly appreciated .
      My Computer


  6. Posts : 11,990
    Windows 7 Ultimate 32 bit
       #6

    Try running sannow again. It usually only fixes one file problem in a run. Let us now if it comes up clean after the next run.
      My Computer


  7. Posts : 6
    Windows 7
    Thread Starter
       #7

    I did another sfc/scannow and the same message appeared only this time it said files will be fixed on reboot. I will reboot and do another scannow.
      My Computer


  8. Posts : 6
    Windows 7
    Thread Starter
       #8

    Rebooted computer, and ran scannow again the same original message came up

    Microsoft Windows [Version 6.1.7600]
    Copyright (c) 2009 Microsoft Corporation. All rights reserved.

    C:\Windows\system32>SFC/SCANNOW

    Beginning system scan. This process will take some time.

    Beginning verification phase of system scan.
    Verification 100% complete.
    Windows Resource Protection found corrupt files but was unable to fix some of th
    em.
    Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For example
    C:\Windows\Logs\CBS\CBS.log
      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 12:28.
Find Us