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: System lockup after login screen following BSOD

03 Sep 2012   #1

Windows 7 professional 64bit
 
 
System lockup after login screen following BSOD

Hi,

I had a BSOD two days ago coming out of standby and ever since the system locks up after reaching the desktop whilst trying to log in. Logging into safe mode works perfectly fine and also logging into the Ubuntu partion has no problems. I have run malware bytes and hard disk diagonistics and found no problems.

This leaves me to believe its a driver/software issue and I'm hoping someone can help narrow this down. Have attached SF zip.

My System SpecsSystem Spec
.

05 Sep 2012   #2

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium 64Bit
 
 

Welcome

Your dump does not give a probable cause, but I've seen some things

BSOD Analyze

Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 7A, {fffff6fc50073098, ffffffffc0000185, c61ef880, fffff8a00e613000}

*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+3717a )

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

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KERNEL_DATA_INPAGE_ERROR (7a)
The requested page of kernel data could not be read in.  Typically caused by
a bad block in the paging file or disk controller error. Also see
KERNEL_STACK_INPAGE_ERROR.
If the error status is 0xC000000E, 0xC000009C, 0xC000009D or 0xC0000185,
it means the disk subsystem has experienced a failure.
If the error status is 0xC000009A, then it means the request failed because
a filesystem failed to make forward progress.
Arguments:
Arg1: fffff6fc50073098, lock type that was held (value 1,2,3, or PTE address)
Arg2: ffffffffc0000185, error status (normally i/o status code)
Arg3: 00000000c61ef880, current process (virtual address for lock type 3, or PTE)
Arg4: fffff8a00e613000, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)

Debugging Details:
------------------


ERROR_CODE: (NTSTATUS) 0xc0000185 - The I/O device reported an I/O error.

DISK_HARDWARE_ERROR: There was error with disk hardware

