Solved Various BSODs during startup and/or within early usage.

[Mitim0]

Hello,

Recently I’ve been a variety of strange issues which usually result in bluescreens. It usually happens while I’m just browsing the internet or digging around in my files. My mouse freezes or lags behind a bit and I know within the next second, I’m about to get a bluescreen. It doesn’t happen during any major games or running any major programs –but I don’t really get much of a chance to run anything big. The chance of this happening is higher just off a cold boot –when I start/use my computer for the first time during the day.

After the bluescreen, what happens next varies, such as (but not always):

I’ve had my computer have trouble to boot after getting the bluescreen: Press switch, fans spin up and nothing shows up on screen. Power off, try again, then it works. I suspect that if I try to power on right after powering off it has trouble. Waiting a bit longer (a few more seconds) and it seems okay.

It boots, but then my bios tells me my overclocking settings are bad and prompts me to set my bios settings back to default. This is a bit amusing/odd as I don’t have anything overclocked and my bios settings are already default (with exception of the floppy drive turned off). I usually oblige anyways and reset everything to default.

Windows looks like it might load...the loading screen appears with the words “windows” but the animated logo never appears. It just hangs here until I power off and try again.

It manages to boot in to windows, but after I type in my password, login, and get to my desktop, I get an instant bluescreen. Sometimes, I don’t even get to type in my password. =_=

If I try safemode, sometimes I get in and it bluescreens after a short while. Or sometimes it’ll bluescreen right away.

Windows repair attempts to repair for a long time before giving up (says it can’t find anything wrong). It also prompts me to try system restore which has worked once in getting me back to my desktop...only to bluescreen again after a short time of usage.


Thing’s I’ve done:

First, I’ve updated my video card drivers and ran windows update.

Tried to boot in to my other windows partition (winXP), it bluescreens as well.

I figure maybe it’s hardware as I can’t even make it in to windows some of the time and seems to happen to both win7 and xp, where I haven’t touched my xp partition for a quite long time. So, I test my ram with memtest86+ and I get red errors. I have four sticks of ram, 1gb each so I pull each one out and test one by one. Each one passes after running for all ten tests. I also try different slots one at a time and don’t see any issues. I try all four sticks together again and I get no issues. As a side note: I also make sure to plug them in, in the same order and facing direction (just to be consistent). The system is just over five years old and all sticks of ram were from the same batch, so I doubt it is ram compatibility errors (though at this point I really don’t know what to look at).

I’ve also reinstalled windows7.

At this point, I should mentioned that this isn’t the first time I’ve encountered the above, but after pulling my ram and putting it back in as well as reinstalling windows, it seemed to have solved the issue a month or so back.

But it seems the problem has reared its ugly head again and this time reseating my ram and going through memtest does nothing. I don’t really want to reinstall windows again (both of these, I suspect it was just a ‘magical temporary fix’ anyway). And when I do get to my desktop every so often and can use my computer, I’m afraid it’ll bluescreen so I’m hesitant to do any work on it. And it happens to be my main working computer. =/

I can’t seem to find any pattern and I don’t really know what to try next so here I am. I’m hoping someone can shed some light on what could be the cause, so at least I’ll know if I need a new computer or not. =b

In the attached files, there are only five minidumps which are the ones that happen when I reach the desktop. But I’ve seen more then five; there are a few bluescreens I get that don’t seem to ‘dump’.

 

[koolkat77]

I'm thinking you need a new PC

Please run these tests and report back the results

1. SFC /scannow to check windows for corruption - http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html
2. Disk check for errors on the hard drive - http://www.sevenforums.com/tutorials/433-disk-check.html
3. Troubleshoot applications by a clean boot - http://www.sevenforums.com/tutorial...ation-conflicts-performing-clean-startup.html
4. Memtest86+ paying close attention to part 3 - http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html.

If you know which RAM stick is causing errors then remove it and tell us if it still BSOD's.

Hard Drive/Storage

Post a screen shot using Crystal Disk Info: CrystalDiskInfo Standard Edition

How to Upload and Post a Screenshot and File in Seven Forums

Make a hard drive test from the hard drive manufacturers website: Hard Drive Diagnostic Procedure

Have you checked for BIOS and other firmware updates?

[B]BIOS Version/Date	American Megatrends Inc. 0603, 03/07/2007[/B]

Peruse these links and tell us if they help:
Thermal Paste and How To Use It | techPowerUp
Avoid Static Damage to Your PC | PCWorld
Power Supply Information and Selection - Tech Support Forum
Basic computer troubleshooting
How To Clear CMOS
How to clean your PC of dust and dirt
How to clean a computer

Have a read through this:

What you are experiencing is a TDR event (Timeout Detection & Recovery). There are many causes of these events, mostly hardware related. Please read my checklist below and see if you can diagnose your particular cause.

A couple of things jump out immediately. Your specs say you have 5GB of RAM, an odd number. That suggests that you added some RAM at some point. Mismatched or failing RAM modules can cause TDRs. You might want to test those sticks one at a time in Slot 1 before anything else. RAM problems can explain some of your other issues too.

Looking at some of your other posts I see you are running dual monitors also. This could be exposing a defect in your 9500GT that is triggering the TDRs. You should test with only one monitor attached to see if this is the case.

You are running lots of stuff on that box, so I would be as deliberate as possible in doing the diagnostic work.

*******
"Display driver xxxxx stopped responding and was recovered"

Timeout Detection & Recovery (TDR) = "Display Driver Stopped Responding and was Recovered" is a useful feature that started in Vista and is also in W7 that allows the OS to try and recover from a video timeout so that the system does not crash to a bluescreen. Symptoms included a screen flash with the TDR message appearing one or more times or the screen blinking out to black. If the system cannot recover it will crash (Stop Error 116 typical). The issue is that the video card is not responding as expected. The solution is in the: why?

