Newly Built System - Windows 7 BSOD.

[Crimson1987]

Hello everyone,

I am new to the forums here, and I am in dire need of some guidance please. I just recently put together a brand new build which hopefully you can see in my system specs. I did a clean install of Windows 7 Professional 64 - bit and have been having it BSOD on me with an recovery message when I log back into windows. I get the following message:

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.48
Locale ID: 1033

Additional information about the problem:
BCCode: 7f
BCP1: 0000000000000008
BCP2: 0000000080050031
BCP3: 00000000000006F8
BCP4: FFFFF80002A885A2
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\090909-21418-01.dmp
C:\Users\CRIMSON\AppData\Local\Temp\WER-48968-0.sysdata.xml

Read our privacy statement online:
Windows 7 Privacy Highlights - Microsoft Windows

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

I am thinking that it might be some kinda of driver that windows does not like that keeps on causing it to crash or maybe possible defective hardware (which I am hoping is not the case.) I have ran the Windows Diagnostics utility on the ram and have also did some CPU stress test, but did not see anything wrong. These crashes happens daily, and I am out of ideas as to what maybe causing the reason. Does anyone have any suggestions I would really appreciate it. I have also attached the .dmp that was created after my most recent crash...all the crashes give me the same exact error I posted above. Oh...one more thing the BSOD does not give me one of those lines that seems to specify the problem more.

Thank you,

Crimson1987

Edit: Sorry thought it would have shown my system specs since I filled that out in my profile but here they are.

System Manufacturer/Model Number Custom Built
OS Windows 7 Professional
CPU AMD Phenom II X4 955BE
Motherboard GIGABYTE MA790FTX - UD5P
Memory G.Skill 1333 4 gigs
Graphics Card XFX ATI Radeon 4980
Sound Card onboard
Screen Resolution 1680x1050

Keyboard Dell Keyboard
Mouse Dynex
PSU CORSAIR TX850W
Case CM 690
Cooling Air
Hard Drives WD 640gig HDD

 

[GailLA]

Do you have any idea of when the BSODs started? You might look in the Reliability Monitor in the Action Center to see if they started after you installed a particular piece of hardware or a new driver. Then try removing the hardware and/or driver from your system to see if that was the culprit.

P.S. Not everything shows up in Reliability Monitor, but it will show when drivers were added and if you know when this started, it can help narrow things down.

 

[zigzag3143]

Could you go into c:\windows\minidump, zip the dump file (*.dmp) and upload it for us to debug? If its not in minidump just search for *.dmp

Ken

 

[Crimson1987]

I tried to do a Zip for the dmp file but it had some error according the winzip, but it still made the zip file. Umm, I tried uploading it was not uploading I'll try again.

Oh sorry...yes it started doing it this past sunday. However I did a reinstall, to see if that would help but it did not so I have not really installed many things atm.

 

[zigzag3143]

let me know if you need help in uploading the file

Ken

 

[Crimson1987]

Yes, I think I need some help on how to upload this file lol...thank you.

The Minidump folder has a like a lockpad icon on it? Maybe that's why it Winzip won't zip it properly and will not allow me to upload it?

 

[zigzag3143]

pretty easy. click on the paper clip shaped icon (attachment) and a window will open. see pic. let me know if you need more k

 

[Crimson1987]

Oh I did that, but it will not upload the zip file. It just says that it fails every time I try.

 

[Crimson1987]

Ok, finally was able to get it to zip. Had to copy the .dmp file to my desktop and zip it from there. Hopefully this will be of big help. Thanks.

 

[Crimson1987]

Anyone Have any suggestions? I really need some help on this guys, any information will be really helpful. thanks.

 

[Dzomlija]

Have a look at this information, from the Microsoft Developer Network that describes what STOP 0x7F means: Bug Check 0x7F: UNEXPECTED_KERNEL_MODE_TRAP.

The first parameter of the bug check in your case is 0x00000008, which means the following:

0x00000008, or Double Fault, indicates that an exception occurs during a call to the handler for a prior exception. Typically, the two exceptions are handled serially. However, there are several exceptions that cannot be handled serially, and in this situation the processor signals a double fault. There are two common causes of a double fault:

• A kernel stack overflow. This overflow occurs when a guard page is hit, and the kernel tries to push a trap frame. Because there is no stack left, a stack overflow results, causing the double fault. If you think this overview has occurred, use the !thread debugger extension to determine the stack limits, and then use the kb (Display Stack Backtrace) debugger command with a large parameter (for example, kb 100) to display the full stack.
• A hardware problem.

Go through the rest of the information on the MSDN website. It may help isolate what is causing this error.

On a related note, I've seen STOP 0x7F numerous times on computers where users have installed BETA drivers, or incompatible "Virtual CD/DVD" drivers. If this is your case, try uninstalling the program, and then locate and install an updated (7-compatible) version.

 

[Crimson1987]

Ugh a hardware issue? Well isn't that just great to know....hmmm, is there a possible way to tell what part might be causing the issue? I am thinking either the cpu or the gpu can be faulty?

 

[Dzomlija]

Remove all "additional" hardware you may have installed, including your graphics card (unless your motherboard is not equipped with an onboard gpu).

Overheating or incorrect overclocking can also cause "hardware issues"...

 

[Dwarf]

I've just had a look at the motherboard manual. There is no on-board graphics, so check which slot you have inserted your graphics card in. It should be in the first slot, nearest the CPU.

 