BUGCHECK_STR:  0x7a_c0000185

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  svchost.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff8800b6ac1c0 -- (.trap 0xfffff8800b6ac1c0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa8007be4170 rbx=0000000000000000 rcx=fffffa80043c4720
rdx=fffffa8007be4171 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80003165990 rsp=fffff8800b6ac350 rbp=0000000000000080
 r8=fffffa8007be4170  r9=fffff8800b6ac188 r10=fffffa800417ae40
r11=fffff8800b6ac370 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
nt!MiRelocateImageAgain+0x48:
fffff800`03165990 f0480fba2e00    lock bts qword ptr [rsi],0 ds:00000000`00000000=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002efb542 to fffff80002e8e1c0

STACK_TEXT:  
fffff880`0b6abea8 fffff800`02efb542 : 00000000`0000007a fffff6fc`50073098 ffffffff`c0000185 00000000`c61ef880 : nt!KeBugCheckEx
fffff880`0b6abeb0 fffff800`02eb4fff : fffffa80`05473df0 fffff880`0b6ac020 fffff800`030c0600 fffffa80`05473df0 : nt! ?? ::FNODOBFM::`string'+0x3717a
fffff880`0b6abf90 fffff800`02e9b789 : 00000000`00000000 00000000`00000001 ffffffff`ffffffff 00000000`00000000 : nt!MiIssueHardFault+0x28b
fffff880`0b6ac060 fffff800`02e8c2ee : 00000000`00000001 fffff8a0`0e613000 00000000`00000000 ffffffff`ffffffff : nt!MmAccessFault+0x1399
fffff880`0b6ac1c0 fffff800`03165990 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
fffff880`0b6ac350 fffff800`0318664f : 00000000`00000004 00000000`00000080 00000000`01000000 00000000`01000000 : nt!MiRelocateImageAgain+0x48
fffff880`0b6ac3a0 fffff800`03165186 : fffff880`0b6ac5f0 fffff880`0b6ac840 fffff880`0b6ac698 fffff880`0b6ac5e8 : nt!MmCreateSection+0x2df
fffff880`0b6ac5a0 fffff800`032e7cc3 : 00000000`00000000 fffff8a0`0534b890 00000000`00000000 00000000`00000001 : nt!NtCreateSection+0x171
fffff880`0b6ac620 fffff800`032e8251 : 00000000`00000000 fffff8a0`0534b890 fffffa80`0544c0a0 fffff880`00000060 : nt!PfpFileBuildReadSupport+0x163
fffff880`0b6ac710 fffff800`032f036e : fffff8a0`00000000 fffff8a0`00000008 fffff8a0`0000012a fffff8a0`00000000 : nt!PfpPrefetchFilesTrickle+0x121
fffff880`0b6ac810 fffff800`032f0c47 : 00000000`00000000 fffff880`0b6acca0 fffff880`0b6aca08 fffff8a0`01f886a0 : nt!PfpPrefetchRequestPerform+0x30e
fffff880`0b6ac960 fffff800`032fd50e : fffff880`0b6aca08 00000000`00000001 fffffa80`0574c270 00000000`00000000 : nt!PfpPrefetchRequest+0x176
fffff880`0b6ac9d0 fffff800`03301d3a : 00000000`00000000 00000000`0000004f 00000000`00000000 fffff880`0b6acb01 : nt!PfSetSuperfetchInformation+0x1ad
fffff880`0b6acab0 fffff800`02e8d453 : fffffa80`04a3a7b0 00000000`00000000 fffffa80`040d30c0 00000000`00000001 : nt!NtSetSystemInformation+0xc8d
fffff880`0b6acc20 00000000`77b72a0a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`016bf988 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77b72a0a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+3717a
fffff800`02efb542 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+3717a

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4fa390f3

FAILURE_BUCKET_ID:  X64_0x7a_c0000185_nt!_??_::FNODOBFM::_string_+3717a

BUCKET_ID:  X64_0x7a_c0000185_nt!_??_::FNODOBFM::_string_+3717a

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

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KERNEL_DATA_INPAGE_ERROR (7a)
The requested page of kernel data could not be read in.  Typically caused by
a bad block in the paging file or disk controller error. Also see
KERNEL_STACK_INPAGE_ERROR.
If the error status is 0xC000000E, 0xC000009C, 0xC000009D or 0xC0000185,
it means the disk subsystem has experienced a failure.
If the error status is 0xC000009A, then it means the request failed because
a filesystem failed to make forward progress.
Arguments:
Arg1: fffff6fc50073098, lock type that was held (value 1,2,3, or PTE address)
Arg2: ffffffffc0000185, error status (normally i/o status code)
Arg3: 00000000c61ef880, current process (virtual address for lock type 3, or PTE)
Arg4: fffff8a00e613000, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)

Debugging Details:
------------------


ERROR_CODE: (NTSTATUS) 0xc0000185 - The I/O device reported an I/O error.

DISK_HARDWARE_ERROR: There was error with disk hardware

BUGCHECK_STR:  0x7a_c0000185

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  svchost.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff8800b6ac1c0 -- (.trap 0xfffff8800b6ac1c0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa8007be4170 rbx=0000000000000000 rcx=fffffa80043c4720
rdx=fffffa8007be4171 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80003165990 rsp=fffff8800b6ac350 rbp=0000000000000080
 r8=fffffa8007be4170  r9=fffff8800b6ac188 r10=fffffa800417ae40
r11=fffff8800b6ac370 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
nt!MiRelocateImageAgain+0x48:
fffff800`03165990 f0480fba2e00    lock bts qword ptr [rsi],0 ds:00000000`00000000=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002efb542 to fffff80002e8e1c0

STACK_TEXT:  
fffff880`0b6abea8 fffff800`02efb542 : 00000000`0000007a fffff6fc`50073098 ffffffff`c0000185 00000000`c61ef880 : nt!KeBugCheckEx
fffff880`0b6abeb0 fffff800`02eb4fff : fffffa80`05473df0 fffff880`0b6ac020 fffff800`030c0600 fffffa80`05473df0 : nt! ?? ::FNODOBFM::`string'+0x3717a
fffff880`0b6abf90 fffff800`02e9b789 : 00000000`00000000 00000000`00000001 ffffffff`ffffffff 00000000`00000000 : nt!MiIssueHardFault+0x28b
fffff880`0b6ac060 fffff800`02e8c2ee : 00000000`00000001 fffff8a0`0e613000 00000000`00000000 ffffffff`ffffffff : nt!MmAccessFault+0x1399
fffff880`0b6ac1c0 fffff800`03165990 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
fffff880`0b6ac350 fffff800`0318664f : 00000000`00000004 00000000`00000080 00000000`01000000 00000000`01000000 : nt!MiRelocateImageAgain+0x48
fffff880`0b6ac3a0 fffff800`03165186 : fffff880`0b6ac5f0 fffff880`0b6ac840 fffff880`0b6ac698 fffff880`0b6ac5e8 : nt!MmCreateSection+0x2df
fffff880`0b6ac5a0 fffff800`032e7cc3 : 00000000`00000000 fffff8a0`0534b890 00000000`00000000 00000000`00000001 : nt!NtCreateSection+0x171
fffff880`0b6ac620 fffff800`032e8251 : 00000000`00000000 fffff8a0`0534b890 fffffa80`0544c0a0 fffff880`00000060 : nt!PfpFileBuildReadSupport+0x163
fffff880`0b6ac710 fffff800`032f036e : fffff8a0`00000000 fffff8a0`00000008 fffff8a0`0000012a fffff8a0`00000000 : nt!PfpPrefetchFilesTrickle+0x121
fffff880`0b6ac810 fffff800`032f0c47 : 00000000`00000000 fffff880`0b6acca0 fffff880`0b6aca08 fffff8a0`01f886a0 : nt!PfpPrefetchRequestPerform+0x30e
fffff880`0b6ac960 fffff800`032fd50e : fffff880`0b6aca08 00000000`00000001 fffffa80`0574c270 00000000`00000000 : nt!PfpPrefetchRequest+0x176
fffff880`0b6ac9d0 fffff800`03301d3a : 00000000`00000000 00000000`0000004f 00000000`00000000 fffff880`0b6acb01 : nt!PfSetSuperfetchInformation+0x1ad
fffff880`0b6acab0 fffff800`02e8d453 : fffffa80`04a3a7b0 00000000`00000000 fffffa80`040d30c0 00000000`00000001 : nt!NtSetSystemInformation+0xc8d
fffff880`0b6acc20 00000000`77b72a0a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`016bf988 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77b72a0a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+3717a
fffff800`02efb542 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+3717a

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4fa390f3

FAILURE_BUCKET_ID:  X64_0x7a_c0000185_nt!_??_::FNODOBFM::_string_+3717a

BUCKET_ID:  X64_0x7a_c0000185_nt!_??_::FNODOBFM::_string_+3717a

Followup: MachineOwner
---------
BSOD Index STOP 0x0000007A: KERNEL_DATA_INPAGE_ERROR

1) Reseat the sata and power
2) Start with Disk Check for errors on your hard drive: Disk Check
3) Seatool for dos: SeaTools | Seagate Burn it in a blank cd. boot from the CD, click on "Accept", wait for it to finish detecting the drives, then in the upper left corner select "Basic Tests", then select "Long Test" and let it run.

