BSOD randomly multiple times a day

[Krumlov]

Hey guys, I am here because I cannot find a solution to my annoying problem with Win7.
I have a new machine that came with Vista which I quickly upgraded to Win7 Ultimate 64bit.

My problem is that multiple times during the day I have random BSOD's that make my computer restart and are just an all around pain. (No damage seems to be done to the machine.)

The BSOD's happen during many random times, including while the machine is idle and I am not attending to it, while a browser is open to email, and while I am downloading software. (Most happen during idle periods.)

Here is the picture of the explanation I am given in SafeMode:

Thanks for any help given.

 

[wallyinnc]

Krumlov, welcome to the forums
Pls take a look here for collecting and providing info about crashes. I think more will be needed rather than that screen
Tks

 

[Krumlov]

I am trying hard to make a copy of my .dmp files, but it still will not allow me to. I follow the directions and it still does not work. I get an error: "File not found or not read permission."
I look up the error and it always has to do with 2GB+ files on XP.. so I don't understand how I am supposed to get you guys the files.

EDIT: Nevermind, I figured out how to do it. WinRAR was giving me the bulk of the problems. Files posted above.

 

[usasma]

Running the last 10 minidumps (the one's from December)...
Be back in a few with the analysis....

 

[usasma]

It looks to me like it's the driver for your Marvell Yukon network card (yk62x64.sys Mon Feb 23 10:02:27 2009)

Also, there's an older driver here: AtiPcie.sys Mon Nov 06 11:59:54 2006
It probably belongs to the chipset drivers for your motherboard.

Please go to the manufacturer's website and download the latest Windows 7 driver for each device.
Then uninstall each device from your system (you may not find an uninstaller for the ATIPCIE.SYS file).
Then install the freshly downloaded files.
Reboot and check the C:\Windows\System32\drivers folder for the date of the ATIPCIE.SYS file. Check the date on the Marvell Yukon driver also - and post back with each of them.

Here's a summary of the BSOD's:

Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Thu Dec  3 01:10:14.400 2009 (GMT-5)
System Uptime: 0 days 11:17:38.398
BugCheck 7F, {8, 80050031, 6f8, fffff80003093609}
Probably caused by : NETIO.SYS ( NETIO!CompareSecurityContexts+6a )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Fri Dec  4 20:36:09.302 2009 (GMT-5)
System Uptime: 0 days 5:57:56.909
BugCheck 9F, {3, fffffa80048aca20, fffff80000b9c518, fffffa8008c74a00}
*** WARNING: Unable to verify timestamp for yk62x64.sys
*** ERROR: Module load completed but symbols could not be loaded for yk62x64.sys
Probably caused by : yk62x64.sys
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Fri Dec  4 23:47:43.548 2009 (GMT-5)
System Uptime: 0 days 3:10:27.156
BugCheck 7F, {8, 80050031, 6f8, fffff800030cd609}
Probably caused by : NETIO.SYS ( NETIO!CompareSecurityContexts+6a )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Mon Dec  7 02:24:15.155 2009 (GMT-5)
System Uptime: 0 days 3:09:09.152
BugCheck 7F, {8, 80050031, 6f8, fffff800030ce609}
Probably caused by : NETIO.SYS ( NETIO!CompareSecurityContexts+6a )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Mon Dec  7 18:52:25.698 2009 (GMT-5)
System Uptime: 0 days 6:19:45.306
BugCheck 7F, {8, 80050031, 6f8, fffff80003092609}
Probably caused by : NETIO.SYS ( NETIO!CompareSecurityContexts+6a )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Tue Dec  8 23:13:10.042 2009 (GMT-5)
System Uptime: 0 days 0:13:58.665
BugCheck 7F, {8, 80050031, 6f8, fffff80003081609}
Probably caused by : NETIO.SYS ( NETIO!CompareSecurityContexts+6a )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Tue Dec  8 22:58:10.749 2009 (GMT-5)
System Uptime: 0 days 3:57:29.356
BugCheck 7F, {8, 80050031, 6f8, fffff800030db609}
Probably caused by : NETIO.SYS ( NETIO!CompareSecurityContexts+6a )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Tue Dec  8 18:37:25.674 2009 (GMT-5)
System Uptime: 0 days 8:51:42.671
BugCheck 7F, {8, 80050031, 6f8, fffff800030db609}
Probably caused by : NETIO.SYS ( NETIO!CompareSecurityContexts+6a )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Wed Dec  9 12:23:18.984 2009 (GMT-5)
System Uptime: 0 days 0:09:00.982
BugCheck 7F, {8, 80050031, 6f8, fffff80003095609}
Probably caused by : NETIO.SYS ( NETIO!CompareSecurityContexts+6a )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Wed Dec  9 15:44:29.073 2009 (GMT-5)
System Uptime: 0 days 3:20:21.071
BugCheck 7F, {8, 80050031, 6f8, fffff800030d1609}
Probably caused by : NETIO.SYS ( NETIO!CompareSecurityContexts+6a )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System

 

[Krumlov]

I found the driver for the yk62x64.sys and updated it.
The other one does not have Win7 drivers. It only have Vista 32/64bit drivers.

EDIT: Now I also see that ATIPCIE.sys is a Vista driver.. do I even need it then?

EDIT2: Another BSOD just happened. Uploaded.

 

[jcgriff2]

Next is to update your Relatek drivers -

 RTKVHD64.sys Thu Sep 18 06:50:25 2008 (48D23271)
 RTSTOR64.SYS Thu Jun 05 07:21:42 2008 (4847CC46)

Regards. . .

jcgriff2

.

 

[usasma]

Do you have 2 different network cards (the wired kind) on your system?
Please do the following so we can check this out:
MSINFO32
Please go to Start and type in "msinfo32.exe" (without the quotes) and press Enter
Save the report as an .nfo file, then zip up the .nfo file and upload/attach the .zip file with your next post.

Also, try this for the ATIPCIE.SYS driver file

Compatibilty Mode
1 - Download the latest driver from the manufacturer's website.
2 - Uninstall the current drivers using the Control Panel...Programs and features...Uninstall a program applet. Then verify that the driver/device has been removed in Device Manager
3 - Right click on freshly downloade driver installation file and select "Properties"
4 - Select the Compatibility tab - and do the following:
- Click on the "Change settings for all users" button
- Click on the box to select "Run this program in compatibility mode for" and then select Windows Vista Service Pack 1
- Click on the box to select "Run as administrator"
- Click on OK to exit all the dialogs
5 - Right click on the driver installation file and select "Run as administrator"
6 - Let it install and see if that stops the BSOD's.

 

[Krumlov]

Alright, working on the tasks you guys gave me. It is hard to download drivers while being hounded with BSOD's haha; two since I tried downloading (Posted in the zip folder below).

The .nfo file is also included in the zip folder.

Next is to update your Relatek drivers -

 RTKVHD64.sys Thu Sep 18 06:50:25 2008 (48D23271)
 RTSTOR64.SYS Thu Jun 05 07:21:42 2008 (4847CC46)

Regards. . .

jcgriff2

Also, I have taken care of the two drivers listed above, THANKS!

 

[usasma]

Please disable this device in Device Manager:
sptd ROOT\LEGACY_SPTD\0000 This device is not present, is not working properly, or does not have all its drivers installed.
I think that it has something to do with Daemon Tools/Alcohol or another CD/DVD burning/ripping program

Otherwise the issue seems to be related to your networking drivers. Please download the most current version, then uninstall the one that's on the system, then install the freshly downloaded one.

These drivers still need updating:

AtiPcie.sys  Mon Nov 06 11:59:54 2006
RTSTOR64.SYS Thu Jun 05 07:21:42 2008
GEARAspiWDM.sys Tue Apr 08 15:15:59 2008
RTKVHD64.sys Thu Sep 18 06:50:25 2008

Download on another computer and use a flash drive to get it to the crashing system. Lot's easier than fighting with corrupted downloads!

Good luck!

 

[Krumlov]

I fixed the device issue, that was hazardous because of how different device manager looks compared to previous versions..

I am continuing to find more an more drivers. I Finally got the AtiPcie.sys driver updated, and right now I am getting the RTSRO64.sys and RTKVHD64.sys.

Yesterday I had 5 BSOD -.-

 

[usasma]

As you get time, please post the memory dump files (and note the changes that you've made to the system).
That'll give us some stuff to work with - and will help us to figure out what's causing this.

 

[Krumlov]

Here is the new minidump file.. prepare to be amazed.

I got a little heated the other day and "found" Driver Genius Pro.
Its a legitimate program that is supposed to fix all of your drivers.
(I do not recommend it if you hate slow download speeds.. 1kb/s is a joke.)
That found 2 motherboard drivers, the Realtek audio drivers, and NVIDIA display drivers that were out of date. It gave me the install files and now all seems to work fine. I would like to note that I have JUST finished the last install and I have been BSOD now for about an hour. I will be sure to post once I get another.

 

[Geo64]

Please don't use those driver services or software. They mess up Windows quicker than malware can. Perhaps you were lucky this time but you'll be much better off visiting Realtek and NVIDIA's websites in the future, for drivers.

I noticed you have ZoneAlarm installed. If you run into problems from here, uninstalling that should be the first thing to try. That being said, I use it myself and it's great. It can cause issues on certain systems though.

 

[Krumlov]

Okay, so now there are massive problems. Either that Driver program made things worse or more problems are popping up.

Here is the Minidump from just today.. its about 12 files.
And if you guys could give me an update on which drivers I need to find, I will get right to it.

Thanks!

 

[usasma]

24 crash dumps in 3 days
All but one are virtually identical to this:

BugCheck 7F, {8, 80050031, 6f8, fffff800030xxxxx}
Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )

The one different one is a STOP 0x9F:

BugCheck 1000009F, {4, 258, fffffa8003a00b60, fffff80000b9c510}
Probably caused by : RTSTOR64.SYS ( RTSTOR64+4248 )

And here's the older drivers that should be updated:

AtiPcie.sys  Mon Nov 06 11:59:54 2006
RTSTOR64.SYS Thu Jun 05 07:21:42 2008 - Realtek Semiconductor Corp. High-Speed USB Media Card Reader Software
GEARAspiWDM.sys Tue Apr 08 15:15:59 2008
RTKVHD64.sys Thu Sep 18 06:50:25 2008

Please note that the driver mentioned in the STOP 0x9F error is also listed as one of the older drivers.
More info on that driver here: http://data.versiontracker.com/driv.../sp39501-40000/sp39907_ext/extract/Readme.txt

Please download the latest, Win7 driver for each of these drivers
Then uninstall the current drivers,
Then install the freshly downloaded driver packages.

If you're unable to find Win7 drivers, please post back for instructions on running the installer in compatiblity mode for all users.

 

[Krumlov]

Okay, so I took my computer down to the tech help guys at my college.. they did some decent work on it.

We fixed all the drivers except for one of the realtek drivers. Instead we just uninstalled that. For some reason I can use sound but not a microphone haha. I can fix that on my own later.

No BSOD though since we fixed it all. Thanks to everyone who offered imput and helped me out. I will be sure to post and PM again if another one comes back up.

--Harrison Whitmarsh

 

[Krumlov]

Spoke too soon.

 

[usasma]

RTSTOR64.sys is still outdated: RTSTOR64.SYS Thu Jun 05 07:21:42 2008

Not much info in the memory dump file.

Please run Driver Verifier according to these instructions:

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.


So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista Startup Repair feature).


Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Automatically select unsigned drivers" and click "Next"
If no drivers show up, then select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.


Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out.


Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.


If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.
If that doesn't work, post back and we'll have to see about fixing the registry entry off-line.


More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users
​

 

[Krumlov]

So I ran Driver Verifier. I was one of those cases where it crashes before any information is given. I am using "System Restore" right now.

What was I trying to learn by running Driver Verifier, and was it a bad thing that I had to system restore?

I will continue looking for that driver update.

(Also, here is the minidump error file that I got, it was a "c4" error this time.)