Laptop blue Screens whenever I pick it up

YougotJEWDhard

Estimable
Nov 21, 2014
7
0
4,510
0
Running on windows 8.1.
I started having this problem a couple weeks ago. I constantly play WoW on this laptop i bought a year ago new for about a grand. I am at a dead end on options. I run on a Toshiba Satillite S55-A5279. 8g RAM, GT740M Nvidia card, i7 processor and 1terrabite HDD. I keep getting a critical process has died!
 

Alec Mowat

Honorable
Jan 8, 2014
109
0
10,660
11
Doesn't say much, csrss.exe looks like a Windows system file.

This ~might~ help, could be a corrupt profile.
http://blog.vilmatech.com/csrss-exe-fix-csrss-exe-problems/

Open CMD as administrator and run "sfc /scannow"
Run Maleware Bytes and verify there's no virus.

I'd check your RAM and HD for errors. Use HD tuner for the harddrive, run Memtest86 and verify that the RAM is OK. Windows might be corrupt from a dying harddrive or bad RAM.
 

Alec Mowat

Honorable
Jan 8, 2014
109
0
10,660
11
CRITICAL_PROCESS_DIED (ef)
A critical system process died
Arguments:
Arg1: ffffe00102985900, Process object or thread object
Arg2: 0000000000000000, If this is 0, a process died. If this is 1, a thread died.
Arg3: 0000000000000000
Arg4: 0000000000000000

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

----- ETW minidump data unavailable-----

PROCESS_OBJECT: ffffe00102985900

IMAGE_NAME: csrss.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 0

MODULE_NAME: csrss

FAULTING_MODULE: 0000000000000000

PROCESS_NAME: csrss.exe

EXCEPTION_CODE: (NTSTATUS) 0x18ec8880 - <Unable to get error code text>

BUGCHECK_STR: 0xEF_18ec8880

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

CURRENT_IRQL: 0

ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre

STACK_TEXT:
ffffd000`21865dc8 fffff802`c2627dd0 : 00000000`000000ef ffffe001`02985900 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
ffffd000`21865dd0 fffff802`c254779c : ffffe001`02985900 ffffe001`18ec8ba0 00000000`00000001 00000000`00000002 : nt!PspCatchCriticalBreak+0xa4
ffffd000`21865e10 fffff802`c23b2c11 : ffffe001`02985900 ffffe001`18ec8ba0 ffffe001`02985900 ffffe001`02985900 : nt! ?? ::NNGAKEGL::`string'+0xba4c
ffffd000`21865e70 fffff802`c23b299e : ffffffff`ffffffff ffffe001`02985900 ffffe001`02985900 ffffe001`18ec8880 : nt!PspTerminateProcess+0xe5
ffffd000`21865eb0 fffff802`c21679b3 : ffffe001`02985900 ffffe001`18ec8880 ffffd000`21865fa0 ffffd000`21866b00 : nt!NtTerminateProcess+0x9e
ffffd000`21865f20 fffff802`c215fe00 : fffff802`c21a7b83 ffffd000`21866a58 ffffd000`21866a58 ffffd000`21866b00 : nt!KiSystemServiceCopyEnd+0x13
ffffd000`218660b8 fffff802`c21a7b83 : ffffd000`21866a58 ffffd000`21866a58 ffffd000`21866b00 0000003b`25441040 : nt!KiServiceLinkage
ffffd000`218660c0 fffff802`c2167dc2 : ffffd000`218669c0 0000003b`25440f98 00000000`c0000016 ffffe001`02985de8 : nt! ?? ::FNODOBFM::`string'+0x3b4d3
ffffd000`21866920 fffff802`c2166514 : 00000000`00000000 ffffe000`fcf20f50 00000000`00000001 ffffd000`21866b00 : nt!KiExceptionDispatch+0xc2
ffffd000`21866b00 00007ffe`161b3e80 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x214
0000003b`25440fa0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffe`161b3e80


STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

IMAGE_VERSION:

FAILURE_BUCKET_ID: 0xEF_18ec8880_IMAGE_csrss.exe

BUCKET_ID: 0xEF_18ec8880_IMAGE_csrss.exe

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0xef_18ec8880_image_csrss.exe

FAILURE_ID_HASH: {525aec98-2b98-4e55-1724-dce349dd8699}

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

2: kd> lmvm csrss
start end module name
 

Alec Mowat

Honorable
Jan 8, 2014
109
0
10,660
11
Doesn't say much, csrss.exe looks like a Windows system file.

This ~might~ help, could be a corrupt profile.
http://blog.vilmatech.com/csrss-exe-fix-csrss-exe-problems/

Open CMD as administrator and run "sfc /scannow"
Run Maleware Bytes and verify there's no virus.

I'd check your RAM and HD for errors. Use HD tuner for the harddrive, run Memtest86 and verify that the RAM is OK. Windows might be corrupt from a dying harddrive or bad RAM.
 

Alec Mowat

Honorable
Jan 8, 2014
109
0
10,660
11
2014-11-21 01:47:28, Info CSI 0000085e [SR] Verify and Repair Transaction completed. All files and registry keys listed in this transaction have been successfully repaired

It did find an issue.

I'd run
chkdsk C: /F

And reboot

I'd actually check your hardware at this point as well, could be a bad harddrive.
 
Thread starter Similar threads Forum Replies Date
Chocket Laptop Tech Support 2
akaishinobi20 Laptop Tech Support 2
T Laptop Tech Support 1
A Laptop Tech Support 0
F Laptop Tech Support 2
S Laptop Tech Support 1
J Laptop Tech Support 4
John21903 Laptop Tech Support 2
S Laptop Tech Support 0
plasmadiver Laptop Tech Support 0
M Laptop Tech Support 1
J Laptop Tech Support 1
Sérgio Ferreira Laptop Tech Support 0
S Laptop Tech Support 0
fughyumi Laptop Tech Support 2
M Laptop Tech Support 0
B Laptop Tech Support 0
H Laptop Tech Support 8
D Laptop Tech Support 3
Evident10 Laptop Tech Support 0

ASK THE COMMUNITY