BSOD after login, error 0x0000001E

[hypemaster]

Hi!

I'm getting this BSOD 4-5 seconds after logging in.
This is not the first time it happens but the last time I figured out how to fix it by myself.
I simply used the boot tool via F8 at booting. I selected boot with the last functioning configuration and it ran well for about a week without problems.
This time the trick is not working and I'm getting the BSOD again.

Can anyone help?

Thank you

 

[hypemaster]

I've installed just now BlueScreenView and that's what comes up:

022113-15756-01.dmp
21/02/2013 10:39:38
KMODE_EXCEPTION_NOT_HANDLED
0x0000001e	ffffffff`c0000005	
fffff880`03bbad80
00000000`00000000
00000000`00000000
ntoskrnl.exe
ntoskrnl.exe+75c40	NT Kernel & System	Microsoft® Windows® Operating System	Microsoft Corporation	6.1.7601.18044 (win7sp1_gdr.130104-1431)	x64	ntoskrnl.exe+75c40					C:\Windows\Minidump\022113-15756-01.dmp	4	15	7601	282.888

I'm wondering what happened to ntoskrnl.exe

 

[koolkat77]

Ntoskrnl is not the true cause of the crash.

Do you get BSOD-s in safe mode?

Start with testing Ram:

Take memtest. Run for 8 passes and test each stick in a know good slot for an additional 6 passes.

• http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

   Note

Pay close attention to part 3 of the tutorial in order to rule out the faulty stick.

   Information

Errors are sometimes found after 8 passes.

   Tip

Do this test overnight, before going to bed.

If Memtest86+ does not find any errors with ram run Windows Memory Diagnostics for 7-8 passes following its tutorial:

• http://www.sevenforums.com/tutorials/715-memory-diagnostics-tool.html

Then enable driver verifier and see if it catches any misbehaving drivers:

• Driver Verifier Enable/Disable

 

[hypemaster]

Thank you koolkat77.

After a "clean boot" and the selection of boot with the last functioning configuration under F8 the PC it's booting correctly.

I'll run Memtest anyway tonight and post results.

I'll keep you posted.

 

[koolkat77]

Please do.

And your crashes are very similar to this thread, I will post a summary of your BSOD-s (from the month of Feb) in a while.

Go through for reference:
http://www.sevenforums.com/bsod-hel...browse-button-accessing-network-resource.html

Here they are:

The following is for informational purposes only:

BSOD BUGCHECK SUMMARY

Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
Debug session time: Fri Jan  4 15:45:25.500 2013 (UTC + 6:00)
System Uptime: 0 days 17:46:22.705
*** WARNING: Unable to verify timestamp for iaStor.sys
*** ERROR: Module load completed but symbols could not be loaded for iaStor.sys
Probably caused by : iaStor.sys ( iaStor+50ceb )
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0x9088
PROCESS_NAME:  IAANTmon.exe
FAILURE_BUCKET_ID:  X64_0x9088_iaStor+50ceb
CPUID:        "Intel(R) Core(TM) i5 CPU         650  @ 3.20GHz"
MaxSpeed:     3200
CurrentSpeed: 3192
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
Debug session time: Fri Feb  1 13:13:17.501 2013 (UTC + 6:00)
System Uptime: [B]15 days 4:56:56.171[/B]
*** WARNING: Unable to verify timestamp for iaStor.sys
*** ERROR: Module load completed but symbols could not be loaded for iaStor.sys
Probably caused by : iaStor.sys ( iaStor+50ceb )
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0x9088
PROCESS_NAME:  IAANTmon.exe
FAILURE_BUCKET_ID:  X64_0x9088_iaStor+50ceb
CPUID:        "Intel(R) Core(TM) i5 CPU         650  @ 3.20GHz"
MaxSpeed:     3200
CurrentSpeed: 3192
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18044.amd64fre.win7sp1_gdr.130104-1431
Debug session time: Thu Feb 21 15:38:31.498 2013 (UTC + 6:00)
System Uptime: 0 days 0:01:21.981
Probably caused by : ksecdd.sys ( ksecdd!KsecProcessSecurityContext+293 )
BUGCHECK_STR:  0x1E_c0000005_R
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x1E_c0000005_R_ksecdd!KsecProcessSecurityContext+293
CPUID:        "Intel(R) Core(TM) i5 CPU         650  @ 3.20GHz"
MaxSpeed:     3200
CurrentSpeed: 3192
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18044.amd64fre.win7sp1_gdr.130104-1431
Debug session time: Thu Feb 21 22:11:28.935 2013 (UTC + 6:00)
System Uptime: 0 days 0:01:16.418
Probably caused by : ksecdd.sys ( ksecdd!KsecProcessSecurityContext+293 )
BUGCHECK_STR:  0x1E_c0000005_R
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x1E_c0000005_R_ksecdd!KsecProcessSecurityContext+293
CPUID:        "Intel(R) Core(TM) i5 CPU         650  @ 3.20GHz"
MaxSpeed:     3200
CurrentSpeed: 3192
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18044.amd64fre.win7sp1_gdr.130104-1431
Debug session time: Thu Feb 28 14:00:22.278 2013 (UTC + 6:00)
System Uptime: 0 days 0:03:52.387
Probably caused by : ksecdd.sys ( ksecdd!KsecProcessSecurityContext+293 )
BUGCHECK_STR:  0x1E_c0000005_R
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x1E_c0000005_R_ksecdd!KsecProcessSecurityContext+293
CPUID:        "Intel(R) Core(TM) i5 CPU         650  @ 3.20GHz"
MaxSpeed:     3200
CurrentSpeed: 3192
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18044.amd64fre.win7sp1_gdr.130104-1431
Debug session time: Thu Feb 28 14:01:58.368 2013 (UTC + 6:00)
System Uptime: 0 days 0:00:43.476
Probably caused by : ksecdd.sys ( ksecdd!KsecProcessSecurityContext+293 )
BUGCHECK_STR:  0x1E_c0000005_R
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x1E_c0000005_R_ksecdd!KsecProcessSecurityContext+293
CPUID:        "Intel(R) Core(TM) i5 CPU         650  @ 3.20GHz"
MaxSpeed:     3200
CurrentSpeed: 3192

