BSODs every day... need help


  1. Posts : 1
    win7 ultimate 32 bit
       #1

    BSODs every day... need help


    Hi guys,

    i have a serious problem with my new config... i built it 2 weeks ago, and since then i get the BSODs almost every day.
    i run memtest on both RAMs, individually both were OK, but when tried to run the test on dual, the system crashed after few seconds.
    checkdisk showed no problems on the harddrive
    today i tried to run SFC/scannow, but it stopped at 17%, and the program said: "windows resource protection could not perform the requested operation"
    and btw the everest says as a video debug: YOU HAVE NOT CONNECTED ONE OF YOUR VIDEO CARD POWER CONNECTORS TO THE POWER SUPPLY....

    i attached the minidumps and the sfc problem details file.

    Any ideas?

    Your help will be highly appreciated, please help me!

    Thank you in advance!
      My Computer


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

    Welcome to SF!

    It appears you are using the Windows 7 Beta. Are you using a crack to make it still work after the expiration period?

    The Betas and Release Candidate have expired. Please buy a copy of Windows 7 from a reputable source, and do a clean install.

    Do not try to upgrade, just reformat and do a clean install.

    Code:
    Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Users\Jonathan\_jcgriff2_\dbug\__Kernel__\070210-13026-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: 
    Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ntkrnlpa.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
    Windows 7 Kernel Version 7100 MP (4 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7100.0.x86fre.winmain_win7rc.090421-1700
    Machine Name:
    Kernel base = 0x8283e000 PsLoadedModuleList = 0x82986810
    Debug session time: Fri Jul  2 16:37:32.204 2010 (UTC - 4:00)
    System Uptime: 0 days 0:04:20.437
    Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ntkrnlpa.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ....................
    Loading User Symbols
    Loading unloaded module list
    ....
    Unable to load image \SystemRoot\System32\win32k.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for win32k.sys
    *** ERROR: Module load completed but symbols could not be loaded for win32k.sys
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 1000008E, {c0000005, 828732f9, 9dd61ae8, 0}
    
    ***** Kernel symbols are WRONG. Please fix symbols to do analysis.
    
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Your debugger is not using the correct symbols                 ***
    ***                                                                   ***
    ***    In order for this command to work properly, your symbol path   ***
    ***    must point to .pdb files that have full type information.      ***
    ***                                                                   ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***                                                                   ***
    ***    Type referenced: nt!_KPRCB                                     ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Your debugger is not using the correct symbols                 ***
    ***                                                                   ***
    ***    In order for this command to work properly, your symbol path   ***
    ***    must point to .pdb files that have full type information.      ***
    ***                                                                   ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***                                                                   ***
    ***    Type referenced: nt!_KPRCB                                     ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Your debugger is not using the correct symbols                 ***
    ***                                                                   ***
    ***    In order for this command to work properly, your symbol path   ***
    ***    must point to .pdb files that have full type information.      ***
    ***                                                                   ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***                                                                   ***
    ***    Type referenced: nt!_KPRCB                                     ***
    ***                                                                   ***
    *************************************************************************
    Probably caused by : win32k.sys ( win32k+d70f0 )
    
    Followup: MachineOwner
    ---------
      My Computer


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

    One other thing, you should consider buying the 64-bit version of Windows 7. It should perform better than the 32-bit version, and allow you to use your full 4GB of RAM.
      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 20:24.
Find Us