There is no one-size-fits-all solution to TDR errors. But the problem is usually found in the local environment (your computer). Finding the cause is a matter of checking every possible cause and uncovering the culprit through a simple process of elimination. By methodically running down a checklist of diagnostic procedures you should be able to find the cause and can correct it.

There are numerous reports of hardware solutions to TDR's. The most common are:

• Poor Cooling
• Problems with the power supply
• Overclocking Issues
• Bad System memory or incorrect memory timings
• Defective PC Components

The order you do the diagnostics is not all that important. My personal strategy is to do the cheap & easy stuff first, the cheap & harder stuff next, and then the stuff that costs last. But whatever order you do it in you need to check or confirm the following:

SOFTWARE
Poorly written software and games will cause TDRs. But if this were the case it would affect lots of people, not just a few. Check the game's website & forums for patches and tips.
See if other people in the forums are having the same problem and if they were able to solve it and how.
You could also be asking too much of your video card. Check to see if your video card is tested and recommended for the game/program. Test the game at reduced settings.

WHAT ACTIONS CAUSE THE PROBLEM
It helps if you can isolate the actions that trigger the TDR. Most often it will be an application using 3D graphics. But if the incidents occur constantly it would point more towards defective hardware. If it happens more specifically (just when running Game X) it points towards overheating, settings, software, or driver issues.

GENERAL SYSTEM PERFORMANCE
You need to eliminate the possibility that your computer has a global problem. You can use a program like Prime95 to stress test your system. Free Software - GIMPS
You can run the "Stress Test" for a few hours or overnight. This will not tell you what the problem is, but it is helpful to uncover any issues your system has with instability and cooling.

OVERHEATING
Running a video intensive game for hours can generate some serious heat and overheating will cause video errors. You can check your temps by looking at your BIOS readings or use a free program like Speedfan SpeedFan - Access temperature sensor in your computer .
A real easy test is to just pull the side panel(s) off your case (You can also blow a house fan directly into the open case) and see if the problem goes away or gets better. If it does then the issue is definitely overheating. If you are overheating you need to look at installing some cooling upgrades. You want to look at ventilating the case (more or bigger fans), Upgrade your case to a larger gaming case (lots of fans, water-cooling), etc.
There are free utilities like BurninTest PassMark BurnInTest software - PC Reliability and Load Testing that you can use to test your system's cooling capability. Caution is recommended using these types of programs.

VIDEO DRIVERS
Bad drivers happen and they can get corrupted. Before installing or reinstalling any video drivers first completely uninstall all video software and the drivers. (Some people say to run a cleaner program from safe mode, some say this is unnecessary). Never rely on the driver package to overwrite the old drivers. Also: Delete the video driver folder (ex: C:\NVIDIA) in Windows Explorer (or windows may install the same drivers again!).
After uninstalling the old drivers and rebooting Windows 7 will install it's own WDDM 1.1 driver. Check for the video problem while using the generic Windows driver.
You can then install the latest drivers for your card (or try older drivers).
See This Tutorial: http://www.sevenforums.com/tutorials/43216-installing-updating-drivers-7-a.html#post414637

DEVICE MANAGER
Look in Device Manager and make sure there are no problem devices (yellow ! icon). Correct these by loading the correct drivers or disable the problem device and see if the video problem goes away.

POOR CONNECTIONS
Reseat video card and memory modules. Make sure the contacts are clean. Check all the electrical connections.

CHECK YOUR MOTHERBOARD VOLTAGES
In BIOS, check the listed voltages against the manufacturer recommended specs. Reset the voltages to factory defaults and see if the video problems disappear.

MEMORY
Memory errors can cause video problems. Run a program like Memtest86+ for at least 3 passes to see if there are any memory errors. Memtest86+ - Advanced Memory Diagnostic Tool .
You can also test for a bad memory module by installing one stick and testing, and then switch it out for the next stick, etc.

OVERCLOCKING
Overclocking can be a trial and error process. The clocks and/or multipliers you set or change for CPU, Memory, or GPU could be unstable. Eliminate this as a possibility by resetting these to their defaults to see if that clears the video problems. The simplest way to do this is to "Restore Bios Defaults", or Clear CMOS.

UNDERCLOCKING
Some people have reported that by going into the video cards control panel and "down-clocking" the cards performance settings they were able to clear up the TDRs. Since W7 does not seem to tolerate any hiccups in the GPU, this would allow you to run a poor perforning card in the W7 enviroment.
So for instance, you could set the GPU clock from a 777 MHz factory setting to 750MHz, and the ram clock from a 1126MHz factory setting to 1050Mhz, or similar small change for your particular card.

BIOS
Check for and install an updated BIOS, particularly if it says the newer BIOS corrects memory errors or bug fixes. You could also try loading the BIOS defaults.
While you are there, check the motherboard manufacturers forums to see if others are having issues with the same board.

WINDOWS POWER MANAGEMENT
Eliminate Power Management settings as a possible cause, especially if you are working with a laptop. These settings could be particularly important if the issue is in playing games.
Go to Control Panel > Hardware & Sound > Power Options. Under "Select a Power Plan" you will find that "Balanced" is the default setting.
At the bottom you will see a Down arrow next to "Show Additional Plans". Click that and select "High Performance". See if the TDR issue is affected.
Alternately, you can click "Change Plan Settings" next to the "Balanced" plan and change the setting to "Never" put the computer to sleep (This is the default on a desktop) and/or change when the display is turned off as a test.

