- Joined
- Apr 21, 2012
- Messages
- 47
- Reaction score
- 0
Hello there,
It seems my BSOD issues have returned. Not sure why, everything was working fine until I attempted (ironically) to make some backup discs of my various mods and other work and toward the end of the burn it bluescreened. Tried it three times, did the same at different points. Then it started bluescreening approx every 20 minutes. The best way I can illustrate is with a screenshot from Bluescreen Reader.
It started with RTKVHD674.sys, which is a RealTek HD Audio Driver. I went and updated this driver (despite the fact I don't use the onboard sound).
As you can see, ntoskrnl.exe started then, which I know is indicative of an error somewhere else (i.e it isn't the kernel thats causing it). So I went and also updated my Onboard LAN and Chipset drivers (per the advice given to me on my last thread that they were outdated)
I decided to test it for a while and played FH2 for a few hours. No BSOD. I went to bed and left my PC at the desktop.
I awoke to find it had Bluescreened again, but now at ataport.sys. Apparently this can be caused by a broken or incorrect driver. I wonder whether I got the correct driver for my MB and so forth. Other than that I am clueless. Last time I got these BSODs I dug into everything, removed everything that was incompatible, ran anti-virus and anti-spyware scans, the works.
Attached is the dmp file for the most recent bluescreen. Also, see below for CPU-Z Screenshots
http://www.mediafire.com/?kjj8rvpwt33d9ww
It seems my BSOD issues have returned. Not sure why, everything was working fine until I attempted (ironically) to make some backup discs of my various mods and other work and toward the end of the burn it bluescreened. Tried it three times, did the same at different points. Then it started bluescreening approx every 20 minutes. The best way I can illustrate is with a screenshot from Bluescreen Reader.
It started with RTKVHD674.sys, which is a RealTek HD Audio Driver. I went and updated this driver (despite the fact I don't use the onboard sound).
As you can see, ntoskrnl.exe started then, which I know is indicative of an error somewhere else (i.e it isn't the kernel thats causing it). So I went and also updated my Onboard LAN and Chipset drivers (per the advice given to me on my last thread that they were outdated)
I decided to test it for a while and played FH2 for a few hours. No BSOD. I went to bed and left my PC at the desktop.
I awoke to find it had Bluescreened again, but now at ataport.sys. Apparently this can be caused by a broken or incorrect driver. I wonder whether I got the correct driver for my MB and so forth. Other than that I am clueless. Last time I got these BSODs I dug into everything, removed everything that was incompatible, ran anti-virus and anti-spyware scans, the works.
Attached is the dmp file for the most recent bluescreen. Also, see below for CPU-Z Screenshots
http://www.mediafire.com/?kjj8rvpwt33d9ww