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: Windows won't go past welcome screen!

04 Mar 2012   #41
writhziden

Windows 7 Home Premium 64 Bit
 
 

Excellent. Let us know how the diagnostics go.


My System SpecsSystem Spec
.
04 Mar 2012   #42
ElieJK90

Windows 7 Home Premium
 
 

Ok so these are the results of both short and long diagnostics test. I'm so disappointed.
My System SpecsSystem Spec
04 Mar 2012   #43
writhziden

Windows 7 Home Premium 64 Bit
 
 

Understandably, but at least now you know why the computer will not boot. You can backup your data through a repair or installation DVD, or even just through the Recovery Environment (Advanced Boot Options -> Repair Your Computer -> System Recovery Options -> Copy & Paste - in Windows Recovery Console)
My System SpecsSystem Spec
.

04 Mar 2012   #44
ElieJK90

Windows 7 Home Premium
 
 

So if I go for "Repair Your Computer" what will happen?
Please don't tell me I have to buy a new hard disk?
My System SpecsSystem Spec
04 Mar 2012   #45
writhziden

Windows 7 Home Premium 64 Bit
 
 

You will have to either buy a new hard disk or RMA your current one if it is still under warranty.

If you go to Repair Your Computer, you want to select System Image Recovery from the Recovery Environment. Then, when it says it did not find an image, cancel out of that dialog, hit next on the screen that remains after cancelling out of the dialog, and then select advanced. Then follow the tutorial for copying and pasting in the Windows Recovery Console starting from Step 2).
My System SpecsSystem Spec
04 Mar 2012   #46
ElieJK90

Windows 7 Home Premium
 
 

RMA?
My System SpecsSystem Spec
04 Mar 2012   #47
ElieJK90

Windows 7 Home Premium
 
 

Could it possibly be that the hard disk is not in its proper place? Should I still try to remove it and put it back in?
My System SpecsSystem Spec
04 Mar 2012   #48
writhziden

Windows 7 Home Premium 64 Bit
 
 

Quote   Quote: Originally Posted by ElieJK90 View Post
RMA?
Return Merchanidse Authorization (the manufacturer will issue a return for the device under warranty and provide a replacement; you may have to pay for shipping and handling costs or a small fee for the replacement).


Quote   Quote: Originally Posted by ElieJK90 View Post
Could it possibly be that the hard disk is not in its proper place? Should I still try to remove it and put it back in?
Yes, this is one of the first things I recommended trying. Your drive may not be properly connected to the system.

post #29