POWER SUPPLY
You need to know that your power supply is delivering sufficient power. Power supply problems are the most common cause of video problems, especially using high end cards.
Check the power supply's amperage ratings. Be sure it has the ample amperage for your video card and the rest of the system.
Test the supply with multimeter to measure for a steady 12v to the card's power connectors. (The only true way to test a power supply would be to use the very expensive diagnostic equipment used in labs). But for us regular folks: I tested my power supply by hooking up my multimeter to the PCI-E connectors that I was using to power my video card (I used a spare pair from the power supply to run the card while I was testing). I then observed the meter while I used the computer, first watching the voltage, then the amps, to see if there was any drop-off or erratic behavior while booting or using the computer. My readings were rock solid. So I declared my power supply good.
Otherwise you need to replace the supply to eliminate this possibility. Or borrow one from another computer.

VIDEO CARD
I suspect that a video card must perform flawlessly to operate in a Windows 7 environment and run the most recent games. If you tried all the above diagnostics and no problems were found then that leaves you with only one possibility: a defective video card. Some brands have the problem more consistently than others. You could check their forums for clues.
You could try your card in another computer running W7 to see if the problem goes along with the card.
You could try a different card in your computer. I bought an inexpensive card to use. My TDR's disappeared using a "lesser" card. Or borrow a card from another computer.
Otherwise RMA or replace the card.

TDR complaints have come from PC owners running virtually every PC configuration. They occur regardless of which video engine, manufacturer, driver, or system used. They are too numerous to write off as a random problem, but at the same time if people are getting their systems to run correctly using the same hardware and software that you are then it follows that your problem must be solvable.

More Info Here:
Timeout Detection and Recovery of GPUs through WDDM
NVIDIA Statement on TDR Errors - NVIDIA Forums
27116: ATIKMDAG has stopped responding error message

 

[Mitim0]

Hi koolkat77,
Thanks for reading my long post. =b

System File Checker didn't find anything wrong. The exact results are:

Beginning system scan. This process will take some time.
Beginning verification phase of system scan.
Verification 100% complete.
Windows Resource Protection did not find any integrity violations.
​

Disk checks also don't come up with anything either. I did check the bios if there was an update for issues, but all of the updates listed seem to just add support for new cpus for that motherboard. Didn't seem relevant so I didn't update. I couldn't find any evidence of issues though like mine.

When I run memtest86+, I just let it run from test 1 to 10 until it says something along the lines of "Pass complete, no errors found. Press esc to exit". Is this actually just one pass and I should let it run longer? One pass may not be a thorough " test" ?

I should also add that if I can make it through the first hour or so of normal usage, I *think* my system is fine for the day -I can play games, videos, browse the net, work, etc. Currently I've been using it for eight hours now. I guess one of the restarts managed to make it through all the 'hoops' and not crash? Could there be possibly something to do with a cold start when I turn on my computer the next day? I shall try more passes on memtest86+ tomorrow when there is an increased chance of these issues happening again.

I believe (hope) my hard drives are okay... Crystal Disk Info screenshots are attached and they seem fine. I have three physical drives, spread out over six letters. =b

 

[koolkat77]

They look fine. Keep us posted of the rest of the steps.

 

[Mitim0]

Well, after some time, it seems my ram is okay. I tested each stick on it's own 4-5 passes in different slots and then all sticks together for 5 passes. This makes me doubt it is my ram. Hrm, not quite sure what else to look at. I've tried running a video card benchmark and it's worked fine as well. :huh:

Maybe...it is windows after all. :huh:

Added my latest minidump.

 

[koolkat77]

I think its your RAM. Have you seen part 3 of the tutorial?

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {41289, 75001, 97, ce000000075015}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4a99 )

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041289, The subtype of the bugcheck.
Arg2: 0000000000075001
Arg3: 0000000000000097
Arg4: 00ce000000075015

Debugging Details:
------------------


BUGCHECK_STR:  0x1a_41289

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  SearchProtocol

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002b1d6dd to fffff80002ac6c00

