• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Blue Screens of Death

Octavarium

Junior Member
So, I've been enjoying the new computer I recently built. Unfortunately, it has some major problems. Like a lot of blue screens of death.

Here's the lowdown - What usually happens is that I'll be running 3 or so programs (Pretty much always AIM, iTunes, and Opera with 2-3 tabs), and then they stop responding. Not completely, because I can still minimize, maximize, etc, but I can't interact with them. No typing, link-clicking, closing, or anything. After 30 or so seconds, the computer stops responding altogether.

Then it's crash time for me. The screen goes all blue (duh) and then shows a whole bunch of numbers and letters I can't quite think of. It stops at the bottom for half of a second, where it says "Beginning physical memory dump" before automatically restarting, disk checking, and everything.

I know overheating can cause this problem. I originally thought so (I had my CPU and GPU overclocked), so I put them back at stock speeds. It still happens, albeit less frequently. I also know stuff like having your RAM seated wrong, etc. can cause the problem. I recently went in my computer to make sure everything was hooked up (and put in) right, and it all was. Still happens. So, can anyone tell me what might be causing the problem? And if so, what can be done to fix it? I really don't want to reformat/repartition my hard drive, because I have a lot of games and such on there (They're legal, but they're from Direct2Drive), and don't want to go through the crap of doing that again. Thanks in advance.
 
If you can get into Windows long enough to do this, follow these instructions to keep your computer from automatically rebooting when it gets an errors so that you can actually see what the error is. Knowing the error code can often lead to the cause of the problem.

Right-click on the My Computer icon on your Desktop.
Left-click on Properties.
In the System Properties window, click on the Advanced tab.
Click on the Settings button under the "Startup and Recovery" section.
Remove the check from the box next to "Automatically restart".
Click OK twice.


After you do this, the next time you get a blues creen error, the error will stay on the screen until you physically restart the computer. When you get another blue screen, make note of the section immediately after STOP: at the top of the screen (the first set of "0x000000.." numbers and the error message after the rest of the groups of numbers are primarily what we will need to know).
 
ive had the same problem with my old old computer...if i remember correctly we fixed it buy formatting it, then getting ALL the updates but then again that was a crappy comp, what are you system specs?
 
Okay, I finally got one of the errors, and this is what I got.

STOP: c000021a {Fatal System Error}
The Windows SubSystem system process terminated unexpectedly with a status of 0x
x0000006 (ox75b92f1a 0x0110fabc).

The system has been shut down.



I had NVFirewall, but I uninstalled it.

My specs are -

AMD 3500
eVga 7800GT
2Gb GeiL RAM
Western Digital 80Gb HDDs (x2)
Asus A8N5X Mobo

I have the HDDs in RAID 0, could that be a problem?

Also, is there a way I could make the hard drives run in separate partitions so that I can put all of my games and such on one before reformatting the other, then switching them and doing the same? Because I really don't want to have to reinstall everything, especially my downloaded movies. Thanks in advance, once again.
 
Run Memtest overnight to make sure it's the problem.

Are you OC'd?

Fern

EDIT: I meant to say, run memtest overnight to make sure ram's not the problem.
 
Well, I finally got around to running Memtest.

I ran it all night, it got about 4000% coverage on each of them (I had to run two programs of it), 0 errors.

Are there any other possible problems?
 
I've seen a few cases of the anig worm causing winlogon.exe to fail recently.
To check for the anig worm, go to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon and look for NTgina.dll
 
Well, sorry for being late.

I searched for it, couldn't find it, used the search feature in Regedit, still couldn't find it.

Should I just get some better cooling? My friend still insists that's what's causing the problem.
 
-get a tempurature monitoring program and check your temps
-what psu do you have? Need complete specs!
-does your computer also crash during prime 95?
-HAve you tried reinstalling windows?

 
Google c000021a and see what comes up. It seems there are programs that could be causing this error for you. I'd suggest spyware/virus scans and uninstalling programs that are suspect.
 
Originally posted by: Octavarium
So, I've been enjoying the new computer I recently built. Unfortunately, it has some major problems. Like a lot of blue screens of death.

Here's the lowdown - What usually happens is that I'll be running 3 or so programs (Pretty much always AIM, iTunes, and Opera with 2-3 tabs), and then they stop responding. Not completely, because I can still minimize, maximize, etc, but I can't interact with them. No typing, link-clicking, closing, or anything. After 30 or so seconds, the computer stops responding altogether.

