Jump to content

Welcome to Geeks to Go - Register now for FREE

Geeks To Go is a helpful hub, where thousands of volunteer geeks quickly serve friendly answers and support. Check out the forums and get free advice from the experts. Register now to gain access to all of our features, it's FREE and only takes one minute. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more.

Create Account How it Works
Photo

Regular BSOD on boot up.


  • Please log in to reply

#1
Seltox

Seltox

    Member

  • Member
  • PipPipPip
  • 254 posts
Hi,
My system:

OS: Windows 7 Ultimate x64
Motherboard: abit IP-35 Pro
Video: XFX Alpha Dog 8800GT
PSU: Corsair HX-620
CPU: Pentium D 945 or 950 (not sure)
RAM: 2GB (2x 1GB sticks) Corsair DDR2 in Dual Channel

Now, the problem.. Sometimes when I start up Windows, right after I log into my user, i'll get a Blue screen which will say something along the lines of "Dumping physical memory to disk". It happens rather quickly so I can't remember exactly what it says. This doesn't happen all the time, and i'm able to just restart and my computer is fine, which is why I haven't been too concerned about it. But, it does happen maybe 2-3 times a week.

When my PC has started back up, it has a "Windows has recovered from an unexpected shutdown" window, and has these codes:

BCCode: 50
BCP1: FFFFFA800680C000
BCP2: 0000000000000000
BCP3: FFFFF80002CBF4FA
BCP4: 0000000000000000



Any ideas on what causes this? Whether I should be worried/how to fix it?

Cheers,
Seltox
  • 0

Advertisements


#2
Jordi Ruiz

Jordi Ruiz

    Member

  • Member
  • PipPip
  • 24 posts
Hi Seltox,

Without the message of the BSOD it's difficult to discover the problem of the error.
A few month ago I repair a computer with a similar problem, it restart randomly after a BSOD. The problem with that computer was a bad RAM module.
You can try to extract one RAM module, if the problem persist put this module another time and extract the other module. In my opinion this could solve your problem.
I wait your answer. Bye.
  • 0






Similar Topics

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP