Prime95 Instant BSOD

Hello. After reinstalling my operating system after having almost all the hardware in my computer replaced by dell, I was getting random shut downs every 15 minutes to 1 hour doing various tasks on the computer. I was told by a dell tech to try running a prime 95 stress test to see if the CPU might have something to do with it. When I run Prime95 Small FFT's test, I get an instant BSOD blaming ntoskrnl.exe+75c00.

Specs:
Processor: Intel (R) Core i7 980x Gulftown
Motherboard : Alienware x58 Chipset
Graphics: 2x ATI Radeon HD 5970 Crossfire
Hard Drive: 2x Western Digital 640gb Sata II Raid 0 Array
Memory: 3x 2gb 1867 Mhz Kingston Hyper X Sticks
Power Supply: 1000 Watt

Welcome, please follow the Blue Screen of Death (BSOD) Posting Instructions :) .

Hi thanks of the files :) .
The bug checks varies a bit, but not one mentions Prime95 as the active as the active process.

Can you elaborate on which parts were replaced by Dell (and possibly if you know, for what reason)?
When a PC instantly reboots/BSOD's when starting Prime95 a few things come to mind.
Most common is high temperatures, the others are a PSU fault, an unstable overclock,
the least common are a faulty motherboard and / or CPU.
Are you sure that the PC bug checks and not just restarts as a safety mechanism, do you see the BSOD?
Are you monitoring the temperatures in any way?

• Download Speccy and post a Screenshot of the summary window.

As for the bugchecks, as I said they vary so will deal with the obvious first than continue
from there once the above (the reason that the PC can't handle Prime) is cleared.


You have a very old driver that doesn't do nothing but trouble regardless
of the other reasons the PC is unstable.

Code:

BugCheck 24, {1904fb, fffff8800a73f3f8, fffff8800a73ec60, fffff80002c80a7e}

*** WARNING: Unable to verify timestamp for SiWinAcc.sys
*** ERROR: Module load completed but symbols could not be loaded for SiWinAcc.sys
Probably caused by : SiWinAcc.sys ( SiWinAcc+102e )

Code:

lmvm SiWinAcc
start             end                 module name
fffff880`01364000 fffff880`0136d000   SiWinAcc T (no symbols)           
    Loaded symbol image file: SiWinAcc.sys
    Image path: \SystemRoot\system32\DRIVERS\SiWinAcc.sys
    Image name: SiWinAcc.sys
    Timestamp:        Fri Jun 15 03:02:02 2007

Code:

SATALink driver accelerator    c:\windows\system32\drivers\siwinacc.sys

• Driver Reference Table - siwinacc.sys
  Silicon Image driver - comes with package for the SIxxxx drivers.

I found an updated version from 2010 but it's best you use your Service Tag to update the drivers.

• Dell Support

Post back with the results :).

*Please see the following post to help explain the Silicon driver problem*

Thank you for your time kind sir.

