Overclock.net banner

Need help!!!!!!!

497 Views 18 Replies 5 Participants Last post by  graphicsman
Ok. i finally got a legit copy of an OS, XP 64 bit, but i still sometimes get the blue screen of death!!! How can i diagnose this??? I am lost and need help!!! It is driving me up a wall. Is there a way i can try to force it to do it again, like a system test or something?? I ran a check on the ram with ubunto, and it came back 100% ok.. SO where i start???

Help PLEASE ! ! ! :swearing:
1 - 19 of 19 Posts
it says it is a hardware issue, i have turned off the restart so i can write down what the error is, but the only problem is it happens in a bluemoon, is there a way i can force it??
Run prime or orthos for a good while and see if it errors. If not then you might want to reinstall drivers, maybe the OS and find newest drivers for everything.
where can i get those programs??
ok i ran ortho for five minutes and this is what i got

Type: Blend - stress CPU and RAM Min: 8 Max: 4096 InPlace: No Mem: 3839 Time: 15
CPU: 3000MHz FSB: 333MHz [333MHz x 9.0 est.]
CPU: 3000MHz FSB: 333MHz [333MHz x 9.0 est.]
3/2/2009 9:33 PM
Launching 2 threads...
Using CPU #0
Beginning a continuous self-test to check your computer.
Press Stop to end this test.
Test 1, 4000 Lucas-Lehmer iterations of M19922945 using 1024K FFT length.
Test 2, 4000 Lucas-Lehmer iterations of M19922943 using 1024K FFT length.
Test 3, 4000 Lucas-Lehmer iterations of M19374367 using 1024K FFT length.
Torture Test ran 4 minutes 42 seconds - 0 errors, 0 warnings.
Execution halted.

Using CPU #1
Beginning a continuous self-test to check your computer.
Press Stop to end this test.
Test 1, 4000 Lucas-Lehmer iterations of M19922945 using 1024K FFT length.
Test 2, 4000 Lucas-Lehmer iterations of M19922943 using 1024K FFT length.
Test 3, 4000 Lucas-Lehmer iterations of M19374367 using 1024K FFT length.
Torture Test ran 4 minutes 42 seconds - 0 errors, 0 warnings.
Execution halted.

i did the cpu and ram, what else should i do??
See less See more
5 minutes is not enough of a test in Orthos. You need at least 15 minutes to an hour or two for prelim testing, then a good 8-10hrs (or 24hrs for you hard core bastiges).
Quote:


Originally Posted by Demented
View Post

5 minutes is not enough of a test in Orthos. You need at least 15 minutes to an hour or two for prelim testing, then a good 8-10hrs (or 24hrs for you hard core bastiges).

ok, do i need to adjust the priority??
See less See more
Well, looking at your post you're just trying to BSOD purposely, right? OCCT and Orthos will BSOD if the CPU or system becomes unstable under the stress. I'f you're not OCing your chip, and the BSODs come randomly, not much else you can do but play with your BIOS settings until you get a combo that will be unstable. However, take caution when doing this. It could be any number of things causing the BSODs.

Just for stress testing, OCCT custom test for 15 minutes, Medium Data Set, at high priority is a good start. You can increase the time, or let it run an Infinte test at the same settings...should BSOD...
ok i have done the orthos for one hour and 45 mins, it still says its ok, :swearing:

any other advice, is there a way to test my graphicscard, because this is weird, it happens at odd times, the last time was over two months ago, what the hell!!!!! any more advice from anyone??
Quote:


Originally Posted by graphicsman
View Post

ok i have done the orthos for one hour and 45 mins, it still says its ok, :swearing:

any other advice, is there a way to test my graphicscard, because this is weird, it happens at odd times, the last time was over two months ago, what the hell!!!!! any more advice from anyone??

Well, the latest version of OCCT has a GPU stress test you can try, tho I've never used it.

Hope that helps!
See less See more
2
ok, so i finally got it to give me a blue screen of death.

it says stop: 0x0000007E

under it it says nv4_disp.dd

so where do i find out from that what it is, and how i can fix it???
Quote:


Originally Posted by graphicsman
View Post

i meant nv4_disp.dll lol

Well, I tried to search for help on your specific error code, but couldn't find anything pinpointing it.

I did, however, find an older page with a lot of info on all sorts of Windows error codes here.

Hope that helps.
See less See more
Quote:


Originally Posted by graphicsman
View Post

ok, so i finally got it to give me a blue screen of death.

it says stop: 0x0000007E

under it it says nv4_disp.dd

so where do i find out from that what it is, and how i can fix it???

Is this the same error from before? nv4_disp.dll is going to be a video card driver problem. I would uninstall your GPU drivers and run a driver cleaner to get them off your system and then download and install the correct, up-to-date XP 64-bit drivers (I think that is what you said your OS was) from Nvidia's website.
See less See more
Quote:


Originally Posted by Ziggy
View Post

Is this the same error from before? nv4_disp.dll is going to be a video card driver problem. I would uninstall your GPU drivers and run a driver cleaner to get them off your system and then download and install the correct, up-to-date XP 64-bit drivers (I think that is what you said your OS was) from Nvidia's website.


ok ive done this, and also ran a atitools test for over 5 hours, and it came back with no errors, but i dont know if its testing both cards or just one..
See less See more
Quote:


Originally Posted by Ziggy
View Post

Is this the same error from before? nv4_disp.dll is going to be a video card driver problem. I would uninstall your GPU drivers and run a driver cleaner to get them off your system and then download and install the correct, up-to-date XP 64-bit drivers (I think that is what you said your OS was) from Nvidia's website.

ok ive downloaded three different sets of drivers, and the only time my error came back is when i enabled SLI
See less See more
1 - 19 of 19 Posts
This is an older thread, you may not receive a response, and could be reviving an old thread. Please consider creating a new thread.
Top