HardHang every night, no BSOD, not fixed in startup, common 0xC000000D

[MarioHadEnough]

Dear supporters, enough is enough...

The system should be stable, but every morning I find it frozen -- only alternative is a forced shut down. I tried everything I was comfortable with, and more. BIOS update was a nightmare in itself... anyway - you have here attached all the information from event viewer (I think), and info about the system.
Here is the software I run:
- Acronis for backup
- Norton 360 firewall and antivirus
- Intel rapid storage
- dreamweaver, acrobat 7.0, photoshop elements
- Teamviewer 5
- Epson wireless printer (workforce 840)
- MS office, skype, Nvidia, Firefox, etc...

I updated everything under the sun (drivers, sw, etc). The hangs happen with or without system loaded with running software. Sometimes overnight, sometimes in the middle of the day, with no clear reason or rime. It's just happening... 6 critical events in the last 7 days, PLUS 50 errors in the same period.

This morning, I downloaded and run Malwarebytes - nothing found. Norton also says I have nothing.

Then I downloaded and run Windows Debugger, and got a report I copy here below, using a memory.dmp file created after the last hang last night:

X*X*X*X*X*X*X*X StartOfTheReport X*X*X*X*X*X*X*X

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Loading Dump File [C:\Users\Mario Sarli\Desktop\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available
Symbol search path is: srv*c:\symbols\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Machine Name:
Kernel base = 0xfffff800`0305e000 PsLoadedModuleList = 0xfffff800`032a2670
Debug session time: Fri Jul 20 08:07:01.913 2012 (UTC - 4:00)
System Uptime: 0 days 23:57:09.646
Loading Kernel Symbols
...............................................................
Loading User Symbols
Loading unloaded module list
******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information.
BugCheck 9F, {3, fffffa800d56da10, fffff80000b9c3d8, fffffa800cffde10}
Probably caused by : pci.sys
Followup: MachineOwner

X*X*X*X*X*X*X*X EndOfTheReport X*X*X*X*X*X*X*X

The big question is: What do I do next? [[[Fix pci.sys? (how?) Change something? What?]]]

Looking forward to having a stable system... I really need one:shock:.
Best,
Mario

 

[FredeGail]

Hello Mario and welcome to Sevenforums.

BSOD Analyse

Suspecting Memory

Looking at your bugcheck it's likely that a memory corruption event was triggered. Though a driver could be causing the memory to be borked, but we're usually suggesting a memory test before moving forward. Do a scan with Memtest86+. Memtest is a scanner that'll check your sticks for errors.

   Warning

:info: Note that the below instructions may break your WARRANTY rules. If you're unsure check manuals, separated warranty papers, stickers on computer for secure permission.

To ensure that we'll know if it's the slots on the motherboard that's broken, or the sticks itself - we have a little procedure we'll recommend. Remove 1 stick, scan the other with Memtest in the current slot. After 7 passes, move the stick to another slot and scan, and so on and so forth until you've scanned all the sticks, and all the slots, one by one.

Memtest86+ - Advanced Memory Diagnostic Tool

Best Regards,
Frederik.

 

[MarioHadEnough]

Ok -- THANK YOU for the answer, FredeGail! I'm downloading and running the memtests (7 times, as indicated). Back when I bout the parts and assembled this machine, I did a memory test with memtest... so I expect the memory sticks to be ok, but I'll test it anyway. If I find anything wrong, I'll come back here immediately.

After the test, if the memory is fine, I'll leave the computer running overnight and will post the new crash report in the morning tomorrow, or as soon as it happens
Thank you once again,
Mario

 

[FredeGail]

You're welcome!

Best Regards,
Frederik.

 

[Vir Gnarus]

While you should go ahead and do the memtest, I want to add something which I found odd. You said you went heavy on updating drivers, but this latest crashdump shows your NIC drivers being from way back in January 2011. I also find it strange that the crashdump timestamp on the file itself is 07-25-2012, but the debug session time listed inside the crashdump is July 20, 2012. Very weird. Either way, see what you can do about your Realtek NIC drivers associated with your Gigabyte motherboard.

Also, do you have your power options set to put your system in any sort of sleep/power down state overnight? The system may be going into a type of hybrid sleep state that is unsupported by your motherboard/NIC card.

Analysts:

The latest crashdump given showed an issue that dealt with a device that was stuck for a long period of time performing a power IRP. This is basically I/O that's done with the device to change its power state. I went ahead and dumped the related power IRP to see what was up:

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

DRIVER_POWER_STATE_FAILURE (9f)
A driver has failed to complete a power IRP within a specific time (usually 10 minutes).
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: fffffa800d56da10, Physical Device Object of the stack
Arg3: fffff80000b9c3d8, nt!TRIAGE_9F_POWER on Win7, otherwise the Functional Device Object of the stack
Arg4: [COLOR=Green]fffffa800cffde10[/COLOR], The blocked IRP

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

TRIAGER: Could not open triage file : C:\Program Files (x86)\Windows Kits\8.0\Debuggers\x64\triage\modclass.ini, error 2

DRVPOWERSTATE_SUBCODE:  3

IMAGE_NAME:  pci.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce7928f

MODULE_NAME: pci

FAULTING_MODULE: fffff88000f70000 pci

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

STACK_TEXT:  
fffff800`00b9c388 fffff800`031476c2 : 00000000`0000009f 00000000`00000003 fffffa80`0d56da10 fffff800`00b9c3d8 : nt!KeBugCheckEx
fffff800`00b9c390 fffff800`030e7e3c : fffff800`00b9c4c0 fffff800`00b9c4c0 00000000`00000000 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x34050
fffff800`00b9c430 fffff800`030e7cd6 : fffffa80`0c7f7c58 fffffa80`0c7f7c58 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x6c
fffff800`00b9c4a0 fffff800`030e7bbe : 000000c8`c4dfd2d6 fffff800`00b9cb18 00000000`005457d1 fffff800`03253ca8 : nt!KiProcessExpiredTimerList+0xc6
fffff800`00b9caf0 fffff800`030e79a7 : 00000042`82a548c2 00000042`005457d1 00000042`82a548f6 00000000`000000d1 : nt!KiTimerExpiration+0x1be
fffff800`00b9cb90 fffff800`030d4eca : fffff800`0324fe80 fffff800`0325dcc0 00000000`00000002 fffff880`00000000 : nt!KiRetireDpcList+0x277
fffff800`00b9cc40 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cc00 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  X64_0x9F_3_Rt64win7_IMAGE_pci.sys

BUCKET_ID:  X64_0x9F_3_Rt64win7_IMAGE_pci.sys

Followup: MachineOwner
---------
0: kd> !irp [COLOR=Green]fffffa800cffde10 [/COLOR]1
Irp is active with 3 stacks 2 is current (= 0xfffffa800cffdf28)
 No Mdl: No System Buffer: Thread 00000000:  Irp stack trace.  
Flags = 00000000
ThreadListEntry.Flink = fffffa800cffde30
ThreadListEntry.Blink = fffffa800cffde30
IoStatus.Status = [COLOR=Red]c00000bb[/COLOR]
IoStatus.Information = 00000000
RequestorMode = 00000000
Cancel = 00
CancelIrql = 0
ApcEnvironment = 00
UserIosb = 00000000
UserEvent = 00000000
Overlay.AsynchronousParameters.UserApcRoutine = 00000000
Overlay.AsynchronousParameters.UserApcContext = 00000000
Overlay.AllocationSize = 00000000 - 00000000
CancelRoutine = 00000000   
UserBuffer = 00000000
&Tail.Overlay.DeviceQueueEntry = fffffa800cffde88
Tail.Overlay.Thread = 00000000
Tail.Overlay.AuxiliaryBuffer = 00000000
Tail.Overlay.ListEntry.Flink = fffffa80146a5968
Tail.Overlay.ListEntry.Blink = fffff80003284b00
Tail.Overlay.CurrentStackLocation = fffffa800cffdf28
Tail.Overlay.OriginalFileObject = 00000000
Tail.Apc = 00000000
Tail.CompletionKey = 00000000
     cmd  flg cl Device   File     Completion-Context
 [  0, 0]   0  0 00000000 00000000 00000000-00000000    

            Args: 00000000 00000000 00000000 00000000
>[ [COLOR=Orange]16, 3[/COLOR]]   0 e1 fffffa8010d6e050 00000000 fffff80003321200-fffffa8012802be0 Success Error Cancel pending
           \Driver\[COLOR=Red]RTL8167    [/COLOR]nt!PopSystemIrpCompletion
            Args: 00016600 00000000 00000006 00000006
 [  0, 0]   0  0 00000000 00000000 00000000-fffffa8012802be0    

            Args: 00000000 00000000 00000000 00000000
0: kd> !error [COLOR=Red]c00000bb[/COLOR]
Error code: (NTSTATUS) 0xc00000bb (3221225659) - [COLOR=Red]The request is not supported[/COLOR].

The IRP showed the responsible driver object and device object, that being related to Realtek NICs, showing up as the one hanging the IRP. The status of the IRP shows what appears to be that the IRP is responding that it does not support that kind of request (power IRP). What exactly is the IRP? It's a power IRP (Major function code 16), that's trying to do a remove device (Minor function code 3).

Now, correct me if I'm wrong, but I don't know any moment when a network controller on a motherboard or a PCI NIC card would ever want to be removed. So something tells me there's some sort of power state on the system that's going on that this device is incompatible with. I can try and verify this speculation by looking further in, but I'm not sure I have time at the moment. Suffice to say, something is trying to force this network controller device off Windows, and it's simply not accepting the request to do so, so it hangs up on that, never finishes, and the system crashes. That's at least my interpretation of it.

Btw, here's how I got the dirt on the driver object and its associated driver:

0: kd> !irp fffffa800cffde10 1
Irp is active with 3 stacks 2 is current (= 0xfffffa800cffdf28)
 No Mdl: No System Buffer: Thread 00000000:  Irp stack trace.  
Flags = 00000000
ThreadListEntry.Flink = fffffa800cffde30
ThreadListEntry.Blink = fffffa800cffde30
IoStatus.Status = c00000bb
IoStatus.Information = 00000000
RequestorMode = 00000000
Cancel = 00
CancelIrql = 0
ApcEnvironment = 00
UserIosb = 00000000
UserEvent = 00000000
Overlay.AsynchronousParameters.UserApcRoutine = 00000000
Overlay.AsynchronousParameters.UserApcContext = 00000000
Overlay.AllocationSize = 00000000 - 00000000
CancelRoutine = 00000000   
UserBuffer = 00000000
&Tail.Overlay.DeviceQueueEntry = fffffa800cffde88
Tail.Overlay.Thread = 00000000
Tail.Overlay.AuxiliaryBuffer = 00000000
Tail.Overlay.ListEntry.Flink = fffffa80146a5968
Tail.Overlay.ListEntry.Blink = fffff80003284b00
Tail.Overlay.CurrentStackLocation = fffffa800cffdf28
Tail.Overlay.OriginalFileObject = 00000000
Tail.Apc = 00000000
Tail.CompletionKey = 00000000
     cmd  flg cl [COLOR=Green]Device   [/COLOR]File     Completion-Context
 [  0, 0]   0  0 00000000 00000000 00000000-00000000    

            Args: 00000000 00000000 00000000 00000000
>[ 16, 3]   0 e1 [COLOR=Green]fffffa8010d6e050 [/COLOR]00000000 fffff80003321200-fffffa8012802be0 Success Error Cancel pending
           \Driver\RTL8167    nt!PopSystemIrpCompletion
            Args: 00016600 00000000 00000006 00000006
 [  0, 0]   0  0 00000000 00000000 00000000-fffffa8012802be0    

            Args: 00000000 00000000 00000000 00000000

0: kd> !devobj [COLOR=Green]fffffa8010d6e050[/COLOR]
Device object (fffffa8010d6e050) is for:
 InfoMask field not found for _OBJECT_HEADER at fffffa8010d6e020
 \Driver\RTL8167 [COLOR=Blue]DriverObject fffffa800fb15e70[/COLOR]
Current Irp 00000000 RefCount 0 Type 00000017 Flags 00002050
DevExt fffffa8010d6e1a0 DevObjExt fffffa8010d6f8e0 
ExtensionFlags (0x00000800)  
                             Unknown flags 0x00000800
AttachedTo (Lower) fffffa800d56da10 \Driver\pci
Device queue is not busy.

0: kd> !drvobj [COLOR=Blue]fffffa800fb15e70 [/COLOR]7
fffff80003284fb0: Unable to get value of ObpRootDirectoryObject
fffff80003284fb0: Unable to get value of ObpRootDirectoryObject
Driver object (fffffa800fb15e70) is for:
 \Driver\RTL8167
Driver Extension List: (id , addr)

Device Object list:
fffffa8010d6e050  

DriverEntry:   fffff880051921dc    [COLOR=Red]Rt64win7[/COLOR]
DriverStartIo: 00000000    
DriverUnload:  fffff880018cbcb0    ndis!ndisMUnloadEx
AddDevice:     00000000    

Dispatch routines:
[00] IRP_MJ_CREATE                      fffff88001823d20    ndis!ndisCreateIrpHandler
[01] IRP_MJ_CREATE_NAMED_PIPE           fffff880018ba490    ndis!ndisDummyIrpHandler
[02] IRP_MJ_CLOSE                       fffff88001823560    ndis!ndisCloseIrpHandler
[03] IRP_MJ_READ                        fffff880018ba490    ndis!ndisDummyIrpHandler
[04] IRP_MJ_WRITE                       fffff880018ba490    ndis!ndisDummyIrpHandler
[05] IRP_MJ_QUERY_INFORMATION           fffff880018ba490    ndis!ndisDummyIrpHandler
[06] IRP_MJ_SET_INFORMATION             fffff880018ba490    ndis!ndisDummyIrpHandler
[07] IRP_MJ_QUERY_EA                    fffff880018ba490    ndis!ndisDummyIrpHandler
[08] IRP_MJ_SET_EA                      fffff880018ba490    ndis!ndisDummyIrpHandler
[09] IRP_MJ_FLUSH_BUFFERS               fffff880018ba490    ndis!ndisDummyIrpHandler
[0a] IRP_MJ_QUERY_VOLUME_INFORMATION    fffff880018ba490    ndis!ndisDummyIrpHandler
[0b] IRP_MJ_SET_VOLUME_INFORMATION      fffff880018ba490    ndis!ndisDummyIrpHandler
[0c] IRP_MJ_DIRECTORY_CONTROL           fffff880018ba490    ndis!ndisDummyIrpHandler
[0d] IRP_MJ_FILE_SYSTEM_CONTROL         fffff880018ba490    ndis!ndisDummyIrpHandler
[0e] IRP_MJ_DEVICE_CONTROL              fffff880018ba020    ndis!ndisDeviceControlIrpHandler
[0f] IRP_MJ_INTERNAL_DEVICE_CONTROL     fffff880018ba490    ndis!ndisDummyIrpHandler
[10] IRP_MJ_SHUTDOWN                    fffff880018ba490    ndis!ndisDummyIrpHandler
[11] IRP_MJ_LOCK_CONTROL                fffff880018ba490    ndis!ndisDummyIrpHandler
[12] IRP_MJ_CLEANUP                     fffff880018ba490    ndis!ndisDummyIrpHandler
[13] IRP_MJ_CREATE_MAILSLOT             fffff880018ba490    ndis!ndisDummyIrpHandler
[14] IRP_MJ_QUERY_SECURITY              fffff880018ba490    ndis!ndisDummyIrpHandler
[15] IRP_MJ_SET_SECURITY                fffff880018ba490    ndis!ndisDummyIrpHandler
[16] IRP_MJ_POWER                       fffff8800186df80    ndis!ndisPowerDispatch
[17] IRP_MJ_SYSTEM_CONTROL              fffff8800188eee0    ndis!ndisWMIDispatch
[18] IRP_MJ_DEVICE_CHANGE               fffff880018ba490    ndis!ndisDummyIrpHandler
[19] IRP_MJ_QUERY_QUOTA                 fffff880018ba490    ndis!ndisDummyIrpHandler
[1a] IRP_MJ_SET_QUOTA                   fffff880018ba490    ndis!ndisDummyIrpHandler
[1b] IRP_MJ_PNP                         fffff880018c6110    ndis!ndisPnPDispatch

0: kd> lmvm [COLOR=Red]Rt64win7[/COLOR]
start             end                 module name
fffff880`0512e000 fffff880`05195000   Rt64win7 T (no symbols)           
    Loaded symbol image file: Rt64win7.sys
    Image path: \SystemRoot\system32\DRIVERS\Rt64win7.sys
    Image name: Rt64win7.sys
    Timestamp:        Thu Jan 13 06:57:19 2011 (4D2EE89F)
    CheckSum:         0006BB92
    ImageSize:        00067000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

 

[MarioHadEnough]

Hi All,
All memtests completed (each stick and each slot) and found nothing wrong. I'll leave the computer running overnight and will post the new crash report / memory dump file ... in the morning tomorrow, or as soon as it happens.

Vir Gnarus -- GREAT reply! Let me address a few parts of your post:
-- Drivers were updated by going into Device Manager, right click, and (ask windows to) search for new drivers. All resulted in the same message saying the drivers used are the latest. Gigabyte website had the same result.
-- If there is a better way to search for driver updates, please let me know.
-- Before posting, I downloaded and run the SF Diag Tool.exe, and uploaded the zipped file. I didn't check dates.
-- Is there a way to cleanup all crash-logs, so I can make sure I'm uploading the newest files next time?
-- I'll go back to gigabyte website and try again to find newer drivers for the network card.
-- Mobo supports sleep and hibernation. I used sleep and it crashed. I used 'always on' and it crashes just as much... but this way I can see the screen saver frozen. Don't know about hybrid states.
-- IF we are sure the problem is the network card (100% sure).... can I buy another card and solve this problem? If so, which one? (then you are all invited to a "destroy this ^&$#$% card" party...)

Thanks again,
Mario

 

[Vir Gnarus]

The best way to update drivers for anything is to do it manually: if you are using an OEM (Dell, HP, etc.), download/install from their website; if custom-built, download and install from each manufacturer (Gigabyte for your motherboard). Windows driver repository is updated very, very infrequently, so it only should be used to retrieve initial drivers not already provided with Windows installation in order to get things going at first before you go and update them yourself. This also pretty much applies to any driver CDs that come with hardware you purchase: toss them out and make your own updated driver CD(s).

Yes, you can clean up minidumps by cleaning out C:/Windows/Minidump.

Make sure your BIOS is also updated, as this can play a role in the whole sleep/hibernate compatibility. Also, are you using a network card, or just the network connection built-in to the motherboard?

 

[MarioHadEnough]

Hello Vir Gnarus... and team,
Yesterday I went to Mobo website and downloaded all applicable drivers, installed them... there was a network driver update issued just a few days ago - interesting!)... These updates included intel drivers and sound drivers as well.

