Windows 7 Forums

Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSOD At Welcome Screen, error 0x000000F4

31 Dec 2012   #1
Thyatira

Windows 7 Home Premium x64
 
 
BSOD At Welcome Screen, error 0x000000F4

Greetings all,

Thanks for taking the time to read this. I'll give some background into the issue I'm experiencing.

Several weeks ago, I began receiving several random BSOD but didn't think much of them at the time. I do not have the dumps, error codes, or timing of those. The only notable hardware or software events within the past few weeks were:

a) Removed then reinstalled the same LG Blu-ray Drive (Model GBC-H20L)
b) Updated Nvidia Geforce drivers to 310.70 (using a clean uninstallation of my previous drivers and installation of the new driver)
c) Removed and reinstalled Nvidia HD Audio drivers

It should be noted that my PC was booting up and running fine (save those random BSOD's) after I made these changes. Fast forward to today, and I cannot boot into Windows. Specifically, whether I boot normally or into any type of Safe Mode, my PC:

a) Freezes upon attempting to restart or shut down from the login screen, sometimes giving me a BSOD.
b) Once logged in, at the welcome screen, hangs for several seconds and then freezes, usually giving me a BSOD.

These are two separate BSOD's which contained slightly different error codes:

Attachment 248013

Attachment 248014

Unfortunately, I haven't been able to actually load Windows to get any BSOD dump files. I have followed steps 1-8 in the Troubleshooting Windows 7 Failure to Start thread to no avail. The only thing I haven't done is remove my HD to another computer to assess it with Malwarebytes. Here are the results of each step:

1) I only have one HD. Again, I cannot boot either normally or into any type of Safe Mode.

2) Ran Windows Defender Offline. Results:

Attachment 248010

Then ran Kaspersky Rescue. The results, which to me were unremarkable:

Attachment 248011
Attachment 248012

As noted above, I did not run Malwarebytes. Still BSOD and freezing as above.

3) Even though nothing was found, I ran sfc /scannow multiple times. There was nothing to fix. Still BSOD and freezing as above. I tried to run this again later, and it is now stuck in "System repair pending which requires reboot to complete".

4) Ran Startup Repair at least 3 times with reboots between each. There was nothing to fix. Still BSOD and freezing as above.

5) I skipped this step since, as far as I can tell, I did not need an installer. I'm able to load into System Recovery Options.

6) As with step 5, I don't think I needed to do this step.

7) Ran System Restore. I had several restore points to choose from, going back several weeks. I tried two restore points that I know for sure were before my system was BSODing and freezing. However, after multiple attempts to restore, I received this error:

Attachment 248015

Still BSOD and freezing as above. I have a much earlier restore point (over a year ago), but I'm holding off on this as a very last resort.

8) Ran Partition Wizard and followed the instructions. Using System Reserved Partition as Active and upon rebooting after the third Startup Repair, my system ran a CHKDSK scan. Still BSOD and freezing as above. Setting my Windows 7 disk as Active did not work - I received a BOOTMGR missing error. I put the System Reserved Partition as Active again. Still BSOD and freezing as above.

I'm holding off doing a clean reinstall or restoring to that old restore point at this time in case there are other reasons for this issue or other, less drastic options available to fix it. Please let me know if any additional information would be helpful. I would love to at least get into Safe Mode to grab those dump files. My build is as follows:

OS: Windows 7 Home Premium x64
CPU: Intel Core i7-930
Motherboard: ASUS P6X58D-E
Memory: Patriot Viper 6GB
Graphics Card: Nvidia Geforce GTX 470
Hard Drive: WD 1TB 7200 RPM
PSU: Cooler Master Silent Pro 1000W

Thanks for the help!


My System SpecsSystem Spec
.
31 Dec 2012   #2
Pauly

Win7 Ultimate X64
 
 

Its hard to be specific with no dump files, if you have drive in another machine check %sysroot%\windows\minidump folder for any dumps and upload if you have any
Try some bootable hardware checks
RAM - Test with Memtest86+
Hard Drive Diagnostic Procedure
SeaTools | Seagate
Disk Check
My System SpecsSystem Spec
31 Dec 2012   #3
Thyatira

Windows 7 Home Premium x64
 
 