STACK_TEXT:  
fffff880`0729f978 fffff800`02b1d6dd : 00000000`0000001a 00000000`00041289 00000000`00075001 00000000`00000097 : nt!KeBugCheckEx
fffff880`0729f980 fffff800`02afab9a : 89700000`968ae005 fffffa80`05726330 00000000`00000a50 fffff8a0`0011f8b8 : nt! ?? ::FNODOBFM::`string'+0x4a99
fffff880`0729f9c0 fffff800`02a91b61 : fffffa80`045cab00 fffffa80`05f5a060 00000000`00000000 89700000`968ae005 : nt!MiGetPageProtection+0xaa
fffff880`0729fa00 fffff800`02a917fa : fffffa80`05726330 fffffa80`0601e060 fffffa80`0601e060 00000000`00075000 : nt!MiQueryAddressState+0x2b1
fffff880`0729fa50 fffff800`02da18d4 : fffff880`00000002 00000000`00076000 fffffa80`05726330 fffff880`00000000 : nt!MiQueryAddressSpan+0xaa
fffff880`0729fac0 fffff800`02ac5e93 : 00000000`00000a50 fffffa80`05f5a060 fffff880`0729fbf8 00000000`050be138 : nt!NtQueryVirtualMemory+0x382
fffff880`0729fbb0 00000000`76d8154a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`050be118 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76d8154a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+4a99
fffff800`02b1d6dd cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+4a99

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  5147d9c6

FAILURE_BUCKET_ID:  X64_0x1a_41289_nt!_??_::FNODOBFM::_string_+4a99

BUCKET_ID:  X64_0x1a_41289_nt!_??_::FNODOBFM::_string_+4a99

Followup: MachineOwner
---------

Do a http://www.sevenforums.com/tutorials/219487-clean-reinstall-factory-oem-windows-7-a.html if required.

 

[Mitim0]

Yes, I looked at part 3 "Part 3: If You Have Errors", but I can't get any of my sticks of ram to show up with any errors even after multiple passes right now. I kind of wish I could... then at least I have something to go on. Interestingly today my system was fine...but on the next day...who knows. I have reinstalled win7 from my original cd somewhat recently and would rather avoid doing it again, but I guess if the cause really is windows, then I'll have to. Just need to figure out a way of knowing the real cause. =/ I'll post back if/when it blue screens again if anything new pops up.

 

[koolkat77]

Okay

 

[Mitim0]

Just when I thought maybe the worst of it was over...after a few days, I got two bluescreens, both within 10-15 mins of getting to the desktop. In between rebooting, the bios at one point said it didn't recognise my cpu. *_* Rebooting after it said that was okay though. Very...weird.

Attached are the two new dump files. What program can be used to read them?

 

[koolkat77]

Here's what you have to install: http://www.sevenforums.com/crash-lo...d-analysis-getting-started-5.html#post2251058
Here's a guide on how I do it: http://www.sevenforums.com/crash-lockup-debug-how/277355-debugging-bsod-my-way.html

I'll check your dumps and post what I think about it. I've also requested two of my hardware friends and a senior bsod analyst to take a look at your thread.

 

[koolkat77]

I think I'd just wait to hear why my friends have to say about it.

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 7F, {8, 80050031, 6f8, fffff80002adfe28}

Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )

Followup: MachineOwner
---------

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault).  The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
        use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
        use .trap on that value
Else
        .trap on the appropriate frame will show where the trap was taken
        (on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
Arg2: 0000000080050031
Arg3: 00000000000006f8
Arg4: fffff80002adfe28

Debugging Details:
------------------


BUGCHECK_STR:  0x7f_8

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  iexplore.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff880070c38f0 -- (.trap 0xfffff880070c38f0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000007fffffffff rbx=0000000000000000 rcx=fffff68000000000
rdx=ffff080000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002ae041c rsp=fffff880070c3a80 rbp=fffff880070c3b00
 r8=fffff70001080060  r9=fffff6fb80008400 r10=fffff70001000000
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
nt!MmAccessFault+0x5fc:
fffff800`02ae041c a16000080100f7ffff mov   eax,dword ptr [FFFFF70001080060h] ds:fffff700`01080060=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002ad31a9 to fffff80002ad3c00

STACK_TEXT:  
fffff880`009eec68 fffff800`02ad31a9 : 00000000`0000007f 00000000`00000008 00000000`80050031 00000000`000006f8 : nt!KeBugCheckEx
fffff880`009eec70 fffff800`02ad1672 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`009eedb0 fffff800`02adfe28 : 00000000`00000000 00000000`00000000 fffff880`070c30a0 fffff800`02ad1d2e : nt!KiDoubleFaultAbort+0xb2
fffff880`070c3000 fffff800`02ad1d2e : 00000000`00000000 00000000`00000000 00000000`00000000 fffff6fb`7dbee000 : nt!MmAccessFault+0x8
fffff880`070c3020 fffff800`02ae041c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
fffff880`070c31b0 fffff800`02ad1d2e : 00000000`00000000 fffff700`01080060 00000000`00000000 fffff6fb`7dbee000 : nt!MmAccessFault+0x5fc
fffff880`070c3310 fffff800`02ae041c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
fffff880`070c34a0 fffff800`02ad1d2e : 00000000`00000000 fffff700`01080060 00000000`00000000 fffff6fb`7dbee000 : nt!MmAccessFault+0x5fc
fffff880`070c3600 fffff800`02ae041c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
fffff880`070c3790 fffff800`02ad1d2e : 00000000`00000000 fffff700`01080060 00000000`00000000 fffff6fb`7dbee000 : nt!MmAccessFault+0x5fc
fffff880`070c38f0 fffff800`02ae041c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
fffff880`070c3a80 fffff800`02ad1d2e : 00000000`00000000 fffff700`01080060 00000000`00000000 fffff6fb`7dbee000 : nt!MmAccessFault+0x5fc
fffff880`070c3be0 fffff800`02ae041c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
fffff880`070c3d70 fffff800`02ad1d2e : 00000000`00000000 fffff700`01080060 00000000`00000000 fffff6fb`7dbee000 : nt!MmAccessFault+0x5fc
fffff880`070c3ed0 fffff800`02ae041c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
fffff880`070c4060 fffff800`02ad1d2e : 00000000`00000000 fffff700`01080060 00000000`00000000 fffff6fb`7dbee000 : nt!MmAccessFault+0x5fc
fffff880`070c41c0 fffff800`02ae041c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
fffff880`070c4350 fffff800`02ad1d2e : 00000000`00000000 fffff700`01080060 00000000`00000000 fffff6fb`7dbee000 : nt!MmAccessFault+0x5fc
fffff880`070c44b0 fffff800`02ae041c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
fffff880`070c4640 fffff800`02ad1d2e : 00000000`00000000 fffff700`01080060 00000000`00000000 fffff6fb`7dbee000 : nt!MmAccessFault+0x5fc
fffff880`070c47a0 fffff800`02ae041c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
fffff880`070c4930 fffff800`02ad1d2e : 00000000`00000000 fffff700`01080060 00000000`00000000 fffff6fb`7dbee000 : nt!MmAccessFault+0x5fc
fffff880`070c4a90 fffff800`02ae041c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
fffff880`070c4c20 fffff800`02ad1d2e : 00000000`00000000 fffff700`01080060 00000000`00000000 fffff6fb`7dbee000 : nt!MmAccessFault+0x5fc
fffff880`070c4d80 fffff800`02ae041c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
fffff880`070c4f10 fffff800`02ad1d2e : 00000000`00000000 fffff700`01080060 00000000`00000000 fffff6fb`7dbee000 : nt!MmAccessFault+0x5fc
fffff880`070c5070 fffff800`02ae041c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
fffff880`070c5200 fffff800`02ad1d2e : 00000000`00000000 fffff700`01080060 00000000`00000000 fffff6fb`7dbee000 : nt!MmAccessFault+0x5fc
fffff880`070c5360 fffff800`02ae041c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
fffff880`070c54f0 fffff800`02ad1d2e : 00000000`00000000 fffff700`01080060 00000000`00000000 fffff6fb`7dbee000 : nt!MmAccessFault+0x5fc
fffff880`070c5650 fffff800`02ae041c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
fffff880`070c57e0 fffff800`02ad1d2e : 00000000`00000000 fffff700`01080060 00000000`00000000 fffff6fb`7dbee000 : nt!MmAccessFault+0x5fc
fffff880`070c5940 fffff800`02ae041c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
fffff880`070c5ad0 fffff800`02ad1d2e : 00000000`00000000 fffff700`01080060 00000000`00000000 fffff6fb`7dbee000 : nt!MmAccessFault+0x5fc
fffff880`070c5c30 fffff800`02ae041c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
fffff880`070c5dc0 fffff800`02ad1d2e : 00000000`00000000 fffff700`01080060 00000000`00000000 fffff6fb`7dbee000 : nt!MmAccessFault+0x5fc
fffff880`070c5f20 fffff800`02ae041c : 004c005c`00530045 0043005c`0057004f 00450054`004e004f 0049002e`0054004e : nt!KiPageFault+0x16e
fffff880`070c60b0 fffff800`02ad1d2e : 00000000`00000000 fffff700`01080060 0049004d`005c0000 fffff6fb`7dbee000 : nt!MmAccessFault+0x5fc
fffff880`070c6210 fffff800`02ae041c : 00520045`00530055 00490054`005c0053 00500041`005c004d 00540041`00440050 : nt!KiPageFault+0x16e
fffff880`070c63a0 fffff800`02ad1d2e : 00000000`00000000 fffff700`01080060 005c004c`00410000 fffff6fb`7dbee000 : nt!MmAccessFault+0x5fc
fffff880`070c6500 fffff800`02ae041c : 00310038`00310042 00420039`00440051 004f004c`003b005c 00440045`00470047 : nt!KiPageFault+0x16e
fffff880`070c6690 fffff800`02ad1d2e : 00000000`00000000 fffff700`01080060 0053004a`002e0000 fffff6fb`7dbee000 : nt!MmAccessFault+0x5fc
fffff880`070c67f0 fffff800`02ae041c : 004d0049`0054005c 00500050`0041005c 00410054`00410044 0041004f`0052005c : nt!KiPageFault+0x16e
fffff880`070c6980 fffff800`02ad1d2e : 00000000`00000000 fffff700`01080060 005d0032`005b0000 fffff6fb`7dbee000 : nt!MmAccessFault+0x5fc
fffff880`070c6ae0 fffff800`02ae041c : 0057004f`004c005c 004e004f`0043005c 0054004e`00450054 00350045`0049002e : nt!KiPageFault+0x16e
fffff880`070c6c70 fffff800`02ad1d2e : 00000000`00000000 fffff700`01080060 00410039`00380000 fffff6fb`7dbee000 : nt!MmAccessFault+0x5fc
fffff880`070c6dd0 fffff800`02ae041c : 00440044`00520041 0056004b`00530049 004d0055`004c004f 0055005c`00340045 : nt!KiPageFault+0x16e
fffff880`070c6f60 fffff800`02ad1d2e : 00000000`00000000 fffff700`01080060 00350045`00490000 fffff6fb`7dbee000 : nt!MmAccessFault+0x5fc
fffff880`070c70c0 fffff800`02ae041c : 00520045`00530055 00490054`005c0053 00500041`005c004d 00540041`00440050 : nt!KiPageFault+0x16e
fffff880`070c7250 fffff800`02ad1d2e : 00000000`00000000 fffff700`01080060 00540045`004e0000 fffff6fb`7dbee000 : nt!MmAccessFault+0x5fc
fffff880`070c73b0 fffff800`02ae041c : 00410030`00310041 00430043`00430043 00440042`00420045 005c0000`00350046 : nt!KiPageFault+0x16e
fffff880`070c7540 fffff800`02ad1d2e : 00000000`00000000 fffff700`01080060 004d0055`004c0000 fffff6fb`7dbee000 : nt!MmAccessFault+0x5fc
fffff880`070c76a0 fffff800`02ae041c : 00540046`004f0053 00590052`0043005c 0045004e`00540050 004c0052`00550054 : nt!KiPageFault+0x16e
fffff880`070c7830 fffff800`02ad1d2e : 00000000`00000000 fffff700`01080060 004c005c`00530000 fffff6fb`7dbee000 : nt!MmAccessFault+0x5fc
fffff880`070c7990 fffff800`02ae041c : 0055005c`00340045 00530052`00450053 004d0049`0054005c 00500050`0041005c : nt!KiPageFault+0x16e
fffff880`070c7b20 fffff800`02ad1d2e : 00000000`00000000 fffff700`01080060 00450054`004e0000 fffff6fb`7dbee000 : nt!MmAccessFault+0x5fc
fffff880`070c7c80 fffff800`02ae041c : 0034003d`00440052 00330039`00310036 003b0031`00300034 0045004c`00490054 : nt!KiPageFault+0x16e
fffff880`070c7e10 fffff800`02ad1d2e : 00000000`00000000 fffff700`01080060 003d0054`004e0000 fffff6fb`7dbee000 : nt!MmAccessFault+0x5fc
fffff880`070c7f70 fffff800`02ae041c : 00200059`00520041 00450054`004e0049 00540045`004e0052 004c0049`00460020 : nt!KiPageFault+0x16e
fffff880`070c8100 fffff800`02ad1d2e : 00000000`00000000 fffff700`01080060 0054004e`00450000 fffff6fb`7dbee000 : nt!MmAccessFault+0x5fc
fffff880`070c8260 fffff800`02ae041c : 004d0045`0054005c 00410052`004f0050 00490020`00590052 00520045`0054004e : nt!KiPageFault+0x16e
fffff880`070c83f0 fffff800`02ad1d2e : 00000000`00000000 fffff700`01080060 00000000`0000a400 fffff6fb`7dbee000 : nt!MmAccessFault+0x5fc
fffff880`070c8550 fffff800`02ae041c : 00000000`00000001 fffffa80`047e3ef0 fffffa80`047d16a8 fffff880`010cd656 : nt!KiPageFault+0x16e
fffff880`070c86e0 fffff800`02ad1d2e : 00000000`00000000 fffff700`01080060 00380034`00001000 fffff6fb`7dbee000 : nt!MmAccessFault+0x5fc
fffff880`070c8840 fffff800`02ae041c : 00000000`00000001 fffffa80`047dfe00 fffffa80`05bac0e0 fffff800`02a1a156 : nt!KiPageFault+0x16e
fffff880`070c89d0 fffff800`02ad1d2e : 00000000`00000000 fffff700`01080060 fffffa80`060ac000 fffff6fb`7dbee000 : nt!MmAccessFault+0x5fc
fffff880`070c8b30 fffff800`02ae041c : 00000000`00000001 00000000`00000001 fffff900`c1020b70 fffff960`0012d9ec : nt!KiPageFault+0x16e
fffff880`070c8cc0 fffff800`02ad1d2e : 00000000`00000000 fffff700`01080060 00000000`00000000 fffff6fb`7dbee000 : nt!MmAccessFault+0x5fc
fffff880`070c8e20 fffff800`02ae041c : 00000000`00000046 fffff800`02ac9612 00000000`000c7050 fffff960`0012786d : nt!KiPageFault+0x16e
fffff880`070c8fb0 fffff800`02ad1d2e : 00000000`00000000 fffff700`01080060 00000000`043be500 fffff6fb`7dbee000 : nt!MmAccessFault+0x5fc
fffff880`070c9110 fffff800`02ae041c : fffffa80`047d01a0 00000000`7746136a fffffa80`047d16a8 fffffa80`05eb23f8 : nt!KiPageFault+0x16e
fffff880`070c92a0 fffff800`02ad1d2e : 00000000`00000000 fffff700`01080060 00000000`00000000 fffff6fb`7dbee000 : nt!MmAccessFault+0x5fc
fffff880`070c9400 fffff800`02ae041c : fffffa80`047d13f0 fffffa80`047e5e80 fffffa80`047dd1b0 fffffa80`05eb2010 : nt!KiPageFault+0x16e
fffff880`070c9590 fffff800`02ad1d2e : 00000000`00000000 fffff700`01080060 fffffa80`047e5e00 fffff6fb`7dbee000 : nt!MmAccessFault+0x5fc
fffff880`070c96f0 fffff800`02ae041c : fffff980`01275360 fffff980`01275388 fffff980`012753b0 fffff980`012753d8 : nt!KiPageFault+0x16e


STACK_COMMAND:  kb

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

FOLLOWUP_NAME:  MachineOwner

DEBUG_FLR_IMAGE_TIMESTAMP:  5147d9c6

FOLLOWUP_IP: 
nt!KiDoubleFaultAbort+b2
fffff800`02ad1672 90              nop

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  nt!KiDoubleFaultAbort+b2