This computer was assembled here (custom built) after multiple visits to Microcenter. I am using the network connection built-in the mobo, and my comment about a nework card was mistaken - I confused the Nvidia card with network card.

So, Yesterday I cleared all dmp files I found, from folders like minidump and firefox and others - trying to start fresh. The BIOS was updated the week before my first post, and caused extensive headaches -- until I found out the BIOS update had reset my drivers to IDE... upon changing them back to XHD (or whatever that acronym is for RAID enabled), all functioned normally, and crashed normally as it was the norm.

Since the drivers update yesterday, I left the system running overnight, and no crashes... (I'm liking it)... today I'll use it normally, and tonight I'll leave all regular programs I need running - Let's see what happens.

I'll post an update here ASAICA (((As Soon As It Crashes Again))). For now... extremely sincerely, THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU!

No, seriously -- I really mean.... THANK YOU!
All the best,
Mario

 

[Vir Gnarus]

Sounds good, hope this all works out for ya. If you end up finding that this did take care of things, go ahead and mark this thread as solved for future reference.

 

[MarioHadEnough]

Good sign - no errors (no crashes either) in the last 24h.... I haven't seem an Event Viewer screen with so many zeros in a long time.
I'll come back and mark the thread as "closed" if we get to more than 7 days with no errors.
Thank you all once again.
Mario

 

[MarioHadEnough]

Dear VirGnarus and team,

Left system running over the weekend. Only thing open was Firefox, I think. This morning, around 5:30AM, the system restarted itself. I run the SF dialog tool again, and here are the new files produced.

Looking forward to reading your comments,
Mario

 

[Vir Gnarus]

Umm, not sure why, but the latest entry in your syslog is from 04/10/2012. Plus, there's no crashdumps, so I'm not sure any of this can help us. You may need to clean out any previous files generated by the SF dialog tool and then produce brand new ones, instead of trying to overwrite them.

 

[MarioHadEnough]

Umm, not sure why, but the latest entry in your syslog is from 04/10/2012. Plus, there's no crashdumps, so I'm not sure any of this can help us. You may need to clean out any previous files generated by the SF dialog tool and then produce brand new ones, instead of trying to overwrite them.

I'll be happy to do it... (if only I knew how)... then, please:
1) How do I clean out syslog?
2) How do I get the system to produce a crashdump file?
3) How do I make sure the system is (and will be) logging the errors into syslog and crashdump?
thanks again,
Mario

 