Quote   Quote: Originally Posted by writhziden View Post
Problem Devices:
Code:
Security Processor Loader Driver	ROOT\LEGACY_SPLDR\0000	This device is not present, is not working properly, or does not have all its drivers installed.
Code:
  1. Loading Dump File [D:\Kingston\BSODDmpFiles\ElieJK90\Windows_NT6_BSOD_jcgriff2\030312-24882-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506 Machine Name: Kernel base = 0xfffff800`03057000 PsLoadedModuleList = 0xfffff800`0329c670 Debug session time: Sat Mar 3 12:10:43.810 2012 (UTC - 7:00) System Uptime: 0 days 0:01:59.309 Loading Kernel Symbols ............................................................... ................................................................ ...................... Loading User Symbols Loading unloaded module list .... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck C4, {f6, 160, fffffa80067e8270, fffff880042305a9} Unable to load image \SystemRoot\system32\DRIVERS\SFEP.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for SFEP.sys *** ERROR: Module load completed but symbols could not be loaded for SFEP.sys Probably caused by : SFEP.sys ( SFEP+15a9 ) Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* DRIVER_VERIFIER_DETECTED_VIOLATION (c4) A device driver attempting to corrupt the system has been caught. This is because the driver was specified in the registry as being suspect (by the administrator) and the kernel has enabled substantial checking of this driver. If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA will be among the most commonly seen crashes. Arguments: Arg1: 00000000000000f6, Referencing user handle as KernelMode. Arg2: 0000000000000160, Handle value being referenced. Arg3: fffffa80067e8270, Address of the current process. Arg4: fffff880042305a9, Address inside the driver that is performing the incorrect reference. Debugging Details: ------------------ BUGCHECK_STR: 0xc4_f6 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP PROCESS_NAME: SPMgr.exe CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from fffff8000355d3dc to fffff800030d3c40 STACK_TEXT: fffff880`07248578 fffff800`0355d3dc : 00000000`000000c4 00000000`000000f6 00000000`00000160 fffffa80`067e8270 : nt!KeBugCheckEx fffff880`07248580 fffff800`03572ae4 : 00000000`00000160 fffffa80`067e8270 00000000`00000002 00000000`00000100 : nt!VerifierBugCheckIfAppropriate+0x3c fffff880`072485c0 fffff800`0332b210 : 00000000`00000000 fffff880`072487f0 00000000`00000000 fffff980`03dcef00 : nt!VfCheckUserHandle+0x1b4 fffff880`072486a0 fffff800`033ae375 : fffff880`07242000 fffff880`000f0001 00000000`00000000 00000000`00000200 : nt! ?? ::NNGAKEGL::`string'+0x212ce fffff880`07248770 fffff800`03572878 : 00000000`00000000 fffffa80`00000000 00000000`00000248 fffffa80`0671f488 : nt!ObReferenceObjectByHandle+0x25 fffff880`072487c0 fffff880`042305a9 : fffff980`0d584db0 00000000`0001c0fb fffff980`03dceff0 fffff980`03dceff0 : nt!VerifierObReferenceObjectByHandle+0x48 fffff880`07248810 fffff980`0d584db0 : 00000000`0001c0fb fffff980`03dceff0 fffff980`03dceff0 fffff880`07248850 : SFEP+0x15a9 fffff880`07248818 00000000`0001c0fb : fffff980`03dceff0 fffff980`03dceff0 fffff880`07248850 00000000`00000000 : 0xfffff980`0d584db0 fffff880`07248820 fffff980`03dceff0 : fffff980`03dceff0 fffff880`07248850 00000000`00000000 00000000`00000000 : 0x1c0fb fffff880`07248828 fffff980`03dceff0 : fffff880`07248850 00000000`00000000 00000000`00000000 fffff880`04230711 : 0xfffff980`03dceff0 fffff880`07248830 fffff880`07248850 : 00000000`00000000 00000000`00000000 fffff880`04230711 fffff980`0e002fb8 : 0xfffff980`03dceff0 fffff880`07248838 00000000`00000000 : 00000000`00000000 fffff880`04230711 fffff980`0e002fb8 fffffa80`0671f488 : 0xfffff880`07248850 STACK_COMMAND: kb FOLLOWUP_IP: SFEP+15a9 fffff880`042305a9 85c0 test eax,eax SYMBOL_STACK_INDEX: 6 SYMBOL_NAME: SFEP+15a9 FOLLOWUP_NAME: MachineOwner MODULE_NAME: SFEP IMAGE_NAME: SFEP.sys DEBUG_FLR_IMAGE_TIMESTAMP: 46b2beb9 FAILURE_BUCKET_ID: X64_0xc4_f6_VRF_SFEP+15a9 BUCKET_ID: X64_0xc4_f6_VRF_SFEP+15a9 Followup: MachineOwner ---------
  2. Loading Dump File [D:\Kingston\BSODDmpFiles\ElieJK90\Windows_NT6_BSOD_jcgriff2\030312-48422-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506 Machine Name: Kernel base = 0xfffff800`0305d000 PsLoadedModuleList = 0xfffff800`032a2670 Debug session time: Sat Mar 3 12:04:20.408 2012 (UTC - 7:00) System Uptime: 0 days 0:01:36.907 Loading Kernel Symbols ............................................................... ................................................................ .............. Loading User Symbols Loading unloaded module list .... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1000007E, {ffffffffc0000006, fffff8000315c2a3, fffff88005456698, fffff88005455ef0} Probably caused by : hardware_disk Followup: MachineOwner --------- 2: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e) This is a very common bugcheck. Usually the exception address pinpoints the driver/function that caused the problem. Always note this address as well as the link date of the driver/image that contains this address. Some common problems are exception code 0x80000003. This means a hard coded breakpoint or assertion was hit, but this system was booted /NODEBUG. This is not supposed to happen as developers should never have hardcoded breakpoints in retail code, but ... If this happens, make sure a debugger gets connected, and the system is booted /DEBUG. This will let us see why this breakpoint is happening. Arguments: Arg1: ffffffffc0000006, The exception code that was not handled Arg2: fffff8000315c2a3, The address that the exception occurred at Arg3: fffff88005456698, Exception Record Address Arg4: fffff88005455ef0, Context Record Address Debugging Details: ------------------ EXCEPTION_CODE: (NTSTATUS) 0xc0000006 - The instruction at 0x%p referenced memory at 0x%p. The required data was not placed into memory because of an I/O error status of 0x%x. FAULTING_IP: nt!XpressDecodeCreate+73 fffff800`0315c2a3 0fb702 movzx eax,word ptr [rdx] EXCEPTION_RECORD: fffff88005456698 -- (.exr 0xfffff88005456698) ExceptionAddress: fffff8000315c2a3 (nt!XpressDecodeCreate+0x0000000000000073) ExceptionCode: c0000006 (In-page I/O error) ExceptionFlags: 00000000 NumberParameters: 3 Parameter[0]: 0000000000000000 Parameter[1]: 00000000020d0000 Parameter[2]: 00000000c0000185 Inpage operation failed at 00000000020d0000, due to I/O error 00000000c0000185 CONTEXT: fffff88005455ef0 -- (.cxr 0xfffff88005455ef0) rax=0000000000000004 rbx=00000000020cfffd rcx=0000000000000004 rdx=00000000020d0000 rsi=fffff8a0027daf90 rdi=0000000000000001 rip=fffff8000315c2a3 rsp=fffff880054568d8 rbp=0000000000010000 r8=0000000000ce3f56 r9=fffff8a0027daf90 r10=00000000fffff000 r11=0000000000ce3af2 r12=00000000000a7d09 r13=fffff8a0027dd078 r14=0000000000000007 r15=00000000020cf3a4 iopl=0 nv up ei ng nz na po cy cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010287 nt!XpressDecodeCreate+0x73: fffff800`0315c2a3 0fb702 movzx eax,word ptr [rdx] ds:002b:00000000`020d0000=???? Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP PROCESS_NAME: System CURRENT_IRQL: 0 ERROR_CODE: (NTSTATUS) 0xc0000006 - The instruction at 0x%p referenced memory at 0x%p. The required data was not placed into memory because of an I/O error status of 0x%x. EXCEPTION_PARAMETER1: 0000000000000000 EXCEPTION_PARAMETER2: 00000000020d0000 EXCEPTION_PARAMETER3: 00000000c0000185 IO_ERROR: (NTSTATUS) 0xc0000185 - The I/O device reported an I/O error. BUGCHECK_STR: 0x7E EXCEPTION_STR: 0xc0000006_c0000185 FOLLOWUP_IP: +73 00000000`020d0000 ?? ??? FOLLOWUP_NAME: MachineOwner MODULE_NAME: hardware_disk IMAGE_NAME: hardware_disk DEBUG_FLR_IMAGE_TIMESTAMP: 0 STACK_COMMAND: kb FAILURE_BUCKET_ID: X64_0x7E_VRF_IMAGE_hardware_disk BUCKET_ID: X64_0x7E_VRF_IMAGE_hardware_disk Followup: MachineOwner ---------
  1. Update SFEP.SYS using the link I provided in post #10 ASAP. That is what is keeping you from starting Windows with Verifier running. See if that helps resolve the issue.
  2. Points to possible hard disk fault.
The second crash is what is preventing you from entering Windows without Verifier running. Use HD Diagnostic to determine your hard disk manufacturer and find the manufacturer diagnostics. Run all diagnostic tests available on your hard disk to determine whether it is failing. Also, make sure your hard disk is properly connected to your system by doing the following steps:
  1. Shut down and turn off the computer.
  2. Remove the AC adapter, and then remove the battery.
  3. Hold down the power button for 30 seconds to ensure all power is drained from the system (this closes the circuit so any remaining charge can traverse the system and dissipate).
  4. Open the panel covering the hard disk.
  5. Pull the hard disk out of the system and then replace it snugly by sliding the connector into the appropriate slot.
  6. Replace the panel to the computer.
  7. Replace the battery, and then replace the AC adapter.
  8. Turn on the system and see how it responds. Post back your results.
My System SpecsSystem Spec
04 Mar 2012   #49
ElieJK90

Windows 7 Home Premium
 
 

It better be not well connected. Otherwise I'm quite screwed.
Just so I understand 100%.. Reinstalling windows right now won't solve the problem right?
My System SpecsSystem Spec
04 Mar 2012   #50
writhziden

Windows 7 Home Premium 64 Bit
 
 

Quote   Quote: Originally Posted by ElieJK90 View Post
It better be not well connected. Otherwise I'm quite screwed.
Just so I understand 100%.. Reinstalling windows right now won't solve the problem right?
Right because it is a hardware problem. Also see my previous post since I edited it with the proper steps for checking the drive connection (I added my quote from when I previously suggested you check the drive connection; see the bold portion).

I also added a step in the steps for checking the connection. That step will make sure the system is safely free of all electricity before touching components.
My System SpecsSystem Spec
Reply

 Windows won't go past welcome screen!




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
Windows Never goes past the Welcome Screen
As the title says, I simply cannot log in when I run in normal mode. I have to use safe mode, with netwok connections to type this currenty. I let the laptop sit for about two weeks, there seemed to be no problems before hand, but when I tried to turn it on several days ago, it was no longer...
General Discussion
Windows Won't Get Past Start up Screen
Hello, I use Windows 7 64-bit and it wont get past the start-up screen. I would like to retrieve some personal files from my hard drive before i reinstall windows, is there any way i can do this without removing my hard drive and as a last resort could you guys link to some good videos/guides that...
General Discussion
can get past windows screen just prior to the login
i would like some info or pointers on what i can do to get this laptop working, i have rebooted it in safe mode and it attempts to start up, it get to the point where the windows 7 blue log on screen shows up but does not have the login or user account part but the theme shows up, any help i...
General Discussion
Windows 7 won't boot past the loading screen
Hi, My problem is that windows 7 wont get past the loading screen when its loading the OS. I have noticed that it will work when i have only 2GB(one stick) in but when i try to put all 8GB(4 sticks) in, it wont work. This same thing happened when i was trying to install windows 7 from a fresh...
Installation & Setup
Can't get past starting windows screen
I am running a Linux OS right now and am trying to install windows 7. I turn on he computer and run off the disc. It let's me load off the cd but can't get past the starting windows screen. Above the starting windows is a spot of color but no other graphic. What do I do from here?
Installation & Setup
HELP! Windows 7 will not boot up past loading screen!
Ok, so iv put this computer together, installed windows 7 Ultimate 32bit and i got it up and running perfect for like a day. The next morning i switched it on and was working good for couple of hours then it seemed like the whole computer started to slow down and i got a blue screen error. so i...
General Discussion


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 08:14.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App