FAILURE_BUCKET_ID:  X64_TRAP_FRAME_RECURSION

BUCKET_ID:  X64_TRAP_FRAME_RECURSION

Followup: MachineOwner
---------

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff960002b92e5, fffff880095c0f40, 0}

Probably caused by : memory_corruption

Followup: memory_corruption
---------

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff960002b92e5, Address of the instruction which caused the bugcheck
Arg3: fffff880095c0f40, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

Debugging Details:
------------------


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
win32k!DEVLOCKOBJ::bMapTrgSurfaceView+75
fffff960`002b92e5 f60070          test    byte ptr [rax],70h

CONTEXT:  fffff880095c0f40 -- (.cxr 0xfffff880095c0f40)
rax=0000000000000000 rbx=fffff880095c1ba8 rcx=fffff900c00b6cc0
rdx=fffff880095c1ba8 rsi=0000000000000000 rdi=fffff900c00b6cc0
rip=fffff960002b92e5 rsp=fffff880095c1920 rbp=fffff880095c1a30
 r8=fffff900c3745010  r9=000000000000024e r10=00000000000006ea
r11=fffff880095c1900 r12=fffff880095c1a30 r13=0000000000000000
r14=fffff96000382b50 r15=fffff96000382b30
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
win32k!DEVLOCKOBJ::bMapTrgSurfaceView+0x75:
fffff960`002b92e5 f60070          test    byte ptr [rax],70h ds:002b:00000000`00000000=??
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

BUGCHECK_STR:  0x3B

PROCESS_NAME:  conhost.exe

CURRENT_IRQL:  0

MISALIGNED_IP: 
win32k!DEVLOCKOBJ::bMapTrgSurfaceView+75
fffff960`002b92e5 f60070          test    byte ptr [rax],70h

