Windows 7 "White Screen" - Plz Help

Discussion in 'Windows 7 Help and Support' started by Biscuit, Feb 8, 2010.

  1. Biscuit

    Biscuit New Member

    Joined:
    Feb 6, 2010
    Messages:
    26
    Likes Received:
    0
    Need help please advise. Dump files text below. Thanks for your help.

    White screen lock up. New OS operational now for only 3 days. Fresh install BTW not an upgrade 7 - 64 bit running an i7 with Crossfired 5770's and 6GB of Corsair XMS RAM 8-8-8-24. 4 - 750 GB's HDD's in a RAID 10 set up.

    Event #1:

    Loading Dump File [C:\Windows\Minidump\020510-45458-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is: *** Invalid ***
    ************************************************** **************************
    * Symbol loading may be unreliable without a symbol search path. *
    * Use .symfix to have the debugger choose a symbol path. *
    * After setting your symbol path, use .reload to refresh symbol locations. *
    ************************************************** **************************
    Executable search path is:
    ************************************************** *******************
    * Symbols can not be loaded because symbol path is not initialized. *
    * *
    * The Symbol Path can be set by: *
    * using the _NT_SYMBOL_PATH environment variable. *
    * using the -y <symbol_path> argument when starting the debugger. *
    * using .sympath and .sympath+ *
    ************************************************** *******************
    Unable to load image ntoskrnl.exe, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
    Windows 7 Kernel Version 7600 MP (8 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Machine Name:
    Kernel base = 0xfffff800`02a64000 PsLoadedModuleList = 0xfffff800`02ca1e50
    Debug session time: Fri Feb 5 21:49:29.628 2010 (GMT-6)
    System Uptime: 0 days 0:00:18.643
    ************************************************** *******************
    * Symbols can not be loaded because symbol path is not initialized. *
    * *
    * The Symbol Path can be set by: *
    * using the _NT_SYMBOL_PATH environment variable. *
    * using the -y <symbol_path> argument when starting the debugger. *
    * using .sympath and .sympath+ *
    ************************************************** *******************
    Unable to load image ntoskrnl.exe, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
    Loading Kernel Symbols
    ................................................
    Loading User Symbols
    Mini Kernel Dump does not contain unloaded driver list
    ************************************************** *****************************
    * *
    * Bugcheck Analysis *
    * *
    ************************************************** *****************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 124, {0, fffffa8007f3d4a8, 0, 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!_WHEA_ERROR_RECORD_HEADER ***
    *** ***
    ************************************************** ***********************
    ************************************************** ***********************
    *** ***
    *** ***
    *** 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!_WHEA_ERROR_RECORD_HEADER ***
    *** ***
    ************************************************** ***********************
    Unable to load image PSHED.dll, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for PSHED.dll
    *** ERROR: Module load completed but symbols could not be loaded for PSHED.dll

    EVENT #2:

    Loading Dump File [C:\Windows\Minidump\020610-31574-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is: *** Invalid ***
    ************************************************** **************************
    * Symbol loading may be unreliable without a symbol search path. *
    * Use .symfix to have the debugger choose a symbol path. *
    * After setting your symbol path, use .reload to refresh symbol locations. *
    ************************************************** **************************
    Executable search path is:
    ************************************************** *******************
    * Symbols can not be loaded because symbol path is not initialized. *
    * *
    * The Symbol Path can be set by: *
    * using the _NT_SYMBOL_PATH environment variable. *
    * using the -y <symbol_path> argument when starting the debugger. *
    * using .sympath and .sympath+ *
    ************************************************** *******************
    Unable to load image ntoskrnl.exe, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
    Windows 7 Kernel Version 7600 MP (8 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Machine Name:
    Kernel base = 0xfffff800`02a19000 PsLoadedModuleList = 0xfffff800`02c56e50
    Debug session time: Sat Feb 6 08:04:13.986 2010 (GMT-6)
    System Uptime: 0 days 0:00:20.000
    ************************************************** *******************
    * Symbols can not be loaded because symbol path is not initialized. *
    * *
    * The Symbol Path can be set by: *
    * using the _NT_SYMBOL_PATH environment variable. *
    * using the -y <symbol_path> argument when starting the debugger. *
    * using .sympath and .sympath+ *
    ************************************************** *******************
    Unable to load image ntoskrnl.exe, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
    Loading Kernel Symbols
    ................................................
    Loading User Symbols
    Mini Kernel Dump does not contain unloaded driver list
    ************************************************** *****************************
    * *
    * Bugcheck Analysis *
    * *
    ************************************************** *****************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 124, {0, fffffa8007ef78f8, 0, 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!_WHEA_ERROR_RECORD_HEADER ***
    *** ***
    ************************************************** ***********************
    ************************************************** ***********************
    *** ***
    *** ***
    *** 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!_WHEA_ERROR_RECORD_HEADER ***
    *** ***
    ************************************************** ***********************
    Unable to load image PSHED.dll, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for PSHED.dll
    *** ERROR: Module load completed but symbols could not be loaded for PSHED.dll
     
    #1 Biscuit, Feb 8, 2010
    Last edited: Feb 8, 2010
  2. Trouble

    Trouble Noob Whisperer

    Joined:
    Nov 30, 2009
    Messages:
    13,845
    Likes Received:
    833
    Try running the debugger again only this time when you open the debugger and before you open the .dmp go to the file menu and chose symbol path and paste this into the location
    "SRV*c:\symbols*http://msdl.microsoft.com/download/symbols"
    without the outside quotes then open the .dmp and see if you get a better since of the issue.
     
  3. ickymay

    ickymay New Member

    Joined:
    Jan 12, 2009
    Messages:
    1,689
    Likes Received:
    113
    and post the minidump file here and someone could take a look ;)
     
  4. Biscuit

    Biscuit New Member

    Joined:
    Feb 6, 2010
    Messages:
    26
    Likes Received:
    0
    didn't I do that with the text above? sorry.....dump file noob.
     
  5. ickymay

    ickymay New Member

    Joined:
    Jan 12, 2009
    Messages:
    1,689
    Likes Received:
    113
    no we need the actual .dmp file to run through windows debugger and the many commands it uses ;)
     
  6. Biscuit

    Biscuit New Member

    Joined:
    Feb 6, 2010
    Messages:
    26
    Likes Received:
    0
    should I PM it to you?
     
  7. ickymay

    ickymay New Member

    Joined:
    Jan 12, 2009
    Messages:
    1,689
    Likes Received:
    113
    nope it's better if a few people familiar with using windows debugger can take a look as well as me then we have many minds working towards a solution :D

    simply zip the .dmp file out of the minidump folder then attach it here , just look up and theres a paperclip where you can open a dialogue box then choose the file off your hard drive then upload and attach it in this post :p

    N.B. in the text you have posted your debugger hasn't loaded the correct symbols from the Microsoft database :confused:
     
  8. Biscuit

    Biscuit New Member

    Joined:
    Feb 6, 2010
    Messages:
    26
    Likes Received:
    0
    Dump files attached as requested.......ZIPPED. Thanks for your help.
     

    Attached Files:

  9. Trouble

    Trouble Noob Whisperer

    Joined:
    Nov 30, 2009
    Messages:
    13,845
    Likes Received:
    833
    Since all three of the dumps were virtually identical I have posted the results of only one. As you can see the results point to hardware (not much help). So given that, you may want to take a look at the memory settings, timings and voltages, you didn't say what type of MoBo you are using, but if it's an ASUS take a look in the bios, AI Tweaker, try normal or auto just not xmp and see if that makes any difference. Check your temps idle and under a load...check device manager->view->show hidden devices and see if there is anything there showing a problem. If you are currently OC'ing anything of course you may want to reset everything to standard/default and see what happens. The only other thing you might try is safemode or safemode with networking to rule out any third party software / services issues.
     
  10. ickymay

    ickymay New Member

    Joined:
    Jan 12, 2009
    Messages:
    1,689
    Likes Received:
    113
    ok I reckon this is something to do with your Raid 10 setup .......

    windows debugger came up with
    So all three results are exactly the same including the driver stack and cause listed as hardware, and the bugcheck code is the key here BugCheck 124

    microsoft advises
    now I reckon this could be a raid driver or settings in the BIOS although I have to say all your drivers look fully up to date ?

    please run a disk check on all drives using Run Chkdsk /f /r
     
    #10 ickymay, Feb 15, 2010
    Last edited: Feb 15, 2010
  11. Biscuit

    Biscuit New Member

    Joined:
    Feb 6, 2010
    Messages:
    26
    Likes Received:
    0
    wow......thanks for the help. I have a RAID 10 set up with a ASUS P6T Deluxe V2 with 2 WD 750GB HDD's and 2 Seagate 750 GB HDD's all have the same performance specs but I know that mixing 2 drives may cause some issues. Running the Chkdsk /f /r.
     
  12. ickymay

    ickymay New Member

    Joined:
    Jan 12, 2009
    Messages:
    1,689
    Likes Received:
    113
    ignore the microsoft advises quote from my last post that was a mistake as it's the treatment for a Bug Check 0x24: NTFS_FILE_SYSTEM and your error is a BugCheck 0x124 doh! :redface:

    your STOP 0x124 errors are going to be:
    - hardware problems
    - compatibility issues (hardware or driver)
    - corrupted driver (not all agree with this)
    Because of the limited information in the STOP 0x124 memory dumps this is going to be hard to discover from your minidump and we need to start running some stress tests on your hardware

    the Chkdsk result is still relevant and it can still be something in the Raid but we have a few other possibilities too now :)

    Do you have any conflicts in Device manager and any conflicts in System Information \ Conflicts\Sharing or I\O ?

    A common one is soundcard and Gfx card did you get any noises just before you crash ?

    Do you have the latest BIOS and have you tried rolling back your gfx card drivers ?

    Also what antivirus and firewall are you using ?

    what make and model of Power Supply are you using ?
     
  13. Biscuit

    Biscuit New Member

    Joined:
    Feb 6, 2010
    Messages:
    26
    Likes Received:
    0
    Corsair 850W PS......I updated audio drivers cuz I too have seen that somewhere. Updated BIOS from ASUS. Also disabled RAC something or other and the desktop gadgets. Hoping ATI will produce some new graphics drivers cuz I've seen a lot of people rolling back to previous versions. Not sure if this will work but thanks for all of the recommendations. Will obviously post again if I run into it.
     
  14. ickymay

    ickymay New Member

    Joined:
    Jan 12, 2009
    Messages:
    1,689
    Likes Received:
    113
    yup Im not confident the latest 10.1 is stable from ATI and I am running the 09.12 for stability on my HD5770 :cool:
     
  15. Biscuit

    Biscuit New Member

    Joined:
    Feb 6, 2010
    Messages:
    26
    Likes Received:
    0
    arghhhhhhhhhhh. another one. Not sure if its the same thing this time as it did a system reboot in lieu of a white screen hang up. ZIP attached. I did notice that 3 of the 4 dumps happened at 50 minutes past the hour.

    Thanks again for help in advance.
     

    Attached Files:

  16. Trouble

    Trouble Noob Whisperer

    Joined:
    Nov 30, 2009
    Messages:
    13,845
    Likes Received:
    833
    Nope, nothing different, in fact, identical to the one I posted in post #9 here is a link with another discussion of your WHEA_UNCORRECTABLE_ERROR (124) it would seem that most of the recommendation are similar to the ones that have been made here, just wanted you to have as much input as possible
    [2-Int] Stop 0x124 - what it means and what to try - Windows 7 Forums
     
  17. Biscuit

    Biscuit New Member

    Joined:
    Feb 6, 2010
    Messages:
    26
    Likes Received:
    0
    thanks for the info but im actually going back to 9.12 on my ati drivers. havent tried this fix yet. Not sure how to update my audio drivers......cant seem to uninstall the existing ones.
     
  18. Trouble

    Trouble Noob Whisperer

    Joined:
    Nov 30, 2009
    Messages:
    13,845
    Likes Received:
    833
    Have you taken a look at driver sweeper Phyxion.net | Driver Sweeper 2.1.0 released | Driver Sweeper | Driver Sweeper is works for creative and realtek, not sure what sound drivers you have installed.
    Good luck and keep us posted.
     
  19. ickymay

    ickymay New Member

    Joined:
    Jan 12, 2009
    Messages:
    1,689
    Likes Received:
    113
    you could try going into device driver and select your HD5770 then properties and roll back the driver ?

    If you still get issues follow the advice from "trouble" :)
     
  20. Biscuit

    Biscuit New Member

    Joined:
    Feb 6, 2010
    Messages:
    26
    Likes Received:
    0
    Strangely it seems that this event occurs when I either have the changing desktop pics or a screensaver enabled. Going to try and isolate the two to see if I can narrow down further. Will uninstall current install old vid drivers tonight. May be way off base here but looks like a pattern. Thx.
     

Share This Page

Loading...