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 after login

16 Apr 2011   #1

Windows 7 ultimate 32bit
 
 
BSOD after login

Just after login, when the desktop appears the computer BSOD. It happens every time.
What to do?

0: 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: c0000005, The exception code that was not handled
Arg2: 00000001, The address that the exception occurred at
Arg3: 8d527c3c, Exception Record Address
Arg4: 8d527820, Context Record Address

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP:
+19
00000001 ?? ???

EXCEPTION_RECORD: 8d527c3c -- (.exr 0xffffffff8d527c3c)
ExceptionAddress: 00000001
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000008
Parameter[1]: 00000001
Attempt to execute non-executable address 00000001

CONTEXT: 8d527820 -- (.cxr 0xffffffff8d527820)
eax=00000001 ebx=831725bc ecx=00000002 edx=00000000 esi=85bc8a70 edi=831725cc
eip=00000001 esp=8d527d04 ebp=8d527d50 iopl=0 nv up ei pl nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010202
00000001 ?? ???
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 0

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_PARAMETER1: 00000008

EXCEPTION_PARAMETER2: 00000001

WRITE_ADDRESS: GetPointerFromAddress: unable to read from 831a0718
Unable to read MiSystemVaType memory at 83180160
00000001

FOLLOWUP_IP:
+19
00000001 ?? ???

FAILED_INSTRUCTION_ADDRESS:
+19
00000001 ?? ???

BUGCHECK_STR: 0x7E

LAST_CONTROL_TRANSFER: from 830a603b to 00000001

STACK_TEXT:
WARNING: Frame IP not in any known module. Following frames may be wrong.
8d527d00 830a603b 00000002 00000000 85bc8a70 0x1
8d527d50 832469df 00000001 bbc34f64 00000000 nt!ExpWorkerThread+0x10d
8d527d90 830f81d9 830a5f2e 00000001 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19


STACK_COMMAND: kb

SYMBOL_NAME: ANALYSIS_INCONCLUSIVE

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME: Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP: 0

FAILURE_BUCKET_ID: 0x7E_BAD_IP_ANALYSIS_INCONCLUSIVE

BUCKET_ID: 0x7E_BAD_IP_ANALYSIS_INCONCLUSIVE

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

0: kd> .exr 0xffffffff8d527c3c
ExceptionAddress: 00000001
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000008
Parameter[1]: 00000001
Attempt to execute non-executable address 00000001
0: kd> .cxr 0xffffffff8d527820
eax=00000001 ebx=831725bc ecx=00000002 edx=00000000 esi=85bc8a70 edi=831725cc
eip=00000001 esp=8d527d04 ebp=8d527d50 iopl=0 nv up ei pl nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010202
00000001 ?? ???


My System SpecsSystem Spec
.

16 Apr 2011   #2

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by joelinho View Post
Just after login, when the desktop appears the computer BSOD. It happens every time.
What to do?

0: 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: c0000005, The exception code that was not handled
Arg2: 00000001, The address that the exception occurred at
Arg3: 8d527c3c, Exception Record Address
Arg4: 8d527820, Context Record Address

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP:
+19
00000001 ?? ???

EXCEPTION_RECORD: 8d527c3c -- (.exr 0xffffffff8d527c3c)
ExceptionAddress: 00000001
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000008
Parameter[1]: 00000001
Attempt to execute non-executable address 00000001

CONTEXT: 8d527820 -- (.cxr 0xffffffff8d527820)
eax=00000001 ebx=831725bc ecx=00000002 edx=00000000 esi=85bc8a70 edi=831725cc
eip=00000001 esp=8d527d04 ebp=8d527d50 iopl=0 nv up ei pl nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010202
00000001 ?? ???
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 0

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_PARAMETER1: 00000008

EXCEPTION_PARAMETER2: 00000001

WRITE_ADDRESS: GetPointerFromAddress: unable to read from 831a0718
Unable to read MiSystemVaType memory at 83180160
00000001

FOLLOWUP_IP:
+19
00000001 ?? ???

FAILED_INSTRUCTION_ADDRESS:
+19
00000001 ?? ???

BUGCHECK_STR: 0x7E

LAST_CONTROL_TRANSFER: from 830a603b to 00000001

STACK_TEXT:
WARNING: Frame IP not in any known module. Following frames may be wrong.
8d527d00 830a603b 00000002 00000000 85bc8a70 0x1
8d527d50 832469df 00000001 bbc34f64 00000000 nt!ExpWorkerThread+0x10d
8d527d90 830f81d9 830a5f2e 00000001 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19


STACK_COMMAND: kb

SYMBOL_NAME: ANALYSIS_INCONCLUSIVE

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME: Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP: 0

FAILURE_BUCKET_ID: 0x7E_BAD_IP_ANALYSIS_INCONCLUSIVE

BUCKET_ID: 0x7E_BAD_IP_ANALYSIS_INCONCLUSIVE

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

0: kd> .exr 0xffffffff8d527c3c
ExceptionAddress: 00000001
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000008
Parameter[1]: 00000001
Attempt to execute non-executable address 00000001
0: kd> .cxr 0xffffffff8d527820
eax=00000001 ebx=831725bc ecx=00000002 edx=00000000 esi=85bc8a70 edi=831725cc
eip=00000001 esp=8d527d04 ebp=8d527d50 iopl=0 nv up ei pl nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010202
00000001 ?? ???

Its a memory exception caused by an inconclusive driver. We need the DMP file to do analysis




To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.

The procedure:

* Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
* Zip up the copy.
* Attach the ZIP archive to your post using the "paperclip" (file attachments) button.



To ensure minidumps are enabled:

Go to Start, in the Search Box type: sysdm.cpl, press Enter.
Under the Advanced tab, click on the Startup and Recovery Settings... button.
Ensure that Automatically restart is unchecked.
Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
OK your way out.
Reboot if changes have been made.
My System SpecsSystem Spec
17 Apr 2011   #3

Windows 7 ultimate 32bit
 
 

Hi,

Thanks for the quick response. I really appreciate it.
There seems to be a couple of different BSODs going on. I have uploaded all the dumps I have so far.

Regards,
Joel
My System SpecsSystem Spec
.


Reply

 BSOD after login




Thread Tools



Similar help and support threads for2: BSOD after login
Thread Forum
!! Restored image of windows, now wont login, login service error!! General Discussion
BSOD after login, BSOD random while on Chrome.exe BSOD Help and Support
Solved Multiple user accounts, 1 auto login , how to login to another account General Discussion
Attempting to login to most websites results in login page refreshing. Browsers & Mail
BSOD upon login BSOD Help and Support
Solved BSOD during login BSOD Help and Support
BSOD at login BSOD Help and Support

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:29 PM.
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