Keep getting BSODs

[SE14man]

Hi,

I keep getting BSODs but they're never there long enough for me to be able to read them properly.

The PC just restarts before getting the chance to read it.

Is there a way i can either freeze them to see them or enable it to produce a log to say what the issue is.

another thing i'd like to point out is that when the PC is restarted it never shows a screen after the PC is rebooted.... It just shows 'No Signal' then i have to pull the plug and turn it on again to be able to see the screen boot up.

Would this be a PSU issue?

Thanks people in advance

[johns0]

Sounds like either your psu or motherboard is going downhill,if its the MB then the caps might be drying up if your computer details is current.

[SE14man]

Hi there sorry no they're not i should update them actually.

This PC im talking about was bought 2 years ago and is a medion.

It did come with windows 7 but i got too annoyed with windows 7 and put xp pro on it.

But it was since putting XP pro on it ive been getting these BSODs.

I dont know if this is a driver issue or what but id really like to get to the bottom of it without having to put 7 back on.

Thanks for your response!

[johns0]

Did you do a clean install?Winxp is getting really old and vulnerable to viruses and hack programs,might be that which is causing problems,i myself rather have windows 7 than winxp any day.

[videobruger]

You might try:

http://www.resplendence.com/whocrashed

and

Start -> mmc -> Ctrl+M -> Logfiles

[SE14man]

Yes i may go back to Windows 7. But it just affected Flight Simulator a lot. In a way that i could not get full rights and admin control over it and it errored a lot and played up.

I would love to stay with windows 7 but not until i can figure out how to get full admin rights over the whole C: drive. would you be able to help with that?

thanks videobruger. Ill check it out

[SE14man]

Hi again.

I installed the software.

Its not giving me BSODs anymore the whole pc is just locking up completely. So much so that the clock shows the time it locked up on.
With this software though.... i analyse it and it cant create a report because its saying i havent got crash logs enabled. When i follow the procedure it tells me i need to make sure i have a paging file which i do. It seems to be the right size.

Are there any other tests i can run which check drivers?

I tried this command: Start -> mmc -> Ctrl+M -> Logfiles

It did work but just brought me to a screen with an option to add things. No logfiles were there. It was an empty field.

Any other tests i can run?

Thanks

update: The BSOD came up again and i managed to get a photo of it this time it said:

IRQL_NOT_LESS_OR_EQUAL

It asks me to check if any new hardware or software was added.

But the thing is.... all drivers were installed at once along with flight simulator.

All within 1 hour so how would i go about isolating or finding out whats causing the problem?

Thanks

[hech54]

Windows XP

Control Panel
Administrative Tools
Event Viewer
System

[SE14man]

The only error im getting there is one with a yellow triangle with an exclamation mark in it.

Source is Microsoft Antimalware.

Could this be whats causing it?

All other entries are the normal symbol or just the blue exclamation mark.

Thanks

[MISS CHIEVOUS]

OP — first, if you haven't updated your XP since SP2 you very badly need to visit Microsoft. I was astonished to see since my last major SP a few years back a staggering 1,897 MBs of updates. It's never a comfortable experience to browse using IEX with anything remotely hopeful of security, but you'll need to bite the bullet. One year from now — in April 2014 — is Microsoft's Drop Dead Notice: No more updates for XP thereafter. You're well-advised to avoid Windows 7 and wait another year for Microsoft to get its act together such that their (64-Bit, especially) OSs are stable. I'm happily on a 32-Bit flavor of XP Pro because i'm loathe to throw away hundreds of dollars of what they speciously refer to as "Legacy hardware" until it stops working.

The reason I preface my response with that prerequisite is that I think you should do that before you do anything else. Why? Because I'm going to recommend you take the security risks associated with Windows Update, manually download the (I had over 270 if that's any guide) updates, rip them to DVD . . . and then zero-fill your hard drive using the mfg.'s drive tools. Zero-fill means it wipes the drive — the partitions, the data, the programs, the Registry, everything. It's so blank when you complete this process that you don't even have a formatted drive when you're done.

Then reinstall XP to a fresh partition (or drive) and update everything off of the DVD you ripped.

Lastly, I want to suggest something that may seem harebrained but has a disturbing habit of resurfacing in these BSODs like a dead body that won't stay buried: Check every single electrical connection to your motherboard -and- the connection from your chassis to the wall. Many years ago I was getting stampeding BSODs until I finally opened up my chassis and discovered connectors barely hanging on to their pins on the motherboard. WTF??? (and people wonder why every new PSU comes with cables that lock) Don't feel bad OP: In the Molex world of the 20th Century, the frigging heads had no means of locking onto the motherboard. You bump your foot against the chassis accidentally . . . you move it and jar it . . . you have earth tremors. In short, they're hanging on by their short ’n curlies.

But really, zero fill and do a clean install with your hundreds of Microsoft updates pre-collected and burned onto a DVD that's IEx Hotfix Proof.

miss chievous