Everything was going great for 5 hours this morning.
BAM
Screen turned black and computer just kept running. after ten minute i eventually just turned off the PSU.
No overheat problems at all. The GPU was actually using Less power with my newly upgraded PSU and is running even cooler!
I'm about to just quit!
THIS IS SO FRUSTRATING!!!!!!!!!!!!
Here are the event log details in order from 9:03 am to 11:16am.
I uninstaleed the gigabyte NIC card and used the mobo's card, but for somereason im still getting
"Intel(R) 82579V Gigabit Network Connection
Network link is disconnected."
Could that seriously cause BSOD? (no blue screen though, my monitor just turned off compleltely and my computer was still running)Log Name: Microsoft-Windows-Dhcp-Client/Admin
Source: Microsoft-Windows-Dhcp-Client
Date: 4/15/2014 9:03:59 AM
Event ID: 1001
Task Category: Address Configuration State Event
Level: Error
Keywords:
User: LOCAL SERVICE
Computer: JanS.JAN
Description:
Your computer was not assigned an address from the network (by the DHCP Server) for the Network Card with network address 0x240A646E9C92. The following error occurred: 0x79. Your computer will continue to try and obtain an address on its own from the network address (DHCP) server.Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Dhcp-Client" Guid="{15A7A4F8-0072-4EAB-ABAD-F98A4D666AED}" />
<EventID>1001</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>3</Task>
<Opcode>75</Opcode>
<Keywords>0x4000000000000000</Keywords>
<TimeCreated SystemTime="2014-04-15T14:03:59.113648200Z" />
<EventRecordID>182</EventRecordID>
<Correlation />
<Execution ProcessID="960" ThreadID="2704" />
<Channel>Microsoft-Windows-Dhcp-Client/Admin</Channel>
<Computer>JanS.JAN</Computer>
<Security UserID="S-1-5-19" />
</System>
<EventData>
<Data Name="HWLength">6</Data>
<Data Name="HWAddress">240A646E9C92</Data>
<Data Name="StatusCode">121</Data>
</EventData>
</Event>
+++++++++++++++++++++====================+++++++++++++++++++++++=====================+++++++++++++++++++++==============++++++++++++++++++
Log Name: Microsoft-Windows-Dhcp-Client/Admin
Source: Microsoft-Windows-Dhcp-Client
Date: 4/15/2014 9:04:01 AM
Event ID: 1001
Task Category: Address Configuration State Event
Level: Error
Keywords:
User: LOCAL SERVICE
Computer: JanS.JAN
Description:
Your computer was not assigned an address from the network (by the DHCP Server) for the Network Card with network address 0x240A64717155. The following error occurred: 0x79. Your computer will continue to try and obtain an address on its own from the network address (DHCP) server.Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Dhcp-Client" Guid="{15A7A4F8-0072-4EAB-ABAD-F98A4D666AED}" />
<EventID>1001</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>3</Task>
<Opcode>75</Opcode>
<Keywords>0x4000000000000000</Keywords>
<TimeCreated SystemTime="2014-04-15T14:04:01.113651000Z" />
<EventRecordID>183</EventRecordID>
<Correlation />
<Execution ProcessID="960" ThreadID="1352" />
<Channel>Microsoft-Windows-Dhcp-Client/Admin</Channel>
<Computer>JanS.JAN</Computer>
<Security UserID="S-1-5-19" />
</System>
<EventData>
<Data Name="HWLength">6</Data>
<Data Name="HWAddress">240A64717155</Data>
<Data Name="StatusCode">121</Data>
</EventData>
</Event>
++++++++++++++++=================++++++++++++++++++++++++++===================++++++++++++++++++++++=================+++++++++++++++
Log Name: System
Source: Microsoft-Windows-Kernel-Power
Date: 4/15/2014 11:16:17 AM
Event ID: 41
Task Category: (63)
Level: Critical
Keywords: (2)
User: SYSTEM
Computer: JanS.JAN
Description:
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.Event 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="2014-04-15T16:16:17.506010600Z" />
<EventRecordID>81107</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="8" />
<Channel>System</Channel>
<Computer>JanS.JAN</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>
++++++++++++++++++++++++++++++++++++++++++++============++++++++++++++++======================++++++++++++++++++++++++++++++++++++++
Log Name: System
Source: Microsoft-Windows-Kernel-PnP
Date: 4/15/2014 11:16:18 AM
Event ID: 219
Task Category: (212)
Level: Warning
Keywords:
User: SYSTEM
Computer: JanS.JAN
Description:
The driver \Driver\WUDFRd failed to load for the device ACPI\PNP0A0A\2&daba3ff&2.Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Kernel-PnP" Guid="{9C205A39-1250-487D-ABD7-E831C6290539}" />
<EventID>219</EventID>
<Version>0</Version>
<Level>3</Level>
<Task>212</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2014-04-15T16:16:18.020811500Z" />
<EventRecordID>81109</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="56" />
<Channel>System</Channel>
<Computer>JanS.JAN</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="DriverNameLength">24</Data>
<Data Name="DriverName">ACPI\PNP0A0A\2&daba3ff&2</Data>
<Data Name="Status">3221226341</Data>
<Data Name="FailureNameLength">14</Data>
<Data Name="FailureName">\Driver\WUDFRd</Data>
<Data Name="Version">0</Data>
</EventData>
</Event>
++++++++++++++++===================+++++++++++++++++++++++++++====================++++++++++++++++++================++++++++
I went to RUN: DXDIAG because some people said running diablo 3 on DX9 solved there issue.
I Noticed that i was running DIrectX 11
32 bit!!! .. I changed it to 64bit.
Could that have been the problem?
If i run diablo 3 in directx9 would that cause me to have to change my nvidia drivers?
EDIT:
Found this on BNET100999810042 wrote:Soulshox,
Diablo III only runs in DX9. There are no options to change that.
________________________________________________________
I'm available in the forums Monday - Friday, 12 pm - 8 pm Pacific Time
Please provide feedback! -
https://www.surveymonkey.com/s/Omrakos
Ok so its not DX causing the issue.. So it MUST be the errors i pasted above?
Fri Apr 11, 2014 10:30 pm 