You may also go to your hard drive manufacturer website and test your hard drive with the utility provided.

One Q: What antivirus are you using?
Download and install Malwarebytes : Malwarebytes Anti-Malware removes malware including viruses, spyware, worms and trojans, plus it protects your computer and do a full scan for malwares/viruses

Your BIOS version is very old. Please get an update for it from the manufacturers website.
Code:
BIOS Version/Date	Dell Inc. A14, 19/11/2008
Take your time to do the above and post back results

Edit: If you want to skip all the above, lets do a SFC scan for repairing any corrupted windows files:
SFC /SCANNOW Command - System File Checker

You can and enable driver verifier to rule out buggy drivers following instructions on the tut below:
Driver Verifier - Enable and Disable

Check if your system is stable with the verifier enabled
My System SpecsSystem Spec
Reply

 System lockup after login screen following BSOD





Thread Tools



Similar help and support threads for2: System lockup after login screen following BSOD
Thread Forum
Solved changed name in the operating system login screen Customization
Black screen after login, won't system restore Performance & Maintenance
Black screen after login, won't system restore General Discussion
Solved Full System Lockup, no error. BSOD Help and Support
Solved System/Windows 7 Lockup During DVD Playback Music, Pictures & Video
System lockup!! Gahhh 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 09:32 AM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33