BSOD

[The Cool n00B]

I've have my new computer for about a week now and I've been using it like mad (who wouldn't). But whenever I google it everybody seems to think that it's a drivers fault, or that windows does that when it sleeps. So, I went the easy route and adjusted power settings. I optimized everything for performance, it never sleeps, and it never shuts the screen off.that didn't help. The next solution was to run all of the non-Microsoft drivers to the max and see what causes that blue screens, but it said to do that for 24-48 hours. It was hoping its simpler than that. It only blue screens when it stays idle for about 15 minutes. The blue screens also say that it's dumping the physical memory on the disk, so if that could help?

[dragoon20005]

can you do a MemTest?

 

run with one stick of RAM

[The Cool n00B]

can you do a MemTest?

 

run with one stick of RAM

Ok, I'll try that in the morning.

[The Cool n00B]

can you do a MemTest?

 

run with one stick of RAM

Does it matter if the CPU is OCed to 4.4 ghz? It runs at 1.25v which another person with the same processor was able to get stable. I can increase the voltage and see if that helps

[dragoon20005]

Does it matter if the CPU is OCed to 4.4 ghz? It runs at 1.25v which another person with the same processor was able to get stable. I can increase the voltage and see if that helps

for troubleshooting purpose I may revert back to stock and monitor the BSOD

 

check the event log and see what the BlueScreen error says

[Akolyte]

Does it matter if the CPU is OCed to 4.4 ghz? It runs at 1.25v which another person with the same processor was able to get stable. I can increase the voltage and see if that helps

just revert everything to stock!  Because you got to rule out every cause till theres one left.

 

I recommend running memtest86 and updating your drivers, not only that but making sure all your drivers are installed and they are the correct drivers. 

[TDP_Equinox]

http://www.nirsoft.net/utils/blue_screen_view.html
Run that, maximize it, and take a screenshot.
Post that screenshot and hopefully that will tell me what is causing it.

[The Cool n00B]

for troubleshooting purpose I may revert back to stock and monitor the BSOD

 

check the event log and see what the BlueScreen error says

I've checked the event logs and windows can't start fanio.exe due to incompatibilities. fanio is located in SysWow64/drivers. That seems to come up alot.

 

WLAN-AutoConfig frequently returns Warnings.

 

AODDriver4.3 can't be found, frequent

 

I have one that critical, labeled "Kernel-Power" and it says that the system may have crashed.

 

I have some bugchecks:

The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000007e (0xffffffffc0000005, 0xfffff80002ea7622, 0xfffff880031fd598, 0xfffff880031fcdf0). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 080814-19219-01.

The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000007e (0xffffffffc0000005, 0xfffff80002eb9622, 0xfffff880031fd6d8, 0xfffff880031fcf30). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 080814-26769-01.

The computer has rebooted from a bugcheck.  The bugcheck was: 0x00000124 (0x0000000000000000, 0xfffffa800cd05028, 0x00000000b6000000, 0x0000000000100153). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 080714-23368-01.

 

DistributedCOM Error:

Unable to start a DCOM Server: {B3EDE298-AE75-4A1C-AB7E-1B9229B77BBE} as /. The error:

"740"

Happened while starting this command:

C:\PROGRA~2\COMMON~1\INSTAL~1\Driver\9\INTEL3~1\IDriver.exe -Embedding

 

volsnap Error:

The shadow copies of volume C: were deleted because the shadow copy storage could not grow in time.  Consider reducing the IO load on the system or choose a shadow copy storage volume that is not being shadow copied.

 

WHEA Logger Warning:

A corrected hardware error has occurred.

 

Reported by component: Processor Core

Error Source: Corrected Machine Check

Error Type: Cache Hierarchy Error

Processor ID: 5

 

The details view of this entry contains further information.

 

The details view has sensitive info.

 

That's it since they started. I did notice a pattern: blue screens are logged as kernel-power, but they don't have a specific event that causes them each time.

 

Here's to details view of the kernel-power:

- EventData

    BugcheckCode 30     BugcheckParameter1 0x0     BugcheckParameter2 0x0     BugcheckParameter3 0x0     BugcheckParameter4 0x0     SleepInProgress false     PowerButtonTimestamp

0

 

 

--------------------------------------------------------------------------

 

I ran memtest86 twice for 27 minutes. The first time, The pass got to 56% before I stopped it, was 11% on test 9, and had no errors. The second time I got to 49% on the pass, 54% on the test, and was on test8. No errors. The difference was that the first time, my cpu ws overclocked to 4.4 GHz and the second time it was on 3.5GHz, the stock speed. For the tests I also a fan cooling the mosfets, as they tend to get hot.

[SlayerOfHellWyrm]

That right there, is telling me a lot of things did not install correctly...

Is it a recent build, or an upgrade?

[The Cool n00B]

That right there, is telling me a lot of things did not install correctly...

Is it a recent build, or an upgrade?

Recent build, last week.

 

EDIT: I installed all of my drivers off the dvd except for the GPU drivers, I have the latest ones.

[SlayerOfHellWyrm]

Recent build, last week.

 

EDIT: I installed all of my drivers off the dvd except for the GPU drivers, I have the latest ones.

All drivers should be off the manufacturer's website so you have the latest. Assuming no parts were re-used, and you don't have much hardware installed, I'd honestly do a fresh OS installation. Keep everything stock, no overclocking, and don't really install any software until you know it's all stable.

What I'd recommend, is once you have it up, and running, get Prime95, HWMonitor, CPU-Z, and a browser other than IE. (Yes I realize this contradicts what I said about not installing anything, but I'll get to that). Once you have the OS up, run Memtest86, and see if it passes. If it doesn't, you may have a RAM issue. Going from there, if the first pass works, then, get all f the latest drivers, and repeat the process. If it passes, move on to installing HWMonitor, and CPU-Z. Have them running, while you run 2, Prime95 tests. Small FFT's, to test your CPU, monitoring temps and everything as that runs. Then, blend to test your RAM further. I suggest running both for 12 hours and hoping nothing happens. If all of that passes just fine, you should be good to go about installing other software.

