Originally Posted by PimpSkyline
Hey guys, got an issue and since the biggest one is 8350 related here i am lol
Just woke up to One monitor on but black screen and the other in standby. I wiggled the mouse and nothing. Well the H100i fans where barley spinning, so i touched the Rad, well let's just say Hot.
So i restarted the PC and got this.
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 1033
Additional information about the problem:
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1What does it mean?
Google wasn't much help.
My 8350 was sitting around at Least 75C+ for over 6 hours, plus my Mobo was at 65C+ also. (The NB/VRM sink was cooler then the CPU Rad) So you think she is okay?
Thanks guys for your time.
As 1 user said, download 'whocrashed' to get a reading of the dump file...also download 'SF_Diagnostic_Tool' run from desktopp and zip the folder it releases naming it your user name...then google a bsod support group for your OS and someone will point you in the right direction...
may be of helpp:
The CAUSE of the D1 Bug_Check is shown by all 3 debuggers as NETw5s64.sys which is the Intel WiFi
driver. If it is a built-in device check the System Maker and then Intel Downloads for updated drivers.
If a separate WiFi device check with its maker and then Intel Downloads for updated drivers. See
driver update methods in the troubleshooter and in the next message.
BCCode: D1 0x000000D1
Check these KB's
Stop error when you resume a computer that is running Windows 7 or Windows Server 2008 R2
from sleep or from hibernation: "STOP: 0x000000D1"
Stop error on a Windows Server 2008 R2-based or Windows 7-based computer when the operating
system uses a virtual storport miniport driver to save a dump file or a hibernation file: "0x000000D1"
Those and 7 other KB Articles are available
Think Video drivers mainly though it can be others. See the driver section in my generic bluescreen
troubleshooting methods below. BIOS, low level chipset drivers and antivirus/antispyway/security
programs can also cause this. Check the troubleshooter and when you get to the driver and memory testing sections refer to the generic methods in next message and then return to the troubleshooter
A driver tried to access an address that is pageable (or that is completely invalid) while the IRQL was too high.
This bug check is usually caused by drivers that have used improper addresses.
If the first parameter has the same value as the fourth parameter, and the third parameter indicates an execute operation, this bug check was likely caused by a driver that was trying to execute code when the code itself was paged out. Possible causes for the page fault include the following:
The function was marked as pageable and was running at an elevated IRQL (which includes obtaining a lock).
The function call was made to a function in another driver, and that driver was unloaded.
The function was called by using a function pointer that was an invalid pointer.
BCCode: d1 0x000000d1 <-- read this link
if running win7 ^
would recommend removing any image tools (daemon tools ect) and ruunning memtest86