LAST_CONTROL_TRANSFER:  from 0000000000000001 to fffff960002b92e5

STACK_TEXT:  
fffff880`095c1920 00000000`00000001 : fffff900`c00c0010 fffff960`00382b60 fffff900`c37704e0 00000197`000002d5 : win32k!DEVLOCKOBJ::bMapTrgSurfaceView+0x75
fffff880`095c1950 fffff900`c00c0010 : fffff960`00382b60 fffff900`c37704e0 00000197`000002d5 00000000`00000001 : 0x1
fffff880`095c1958 fffff960`00382b60 : fffff900`c37704e0 00000197`000002d5 00000000`00000001 fffff960`00158637 : 0xfffff900`c00c0010
fffff880`095c1960 fffff900`c37704e0 : 00000197`000002d5 00000000`00000001 fffff960`00158637 fffff900`c37704e0 : win32k!`string'+0x10
fffff880`095c1968 00000197`000002d5 : 00000000`00000001 fffff960`00158637 fffff900`c37704e0 fffff880`095c1a30 : 0xfffff900`c37704e0
fffff880`095c1970 00000000`00000001 : fffff960`00158637 fffff900`c37704e0 fffff880`095c1a30 00000000`00000000 : 0x00000197`000002d5
fffff880`095c1978 fffff960`00158637 : fffff900`c37704e0 fffff880`095c1a30 00000000`00000000 fffff880`095c1ba8 : 0x1
fffff880`095c1980 fffff960`0014e54d : fffff900`c00c0010 00000000`00000000 fffff880`095c1ca0 fffff960`00148af8 : win32k!DEVLOCKOBJ::bLock+0x423
fffff880`095c19c0 fffff800`02abed9c : fffffa80`0466b790 00000000`00000000 00000000`00000020 fffffa80`043d2e60 : win32k!NtGdiFlushUserBatch+0xf9
fffff880`095c1c20 000007fe`fe96119a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceGdiTebAccess+0x25
00000000`0020f958 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x000007fe`fe96119a


