|
My girlfriends computer was blue screening repeatedly, so I tested the HD and reinstalled windows fresh after backing her stuff up with an external drive reader. After installing windows, and the MS Office Suite, I had it run Windows Updates. Upon the restart post updating it was BSODing again. I was able to get it to boot into safe mode twice, and regular mode once. In the 7 Recover Console thing, all the restore points created by the system were corrupt so I couldn't do a system restore, and system repair did nothing. I used WinDBG to check the dump file, and its saying that the kernel is the problem, and smss, so I'm leaning toward a RAM issue. I've posted the DMP analysis. Any other ideas? ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* WINLOGON_FATAL_ERROR (c000021a) The Winlogon process terminated unexpectedly. Arguments: Arg1: fffff8a0001367a0, String that identifies the problem. Arg2: 0000000000000000, Error Code. Arg3: ffffffffc0000001 Arg4: 0000000000100448 Debugging Details: ------------------ ERROR_CODE: (NTSTATUS) 0xc000021a - {Fatal System Error} The %hs system process terminated unexpectedly with a status of 0x%08x (0x%08x 0x%08x). The system has been shut down. EXCEPTION_CODE: (NTSTATUS) 0xc000021a - {Fatal System Error} The %hs system process terminated unexpectedly with a status of 0x%08x (0x%08x 0x%08x). The system has been shut down. EXCEPTION_PARAMETER1: fffff8a0001367a0 EXCEPTION_PARAMETER2: 0000000000000000 EXCEPTION_PARAMETER3: ffffffffc0000001 EXCEPTION_PARAMETER4: 100448 ADDITIONAL_DEBUG_TEXT: initial session process or BUGCHECK_STR: 0xc000021a_Session_0_Terminated_PoShutdown DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT PROCESS_NAME: smss.exe CURRENT_IRQL: 0 ANALYSIS_VERSION: 6.3.9600.17029 (debuggers(dbg).140219-1702) amd64fre LAST_CONTROL_TRANSFER: from fffff80002cf7a5e to fffff8000289d640 STACK_TEXT: fffff880`0377d4e8 fffff800`02cf7a5e : 00000000`0000004c 00000000`c000021a fffff880`0377d608 fffffa80`032e7b50 : nt!KeBugCheckEx fffff880`0377d4f0 fffff800`02ae4391 : fffffa80`022a5936 fffff880`0377dca0 00000000`00000100 fffffa80`022a6220 : nt!PoShutdownBugCheck+0xae fffff880`0377d570 fffff800`028ea204 : 00000000`00000000 00000000`00000004 00000000`00000000 00000000`004ef801 : nt!ExpSystemErrorHandler2+0x5e1 fffff880`0377d7a0 fffff800`02cca6c1 : 00000000`c000021a 00000000`00000004 00000000`00000001 fffff880`0377db58 : nt!ExpSystemErrorHandler+0xd4 fffff880`0377d7e0 fffff800`02ccc443 : 00000000`c000021a fffffa80`00000004 fffff8a0`00000001 fffff880`0377db58 : nt!ExpRaiseHardError+0xe1 fffff880`0377db10 fffff800`0289c8d3 : fffffa80`03345b60 00000000`00000001 00000000`004ef898 fffff800`02b94a34 : nt!NtRaiseHardError+0x1a1 fffff880`0377dbb0 00000000`76d1264a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 00000000`004ef878 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76d1264a STACK_COMMAND: kb FOLLOWUP_IP: nt!ExpSystemErrorHandler2+5e1 fffff800`02ae4391 cc int 3 SYMBOL_STACK_INDEX: 2 SYMBOL_NAME: nt!ExpSystemErrorHandler2+5e1 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4ce7951a IMAGE_VERSION: 6.1.7601.17514 FAILURE_BUCKET_ID: X64_0xc000021a_Session_0_Terminated_PoShutdown_nt!ExpSystemErrorHandler2+5e1 BUCKET_ID: X64_0xc000021a_Session_0_Terminated_PoShutdown_nt!ExpSystemErrorHandler2+5e1 ANALYSIS_SOURCE: KM FAILURE_ID_HASH_STRING: km:x64_0xc000021a_session_0_terminated_poshutdown_nt!expsystemerrorhandler2+5e1 FAILURE_ID_HASH: {0e0fd5ed-a2be-0c18-e0be-c2719d2ed362}
|
#
?
Aug 3, 2014 14:43
|
|
|
|
| # ? May 6, 2024 16:44 |
|
|
I think its more likely to be a bad harddrive than RAM, but you can easily test the RAM from a Memtest86+ boot drive. Please post your system specs using the template in the sticky Rules thread if you need further help.
|
|
#
?
Aug 3, 2014 15:35
|
|
|
Sorry, It's a Toshiba Satellite L305D-S5934. I installed Windows 7 Enterprise x64. I replaced the hard drive as well, so it's unlikely to be that. Though I could test the one I put in at work tomorrow. Laptop specs: AMD Turion Dual Core. Looks like it has 3 gigs of ram, seems low. Also Memtest is claiming that the RAM in each slot is a different size and brand. 1024 Qimonda in slot 0 and 2048 Samsung M4 in slot 1. That's weird. edit: Memtest Passed. I suppose I'll test the drive I put in tomorrow. McSpankWich fucked around with this message at 01:35 on Aug 4, 2014 |
|
#
?
Aug 4, 2014 00:47
|
|
|
Sounds more like a hd issue to me as well. Did you do multiple memtest passes? I've had unstable memory pass for a few runs then fail then pass. Could be other hardware issues as well especially if it was dropped recently.
|
|
#
?
Aug 4, 2014 04:38
|
|
|
Well I put a third hard drive in the machine today and reinstalled windows again. It's doing windows updates now. Hopefully this time when it's finished it won't blue screen. The hard drive I took out passed both a quick and an extended test. Is it normal for the RAM to be two separate sizes and manufacturers like that? I always thought they needed to be the same size edit: Welp, BSOD again after the updates. Is it possible that one of the updates is causing it? I literally installed nothing on the machine before doing doing them and it failed again edit2: Turns out the BIOS version that shipped on this model Satellite doesn't support Windows 7! Should be fine after I flash the BIOS. McSpankWich fucked around with this message at 18:15 on Aug 4, 2014 |
|
#
?
Aug 4, 2014 15:26
|
|
|
McSpankWich posted:Is it normal for the RAM to be two separate sizes and manufacturers like that? I always thought they needed to be the same size
|
|
#
?
Aug 4, 2014 22:08
|
|
|
|
| # ? May 6, 2024 16:44 |
|
|
Yea that's what I thought, anyway, the BIOS update fixed the issue and everything is fine now. Thanks for all your help!
|
|
#
?
Aug 5, 2014 01:49
|
|