Computer crashes when I try to log in

Arcanum · 01-25-2012, 07:28 PM

Like the thread title says, only it's not consistent. It has happened 3 times (with the 3rd being moments ago) so far, but with no rhyme or reason that I can see. The first time was a month or so ago, and the second was about a week and a half ago. The screen just flashes to the blue screen (hopefully not of death

) for a few seconds, and then my computer reboots. What's weird is that the first time this happened the blue screen was normal, but the 2nd and 3rd times the screen was dimmed, so I could barely make out what was on the screen. And the screen is only there for a few seconds, so I can't even make out what it's trying to tell me went wrong.

So has anyone heard of this before, or know what might be wrong? I'm running Windows 7 (64-bit I believe), and my rig is only about a year old. If you need extra details let me know.

Japan · 01-25-2012, 10:57 PM

You might want to get all the pertinent information off the BSOD first. Without that you'd probably have to go digging for the file dump and since it doesn't seem to be a constant issue its probably not worth it.

I'd suggest turning off auto-restart on crash and writing down the information the next time it crashes. Here's how you do that.

click the start icon in the lower left of your task bar

right click on "Computer"

Click on "Properties"

Click on "Advanced System Settings" (It will be located on the left side column of the window)

A new window will pop up. Click on The Startup and Recovery settings button

Uncheck the option to Automatically Restart.

The next time it crashes you'll be able to get the important info from the BSOD without it auto rebooting. Specifically you're looking at the friendly error name. (Meaning it uses words instead of a string of unintelligible numbers and letters.)

It will look something (not necessarily exactly) like this.

DRIVER_IRQI_NOT_LESS_OR_EQUAL

notice its in all caps and has dashes.

The next little bit of info is window's helpful tips. These are pretty awesome and don't afraid of anything. (They will probably tell you to reset, or go buy a pony, or some shit.)

After that helpful info is the technical info section. This is pretty important. The first bit of info will give you the windows stop code in hexadecimal format. This is good to know since it can help you find out exactly what killed your computer and caused it to go apeshit.

Right under the stop code will be any drivers that caused the crash. This too is very useful. If its a particular driver that's causing your issue then you can reinstall or remove it to fix the problem.

But yeah, get that blue screen info and you'll be well on your way to resolving the issue.

EDIT: I should have probably made a "barrel roll" reference somewhere in this post. I mean that ship has left port and all, but I'm pretty bummed out about it.

Arcanum · 01-29-2012, 09:33 PM

Soo it happened again. Here's the crap that I wrote down:

PAGE_FAULT_IN_NONPAGED_AREA

Blah blah check recently installed hardware/software. If this persists disable BIOS memory stuff (caching, shadowing)

***STOP: 0X00000050 (0xFFFFFA8007FDD000, 0x0000000000000000, 0xFFFFF80002ED36BA, 0x0000000000000000)

--

So the line about checking hardware/software made me realize this only started happening after I replaced my shitty mouse with a razer mouse that my brother had but wasn't using any more. Gonna go google-fu that, and redownload some drivers. If there's anything anyone can divine from the above, let me know.

Japan · 01-29-2012, 11:13 PM

I'd try re-seating the ram and see if you still get the same problem. One of your RAM sticks might be bad, but it will be hard to pinpoint it since it's an intermittent fault. It could also be your motherboard, in which case it's pretty much hasta la vista.

(Also I think some anti-virus software can cause this. Try uninstalling norton if you have it.)

(Also Also update all your drivers and mobo bios too, if your bios is out of date or something it could be an easy fix.)

Arcanum · 02-02-2012, 06:37 PM

So it wasn't the mouse drivers causing it, since it happened again. Only this time it was different. First was a bluish-teal screen (not the regular blue & white) that had the following on it:

***STOP: 0x0000007E (0xFFFFFFFFC000000, 0x0000000000000000, 0xFFFFF880035CE428, 0xFFFFF880035CDC80)

Also had some text about the BIOS, and ensuring my computer had enough memory.

Then, after rebooting from that screen, I was treated with a regular blue screen with the same kind of text as above and this:

***STOP: 0x0000007E (0xFFFFFFFFC0000005, 0x0000000000000000, 0xFFFFF8800339A428, 0xFFFFF88003399C80)

There was none of that "CAPS_STUFF" on either of the screens. Gonna update my BIOS later tonight, since I'm 99.99999999999% sure it hasn't been updated since this rig was built. (I haven't re-seated my RAM yet either). Also I'm using AVG, not Norton.

Japan · 02-02-2012, 08:52 PM

It really could just be a dying motherboard. Sounds like one or more of the memory sockets is going bad for some reason.

Arcanum · 02-03-2012, 03:58 PM

Well every time it happens, it's when the computer is coming out of sleep mode and it will crash while at the user select screen (or when typing in a password). Otherwise it runs just fine as far as I can tell.

Japan · 02-04-2012, 12:33 AM

Well if you've got another computer or a friend willing to let you troubleshoot with his I'd suggest testing the RAM you have by putting it into a known good mobo. If the problem transfers to the new comp you know it's your ram, if it doesn't it would suggest your motherboard is at fault.

01-25-2012, 07:28 PM	#1
Arcanum Strike the Earth! Join Date: Nov 2007 Location: Canada Posts: 3,185	Computer crashes when I try to log in Like the thread title says, only it's not consistent. It has happened 3 times (with the 3rd being moments ago) so far, but with no rhyme or reason that I can see. The first time was a month or so ago, and the second was about a week and a half ago. The screen just flashes to the blue screen (hopefully not of death ) for a few seconds, and then my computer reboots. What's weird is that the first time this happened the blue screen was normal, but the 2nd and 3rd times the screen was dimmed, so I could barely make out what was on the screen. And the screen is only there for a few seconds, so I can't even make out what it's trying to tell me went wrong. So has anyone heard of this before, or know what might be wrong? I'm running Windows 7 (64-bit I believe), and my rig is only about a year old. If you need extra details let me know. __________________ POS Almighty has spoken.

01-25-2012, 10:57 PM	#2
Japan Sent to the cornfield Join Date: Sep 2007 Location: Myself Posts: 212	You might want to get all the pertinent information off the BSOD first. Without that you'd probably have to go digging for the file dump and since it doesn't seem to be a constant issue its probably not worth it. I'd suggest turning off auto-restart on crash and writing down the information the next time it crashes. Here's how you do that. click the start icon in the lower left of your task bar right click on "Computer" Click on "Properties" Click on "Advanced System Settings" (It will be located on the left side column of the window) A new window will pop up. Click on The Startup and Recovery settings button Uncheck the option to Automatically Restart. The next time it crashes you'll be able to get the important info from the BSOD without it auto rebooting. Specifically you're looking at the friendly error name. (Meaning it uses words instead of a string of unintelligible numbers and letters.) It will look something (not necessarily exactly) like this. DRIVER_IRQI_NOT_LESS_OR_EQUAL notice its in all caps and has dashes. The next little bit of info is window's helpful tips. These are pretty awesome and don't afraid of anything. (They will probably tell you to reset, or go buy a pony, or some shit.) After that helpful info is the technical info section. This is pretty important. The first bit of info will give you the windows stop code in hexadecimal format. This is good to know since it can help you find out exactly what killed your computer and caused it to go apeshit. Right under the stop code will be any drivers that caused the crash. This too is very useful. If its a particular driver that's causing your issue then you can reinstall or remove it to fix the problem. But yeah, get that blue screen info and you'll be well on your way to resolving the issue. EDIT: I should have probably made a "barrel roll" reference somewhere in this post. I mean that ship has left port and all, but I'm pretty bummed out about it. Last edited by Japan; 01-25-2012 at 11:08 PM.

01-29-2012, 09:33 PM	#3
Arcanum Strike the Earth! Join Date: Nov 2007 Location: Canada Posts: 3,185	Soo it happened again. Here's the crap that I wrote down: PAGE_FAULT_IN_NONPAGED_AREA Blah blah check recently installed hardware/software. If this persists disable BIOS memory stuff (caching, shadowing) ***STOP: 0X00000050 (0xFFFFFA8007FDD000, 0x0000000000000000, 0xFFFFF80002ED36BA, 0x0000000000000000) -- So the line about checking hardware/software made me realize this only started happening after I replaced my shitty mouse with a razer mouse that my brother had but wasn't using any more. Gonna go google-fu that, and redownload some drivers. If there's anything anyone can divine from the above, let me know. __________________ POS Almighty has spoken.

01-29-2012, 11:13 PM	#4
Japan Sent to the cornfield Join Date: Sep 2007 Location: Myself Posts: 212	I'd try re-seating the ram and see if you still get the same problem. One of your RAM sticks might be bad, but it will be hard to pinpoint it since it's an intermittent fault. It could also be your motherboard, in which case it's pretty much hasta la vista. (Also I think some anti-virus software can cause this. Try uninstalling norton if you have it.) (Also Also update all your drivers and mobo bios too, if your bios is out of date or something it could be an easy fix.) Last edited by Japan; 01-29-2012 at 11:15 PM.

02-02-2012, 06:37 PM	#5
Arcanum Strike the Earth! Join Date: Nov 2007 Location: Canada Posts: 3,185	So it wasn't the mouse drivers causing it, since it happened again. Only this time it was different. First was a bluish-teal screen (not the regular blue & white) that had the following on it: *STOP: 0x0000007E (0xFFFFFFFFC000000, 0x0000000000000000, 0xFFFFF880035CE428, 0xFFFFF880035CDC80) Also had some text about the BIOS, and ensuring my computer had enough memory. Then, after rebooting from that screen, I was treated with a regular blue screen with the same kind of text as above and this: *STOP: 0x0000007E (0xFFFFFFFFC0000005, 0x0000000000000000, 0xFFFFF8800339A428, 0xFFFFF88003399C80) There was none of that "CAPS_STUFF" on either of the screens. Gonna update my BIOS later tonight, since I'm 99.99999999999% sure it hasn't been updated since this rig was built. (I haven't re-seated my RAM yet either). Also I'm using AVG, not Norton. __________________ POS Almighty has spoken.

02-02-2012, 08:52 PM	#6
Japan Sent to the cornfield Join Date: Sep 2007 Location: Myself Posts: 212	It really could just be a dying motherboard. Sounds like one or more of the memory sockets is going bad for some reason.

02-03-2012, 03:58 PM	#7
Arcanum Strike the Earth! Join Date: Nov 2007 Location: Canada Posts: 3,185	Well every time it happens, it's when the computer is coming out of sleep mode and it will crash while at the user select screen (or when typing in a password). Otherwise it runs just fine as far as I can tell. __________________ POS Almighty has spoken.

02-04-2012, 12:33 AM	#8
Japan Sent to the cornfield Join Date: Sep 2007 Location: Myself Posts: 212	Well if you've got another computer or a friend willing to let you troubleshoot with his I'd suggest testing the RAM you have by putting it into a known good mobo. If the problem transfers to the new comp you know it's your ram, if it doesn't it would suggest your motherboard is at fault.