CHKIMG_EXTENSION: !chkimg -lo 50 -db !win32k
20 errors : !win32k (fffff960002b9246-fffff960002b937e)
fffff960002b9240  fa  ff  48  8b  0d  af *00  0f  00  48  85  c9  74  0c *00  15 ..H......H..t...
fffff960002b9250  04  df  0b  00  ff  15 *00  e2  0b  00  48  83  c4  20 *00  c3 ..........H.. ..
fffff960002b9260  90  90  90  90  90  90 *00  90  90  90  90  90  90  90 *00  90 ................
fffff960002b9270  48  89  5c  24  08  48 *00  6c  24  10  48  89  74  24 *00  57 H.\$.H.l$.H.t$.W
...
fffff960002b92c0  eb  49  0f  ba  67  70 *00  73  1c  48  83  bf  e8  00  00  00 .I..gp.s.H......
fffff960002b92d0  00  74  12  48  8d  4b *00  e8  00  16  06  00  85  c0 *00  05 .t.H.K..........
fffff960002b92e0  0f  ba  6b  18  0a  f6 *00  70  10  74  12  48  8d  4b *00  e8 ..k....p.t.H.K..
fffff960002b92f0  28  d1  05  00  85  c0 *00  05  0f  ba  6b  18  0d  83 *00  01 (.........k.....
...
fffff960002b9340  01  00  00  00  0f  ba *00  24  0e  0f  83  92  01  00  00  f6 .......$........
fffff960002b9350  40  24  40  0f  84  88 *00  00  00  48  83  b8  e8  01  00  00 @[email protected]......
fffff960002b9360  00  0f  84  7a  01  00  00  83  b8  f0  01  00  00  00 *00  84 ...z............
fffff960002b9370  6d  01  00  00  f3  0f *00  80  b0  05  00  00  48  8b *00  f8 m...........H...

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  STRIDE

STACK_COMMAND:  .cxr 0xfffff880095c0f40 ; kb

FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_STRIDE

BUCKET_ID:  X64_MEMORY_CORRUPTION_STRIDE

Followup: memory_corruption
---------

 

[Mitim0]

and finally one more dump. I think I need to stop using this computer in the meantime and try again later. =/ (Thanks for taking a look at my dump files though).

 

[essenbe]

Hi Mitim0, and welcome to Seven forums. The indications point to memory corruption. But first, please go to your motherboards web site and download and install any updated drivers, especially chipset drivers. and make sure you are running the latest bios. Please go into bios and there should be a section called Hardware monitor or some thing similar. Please give me the readings of the +12V, +5V and the +3.3V. Troubleshooting hardware can be very long and time consuming so, bear with us and we will try to find the problem if you will do the work. When you run memtest, it needs to run for 8 passes. Each pass is a serise of about 9-10 tests. But each test and pass checks different things. It takes a minimum of 8 passes to check the ram, I usually run it overnight. Also, what brand is your PSU and how old is it? Here are the instructions of running memtest86+. Be sure to download the latest version from the link in this sutorial. http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

Also, if you don't already have it installed, Download and install CPUz. Pleas post a screenshot of CPUz memory tab, mainboard tab and the SPD tab. Make sure you are running the latest Nvidia drivers which can be downloaded from Drivers - Download NVIDIA Drivers. If you are not sure about the proper way to install the drivers please ask and we will guide you through the process. Proper installation is very important.

Do you have utilities for checking the CPU and GPU temps? I prefer Core Temp for CPU. Other programs will work well too. Keep it open and monitor your CPU temps. Most Graphics cards come with a utility to monitor the temps. If you don't have one, you can use MSI Afterburner.

Let's start there. If you have any questions, feel free to ask.

 

[Britton30]

Although CrystalDiskInfo shows your drive OK, it seems drive related to me. As essenbe said hardware issues are hard to pin down without a lot of testing.
since you have all WD drives, use the Data Life Guard from here.

Hard drive(s)test(s):

Pick one for your HDD brand or use Seatools.
7 Free Hard Drive Testing Software Tools

This will stress your GPU.

Graphics card test:
Video Card Stress Test with Furmark

Check in your BIOS hardware monitor and not what voltages are shown for 12V, 5V, and 3.3V.

IT may be worthwhile to double check all of your power supply connections. By that I mean disconnect and reconnect them to be sure they are all fully seated.
Finally...​

To better help us to help you would you please add your systems specs? Here's the correct way to do it. :SystemInfo See Your System Specs Under System Manufacturer/Model Number add whether it is a desktop or laptop and whether self built. Very important

Log in to Seven Forums and you will be able to transfer the info directly to the specs page in your profile from within the System Info app.

After doing this your specs will be available in each of your posts.
Click on My system Specs in the lower left of this post to see how it should look.
Full instructions are in the tutorial.

 

[Mitim0]

Hi essenbe and Britton30,

Thanks for your help.

Unfortunately, I think things seem to be a bit more worse now as I can’t get in to my desktop at all.
However I haven’t gotten a bluescreen either. Upon various attempts to restart (pressing the power button) results vary from windows attempting to repair (but finding nothing), to just a blank black screen (seems after the bios posts), or to windows attempting to load but nothing happens (windows start up screen, but animated logo missing).

Due to this, I’m unable to do some of what you guys suggested, but I was able to get some information out.

My power supply is a Silencer 610 EPS12V (I attached a picture in case I happen to be reading it wrong)
My voltages in the bios read (I’ve also attached a picture):
VCORE – 1.280v
3.3V – 3.280v
5V – 4.944v
12V – 12.040v

It also shows my CPU and MB temperatures as well: 32c and 30c The temperatures are after the system has been running just a few mins on this screen so it definitely would not be under load, but from memory, my CPU usually won’t go beyond the high 30’s and my MB temp (which I tend to read as the system temp) usually won’t go beyond 50 under load (such as playing a modern game). I am pretty certain of these two values as I tend to keep an eye on them when it starts to get warm in the summer. I use Speedfan for watching this.

For my videocard, I did update my drivers to the latest maybe about a week ago. I’ve also ran Furmark in the recent past as well (after I had updated), but only for a small test which was a minute or so and not at full resolution (it did however make my temp shoot up to 94c and stay there during the whole test ). There seemed to be no issues from it, but not sure that “test” meant anything, but thought I’d mention it as I can’t get in to it and run it again at the moment.

Currently I am doing an extended test on my hard drives using WD’s Data Life Guard (using dos version, booting off a usb). It is currently testing the largest drive, which also holds my system partition. It seems like it’ll take awhile so I figured I’d post up some of the information that I have in the meantime.
As mentioned, I’ve ran memtest for five passes on all my sticks of ram, but I'll take your advice and let it run some more after.

As for updating my bios, I’ll probably leave this until all the current tests are done, as I’ve checked the available updates and they don’t seem to fix anything that applies to me. Also, since win7-64 bit isn’t listed, should I just choose vista-64 bit? (This is the download page if you wanted to see/can read it better then I can: ASUS - P5K )

All of my hardware, with exception of my largest hard drive is roughly hitting five years old now. That hard drive is newer, I’d guess perhaps two years old?

I had no idea there was a program for the forum to fill in your system specs. How convenient. I’ll try to update them if I can.

 

[Britton30]

Hello, Your volt output is well within tolerances and the temps in BIOS are real good.
94C is too hot for your GPU with Furmark though. You could remove it and use a pencil eraser to clean its contacts and be sure to blow away any residue. Make sure it's fully seated when put back.
The PSU is up to the job, I'm unfamiliar with the brand though and no way to check output under a load.

Your BIOS is fairly current and for now I'd leave it as is.

 

[Mitim0]

Hello again,
After a couple of hours of testing my three hard drives, all of them seem fine. No issues reported. I ran both the quick and extended tests on each drive.

Following this, I was able to get back in to my desktop after rebooting. I note that strangely after spending lots of time spent testing (ram or hard drive in this case), I am usually able to get back in to my desktop and everything seems fine (I can use it for the rest of the day with no problems). It is as if my system has a higher chance of working after being all ‘warmed up’ from testing for a few hours.

It’s like when I turn on the system there is:
- A good chance of bluescreens right away/within early usage, windows not booting, etc
- A low chance that my computer decides to work for the day with no problems at all

Then after spent some time testing, the low chance increases.

I ran CPU-Z and took a screenshot of each tab. I’ve also managed to grab the new minidumps from my system as well and updated my system specs using the forum tool. Finally, just to double check, I reran furmark for a short while and the results are the same (also a screenshot is attached if it helps).
Currently, my plan is to let memtest86+ run overnight this time (to get to 8-9+ passes) then try pulling my video card, cleaning it, and then checking other connections.

 

[Britton30]

Hmm, "warm up" may be a clue. After running memtest for 8-9 passes turn it off and let it completely cool off, 2-3 hours. When you power up go immediately to the HArdware monitor in BIOS to see of the volt readings are low. They should be plus/minus 5% of nominal, 3.3V, 5V, and 12V. Maybe the PSU does have to warm up, just a shot.

 

[Vir Gnarus]

In previous scenarios that I've worked with, situations where a system gets more stable when warmed up usually have occurred from problematic PSUs or mobos. Britton is heading in the right direction with this. Either the PSU or the motherboard is bad.

 

[Britton30]

I hadn't thought of mobo issues Vir Gnarus, I found this on the ASUS site: ASUS - P5K
Which may not apply, if I read your drives right you have 200, 320 and 500GB drives.