ok, my pc keeps crashing to a blue screen, which says:

A problem has been detected and windows has been shut down to prevent damage to your computer.

MACHINE_CHECK_EXCEPTION

If this is the first time you've seen this stop error acreen, restart your computer. If this screen appears again, follow these steps:

Check to make sure any new hardware or software is properly installed. If this is a new installation, ask your hardware or software manufacturer for any windows updates you might need.

If problems continue, disable or remove any newly installed hardware or software. Disable BIOS memory options such as caching or shadowing. If you need Safe Mode to remove or disable components, restart your computer, press F8 to select Advanced Startup options, and select Safe Mode.

Technical Information:

*** STOP: 0X0000009C (0X00000000, 0X8054D570, 0XC462C000, 0X00000136)

Beginning dump of physical memory.
Physical memory dump complete.
Contact your system administrator or technical support group for further assistance.

also last night when it did one of these crashes, my pc failed to restart to desktop like normal, instead it loaded to a black screen saying:

Windows could not start because the following file is missing or corrupt:
\WINDOWS\SYSTEM32\CONFIG\SYSTEM

You can attempt to repair this file by starting Windows setup using the original Setup CD-ROM.

Select 'r' at the first screen to start repair.

im unsure if that had anythign to do with the first problem, but i managed to stop that from showing by useing my xp disc etc.

also when my desktop loads i pop up comes up saying:

Unable to start driver for hpoipm07.exe (hpoipm07.exe)

unsure if any of this is connected, and any help would be great, as im at a totall loss, ive tried virus checks, de-frags, i thought the problem may of been due to lack of space on my pc, but i cleared up and now have 16GB, but this problem still happens, if I cant get help, i think its the pc shop for me, and i dont wanna pay those guys.

cheers

Gaz

Hi Gaz, welcome to PCHF.

Sounds like the Config\System and your BSOD's may be related. Most likely a memory fault, but if you could follow the BSOD's link on my signature, it describes how to post log files of these errors back here for inspection.

As for your hpoipm07.exe problem, this is part of your HP PSC or Officejet printer. If you still have this printer connected to your PC, the best way to resolve this issue is to re-install these drivers.

hey mate, cheers for the tip, will dig out my printer disc and re-install. I did read on another forum that someone had a problem around the same as mine and that was due to broken ram, like it had melted or something.

anyways, heres the screen print of the section you want. hope this is what you need, if not let me know and i will try again:

http://i2.photobucket.com/albums/y32...errorforum.jpg

cheers Gaz

is that correct..?

also today when it has crashed, it has given me different technical info, heres what it gave these two times:

STOP: 0X0000008E (0XC0000005, OXBF8147C4, 0XF58D154C, 0X00000000)

Win32K.sys - Address BF8147C4 base at BF800000, Datestamp 45F013F6

and the second one, was really strange, my speakers started to crackle, like there was static interference, then as it stopped it crashed, that code is:

STOP: 0X000000D1 (0X80800000, 0X00000002, 0X00000000, 0XF7AA251F)

ALCXWDM.sys - Address F7AA251F base at F7A70000, Datestamp 3eb2449d

dont know if any of this matters...

Hi Gaz,

Definately looks very very much like faulty RAM. There is another tool you can use to check for faulty memory (memtest).

- If you have a floppy drive and a spare floppy disk (recommended), you can download download: http://www.memtest86.com/memt32.zip

- If not, please download, unzip and use nero to burn this image: http://www.memtest86.com/memtest86-3.2.iso.zip

Reboot with the CD/Floppy in the drive and start memtest. This will ensure there are no problems in memory.

ok, so i ran that test, started it at 2.30. left it goin for near on 5hours, and it just kept goin to 100% and then starting again, ran through 8 times, didnt no what to do, or if i should keep waiting, so i cancled, but took it upon myself to take picutres of the screen and clipped them together so you could see what was on my screen. dno if it helps, or was i just impatient. how long does it normally take for one of these tests..?

heres the image...

http://i2.photobucket.com/albums/y32...reenprint4.jpg