BSOD 7F, Please help before I pull out all my hair!!!

[Nimbus22]

Hi guys,

Please help. I just built a new pc with the following parts running on Windows 7 Ultimate 64bits.

Core i5 750
Gigabyte GA-P55-UD3R
4GB G.Skill Ripjaws DDR3 1600 (F3-12800CL7D-4GBRM)
PNY 1GB 9800GT Energy Efficient Version

Been having random crashes. I have done the following to diagnose what could be the cause via process of elimination.

- tested both 2gb sticks of ram and found one to be defective through memtest86+ v4.00. Removed that stick from my system.

- check the motherboard dimm by moving the good and bad stick of ram around and the dimm slots are good.

- Did a clean reinstall of windows 7 with the stick of 2gb ram that passed memtest86+ without error (14 passes).

- checked temp with hwmonitor and gpuz (temps normal)

- psu is PC power and cooling silencer 610w (been working fine, unlikely the cause)

- device manager shows no conflicts

- Did not update or install anything on the system and let it ran overnight. There were no issues.

- I then proceeded to install the latest intel chipset drivers for my motherboard from gigabyte's site, flash player, windows live mail, and zonealarm extreme security. With only those 4 installs the BSOD returned.

This is the error code from the bsod. It is the same code from before my reinstall.
0x0000007f (0x0000000000000008, 0x0000000080050031, 0x00000000000006f8, 0xfffff80002883609)

I have attached a rar of the minidump file. Please take a look and help me out. Please help me isolate what is the cause of the bsod, as I feel that it is a driver issue instead of hardware issue.

This problem has been driving me crazy for over a week now. I can't do anything with my system out of order.


Thanks in advance guys.

 

[Nimbus22]

anybody have any ideas? please help!

 

[Tews]

anybody have any ideas? please help!

STOP 0x0000007F (UNEXPECTED_KERNEL_MODE_TRAP)

This is probably a memory problem .... This error message can occur if either of the following conditions exists:

• Your computer has hardware or software problems (hardware failure is the most common cause).
• You try to over clock the speed of your computer's processor (for example, you set a 150 MhZ processor to run at 187 MhZ).

The above STOP error means a trap occurred in kernel mode and the trap is either one the kernel is not allowed to have or is always fatal. The most common causes of a STOP 0x7F are:

• Low-level hardware corruption, such as corrupt memory (RAM)
• Mismatched memory modules
• A malfunctioning motherboard

I would strongly suggest replacing all of your memory... RMA it if you can... Hope this helps...

 

[Nimbus22]

Hi Tews,

Thank you for responding to my problem. I have thought of the ram issue. I did test them and one of them was defective. Right now I am running on the remaining 2gb stick of ram that passed memtest86+ on multiple testing session of 5-14 good passes.

Are you recommending that I return the good stick of ram also? And did you happen to see if there are any driver caused conflict in the dump file.

Thanks again Tews and everyone that's looking into this.

 

[Tews]

If you are still getting the same stop error, then yes I would return it, especially if it is still under warranty.. If you are no longer getting a BSOD with just the one stick, then you are probably ok...

 

[Nimbus22]

Thanks Tews. I will keep that in mind as I run the system for the next few days to check for errors. Still could anyone please take a look at the dump file and post a diagosntic of it. I strongly feel that there is a driver that is causing a conflict.

My analysis is based on that when I had the bad stick of ram in along with the good stick of ram, my bsod error code doesn't seem to be all the same. Now with only the good stick of ram my bsod error code 7F is the same time and time again.

I just need someone to take a look at the dump file and post a diagnostic of it so that I can put driver conflict behind me if drivers are not the cause of these bsod.

I don't want to rma both sticks of ram and be without a working computer for two weeks (can you imagine life without a computer and internet?) and then going through the same bsod again only to found out that a driver is the culprit.

I really appreciate the effort that you guys put into helping others out.

Attached is a copy of the dump file again.



Thanks again.

 

[usasma]

More info on the STOP 0x7F error message: BSOD Index

The dump file blames NETIO.SYS, and tcpip.sys is also involved in the stack. These are both components of the Windows networking sub-system. As such we'll have to look at your networking drivers and any protection software that may impact this.

I would:
- remove and replace your Realtek networking drivers
- uninstall ZoneAlarm

Please provide us with this info:

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.

If you're having difficulties with the format, please open an elevated (Run as administrator) Command Prompt and type "msinfo32 /nfo C:\Users\Public\Desktop\TEST.NFO" (without the quotes) and press Enter. Then navigate to the C:\Users\Public\Desktop directory to retrieve the TEST.NFO file. If you have difficulties with making this work, please post back.

Here's a summary of the BSOD:

Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Mon Jan 25 20:05:15.026 2010 (GMT-5)
System Uptime: 0 days 0:16:46.104
BugCheck 7F, {8, 80050031, 6f8, fffff80002883609}
Probably caused by : NETIO.SYS ( NETIO!CompareSecurityContexts+6a )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System

 

[Nimbus22]

Hi Usasma,

First thank you for your help with my bsod. I really appreciate it.

I have attached my msinfo32.nfo for your review.
Please note that the Teredo Tunneling in problem devices is disable by zonealarm with my knowledge. Could you also tell me if there is something wrong with windows error reporting logging error with future date and time? I see an error on there with 1/27/2010 when today is only 1/26/2010.

Also I don't know if what happened this morning to my system is related to this bsod issue or not, but when i turned on my computer this morning, it would not enter bios or load windows and remain stuck on hardware detection screen. I already have the latest bios for my motherboard. After scratching my head for a while, I noticed that one of my dvd writers is not being detected. I do not know if this issue is cause by my dvd writer sharing the same channel with one of my storage hard drive. They were listed as storage hd - channel 1 master and dvd writer - channel 1 slave. Anyway I went into my pc and reconnected the dvd writer into another sata port. Now all my hdds and dvd writers are masters in their own channel. My computer booted right back up and loaded windows.

Ever since I corrected this issue, my computer has been functioning correctly. Screensaver, monitor power down, and sleep working perfectly without windows changing its' setting. Before my system would not enter sleep sometimes and I would find that windows have changed my sleep settings. Any ideas why?

I kind of suspect that my system is bsod-ing due to a conflict with powering down and powering up of my storage drive that was sharing the channel with the dvd writer. This would explain why my system is not entering sleep before since it wasn't correctly powering down that non os hdd. I am just wondering all over. Could this be possible or am I just being a noob. hahahahaa.......

So far I haven't had a bsod in the last 16 hours knock on wood. Sorry for this long winded reply. Please review and let me know of your foundings and ideas.

Thank you so much for your help!

 

[usasma]

I suggest waiting to see if you get any more BSOD's.
Please uninstall the Teredo device in Device Manager - it's likely to be causing problems with the system. In most cases that I see, uninstalling the device will fix networking problems.

 

[Nimbus22]

I set zonealarm to allow teredo tunneling. the device is working normally now. Thanks for the heads up. I will keep a close eye on my system for the next few days to a week to see if the bsod issue has been resolved. I hope it has been taken care of. Thanks again for your help.

 

[usasma]

Glad to hear that it's working for you!
Thanks for letting us know!