[Vir Gnarus]

Type "Event Viewer" in Start Menu and go to Windows Logs > System. See what the latest date for one is. If it is very recent (like from today or yesterday) then you can right click System and select "Save All Events As..." which you can then save and send to us (zip up first).

As for the crashdumps, check C:/Windows/Minidump to see if there's any new dump files present which you can provide us. If there aren't any, than I'll have to check your syslog to see why they weren't made.

 

[MarioHadEnough]

Hello again. Here are the files from system logs in Event Viewer, zipped. Minidump folder is empty.

 

[MarioHadEnough]

HardHang Again!

Hello Again, Vir Gnarus and Team.

The computer had a clean shut down on Sat, 9/1. I restarted today around 7AM, and around 10:40AM the computer was frozen -- the screen saver stopped, and nothing I could do. Pressed Reset...

At restart, I downloaded and run the new SF Diag Tool as per instructions. I added to the zip attached, the following:
- all application logs from event viewer;
- all system logs from event viewer;
- all dmp files I could find in the C drive (one from today, one from 9/1, and 2 older.)

What else can I do??? I'm at a point where I'm game for anything.
If there is no clear culprit yet... how can I stress the system to trigger more events, so we find the problem??? OR... what does your intuition tells you?... I'm up for anything ... crying included .