[zigzag3143]

Ugh a hardware issue? Well isn't that just great to know....hmmm, is there a possible way to tell what part might be causing the issue? I am thinking either the cpu or the gpu can be faulty?

Crimson

After a q2quick look at the dump file the bsod was caused by netIO.sys there isnt a whole lot of info on the reason netio failed but I would try disconnecting any hware that isnt critical like external usb HD, etc. I would also look at the date on netio.sys file to make sure it is current. you can search for it. When one of our true debugging gurus look at the dubegging info they may be able to give you more info.

Ken




Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\090909-21418-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*d:\symbols*Symbol information
Executable search path is:
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02a11000 PsLoadedModuleList = 0xfffff800`02c4ee50
Debug session time: Wed Sep 9 21:16:38.278 2009 (GMT-4)
System Uptime: 0 days 0:08:58.964
Loading Kernel Symbols
...............................................................
................................................................
...................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 7F, {8, 80050031, 6f8, fffff80002a885a2}

Probably caused by : NETIO.SYS ( NETIO!CompareSecurityContexts+6a )

Followup: MachineOwner
---------

2: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault). The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
use .trap on that value
Else
.trap on the appropriate frame will show where the trap was taken
(on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
Arg2: 0000000080050031
Arg3: 00000000000006f8
Arg4: fffff80002a885a2

Debugging Details:
------------------


BUGCHECK_STR: 0x7f_8

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 2

LAST_CONTROL_TRANSFER: from fffff80002a82469 to fffff80002a82f00

STACK_TEXT:
fffff880`02f69ce8 fffff800`02a82469 : 00000000`0000007f 00000000`00000008 00000000`80050031 00000000`000006f8 : nt!KeBugCheckEx
fffff880`02f69cf0 fffff800`02a80932 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`02f69e30 fffff800`02a885a2 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb2
fffff880`02f86000 fffff800`02a4b842 : fffffa80`08ea8080 00000000`00000001 00000000`00000000 fffffa80`049b47c8 : nt!SeAccessCheckWithHint+0x312
fffff880`02f860e0 fffff880`015a1c5a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!SeAccessCheckFromState+0x102
fffff880`02f867d0 fffff880`0159f94f : 00000000`c0000022 00000000`00000000 00000000`00000000 00000000`00000000 : NETIO!CompareSecurityContexts+0x6a
fffff880`02f86840 fffff880`015a19b5 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : NETIO!MatchValues+0xef
fffff880`02f86890 fffff880`015a1845 : fffffa80`08a0d7a0 fffffa80`08e022a0 fffff880`02f86ab8 fffff880`02f871f0 : NETIO!FilterMatch+0x95
fffff880`02f868e0 fffff880`015a2ccb : 00000000`00000000 00000000`00000000 fffff880`02f871f0 fffff880`02f86aa0 : NETIO!IndexListClassify+0x69
fffff880`02f86960 fffff880`0163e4d0 : fffff880`02f871f0 fffff880`02f86e38 fffff880`02f87b70 fffffa80`04aa3030 : NETIO!KfdClassify+0xa4e
fffff880`02f86cd0 fffff880`0163777e : fffff880`01746690 00000000`00000000 fffffa80`08970430 00000000`00000000 : tcpip!WfpAleClassify+0x50
fffff880`02f86d10 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : tcpip!WfpAlepAuthorizeSend+0x94e


STACK_COMMAND: kb

FOLLOWUP_IP:
NETIO!CompareSecurityContexts+6a
fffff880`015a1c5a 448b442470 mov r8d,dword ptr [rsp+70h]

SYMBOL_STACK_INDEX: 5

SYMBOL_NAME: NETIO!CompareSecurityContexts+6a

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: NETIO

IMAGE_NAME: NETIO.SYS

DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc18a

FAILURE_BUCKET_ID: X64_0x7f_8_NETIO!CompareSecurityContexts+6a

BUCKET_ID: X64_0x7f_8_NETIO!CompareSecurityContexts+6a

Followup: MachineOwner


Ken

 

[Anthony]

Check to see if your memory is getting the right amount of volts in your bios, most memory is either 1.8v or 2.0v

Good Luck

 

[Crimson1987]

Hey, guys thanks for all of the information and tips. I have reinstalled the Drivers on my ATI card and left it running on all night (acutally I went to throw in my old nvidia card which I have running on my vista machine, and realized I did not fully uninstall my ati drivers and just tossed the ati card back in), have not got any BSOD's as of yet. I have been looking up on the netIO.sys file and it seems to be some kinda of network driver? My motherboard has 2 ethernet ports. I have net cables plugged into both of them. Do you thinkg that can be casuing an issue?

I have not looked at the netio.sys file as of yet, when I get the time to look at it, what exactly am I looking for? Since it is a .sys file how am I going to open it to check the date as Ken mentioned? Also, can external usb devices like a mouse or keyboard drivers cause this problem or is this error message always related to a hardware problem rather than a incompatible driver? Thanks.


~Crimson

 

[Crimson1987]

Just an update for you guys. I did some more reading on that NetIO.Sys and it seems to relate to the network adapter? So I went into my device manager and updated the drivers on that. Windows actually found new drivers for it and so far no BSOD. So I am hoping that everything is ok.

However, if anyone else cares to look at the dmp file that I posted and give me more suggestions I would appreciate the feedback. Thanks!


~Crimson