Windows 7 Windows 7 "White Screen" - Plz Help

[Biscuit]

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

 

[Trouble]

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.

 

[ickymay]

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.

and post the minidump file here and someone could take a look

 

[Biscuit]

didn't I do that with the text above? sorry.....dump file noob.

 

[ickymay]

didn't I do that with the text above? sorry.....dump file noob.

no we need the actual .dmp file to run through windows debugger and the many commands it uses

 

[Biscuit]

should I PM it to you?

 

[ickymay]

should I PM it to you?

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

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

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

 

[Biscuit]

Dump files attached as requested.......ZIPPED. Thanks for your help.

 

[Trouble]

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.

Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Users\JohnSmith\Desktop\New folder\1_020510-45458-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symbols*Symbol information
Executable search path is:
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
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
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}
Probably caused by : hardware
Followup: MachineOwner
---------
6: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa8007f3d4a8, Address of the WHEA_ERROR_RECORD structure.
Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value.
Debugging Details:
------------------

BUGCHECK_STR: 0x124_GenuineIntel
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 0
STACK_TEXT:
fffff880`033706f0 fffff800`02d1ea89 : fffffa80`07f3d480 fffffa80`05523680 00000000`00000009 00000000`00000001 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`03370c10 fffff800`02c00547 : fffffa80`07f3d480 fffff800`02c795f8 fffffa80`05523680 00000002`00000005 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`03370c40 fffff800`02b68b95 : fffff800`02cdb360 fffffa80`070f2828 fffffa80`070f2820 fffffa80`05523680 : nt!WheapProcessWorkQueueItem+0x57
fffff880`03370c80 fffff800`02ae3161 : fffff880`01065e00 fffff800`02b68b70 fffffa80`05523680 00000000`00000000 : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`03370cb0 fffff800`02d79166 : 1b5c052c`4c8abbac fffffa80`05523680 00000000`00000080 fffffa80`05507040 : nt!ExpWorkerThread+0x111
fffff880`03370d40 fffff800`02ab4486 : fffff880`0316a180 fffffa80`05523680 fffff880`031750c0 39e12f08`c2190f0f : nt!PspSystemThreadStartup+0x5a
fffff880`03370d80 00000000`00000000 : fffff880`03371000 fffff880`0336b000 fffff880`02e9c540 00000000`00000000 : nt!KxStartSystemThread+0x16

STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: hardware
IMAGE_NAME: hardware
DEBUG_FLR_IMAGE_TIMESTAMP: 0
FAILURE_BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_MAE_PRV
BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_MAE_PRV
Followup: MachineOwner
---------
6: kd> lmvm hardware
start end module name
Mini Kernel Dump does not contain unloaded driver list

 

[ickymay]

Dump files attached as requested.......ZIPPED. Thanks for your help.

ok I reckon this is something to do with your Raid 10 setup .......

windows debugger came up with

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa8007f3d4a8, 0, 0}

Probably caused by : hardware

Followup: MachineOwner
---------
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa8007ef78f8, 0, 0}

Probably caused by : hardware

Followup: MachineOwner
---------
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa8007ef78f8, 0, 0}

Probably caused by : hardware

Followup: MachineOwner
---------

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

Bug Check 0x24: NTFS_FILE_SYSTEM

The NTFS_FILE_SYSTEM bug check has a value of 0x00000024. This indicates a problem occurred in ntfs.sys, the driver file that allows the system to read and write to NTFS drives.
Parameters

The following parameters are displayed on the blue screen.Parameter Description
1 Specifies source file and line number information. The high 16 bits (the first four hexadecimal digits after the "0x") identify the source file by its identifier number. The low 16 bits identify the source line in the file where the bug check occurred.
2 If NtfsExceptionFilter is on the stack, this parameter specifies the address of the exception record.
3 If NtfsExceptionFilter is on the stack, this parameter specifies the address of the context record.
4 Reserved


Cause

One possible cause of this bug check is disk corruption. Corruption in the NTFS file system or bad blocks (sectors) on the hard disk can induce this error. Corrupted SCSI and IDE drivers can also adversely affect the system's ability to read and write to disk, thus causing the error.

Another possible cause is depletion of nonpaged pool memory. If the nonpaged pool memory is completely depleted, this error can stop the system. However, during the indexing process, if the amount of available nonpaged pool memory is very low, another kernel-mode driver requiring nonpaged pool memory can also trigger this error.
Resolving the Problem

To debug this problem: Use the .cxr (Display Context Record) command with Parameter 3, and then use the kb (Display Stack Trace) command.

To resolve a disk corruption problem: Check Event Viewer for error messages from SCSI and FASTFAT (System Log) or Autochk (Application Log) that might help pinpoint the device or driver that is causing the error. Try disabling any virus scanners, backup programs, or disk defragmenter tools that continually monitor the system. You should also run hardware diagnostics supplied by the system manufacturer. For details on these procedures, see the owner's manual for your computer. Run Chkdsk /f /r to detect and resolve any file system structural corruption. You must restart the system before the disk scan begins on a system partition.

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

 

[Biscuit]

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.

 

[ickymay]

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.

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!

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 ?

 

[Biscuit]

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.

 

[ickymay]

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.

yup Im not confident the latest 10.1 is stable from ATI and I am running the 09.12 for stability on my HD5770

 

[Biscuit]

yup Im not confident the latest 10.1 is stable from ATI and I am running the 09.12 for stability on my HD5770

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.

 

[Trouble]

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.

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

 

[Biscuit]

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.

 

[Trouble]

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.

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.

 

[ickymay]

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.

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"

 

[Biscuit]

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.