WINDOWS 7 64bit ultimate RTM RANDOM LOCK UPS

[Antman]

...Your initial reaction almost scared me off from this site, but I wanted to prove my self as an honest person. So thanks for welcoming me here.

Stick around. You give good post at the other site. And don't mind Squonksc. He is a good man working with a tedious user problem. One funny thing, when I was reading the thread at the other site, I noted that I was one of two users doing so. Squonk?


IMO, folding@home is a worthy cause. I hope that DirectX 11 will allow it to crunch, er, fold, a bit faster.

And, let's keep digging. CPUs don't get bored.

 

[SquonkSC]

I don't know how, but my initial theory is that the extra CPU cycles it uses are keeping the system busy enough so that it doesn't 'get bored' if you will, and lock up.

Your initial reaction almost scared me off from this site, but I wanted to prove my self as an honest person. So thanks for welcoming me here.

Believe me, folding@home didn't fix your problem.
BSOD doesn't mean "Bored System Off to Dreamland"

BSOD can have a million reasons, software, drivers, failing hardware, heat, too low or too high voltages.

Something you changed has fixed it (in your case), but if you didn't troubleshoot systematically, and kept logs of what you changed, you will never know what fixed it.


My initial reaction was meant to scare you off, because I thought you had bad intentions, but again I apologize.

I saw on the other forum you are a Graphic Designer.
Your knowledge about that can be very useful to a lot of people here, especially in the customization section.

But with all do respect, based on your first post and the posts I read on the other forum, it seems wiser to stick with what you're good at.

Now we have to go back on topic.

I will delete my part of our post exchange with you, because they do not add anything to this thread.
Please do the same.

Geetings,

Michel

 

[windew420]

um im still having lockups. please some1 help me

um im still having lockups. please some1 help me

 

[diablofan]

Stick around. You give good post at the other site. And don't mind Squonksc. He is a good man working with a tedious user problem. One funny thing, when I was reading the thread at the other site, I noted that I was one of two users doing so. Squonk?


IMO, folding@home is a worthy cause. I hope that DirectX 11 will allow it to crunch, er, fold, a bit faster.

And, let's keep digging. CPUs don't get bored.

I don't plan on leaving so quickly. Thank you for welcoming me here.

I know CPUs dont get bored, I phrased that way because I'm not sure how else to explain it right now.

Also, I'm using the console edition of Folding@Home. I tried the Graphical version of it before, and it ran slowly. I switched to the console version and it ran faster.

Believe me, folding@home didn't fix your problem.
BSOD doesn't mean "Bored System Off to Dreamland"

BSOD can have a million reasons, software, drivers, failing hardware, heat, too low or too high voltages.

Something you changed has fixed it (in your case), but if you didn't troubleshoot systematically, and kept logs of what you changed, you will never know what fixed it.


My initial reaction was meant to scare you off, because I thought you had bad intentions, but again I apologize.

I saw on the other forum you are a Graphic Designer.
Your knowledge about that can be very useful to a lot of people here, especially in the customization section.

But with all do respect, based on your first post and the posts I read on the other forum, it seems wiser to stick with what you're good at.

Now we have to go back on topic.

I will delete my part of our post exchange with you, because they do not add anything to this thread.
Please do the same.

Geetings,

Michel

