Weird pc issue.

[GT Fanatic]

Stats first
Win7/8gb ram.amd 9850 proc/gtx460sc/650 ps/ mb m3a78t asus.

This morning I was trying to burn a cd for the trip to work. Burnt one and started on the second one. I was removing songs from the folder and got the blue screen of death. I powered it off and disconnected the power supply and for about 10 seconds and restarted. Nothing. Powered it up like 10 times and maybe it would load the bios splash screen and then nothing. So, I went and did some work on the wife's car and came back and tried a few more times and it loaded up. First the bios screen and then it showed a hardware check screen and at the bottom it said something like this. Some parts of the system may not be overclocked and may not function properly. Not exact words but close enough. Windows loaded up slow after that and rebooted and loaded up fine after that.

Weird things I have been experiencing lately. This is not the only time on a reboot the system will not load up. When windows loads up most of the time I can't do nothing till the a/v loads up. Which can be a couple minutes. Sometimes other programs won't load up as well. Freaking weird and annoying. I have no idea if something is interfering with the programs on start up. It makes no difference if I run ccleaner or not. Could a bad sector had the hard drive being doing any of this?

Thanks for any help or advice.

[Osiris]

I just had this happen to me last month. Turns out it was a bad MOBO. From what I understand, this could be one of three things here. The Proc, mobo, or memory.

BUT, I'm not as well versed as some of the other guys here, so I may be wrong.

[GT Fanatic]

System crashed again. Again I was going to play a song and when I clicked on it, I got the blue screen of death. It shut down and restarted and crashed again. When I rebooted it from there it went into a START UP REPAIR. After that it loaded. Does this mean it's a software issue? Thanks

[mstng86]

Is your processor overclocked?

[Josh.0]

try scanning with this http://www.malwarebytes.org/

[GT Fanatic]

Is your processor overclocked?

nothing is overclocked except the video card came factory overclocked.

[GT Fanatic]

try scanning with this http://www.malwarebytes.org/

Running scan will post stats when finished. Thanks

[GT Fanatic]

Malwarebytes' Anti-Malware 1.51.1.1800

https://www.malwarebytes.org

Database version: 7621

Windows 6.1.7600
Internet Explorer 8.0.7600.16385

08/31/2011 1253 PM
mbam-log-2011-08-31 (12-23-53).txt

Scan type: Full scan (C:\|G:\|)
Objects scanned: 342771
Time elapsed: 34 minute(s), 44 second(s)

Memory Processes Infected: 0
Memory Modules Infected: 0
Registry Keys Infected: 0
Registry Values Infected: 0
Registry Data Items Infected: 0
Folders Infected: 0
Files Infected: 0

Memory Processes Infected:
(No malicious items detected)

Memory Modules Infected:
(No malicious items detected)

Registry Keys Infected:
(No malicious items detected)

Registry Values Infected:
(No malicious items detected)

Registry Data Items Infected:
(No malicious items detected)

Folders Infected:
(No malicious items detected)

Files Infected:
(No malicious items detected)

[mstng86]

do you have multiple memory sticks? If so, pull them out one by one and see how it goes.

[GT Fanatic]

do you have multiple memory sticks? If so, pull them out one by one and see how it goes.

The only thing with that is, the problem is not consistent yet. It's happened twice in 4 days. And I don't know if the 'start up repair' actually fixed the problem.

[Osiris]

Maybe you have a bad/conflicted driver somewhere. I say reformat.

[CJ]

That sounds like CMOS issues. The "some parts of this system" message is a typical CMOS reset message - meaning your motherboard failed to post so it went failsafe and reset the CMOS data. Most motherboards will reset the CMOS if the motherboard fails to post 3 times in a row. Now, if you EVER get a lock on post you're experiencing major problems. Processor, motherboard, or memory almost always. Other things that can cause this is overheating the memory controller - it can cause a locked post until it cools down enough. I think we need a little bit more of the symptoms to get a good idea. When it locks up and crashes what were you doing, how hot was it in the room, how long had the system been flogged, etc.. A good place to start is to swap out memory modules, because that is usually the highest percentage of problems on these newer systems.

[GT Fanatic]

That sounds like CMOS issues. The "some parts of this system" message is a typical CMOS reset message - meaning your motherboard failed to post so it went failsafe and reset the CMOS data. Most motherboards will reset the CMOS if the motherboard fails to post 3 times in a row. Now, if you EVER get a lock on post you're experiencing major problems. Processor, motherboard, or memory almost always. Other things that can cause this is overheating the memory controller - it can cause a locked post until it cools down enough. I think we need a little bit more of the symptoms to get a good idea. When it locks up and crashes what were you doing, how hot was it in the room, how long had the system been flogged, etc.. A good place to start is to swap out memory modules, because that is usually the highest percentage of problems on these newer systems.

Heat is no issue in the computer room. Always freezing in there.
Bryan has me testing the ram right now to narrow down which stick might be bad. Since I pulled 2 sticks out it has been fine so far. Just a waiting game now.

[CJ]

Heat is no issue in the computer room. Always freezing in there.
Bryan has me testing the ram right now to narrow down which stick might be bad. Since I pulled 2 sticks out it has been fine so far. Just a waiting game now.

You can have a heatsink clogged with dust and it overheat even if it's 60 in that computer room. If you pulled 2 sticks then I'm assuming you have 4, and your dimm banks were full. That usually causes issues with overloading/overheating your memory controller. I've had this happen at least 3 times. Increasing your MCH voltage will probably stabilize the issue.

[Tx Redneck]

Deal is though, it just started doing it. It was fine in Tx. It must be the thin air up in Co.

And Blues Screen View showed it to be the ntoskrnl.exe which has always been bad dimm(s) in every case I dealt with.