Then it's crash time for me. The screen goes all blue (duh) and then shows a whole bunch of numbers and letters I can't quite think of. It stops at the bottom for half of a second, where it says "Beginning physical memory dump" before automatically restarting, disk checking, and everything.

I know overheating can cause this problem. I originally thought so (I had my CPU and GPU overclocked), so I put them back at stock speeds. It still happens, albeit less frequently. I also know stuff like having your RAM seated wrong, etc. can cause the problem. I recently went in my computer to make sure everything was hooked up (and put in) right, and it all was. Still happens. So, can anyone tell me what might be causing the problem? And if so, what can be done to fix it? I really don't want to reformat/repartition my hard drive, because I have a lot of games and such on there (They're legal, but they're from Direct2Drive), and don't want to go through the crap of doing that again. Thanks in advance.

If you open the dump in a debugger, what does it say? Typically that will point to the problem immediately.
 
I'll answer these in order...

I have somewhat of a temp monitoring program, but it's quite unreliable. They're all normal. When I randomly check my temps in the BIOS, they're also normal. Do you happen to know of any free programs I can use to check?

PSU -
Turbolink
Switching Power Supply
Model: LC-A420ATX 12V
VAC - Input
VDC (A some-what picture here, one line on top, three segmented ones on bottom)
Max DC output

Voltage 120/230C
+3.3 +5 +12
17A 25A 28A

Current 10A/5A
-12 -5 +5SB
1.0A 1.0A 3.0A

Frequency
60/50hz
BLK GRN GRY
COM P-ON PG

I know a little bit about power supplies, so I tried to make it somewhat readable by group...

I accidentally ran SuperPI instead of Prime 95, but it didn't crash. I'll try Prime tonight.

I haven't tried reinstalling Windows, I haven't bothered to yet. Would it be really worth it?


I tried doing a google search for all of the relevant parts, and all of the results are irrelevant. They all relate to Norton GoBack (Which I've deleted), or Internet Explorer service packs which came in SP2 and I have.


As for a debugger, could you clarify? Sorry for being stupid, but I'm not quite sure what you're saying. Any specific programs/instructions?


Thanks in advance.

 
Open up the memory dump in a debugger, and that should point to the problem.

If you aren't sure how to do this, mail me the files found in c:\windows\minidumps, and run MPSReports (see my .sig) and send me the resulting .cab file. I'll look at the dump and see if I can tell you what the problem is.

 
Send me a few of the latest dumps, zipped. Please include the URL of this topic in all e-mails.

So far, though, it looks like your nvidia driver is to blame (2 of 3 that I looked at, but they're older - best to look at recent ones).
 
Earlier dumps pointed to the nVidia driver, nv_disp. However, the new dumps point to a CPU/motherboard/RAM issue.

Try updating to the latest nVidia driver first. If that doesn't help, all I can state is I don't see a specific driver having an issue - both of these dumps point to different issues.
 
Well, I updated the drivers, and it's still happening, although it has been cut down by a little bit once again.


Is there anything I can do about the processor/mobo/memory issues?
 
Try this - take another hard drive, stick it in there, remove everything else you can. Put a generic XP install on there. Do not install ANY third party drivers at all - unless Microsoft made it, don't install it.

Now, can you make the machine crash?
 
high guys,

i m new to this forum and i was just browsing through cause i ve been having BSODs with the new rig i have just setup.

I read here that you can actually see what is going on by reading the minidumbs. Well......it seems my minidumb files are full of giberish!!!! how can i learn to read all that jazz?

thnx for your time
 
Originally posted by: alejandroAT
high guys,

i m new to this forum and i was just browsing through cause i ve been having BSODs with the new rig i have just setup.

I read here that you can actually see what is going on by reading the minidumbs. Well......it seems my minidumb files are full of giberish!!!! how can i learn to read all that jazz?

thnx for your time

You'll need to download the Microsoft debugger, and then set up the paths in your debugger as documented on the download page. Strictly speaking you don't need to download the symbol files, just make a directory on c:\ (c:\websymbols or somesuch) and, in the debugger, configure the path appropriately.
 
Back
Top