I know that. I've tried an all minimal hard ware solution, locked up still. I've tried no video card, (even though it doesn't more power than it gets from the PCIE slot, and it locked, although it locked but the screen looked very...odd. Nearly all white with a few striped of black and few clips of the screen.

Although to be honest, my position as a graphcs designer there is misleading. I'm more of the programmer type, than the artisan. I'm not that good at making graphics. I'm better at taking other graphics and making logos out of them. But, as I've said I'm the programming type of person.

Okay, back to the topic now:

I had a clean install of Windows 7 7600. When I installed it, I was using an nForce NIC, the one that was built onto the motherboard of my computer. Then my computer locked up. So I went back to the thread I made about the lock ups and tried what I posted, disabling some of the special effects and that. So I did those, and then it locked up again.

So I posted that I was having those locking issues again, and some one pointed out it may be the nForce NIC. So I disabled it in BIOS and then installed the DLink DFE-530TX+ NIC card. I booted into windows, and it installed the card. A few hours later, it locked again.

So I swapped back, and it repeated. Then I swapped again, but that time, I also threw in my Creative SB-Live! 24 Bit card and disable my onboard sound controller.

The only thing that might be causing the lock ups from rewriting what I've done since it's started is the audio controller. I'm going to kill F@H and run my computer like I would for a few hours, if it works with no problems, then I found my solution.

 

[SquonkSC]

um im still having lockups. please some1 help me

Hi Windew,

Can you give me as detailed as possible,

1. all the devices connected to your machine (ext drives, printers, scanner, usbhubs, bluetooth dongle etc..)
2. devices in the machine like pci cards
3. all none Microsoft or Adobe software
4. Installed ASUS AI by any chance? Or any other Asus tool from the driver CD?
5. temperatures of CPU, GPU, Mainboard on idle and normal load.
6. Can you provide us with the exact type number of your coolermaster PSU?
7. Silly question, but you have the 6 pin connector hooked to your graphics card, right?



And a few things you can do and post back about:

Go to Bios and set to Default options.
Remove 2 strips of ram, leaving only 2gb

check if that works.

If not, take that one out and replace with one of the others.
test again.
Still not good, test the last one.

If this makes no difference, stay with 2gb for now, until we find the problem.

Then go to device manager and disable your networkcard.
Test again.

still not good.

Post back.

good luck

 

[diablofan]

I have another suggestion to try. While you have one stick of memory in the computer run a memory test with it. I personally use MEMTEST86+. Burn to a disc and boot into it.

If it comes up with any errors, then it seems you have a bad stick of memory. Run that with each stick. Then run it with both.

 

[magicdave26]

First off, I am a Super Mod over at thehotfix working aslong side Diablofan, and I can vouch he is a good man and would never try to scam anyone..


Ok that said, I did experience random lockups with Windows 7 a while back during testing and for me, it came down to me mixing RAM speeds combined with a dualcore CPU, I had no problem with a single core CPU at first while mixing the RAM speeds and sizes, but I was bought a DualCore CPU for my birthday and as soon as I installed it, I started experiencing the exact same lockups being talked about here, the screen just freezes and does nothing.

My specs at the lockup time were

ASUS Mainboard (forget the model)
2x 1gb @ 667
1x 1gb @ 800
Athlon 64 X2 5200+ 2.7ghz


As soon as I removed the 800Mhz 1Gb strip, the lockups dissapeared.


Dont know if this setup applies to anyone else here, but some food for thought.


Cheers

Dave

 

[SquonkSC]

First off, I am a Super Mod over at thehotfix working aslong side Diablofan, and I can vouch he is a good man and would never try to scam anyone..



As soon as I removed the 800Mhz 1Gb strip, the lockups dissapeared.

Dont know if this setup applies to anyone else here, but some food for thought.

Cheers

Dave

Thanks Dave,

DiabloFan and I have settled the initial issue (I hope), but thanks anyway.

And also thanks for your input.

In my latest post to Windews, I asked him to take out the rams and check them one by one.
Among some other suggestions.

Do hope he doesn't have a Monday morning mainboard.

greetz

 

[magicdave26]

Thanks Dave,

DiabloFan and I have settled the initial issue (I hope), but thanks anyway.

And also thanks for your input.

In my latest post to Windews, I asked him to take out the rams and check them one by one.
Among some other suggestions.

Do hope he doesn't have a Monday morning mainboard.

greetz

Yea, I have had many monday morning mainboards in my time, Good plan testing the RAMs 1 by 1, weird stuff happens when RAM plays up.

 

[diablofan]

Okay, so as I posted before, I would kill F@H and see how long it would run.

Well, I did just that, and much to my dismay, the computer locked up about 5 mins ago, (I'm posting from my mom's computer right now). I'm thinking that F@H might have kept it stable but I'm not sure how to explain that one.

 

[magicdave26]

Do you have a power setting set for the CPU to drop down to 5% or so when not in use ? You know the one that is intended for Laptops on Power Saver mode ?

F@H Keeping the CPU throttled at 100% ?

Another idea..


You could test this theory by using Prime95 Stress tester too

 

[zigzag3143]

Do you have a power setting set for the CPU to drop down to 5% or so when not in use ? You know the one that is intended for Laptops on Power Saver mode ?

F@H Keeping the CPU throttled at 100% ?

Another idea..


You could test this theory by using Prime95 Stress tester too

BTW make sure you throttle folding@ because it is stqrongly recommended not to run at 100% for thermal reasons. I melted an IBM and a dell with seti@ in the same way.

KEn

 

[SquonkSC]

Do you have a power setting set for the CPU to drop down to 5% or so when not in use ?

Good suggestion.

Not likely, but is worth trying out.

Would be hot news if 5% throttle crashes the system.

greetz

 

[windew420]

i am curious why does my cpu and multiplier fluxtuate is that normal?
btw i increased my cpu voltage to 1.35 volts.

does prime 95 work on win7?

mega thanks for all your help

ty ty ty i think im getting closer to win7 bliss.

i cant wait to figure this out so i can help other people with similar problems.

 

[SquonkSC]

i am curious why does my cpu and multiplier fluxtuate is that normal?
btw i increased my cpu voltage to 1.35 volts.

does prime 95 work on win7?

mega thanks for all your help

ty ty ty i think im getting closer to win7 bliss.

Have you done any of the list of suggestions I made a few posts back?

And can you update us on the status of your problem at this moment?

greetz

 

[magicdave26]

i am curious why does my cpu and multiplier fluxtuate is that normal?
btw i increased my cpu voltage to 1.35 volts.

does prime 95 work on win7?

mega thanks for all your help

ty ty ty i think im getting closer to win7 bliss.

i cant wait to figure this out so i can help other people with similar problems.

CPU & Multiplier will fluxtuate due to a power saver feature for the CPU as I mentioned earlier, check if you have a Minimum Processor State set to 5% in Power Settings

 

[Antman]

The fluctuations are Intel SpeedStep. Can be enabled/disabled in BIOS.

 

[windew420]

should i have speed step enabled or disabled i guess what iam saying is witch one is better.


also i am gathering info and will post when done sorry all just been busy today

 

[diablofan]

@Dave: My power setting shows that the minimum usage is set to 5%. I'm currently running Prime95 to see if it has the same effect as F@H. Also, F@H was set to 100% usage.

@zigzag: I'll turn down F@H to 80% if I have to run it to keep my computer stable.

@squonksc: That seems to be the theory it's evolved into, so if it turns out to be true, then we have a slight problem possibly.

@windew: Prime 95 does run on Windows 7, in fact I'm running it right now. There is also a 64Bit edition as well.

 

[Antman]

should i have speed step enabled or disabled i guess what iam saying is witch one is better.

Under normal circumstances, SpeedStep is a good thing. The theory being applied to your problem at the moment would prescribe that you disable speedstep.