For the time being, I've put my HDD in another machine. Sorry for not doing this earlier - I don't know what I was thinking. Anyway, I've got two dump files (one from September, one from yesterday). Unfortunately, SF Diagnostic Tool was extracting information from this second computer, so I figured none of it would be useful. If you need anything else, let me know. I will get to the checks in your post ASAP.
My System SpecsSystem Spec
.

01 Jan 2013   #4
Pauly

Win7 Ultimate X64
 
 

Ran the two dumps provided, older one is 0x124 error BSOD Index
Have a look through this Stop 0x124 - what it means and what to try
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 124, {0, fffffa80076fb568, 0, 0}
Probably caused by : GenuineIntel
Followup: MachineOwner
---------
0: 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: fffffa80076fb568, 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:  WIN7_DRIVER_FAULT
PROCESS_NAME:  System
CURRENT_IRQL:  0
STACK_TEXT:  
fffff880`033706f0 fffff800`0351fca9 : fffffa80`076fb540 fffffa80`0556ab50 00000000`00000001 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`03370c10 fffff800`03400547 : fffffa80`076fb540 fffff800`0347a2d8 fffffa80`0556ab50 00000000`00000000 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`03370c40 fffff800`03367945 : fffff800`034dbae0 00000000`00000001 00000000`00000000 fffffa80`0556ab50 : nt!WheapProcessWorkQueueItem+0x57
fffff880`03370c80 fffff800`032e6841 : fffff880`01263f00 fffff800`03367920 fffffa80`0556ab00 00000000`00000000 : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`03370cb0 fffff800`03573e6a : cac4cac4`e2e6e2e6 fffffa80`0556ab50 00000000`00000080 fffffa80`054ff040 : nt!ExpWorkerThread+0x111
fffff880`03370d40 fffff800`032cdec6 : fffff880`0316a180 fffffa80`0556ab50 fffff880`031750c0 f78ff78f`4bc34bc3 : nt!PspSystemThreadStartup+0x5a
fffff880`03370d80 00000000`00000000 : fffff880`03371000 fffff880`0336b000 fffff880`033709e0 00000000`00000000 : nt!KiStartSystemThread+0x16
 
STACK_COMMAND:  kb
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: GenuineIntel
IMAGE_NAME:  GenuineIntel
DEBUG_FLR_IMAGE_TIMESTAMP:  0
FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE_PRV
BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE_PRV
Followup: MachineOwner
---------
0: kd> !errrec [fffffa80076fb568]
===============================================================================
Common Platform Error Record @ fffffa80076fb568
-------------------------------------------------------------------------------
Record Id     : 01cd98fe763ee183
Severity      : Fatal (1)
Length        : 928
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 9/22/2012 20:11:49 (UTC)
Flags         : 0x00000002 PreviousError
===============================================================================
Section 0     : Processor Generic
-------------------------------------------------------------------------------
Descriptor    @ fffffa80076fb5e8
Section       @ fffffa80076fb6c0
Offset        : 344
Length        : 192
Flags         : 0x00000001 Primary
Severity      : Fatal
Proc. Type    : x86/x64
Instr. Set    : x64
Error Type    : Micro-Architectural Error
Flags         : 0x00
CPU Version   : 0x00000000000106a5
Processor ID  : 0x0000000000000002
===============================================================================
Section 1     : x86/x64 Processor Specific
-------------------------------------------------------------------------------
Descriptor    @ fffffa80076fb630
Section       @ fffffa80076fb780
Offset        : 536
Length        : 128
Flags         : 0x00000000
Severity      : Fatal
Local APIC Id : 0x0000000000000002
CPU Id        : a5 06 01 00 00 08 10 02 - bd e3 98 00 ff fb eb bf
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
Proc. Info 0  @ fffffa80076fb780
===============================================================================
Section 2     : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor    @ fffffa80076fb678
Section       @ fffffa80076fb800
Offset        : 664
Length        : 264
Flags         : 0x00000000
Severity      : Fatal
Error         : Internal timer (Proc 2 Bank 5)
  Status      : 0xfe00000000800400
  Address     : 0x000038000381696e
  Misc.       : 0x0000000000007fff
Recent dump is 0x3D error BSOD Index
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 3D, {fffff88003391fc0, 0, 0, fffff800032ccdd0}
Probably caused by : ntkrnlmp.exe ( nt!KiInterruptHandler+29 )
Followup: MachineOwner
---------
7: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
INTERRUPT_EXCEPTION_NOT_HANDLED (3d)
Arguments:
Arg1: fffff88003391fc0
Arg2: 0000000000000000
Arg3: 0000000000000000
Arg4: fffff800032ccdd0
Debugging Details:
------------------
 
CONTEXT:  fffff88003391fc0 -- (.cxr 0xfffff88003391fc0)
rax=0000000000000000 rbx=fffffa800680da20 rcx=1bb6903f4ea40000
rdx=0000000000000014 rsi=fffffa80067fc890 rdi=fffffa80067eb8c0
rip=fffff800032ccdd0 rsp=fffff880033929a8 rbp=fffffa80067fc890
 r8=0000000000000065  r9=0000000000000000 r10=0000000000000000
r11=fffff88003392560 r12=fffffa80067eb8c0 r13=fffffa80067eb0d8
r14=fffffa80065c8200 r15=0000000000000000
iopl=0         nv up ei ng nz ac po cy
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00000297
nt!DbgBreakPoint:
fffff800`032ccdd0 cc              int     3
Resetting default scope
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0x3D
PROCESS_NAME:  System
CURRENT_IRQL:  7
TAG_NOT_DEFINED_c000000f:  FFFFF88003399FB0
LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff800032ccdd0
STACK_TEXT:  
fffff880`03391708 fffff800`032d4569 : 00000000`0000003d fffff880`03391fc0 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
fffff880`03391710 fffff800`032d08c9 : fffffa80`0595c350 00000000`00000000 fffff880`03391fc0 fffff800`032ffe20 : nt!KiBugCheckDispatch+0x69
fffff880`03391850 fffff800`032ffaed : fffff880`010142f4 fffff880`0101258c fffff880`01000000 fffff880`03392768 : nt!KiInterruptHandler+0x29
fffff880`03391880 fffff800`032fe8c5 : fffff800`0341bdb4 fffff880`033918f8 fffff880`03392768 fffff800`03256000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`033918b0 fffff800`0330f851 : fffff880`03392768 fffff880`03391fc0 fffff880`00000000 fffffa80`067eb8c0 : nt!RtlDispatchException+0x415
fffff880`03391f90 fffff800`032d4642 : fffff880`03392768 fffffa80`0680da20 fffff880`03392810 fffffa80`067fc890 : nt!KiDispatchException+0x135
fffff880`03392630 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatch+0xc2
 
STACK_COMMAND:  kb
FOLLOWUP_IP: 
nt!KiInterruptHandler+29
fffff800`032d08c9 90              nop
SYMBOL_STACK_INDEX:  2
SYMBOL_NAME:  nt!KiInterruptHandler+29
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: nt
IMAGE_NAME:  ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP:  503f82be
FAILURE_BUCKET_ID:  X64_0x3D_nt!KiInterruptHandler+29
BUCKET_ID:  X64_0x3D_nt!KiInterruptHandler+29
Followup: MachineOwner
---------
So neither dump specifies a cause

