lsass.exe

[blondie]

Has failed to initialize. It shows the windows logo, then it pops up like that (error code 0xc0000005.) I googled it, but the description of the problem was vague, so I need someone to tell me the stuff.

[wut]

Screeny ?

[blondie]

Lol, okay. You can't go to the part where you click on your name and type in your password. So no, no screeny. I pretty much described everything, seeing as the rest of the screen is black.

[Inf3cted]

Okay, So wait. What happened? I'm not getting it. Lol.

[luka102]

Take a pic with your camera

[atirox]

It works like this, Windows decided it hates you so it showed you a stop message, or BSOD. also, its not possible to get a screenie when NTOSKRNL.EXE isnt running, which is what the Stop error tells you.

What are the parameters of the error? you know, it says STOP 0x00000000 (0x????????, 0x????????, 0x????????, 0x????????). everything in the brackets are parameters, and i need to know these to actually help you save your system.

NTOSKRNL.EXE (and its brothers, NTKRNLMP.EXE, NTKRNLPA.EXE, and NTKRPAMP.EXE) is the actual heart of Microsoft's most loved and hated system, Windows NT. This includes its decendants, being Windows 2000, XP, Vista, and 7. This program is the brain of Windows. When it has a problem, it executes a Kernel Panic. This brings everything to a grinding halt, and spits out your stop error with some hexadecimal numbers. If you were in windows, completely logged in and using it, then it will also dump the memory. usually this is a kernel dump, but sometimes can be a register dump and sometimes even a memory dump, where it dumps the contents of the physical memory. If you werent in windows, that means that you just get the lovely blue screen with some hexadecimal numbers on it. If you werent in windows yet, this usually means that windows cant start, and therefore, safemode wont work. so dont bother trying.

[luka102]

It works like this, Windows decided it hates you so it showed you a stop message, or BSOD. also, its not possible to get a screenie when NTOSKRNL.EXE isnt running, which is what the Stop error tells you.

What are the parameters of the error? you know, it says STOP 0x00000000 (0x????????, 0x????????, 0x????????, 0x????????). everything in the brackets are parameters, and i need to know these to actually help you save your system.

NTOSKRNL.EXE (and its brothers, NTKRNLMP.EXE, NTKRNLPA.EXE, and NTKRPAMP.EXE) is the actual heart of Microsoft's most loved and hated system, Windows NT. This includes its decendants, being Windows 2000, XP, Vista, and 7. This program is the brain of Windows. When it has a problem, it executes a Kernel Panic. This brings everything to a grinding halt, and spits out your stop error with some hexadecimal numbers. If you were in windows, completely logged in and using it, then it will also dump the memory. usually this is a kernel dump, but sometimes can be a register dump and sometimes even a memory dump, where it dumps the contents of the physical memory. If you werent in windows, that means that you just get the lovely blue screen with some hexadecimal numbers on it. If you werent in windows yet, this usually means that windows cant start, and therefore, safemode wont work. so dont bother trying.

He's getting the bsod at the login screen

[blondie]

Fixed it. I should apply for tech crew.

[atirox]

If you'll notice VDominusV's second post, he cant get to the logon screen.

can we get this thread closed?