I will start by giving you a short summary of my recent PC problems. Originally my PC randomly stopped posting one day and so in an attempt to find out what was causing it, Dell ended up replacing everything except the hard drives (CPU, Memory, GPU's, Motherboard, CPU Liquid Cooling Module, PSU) until they found out it was a faulty CPU. After that the computer would post but I would get random shutdowns every 15 minutes to 1 hour doing random things like watching videos, playing games, installing programs from desktop, even when sitting idle it seemed sometimes. Since then I formatted and reinstalled windows and have just now recently updated all my drivers. I have not had a random restart in about 18 hours, but the tech wanted me to make sure that everything was working properly with the new CPU so he recommended I test with Prime95. He said I should be able to get through a Small FFT's test with Prime95 without any problems. When I start Prime95 Small FFT's test, I get an instant BSOD. Yes I can see the BSOD, it is not a debugging window. Its the same BSOD that come up in Blue Screen Viewer in the dump files. The main one is the ntskrnl.exe + 75c00. He said that if I can't get through a Small FFT's test, then something is wrong and it isn't build right, or its a possible software problem.

So pretty much I am trying to figure out why my computer can't run a stress test without BSOD'ing.

EDIT: The CPU is not overheating, the hottest I ever seen it get before crashing is around 65 to 70 degrees celsius when attempting to run the stress test. In fact the test doesn't even really start to be honest to even give it a chance to jump more than 10-15 degrees from its normal 38 to 40 degree celsius range. The monitoring software I use is HW Monitor and CPU-Z.

Here is the Speccy SS requested below.

I have recently added 50+ more windows updates that I didn't know I was missing and windows is now fully up to date. After doing that I tested Prime95 and I am getting the same BSOD. I will upload an updated version of the SF folder requested on thread creation. Thanks again for your time YoYo. Hope to speak to you soon.

New news to report.

I just got my first random BSOD while just browsing the internet for new drivers after about 20 hours without one. What is even crazier is when I log back on, my minidump folder is EMPTY! What could have caused this? Luckily I was able to catch the debug code on the BSOD which seems to be the same exact code I get when Prime95 crashes. Its the 0x000003b one.

Okay, about the Silicon driver. The Silicon drivers that I downloaded from Dell don't seem to be installing right. When I click on the setup file it says windows configures 3132-W-D for about 2 seconds and then the window just disappears not giving any confirmation or message letting me know it installed right. I tried going to the Silicon website to update my drivers but the Only drivers I could find for the 3132 software I could find required a Bios and special card I think? I am having trouble finding the correct drivers, but when I look at device manager it says my drivers for it are up to date and it dates them at 06/24/2009. Under the properties under device location it says no device detected, and all the fields under device information are all blank. I do not remember having this controller on my system before. After installing what I thought were the wrong drivers I started getting a phantom SATA controller showing up under "Other Devices" and it kept failing to update the driver. So I did a system restore and I now for the first time am seeing a Silicon SATA link controller under my Storage Controllers for the first time saying that its working properly and the driver is up to date as of 2009. This is very confusing, I guess I am going to have to wait until you get back to me to figure out how to update the drivers for it. Also, is there even a way to confirm through my hardware that I even have this SATA Controller linked to my system? Since I don't have any PCI express card plugged in for any special raid controller, the only drivers I could find required a Bios and all that. I am going to go ahead and update my SF Diagnosis File to see if you see a change in the driver or if it was updated from 2007 to 2009 possibly. Sorry, just very confused at the moment. I probably need to get some sleep, heh.

For now, the biggest news is that I am now getting the random BSOD's again WITHOUT running Prime95 stress test just doing normal windows tasks. I suspect something wrong with the CPU they replaced the old one with. I think maybe the VID default core voltage was set too low at the factory or something because my BIOS is set to optimal defaults and I am not overclocked at all. Only other weird thing is my memory multiplier is set to 133x14 = 1867 Mhz. Why is it showing in speccy that they are running at 935 Mhz? I am assuming because of the Intel (R) Speed Step technology it is underclocking my RAM while the CPU is idle? I also noticed that even though my Vcore is suppose to be default about 1.12-1.2 V, it is sitting idle at about .936 V. Probably again a possible side effect of the Speed Step technology.

Some additional important information that you might find useful:

I have run chkdsk /f/r manually using the windows chkdsk checking both the repair and find bad files and sectors options.

I have also run Memtest86+ for 5 passes with each of my 3 memory sticks and received no errors. When I put all 3 sticks in and ran for 5 passes, I got 2 errors on test 7. I have heard that this doesn't neccescarily mean a memory problem, it could just be some bug that happens in certain situations? Not to mention it is brand new memory. I also doubt its the memory controller as it is also a brand new motherboard.

I don't know whats going on, but hopefully with your help, YoYo, we just might be able to get to the bottom of this. The last thing I wanted to do was to exchange my system with Dell if there was anything I could do about it. So if we can figure this out somehow, it would really mean a lot to me.

Once again, thank you for your time and effort YoYo. I hope to hear back from you soon.

Note: I also want to apologize as I have edited the last 2 posts extensively over the past couple hours as I have answered many of my questions I had written myself due to research and troubleshooting on my own. I apologize if it has caused any confusion if you had happened to read them during that time.

(Updated SF File below was from before the last random BSOD deleted my minidump folder)

Hi thanks for the added info :) .
From the last two bug checks I was able to verify that the Silicon RAID controller driver was not updated,
I wouldn't worry about it at the moment as there is something else I want you to perform as a test
in which I'll elaborate further later in this post.

At this point I suspect (even if they are new) the Motherboard, RAM, PSU, CPU and BIOS settings
as the possible culprits.

I think maybe the VID default core voltage was set too low at the factory or something because my BIOS is set to optimal defaults and I am not overclocked at all.

Please set the X.M.P profiles, where available, for the RAM mostly.
Some motherboards have a Safe setting as well as a Normal setting, if yours does
please set it to Normal.

Only other weird thing is my memory multiplier is set to 133x14 = 1867 Mhz. Why is it showing in speccy that they are running at 935 Mhz? I am assuming because of the Intel (R) Speed Step technology it is underclocking my RAM while the CPU is idle?

No, this is normal. That is how DDR or Double Data Rate works, 935*2= 1870 or ~1866.

I also noticed that even though my Vcore is suppose to be default about 1.12-1.2 V, it is sitting idle at about .936 V. Probably again a possible side effect of the Speed Step technology.

Yes that is normal as well, not so much a side effect.

I noticed that all of the bug checks (apart from one which was a TDR so it's not really a bug check)
occurred on processor #5.
Please try eliminating cores by starting the Prime95 test using only 1 thread and working your way up
until instability is reached.

Attachment 292178

If you still crash at the get go try eliminating the cores from Windows all together.
The disadvantage of this method is you'll have to restart to take effect each time a change is made.

> Run > msconfig :
Attachment 292179