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
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.
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.
Hello again. Here are the files from system logs in Event Viewer, zipped. Minidump folder is empty.
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
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
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).
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>DC0709000300050010002B0008007E03DC0709000300050014002B0008007E03A81B00003C00000001000000A81B 000000000000D40D00000100000000000000</Binary>
</EventData>
</Event>
Last edited by MarioHadEnough; 05 Sep 2012 at 16:05. Reason: new info, file attached
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.
Quote