Random BSOD's. Don't know what it is.

Drekerc

Reputable
Sep 28, 2014
15
0
4,520
Hi,

Since I got windows 8 on my Desktop PC (self build) I get random BSOD's (with the sad smiley). Sometimes when I wake the PC up from sleep, and sometimes just when I'm searching the web. Those screens are gone so fast that I don't had the time to check wht he is saying as error. I know it as something with drivers, but don't know what exactly. Did memory tests, HDD tests, tested my graphics card... Nothing. I also tried to get more information with Driver Verifier. When he started up, a few seconds later I get a BSOD with other information than I got with my random BSOD's. This BSOD Says : DRIVER_VERIFIER_I/OMANAGER_VIOLATION...something like that. The CPU is an Intel Core 2 Quad Q9550. The motherboard is an EP45-DS4 from Gigabyte (6 years old). The latest drivers are from 2008, so I think it is possible that Windows 8 is just to modern and new for such an old motherboard, but I'm not sure of that. Hope you guys maybe can help me out? I was planning to buy a new motherboard and CPU already, but I wan't to make sure that it will be gone when I do that...

Thanks for your help.
 
looked at another of your bugchecks, looked like a bugcheck coming out of a sleep state (hibernation)
you have a old machine, with no available BIOS updates, You might install the intel chipset update
http://www.intel.com/products/processor/core2quad/specifications.htm

\SystemRoot\system32\DRIVERS\Rt630x64.sys Wed Oct 19 05:12:55 2011
Realtek PCI/PCIe Adapters is old, update from
http://www.realtek.com.tw/downloads/downloadsView.aspx?Langid=1&PNid=7&PFid=10&Level=3&Conn=2

if you can not get hibernation working with updated drivers, you should disable hibernation.
==========
looking at the last bugcheck, verifier found that a hardware driver was processing requests that did not match its ID
(ie, catching and processing other drivers data)
I would guess it is this driver
SystemRoot\system32\drivers\WmVirHid.sys Tue Apr 27 13:08:53 2010
: Logitech WingMan Virtual Hid Device Driver (update the software from http://www.logitech.com/en-us/support )

the bugcheck was in the HID subsystem (human interface devices subsystem, keyboard, mouse, not sure what device)
(need a kernel memory dump rather than a minidump)
----------
update this driver
\SystemRoot\system32\DRIVERS\wg111v3.sys Wed Nov 18 01:47:46 2009
it is a old netgear usb wireless driver

---------
update this old driver
\SystemRoot\system32\drivers\ctac32k.sys Wed Jul 02 01:38:22 2008
it is a creative audio driver
 

Drekerc

Reputable
Sep 28, 2014
15
0
4,520


Update the drivers you told beside the Intel and Realtek drivers, what do I actually have to update? The Realtek card reader drivers? Could yo give a specific link? And I can't find an update on the chipset on the Intel website, link? Now set it to kernel. So waiting for next crash.

Paul, where do I have to upload the to for you? Give me the link to the website. Thanks for the help
 
sorry, i posted the wrong link
use this link for the intel chipset update
https://downloadcenter.intel.com/Detail_Desc.aspx?DwnldID=20775

try here for your network driver
http://www.realtek.com.tw/downloads/downloadsView.aspx?Langid=1&PNid=13&PFid=4&Level=5&Conn=4&DownTypeID=3&GetDown=false&Downloads=true





 
it looks like your system did not wake up. it was caused because the hard drive took too long to respond to a wake up signal and the system bugchecked because of it.

the device was
"IDE\DiskST3320620A______________________________3.AAC___\6&20c02bb5&0&0.1.0"


I would assume this is a IDE disk drive Seagate barracuda 320GB drive
it either has bugs in its electronics and did not respond to the signal, or more likely it did not receive the signal to wake up. that would be a bios bug, or a bug in a storage driver that you have installed.

if the drive will not wake up, all you can do is update the drivers or tell windows not to put your drive to sleep. (use control panel, power management to change the time out for your hard drive)
 
-install windows 8.1 and updates.
maybe it was a bug in the atapi.sys driver you have installed.
yours is \SystemRoot\System32\drivers\atapi.sys Wed Jul 25 19:30:33 2012
my version on my 8.1 windows box is dated 8/22/2013

you might scan for rootkits, atapi.sys driver is often the target of rootkits

windows 8.x turns on various low power link states that were turned off by default in windows 7. Old hardware had many bugs in the BIOS and in the Circuits of the hardware where low power states just did not work. People tended not to detect these hardware errors until they installed windows 8.x. Sometimes the OEM will have a special driver for the motherboard to get the system not to bugcheck but most often they just made a driver that turned off the feature.







 

Drekerc

Reputable
Sep 28, 2014
15
0
4,520


I updated Winwdows from the Windows store, don't know what you mean with updateS? Are there more than 1?
 
run control panel, type windows update in the search.
then select check for updates.

updates come out once a month or so. Just make sure your system is not blocking updates. Some malware and pirate versions of windows will also block updates.