Looking forward to your reply,
Mario

 

[MarioHadEnough]

Hi All,
Last night... it crashed again, sometime between 10PM and 7AM today. I run the diag tool again (attached), just in case. I also searched the whole C drive and there are no new dump files...
How do I make sure a crashdump file will be created next time?
thanks,
Mario

 

[Vir Gnarus]

I checked your syslog, and found that while there's plenty of events reporting unexpected shutdowns, there hasn't been any events reporting the actual bugchecks that are occurring. Either there's something dreadfully wrong with your drive I/O that's preventing the system from writing an event to the syslog about the crash as well as not able to generate a crashdump, or you have an issue with your power supply or are experiencing some kind of a short circuit, which often is the case when this happens.

I have to ask, how did you get the "c000000d" errors? Are you actually seeing these in bluescreens? Can you write down any more info from a bluescreen?

Right now, it's best to rule out potential software-side problems. First, run CHKDSK with both options (scan for bad sectors as well as fix problems). Then follow up with SFC /SCANNOW. Make sure you do the SFC scan in the Windows 7 disk environment. Do not run in the Windows Recovery Environment that's present on the drive, rather you should run it off the Windows 7 DVD. Once these have done their job, report anything, including the CBS log from SFC (most likely present in main C:\ directory or C:\Windows\Logs\CBS\CBS.log).

 