I would get the machine back together and run through the hardware checks in earlier post and steps in the 0x124 what to try post, see how you get on and post back, if you get anymore BSOD post the new files these could be handy in narrowing down possible causes

You also have some real old drivers that could do with updating or removing
Quote:
vrtaucbl.sys 15/05/2007 Virtual Audio Cable (WDM) http://www.ventrilo.com/download.php

Lycosa.sys 18/01/2008 Razer Lycosa/Razer Tarantula Keyboard Driver http://www.razersupport.com/index.ph...nloads&_a=view

000.fcl 26/09/2008 CyberLink FCL Driver Video editing software, Multimedia Software and Blu-ray playback software by CyberLink

AsUpIO.sys 06/07/2009 ASUS hardware monitoring software related ASUSTeK Computer Inc. -Support- Drivers and Download

AsIO.sys 03/08/2009 Asus PCProbe Utility ASUSTeK Computer Inc. -Support- Drivers and Download

yk62x64.sys 28/09/2009 Marvell Yukon networking Marvell - Support

mvxxmm.sys 25/12/2009 Marvell Aux NV Bridge DLL - related to mv91xx SCSI HD Controller http://www.marvell.com/support.html

dump_mvxxmm.sys 25/12/2009 and seeing as the is a dump driver generated this is a definate to update

