Sign in with
Sign up | Sign in
Your question

Random Crashes without BSoD or DumpLog

Last response: in Systems
Share
December 27, 2012 5:25:24 PM

Hey guys,

I recently got a new build for Christmas. I will post the specs below. For some reason, after about an hour or so of being on and running stable with the benchmarks it should be getting in all fields, the system will freeze without any BSoD. Right before this happens, you can hear an audible sound come from the speakers or headset that is plugged in. Not too sure what to make of all this as of yet. Any suggestions?

(I have yet to overclock the system either, and all temperatures are under 30 C)

Specs:

ASUS P9X79 PRO mobo
8x4GB ripjaw x PC3 2400
i7 3930k
3x 570 GTX SLi
2 SSD's
3 HDD's
Win 7 x64 Ult
Seasonic Gold 1250w
H100 CPU cooler
Rosewill Thor case
Enough fans to keep the whole house cool
December 27, 2012 5:34:01 PM

Flixxy said:
Hey guys,

I recently got a new build for Christmas. I will post the specs below. For some reason, after about an hour or so of being on and running stable with the benchmarks it should be getting in all fields, the system will freeze without any BSoD. Right before this happens, you can hear an audible sound come from the speakers or headset that is plugged in. Not too sure what to make of all this as of yet. Any suggestions?

(I have yet to overclock the system either, and all temperatures are under 30 C)

Specs:

ASUS P9X79 PRO mobo
8x4GB ripjaw x PC3 2400
i7 3930k
3x 570 GTX SLi
2 SSD's
3 HDD's
Win 7 x64 Ult
Seasonic Gold 1250w
H100 CPU cooler
Rosewill Thor case
Enough fans to keep the whole house cool


Make sure that BSOD display is activated. Under System Properties go to the Advanced Tab then head to Startup and Recovery. Make sure the checkbox is disabled for "Automatically Restart". That should give you BSOD.

Also check eventlog under System for Critical Errors.
m
0
l
December 27, 2012 5:51:12 PM

eerazor said:
Make sure that BSOD display is activated. Under System Properties go to the Advanced Tab then head to Startup and Recovery. Make sure the checkbox is disabled for "Automatically Restart". That should give you BSOD.

Also check eventlog under System for Critical Errors.


Ah, BSoDing is now enabled.

The only critical error I can find states that windows restarted unexpectedly. XML:

- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331C3B3A-2005-44C2-AC5E-77220C37D6B4}" />
<EventID>41</EventID>
<Version>2</Version>
<Level>1</Level>
<Task>63</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000002</Keywords>
<TimeCreated SystemTime="2012-12-27T18:10:13.493607100Z" />
<EventRecordID>2913</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="8" />
<Channel>System</Channel>
<Computer>Dango-PC</Computer>
<Security UserID="S-1-5-18" />
</System>
- <EventData>
<Data Name="BugcheckCode">0</Data>
<Data Name="BugcheckParameter1">0x0</Data>
<Data Name="BugcheckParameter2">0x0</Data>
<Data Name="BugcheckParameter3">0x0</Data>
<Data Name="BugcheckParameter4">0x0</Data>
<Data Name="SleepInProgress">false</Data>
<Data Name="PowerButtonTimestamp">0</Data>
</EventData>
</Event>
m
0
l
Related resources
December 27, 2012 5:52:40 PM

Nothing before it under System? How about under Applications?
m
0
l
December 27, 2012 6:46:09 PM

is that after an hour or so inactivity?
m
0
l
December 28, 2012 5:03:48 PM

That is it in system, I see 5 of those exact reports, because it has crashed this way 5 times. I had enabled BSoDing, and it still does not BSoD, it only freezes, and the USB power goes out. If you unplug and replug in a USB device, there seems to be power, but all power to devices connected when it crashes/freezes goes out right when the crash happens.

There are only some warnings and information logs left in system.

As for applications, there are no criticals, however, there are errors, but I know them from when I had to force close an application that was not responding a few times.

And depending on which time it crashed, the system could have been either inactive for minutes, hours, or have been still in use. The most common crash is about an hour or so after it is started up.
m
0
l
December 28, 2012 8:31:51 PM

I would recommend running a stress test on CPU and RAM. If those run fine, it is most likely a driver Problem.
m
0
l
December 29, 2012 1:21:00 AM

eerazor said:
I would recommend running a stress test on CPU and RAM. If those run fine, it is most likely a driver Problem.


Recommendations on which programs to use?

If not I'll probably use OCCT.
m
0
l
December 29, 2012 4:43:15 AM

Well, I ran about an hour long OCCT test, and nothing happened.

I then took out all dims other than 1, and tested about 3 dims with prime95 before realizing I had 16GB of tested stable 1333. (4x4GB) I decided it would be worth while to see if the system would not freeze with this stable and functioning 1333 ram. Within 10 minutes of starting up, it crashed/froze again, with only the 1333 ram in.

Not too sure what this means, because I also started up in safe mode to idle and see if it would crash (trying to see if it was a driver issue) and this also caused the computer to crash/freeze.

Very confused at this point. Any more ideas?
m
0
l
!