Just had my first BSOD

[Neil79]

Came up with 0x100000001E, used bluescreen viewer to find out what was causing it

Rt64win7.sys which is a realtek NIC driver, i'll say it again I HATE realtek

 

[joeyjojo]

Your hatred for realtek is unfounded - this is almost certainly an overclock issue. What volts?

Do 5 loops of IBT at max memory and post a screenie.

 

[Neil79]

Your hatred for realtek is unfounded - this is almost certainly an overclock issue. What volts?

Do 5 loops of IBT at max memory and post a screenie.

Unfounded how so?, do a google search anyone that has had that BSOD is told to update the driver. I've done just now as the driver was a year old which was the latest from the gigabyte website!. Gigabyte are well behind .

This system is not just 5 loops stable, but 20! and at standard,high and max it's also 8hrs prime stable.

 

[Neil79]

http://www.sevenforums.com/crashes-debugging/61833-blue-screen-death.html

http://social.technet.microsoft.com...f/thread/7503b92e-7977-45b2-9386-6ba5e04fcef1

http://www.sevenforums.com/crashes-debugging/66539-another-win-7-64-bit-bsod-thread.html

As per the information you have provided your issue is with the Realtech driver Rt64win7.sys. Go to your motherboard's website, find your motherboard and update to the latest onboard audio drivers.

It's been 3 days and no BSOD, thank you for your help!

 

[Surveyor]

Unfounded how so?, do a google search anyone that has had that BSOD is told to update the driver. I've done just now as the driver was a year old which was the latest from the gigabyte website!. Gigabyte are well behind .

If that's the case then Realtek can hardly be blamed if you haven't updated the driver.

You don't have to rely on Gigabyte to spoon feed you driver updates.

 

[Neil79]

 

[Surveyor]