BSOD on boot

Page 1 of 4 123 ... LastLast

  1. Posts : 15
    Windows 7 64 bit
       #1

    BSOD on boot


    Hey i've just recently built myself a new pc BUTTT a couple weeks back i started encountering BSOD's on boot. I've got to admit I've had a fair amount of BSOD's and it hasn't taken me too long to figure out the cause but for this one i am receiving no such luck.

    Obviously because it's a new pc on my first day i installed everything extremely fast from drivers too the anti-virus so i could start using it as fast as possible. Because of this i now have no clue as to what could be causing the BSOD's.

    In my opinion this has to be the strangest BSOD ever because none of it makes any sense. If i leave my pc turned off for say 2+ hours then try to fire it up on boot it will get to the windows 7 loading screen and it will BSOD, naturally you would restart your computer this time on boot when it hits the loading screen it starts pulsating then it will BSOD again this time with a different error. If i tried to restart again it would keep going in an endless cycle of these two different BSOD's. So to 'temporarily' fix this problem i would turn my computer on and once the POST test has run i hold the power button till it turns off then fire it up again this 100% always fixes the problem and i don't encounter any BSOD's.

    If i've recently had my pc on within about 1-2 hours or so of it being on previously i can turn my pc on without any BSOD's or restarts.

    I will attach the first BSOD's minidump as i am assuming this will show the main problem.

    thanks in advance
      My Computer


  2. Posts : 15
    Windows 7 64 bit
    Thread Starter
       #2

    hey sorry i just read about the SF diag tool so i'll upload that instead :P
      My Computer


  3. Posts : 1,598
    Microsoft Window 7 Professional 32 bit
       #3

    Hi and welcome

    In looking through your drivers, I see that you have AVG anti virus installed. AVG is known to cause BSOD, on some systems. I suggest that you uninstall it while trouble shooting using the uninstall tool > Info > Tool (32bit) - Tool (64 bit). If you have AVG Identity Protection installed, uninstall it also >Info > Tool. I recommend that you install MSE and make sure Windows Firewall is turned on.

    As the bugcheck code is 50, and memory corruption was blamed, I would download third party called memtestx86, burn it to CD and let it run for at least 7 passes

    Code:
    BugCheck 50, {ffffffffffffff98, 1, fffff88003fe13af, 0}
    
    *** ERROR: Module load completed but symbols could not be loaded for blbdrive.sys
    
    Could not read faulting driver name
    Probably caused by : memory_corruption
    
    Followup: memory_corruption
    ---------
    Let us know if you need help

    Tuan
      My Computer


  4. Posts : 1,598
    Microsoft Window 7 Professional 32 bit
       #4

    As I doubted, AVG was blamed directly in the new minidump you just uploaded
    Code:
    BugCheck 1000007E, {ffffffffc0000005, fffff88003f30ae1, fffff880009a8848, fffff880009a80b0}
    
    Probably caused by : avgldx64.sys ( avgldx64+2cae1 )
    
    Followup: MachineOwner
    ---------
    BugCheck BE, {fffff88003b1541b, 80000001385e4121, fffff880009a8fb0, b}
    
    Unable to load image \SystemRoot\System32\Drivers\avgldx64.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for avgldx64.sys
    *** ERROR: Module load completed but symbols could not be loaded for avgldx64.sys
    Probably caused by : avgldx64.sys ( avgldx64+a2ec )
    
    Followup: MachineOwner
    ---------
    BugCheck 1A, {41790, fffffa80034b0f30, ffff, 0}
    
    Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_PROCESS_HEAP::Free+a2 )
    
    Followup: MachineOwner
    ---------
    BugCheck F4, {3, fffffa8005e72b30, fffffa8005e72e10, fffff80002d99540}
    
    Probably caused by : wininit.exe
    
    Followup: MachineOwner
    ---------
    I would also, update directx:
    Download details: DirectX End-User Runtime
    Finally, run system file check:
    SFC /SCANNOW Command - System File Checker

    Regard

    Tuan
      My Computer


  5. Posts : 15
    Windows 7 64 bit
    Thread Starter
       #5

    Hey, thanks for your help so far i had a hunch it was AVG i've used the un-installation tools to remove it but like i said i have to leave my pc off for a while before it usually BSOD's. I'll reply back later with the results.

    I also ran the SFC /SCANNOW earlier and it kept throwing up:

    Code:
    Repairing 1 components
    2010-07-01 08:05:58, Info                  CSI    000002ec [SR] Beginning Verify and Repair transaction
    2010-07-01 08:05:58, Info                  CSI    000002ee [SR] Cannot repair member file [l:28{14}]"iassdo.dll.mui" of Microsoft-Windows-Networking-Internet_Authentication_Service_Iassdo.Resources, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture = [l:10{5}]"en-US", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
    2010-07-01 08:05:58, Info                  CSI    000002f0 [SR] Cannot repair member file [l:28{14}]"iassdo.dll.mui" of Microsoft-Windows-Networking-Internet_Authentication_Service_Iassdo.Resources, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture = [l:10{5}]"en-US", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
    2010-07-01 08:05:58, Info                  CSI    000002f1 [SR] This component was referenced by [l:266{133}]"Microsoft-Windows-WindowsFoundation-LanguagePack-Package~31bf3856ad364e35~amd64~en-US~6.1.7600.16385.Windows Foundation Language Pack"
    2010-07-01 08:05:58, Info                  CSI    000002f4 [SR] Could not reproject corrupted file [ml:60{30},l:58{29}]"\??\C:\Windows\SysWOW64\en-US"\[l:28{14}]"iassdo.dll.mui"; source file in store is also corrupted
    2010-07-01 08:05:58, Info                  CSI    000002f6 [SR] Repair complete
    2010-07-01 08:05:58, Info                  CSI    000002f7 [SR] Committing transaction
    2010-07-01 08:05:58, Info                  CSI    000002fb [SR] Verify and Repair Transaction completed. All files and registry keys listed in this transaction  have been successfully repaired
    This error came up four times during the scan.

    hehe hopefully the code box thing worked never tried it before.
      My Computer


  6. Posts : 1,598
    Microsoft Window 7 Professional 32 bit
       #6

    Good, excited to hear result from ya, hope no more BSODs
      My Computer


  7. Posts : 15
    Windows 7 64 bit
    Thread Starter
       #7

    Hey, I left my pc like i said and the BSOD that AVG was causing has gone, now i am left with a different one. This time i'm given some information "DRIVER_IRQL_NOT_LESS_OR_EQUAL"

    I am assuming it has something to do with my graphics card drivers that i recently updated.

    minidump attached

    Thanks again
      My Computer


  8. Posts : 1,598
    Microsoft Window 7 Professional 32 bit
       #8

    Did you use the tool that I provide to remove AVG, I still see avg driver in the list of loaded drivers
    Code:
    avgtdia  avgtdia.sys  Wed Apr 14 04:12:20 2010 (4BC4DE34)
    Also, the bugcheck code is 50,
    STOP 0x00000050: PAGE_FAULT_IN_NONPAGED_AREA

    Usual causes: Defective hardware (particularly memory - but not just RAM), Faulty system service, Antivirus, Device driver, NTFS corruption, BIOS
    We have eliminate AVG, supposed that you have followed my advise
    , please download third party called memtestx86, burn it to CD using ISO Recorder v3 and let it run for at least 6 or 7 passess

    Also, go check manufacture's site for latest BIOS update (usually hot fix), as well as other drivers

    Code:
    Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Users\TUANTR~1\AppData\Local\Temp\Rar$DI00.697\070110-22308-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    Symbol search path is: SRV*e:\symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 7 Kernel Version 7600 MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
    Machine Name:
    Kernel base = 0xfffff800`02a60000 PsLoadedModuleList = 0xfffff800`02c9de50
    Debug session time: Thu Jul  1 12:26:15.582 2010 (UTC + 7:00)
    System Uptime: 0 days 0:00:07.987
    Loading Kernel Symbols
    ...............................................................
    ................
    Loading User Symbols
    Loading unloaded module list
    .
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 50, {ffffffffffffff98, 1, fffff88003fe13af, 0}
    
    *** ERROR: Module load completed but symbols could not be loaded for blbdrive.sys
    
    Could not read faulting driver name
    Probably caused by : memory_corruption
    
    Followup: memory_corruption
    ---------
    Best regard,

    Tuan
      My Computer


  9. Posts : 15
    Windows 7 64 bit
    Thread Starter
       #9

    Yes i used the tools to remove AVG as suggested, it asked me to restart afterwards and i think i forgot to so that mite be the reason it was still showing up. I've also already got the latest BIOS update

    I've downloaded and burned memtestx86, i'll leave it running through the night.

    I'll notify you tomorrow of any changes or more problems that i encounter :P Hopefully that BSOD was a one off, i doubt it though
      My Computer


  10. Posts : 15
    Windows 7 64 bit
    Thread Starter
       #10

    hello again, unfortunately still receiving a BSOD.

    I ran memtestx86 all through the night and it got to 8 passes without any errors

    i'll attach the dump from the BSOD, if its any help in bluescreenview its showing that the problem was caused by driver: "ntoskrnl.exe". It is also showing for me that AVG isn't present anymore.

    thanks for all the help so far.
      My Computer


 
Page 1 of 4 123 ... 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 16:22.
Find Us