[MarioHadEnough]

It happened again, as I was typing a long answer... . Since it froze on the screen of the answer, I'm retyping.

The power supply unit is fed with a battery/surge protector, and is a Master Cooler 600W. Shaw we test it? How?

The C00000D error I found in the Event Viewer logs, I think. I had very few blue screens -- my problem is a freeze, a hang of the whole system. Often times on the screen saver, other times it just freezes as I am working - like now. I was typing my answer, and it all stops in there, screen & audio just stop at that point. Only reset or power buttons (press and hold) work.

After your message I run chkdsk with both options selected, and it took a long time. I was away when it ended, so I found the computer re-started. I tried to run the SFC from a Windows DVD restart, but could not. I restarted on HD, opened a elevated prompt, and run a SFC /VERIFYONLY -- no problems found. I'll attach the CBS log after I restart the computer.

Today, my non-stop-backup feature in Acronis hanged twice, but the rest of the computer was operating normally. I stopped it and I'm only using the regular backup running hourly. As this last system-wide hang happened (4:43), Acronis had already been set as described above.

In the next message I'll attach the CBS log (now attached) and any new info I get from Event Viewer -- and it says:
1. Kernel-Power (with the reboot time stamp): The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
2. EventLog (with the crashing time stamp): The previous system shutdown at 4:43:08 PM on ‎9/‎5/‎2012 was unexpected. (Details):
- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider Name="EventLog" />