k
Child-SP          RetAddr           Call Site
fffff880`07c0bcc8 fffff800`03d1036b nt!KeBugCheckEx
fffff880`07c0bcd0 fffff800`03cd1dd8 nt!KipFatalFilter+0x1b
fffff880`07c0bd10 fffff800`03ca9dcc nt! ?? ::FNODOBFM::`string'+0x83d
fffff880`07c0bd50 fffff800`03ca984d nt!_C_specific_handler+0x8c
fffff880`07c0bdc0 fffff800`03ca8625 nt!RtlpExecuteHandlerForException+0xd
fffff880`07c0bdf0 fffff800`03cb95b1 nt!RtlDispatchException+0x415
fffff880`07c0c4d0 fffff800`03c7e2c2 nt!KiDispatchException+0x135
fffff880`07c0cb70 fffff800`03c7ce3a nt!KiExceptionDispatch+0xc2
fffff880`07c0cd50 fffff880`015a76b3 nt!KiPageFault+0x23a
fffff880`07c0cee0 fffff880`015b76a6 ksecdd!KsecProcessSecurityContext+0x293
fffff880`07c0cfe0 fffff880`01854344 ksecdd!InitializeSecurityContextW+0x66
fffff880`07c0d040 fffff880`018551ce tcpip!WfpAlepCreateTokenFromLogonId+0x1c4
fffff880`07c0d160 fffff880`018540c2 tcpip!WfpAleCreateTokenFromLogonId+0x2e
fffff880`07c0d1e0 fffff880`01854735 tcpip!WfpAlepSetSecurity+0x282
fffff880`07c0d2b0 fffff880`01876050 tcpip!WfpAleProcessSecureSocketControl+0xa5
fffff880`07c0d440 fffff880`01875827 tcpip!TcpSetSockOptEndpoint+0x150
fffff880`07c0d540 fffff800`03c8a968 tcpip!TcpTlEndpointIoControlEndpointCalloutRoutine+0x107
fffff880`07c0d5a0 fffff880`018758b0 nt!KeExpandKernelStackAndCalloutEx+0xd8
fffff880`07c0d680 fffff880`01a13056 tcpip!TcpTlEndpointIoControlEndpoint+0x70
fffff880`07c0d6f0 fffff880`01a126e0 afd!WskProTLControlRequest+0x136
fffff880`07c0d780 fffff880`01a12afb afd!WskProControlSocketCore+0x110
fffff880`07c0d800 fffff880`085846c0 afd!WskProAPIControlSocket+0x9b
fffff880`07c0d870 fffff880`08583de6 mrxsmb!SmbWskSetSocketOptions+0x1f0
fffff880`07c0d930 fffff880`0857c082 mrxsmb!SmbWskInitiateAsynchronousConnect+0x1a6
fffff880`07c0da80 fffff880`085823a9 mrxsmb!RxCeInitiateConnectRequest+0x52
fffff880`07c0dab0 fffff880`08582ba5 mrxsmb!RxCeBuildConnectionOverMultipleTransports+0x659
fffff880`07c0dc40 fffff880`070f91b1 mrxsmb!RxCeInitiateConnection+0x151
fffff880`07c0dc80 fffff800`03f1f34a rdbss!RxpWorkerThreadDispatcher+0x1a1
fffff880`07c0dd40 fffff800`03c6f946 nt!PspSystemThreadStartup+0x5a
fffff880`07c0dd80 00000000`00000000 nt!KiStartSystemThread+0x16

 

[hypemaster]

Hi Guys,

I ran MemTest with no errors.

Please find the report attached.

I'll continue running the next suggested tests.

 

[hypemaster]

I just ran Memory Diagnostic tool and no errors came up.

I've just switched on Driver Verifier and i'll let you know if occours any BSOD or any error.

 

[koolkat77]

Hum. Did you get BSOD otherwise?

 

[hypemaster]

Not in the last 4 days and that's awesome
I'm continue checking because the last time the PC was ok for about 1 week after BSOD and then started again with the same problem.