EDIT: No beta drivers for anything until you've had ti working without issue for at least a week, in my opinion.

[The Cool n00B]

All drivers should be off the manufacturer's website so you have the latest. Assuming no parts were re-used, and you don't have much hardware installed, I'd honestly do a fresh OS installation. Keep everything stock, no overclocking, and don't really install any software until you know it's all stable.

What I'd recommend, is once you have it up, and running, get Prime95, HWMonitor, CPU-Z, and a browser other than IE. (Yes I realize this contradicts what I said about not installing anything, but I'll get to that). Once you have the OS up, run Memtest86, and see if it passes. If it doesn't, you may have a RAM issue. Going from there, if the first pass works, then, get all f the latest drivers, and repeat the process. If it passes, move on to installing HWMonitor, and CPU-Z. Have them running, while you run 2, Prime95 tests. Small FFT's, to test your CPU, monitoring temps and everything as that runs. Then, blend to test your RAM further. I suggest running both for 12 hours and hoping nothing happens. If all of that passes just fine, you should be good to go about installing other software.

EDIT: No beta drivers for anything until you've had ti working without issue for at least a week, in my opinion.

Will reinstalling Windows delete my program files and my directory changes? I use a separate internal storage drive with windows installed on an SSD. I've changed a lot of locations, to instead of My Pictures being on the SSD, they're on the HDD.

 

EDIT: Also, I've already used prime for my overclock for 30 min and it's completely stable, with Core Temp and CPU-Z for monitoring. No blue screens since OP, cross your fingers! It might have been the OC, though.

[SlayerOfHellWyrm]

Well, yes, you'd have to set all that up again.

[The Cool n00B]

Well, yes, you'd have to set all that up again.

Is it possible that the mosfets were overheating? They were getting hot to the touch.

[SlayerOfHellWyrm]

They will almost always be somewhat hot to the touch. However, if that was the issue, you'd have a slew of different errors going on.

[The Cool n00B]

They will almost always be somewhat hot to the touch. However, if that was the issue, you'd have a slew of different errors going on.

To avoid going setup again, I've decided to stress test first for an hour or two and see if that's stable. Then I'll mine for dogecoins or something to max out gpu. If thats stable, I'll fold to put it all together. If at the end of that it's not stable, I'll reinstall windows like you said. Anyways, 30 min down in prime, so far so good, temps peeking at 34 degrees C.

[The Cool n00B]

Thanks to anyone who help me out. The issue was an unstable OC.