<EventID Qualifiers="32768">6008</EventID>

<Level>2</Level>

<Task>0</Task>

<Keywords>0x80000000000000</Keywords>

<TimeCreated SystemTime="2012-09-05T20:57:42.000000000Z" />

<EventRecordID>63763</EventRecordID>

<Channel>System</Channel>

<Computer>MainDesktop</Computer>

<Security />

</System>


- <EventData>
<Data>4:43:08 PM</Data>

<Data>‎9/‎5/‎2012</Data>

<Data />

<Data />

<Data>5408</Data>

<Data />

<Data />

<Binary>DC0709000300050010002B0008007E03DC0709000300050014002B0008007E03A81B00003C00000001000000A81B000000000000D40D00000100000000000000</Binary>

</EventData>


</Event>

 

[Vir Gnarus]

How old is your Acronis software? I've seen old Acronis drivers causing a lot of woes for people because they are incompatible with Windows 7. I however am not aware of how it would freeze your system, but if it's causing a race condition or some other form of deadlock, that would definitely do it.

Since this looking more and more like hardware problems, it's time to start running a battery of hardware tests. First, run Prime95 on Torture Test with Blend settings. Have that run overnight (8+ hours). Before doing so, make sure your system is set not to restart at crash. You can do this by typing "advanced system settings" in start menu, then going to Startup & Recovery and then unchecking the restart option (will need to restart to save changes). This is so if it does BSOD, we'll get a blue screen and you can jot down details from it. I'll need the suspect driver name (if present), the bugcheck code, and the following 4 parameters (in parentheses). If your system still reboots despite changing the option under Startup & Recovery, then we are dealing with overheating or power failure, and the CPU should be checked for temps and the power supply replaced.

Whether it does BSOD or not, your next test will be to run it again but on Large FFTs settings (again overnight). Mention and record any system behavior that occurs after this.

Once both these Prime95 tests are done and complete, your next one will be Seatools. Run the DOS version on bootup and have it go through all tests on your system drive, except Advanced. Long Generic will take some time, so best to reserve that for overnight.

As for the PSU itself, outside of the multimeter or swapping it with another PSU there's really no way of testing it through software. We can look at voltage monitors to see if they are stable and sufficient, but it's a bit of a gamble and will only discover some PSU issues.