mv91xx.sys 25/12/2009 Marvell Thor Windows Driver Marvell http://www.marvell.com/support.html

dump_mv91xx.sys 25/12/2009 again dump driver too so update
in particular the ones i highlighted above has/have known issues causing BSOD with win 7 so make sure you update or remove these
My System SpecsSystem Spec
01 Jan 2013   #5
Thyatira

Windows 7 Home Premium x64
 
 

Huh.

And just like that, I was able to successfully boot to the desktop.

To be more specific, I reinstalled my HDD. I ran Memtest - 7 passes with no errors. I was attempting a startup repair again before running a diagnostic on my HDD, and this time startup repair reported errors that it couldn't fix automatically. I let it do its Microsoft thing, then restarted. After a minute or so of hanging on the welcome screen, it finally fully loaded Windows.

Went ahead and updated all the drivers listed in your post except the Virtual Audio Cable driver and the two ASUS drivers. Also updated the bios for my MB. I looked through the Stop 0x124 thread you posted and followed each point, for the most part. Note - I updated the two Marvell drivers (mvxxmm.sys and mv91xx.sys) but was a bit confused about and wasn't sure what to do with the "dump" drivers you listed. Are they (the dump drivers) updated with the actual drivers? Anyway, I've had my system running for several hours now with around a dozen restarts, and I've had zero BSOD's so far. Attached is my SF Diagnostic file for good measure.

Thanks for all the help, Pauly! Still a bit confused about what the issue was (or is, but let's hope it was fixed). Perhaps my HDD cables were loose, or perhaps the startup repair fixed it. Holding off on Marking as Solved for now in case you see/think of something else that is wrong with my system or in case I get another BSOD in the coming hours/days.
My System SpecsSystem Spec
02 Jan 2013   #6
Pauly

Win7 Ultimate X64
 
 

You can ignore the drivers labeled dump_XXXXX i was pointing out that sometimes when a driver is faulty or causes a bsod your computer will may automatically create a driver named dump_"faulty driver name" thats why i wanted you to update those in particular. Everything sounds good to me and theres a good chance you resolved the issue but i would agree leave the thread open for several days until your satisfied then you can mark as solved.

Glad its going good for you i know how annoying BSODs can be i have suffered a few over the years
My System SpecsSystem Spec
Reply

 BSOD At Welcome Screen, error 0x000000F4




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
BSOD - Screen flickers and then Shuts Down, error 0x000000f4
Hi Guys, I've had an incredibly long day today trying to fix this issue for a laptop user. They get a blue screen of death after the screen flickers for a short while. The error report below was created on BlueScreenView, please have a look. I've installed updates, checked graphical drivers...
BSOD Help and Support
BSOD every few hours, even on login screen, 0x000000F4
As the title says, I am getting a BSOD every few hours, even when I haven't yet logged in, or use safe mode. The system hangs on the BSOD screen, doesn't restart after and doesn't actually save a proper dump file. I have tried changing the dump location to another drive and dump file type saved...
BSOD Help and Support
Blue Screen error 0x000000f4 at random intervals
Can anyone help? Normally explorer.exe crashes then the rest all follow. I attached the minidump.zip already
BSOD Help and Support
Blue screen 0x000000F4 error
Hello. I am getting this error in mu Clevo P170HM. It happened suddenly. I can work on my safe mode, in normal mode after 1minute I got blue screen and that error. I got eset antivirus. Info: -win 7 x64 HP -the original installed OS -full retail version -What is the age of system: 1 month...
BSOD Help and Support
Blue Screen of Death.... Error 0x000000F4
Okay. My friend bought a laptop Windows 7 home Premium. (HP) After playing with it instaling few stuf. We got this. (im only writing down the Technical code) *** STOP: 0x000000F4 (0x0000000000000003 , 0xFFFFFA80055E7B30 , 0xFFFFFA80055E7E10 , XFFFFF80002D8D240 If anymore info is needed...
Drivers


Our Sites

Site Links

About Us

Find 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 15:29.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App