Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: Periodic BSOD, even after upgrade

03 Feb 2010   #1
Aslund

Windows 7
 
 
Periodic BSOD, even after upgrade

Hey everyone

I had a random BSOD coming up and decided that I needed a hardware upgrade too, so I changed motherboard, CPU and RAM.
The problem is that I just got a BSOD again and I am quite lost why.
On the old machine the problem seemed to start when I added a second screen to my PC, but even sticking to one screen afterward didn't help. At that time I used the iterated graphic card on the AMD 785G motherboard, but changed in to the AMD Radeon 4550 card without help.
Later I upgraded to AMD Phenom II X4 955, Kingston HyperX CL7 1333MHz and Gigabyte GA-MA790FXT-UD5P, but kept my 4 Western Digital GreenPower hard drives, one 2.5" 7200rpm Hitachi hard drive, a 550W Corsair power supply and a Creative X-Fi Elite Pro.
I guess the problem is the same, but I am not 100% sure.
The result of the minidump have I added below, thanks for your help.

Regards

Sebastian Aslund
-------------------------------------------------------------------------
Edit: I see people add the file instead, so I have added the file instead of posting the whole message.


My System SpecsSystem Spec
.
03 Feb 2010   #2
Jonathan_King

Windows 7 Professional x64
 
 

Welcome!

I am not very skilled in the art of the BSOD, but from what I gather, the problem was caused by NetIO.sys.

See this article here on how to fix it.

If you upgraded from Vista instead of doing a Clean Install, you may want to update your network card drivers, too.

Hope this helps!

~JK

Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Jonathan\Desktop\020310-22776-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbol
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`02a0b000 PsLoadedModuleList = 0xfffff800`02c48e50
Debug session time: Wed Feb  3 06:54:33.742 2010 (GMT-5)
System Uptime: 0 days 0:46:55.100
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, fffff80002a5840f}

Unable to load image \SystemRoot\system32\drivers\NETIO.SYS, Win32 error 0n2
*** WARNING: Unable to verify timestamp for NETIO.SYS
*** ERROR: Module load completed but symbols could not be loaded for NETIO.SYS
Probably caused by : NETIO.SYS ( NETIO+6c5a )

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

1: 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: fffff80002a5840f

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 fffff80002a7c469 to fffff80002a7cf00

STACK_TEXT:  
fffff880`009edce8 fffff800`02a7c469 : 00000000`0000007f 00000000`00000008 00000000`80050031 00000000`000006f8 : nt!KeBugCheckEx
fffff880`009edcf0 fffff800`02a7a932 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`009ede30 fffff800`02a5840f : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb2
fffff880`08e4d000 fffff800`02a4569c : fffff880`08e4d0e0 fffffa80`045ae7c8 00000000`00000000 00000000`00000000 : nt!RtlSidHashInitialize+0x2f
fffff880`08e4d030 fffff800`02a457df : fffffa80`045ae7c8 00000000`00000001 00000000`00000000 00000000`00000000 : nt!SepTokenFromAccessInformation+0xbc
fffff880`08e4d060 fffff880`0159cc5a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!SeAccessCheckFromState+0x9f
fffff880`08e4d750 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : NETIO+0x6c5a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
NETIO+6c5a
fffff880`0159cc5a ??              ???

SYMBOL_STACK_INDEX:  6

SYMBOL_NAME:  NETIO+6c5a

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: NETIO

IMAGE_NAME:  NETIO.SYS

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc18a

FAILURE_BUCKET_ID:  X64_0x7f_8_NETIO+6c5a

BUCKET_ID:  X64_0x7f_8_NETIO+6c5a

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

1: 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: fffff80002a5840f

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 fffff80002a7c469 to fffff80002a7cf00

STACK_TEXT:  
fffff880`009edce8 fffff800`02a7c469 : 00000000`0000007f 00000000`00000008 00000000`80050031 00000000`000006f8 : nt!KeBugCheckEx
fffff880`009edcf0 fffff800`02a7a932 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`009ede30 fffff800`02a5840f : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb2
fffff880`08e4d000 fffff800`02a4569c : fffff880`08e4d0e0 fffffa80`045ae7c8 00000000`00000000 00000000`00000000 : nt!RtlSidHashInitialize+0x2f
fffff880`08e4d030 fffff800`02a457df : fffffa80`045ae7c8 00000000`00000001 00000000`00000000 00000000`00000000 : nt!SepTokenFromAccessInformation+0xbc
fffff880`08e4d060 fffff880`0159cc5a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!SeAccessCheckFromState+0x9f
fffff880`08e4d750 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : NETIO+0x6c5a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
NETIO+6c5a
fffff880`0159cc5a ??              ???

SYMBOL_STACK_INDEX:  6

SYMBOL_NAME:  NETIO+6c5a

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: NETIO

IMAGE_NAME:  NETIO.SYS

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc18a

FAILURE_BUCKET_ID:  X64_0x7f_8_NETIO+6c5a

BUCKET_ID:  X64_0x7f_8_NETIO+6c5a

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

1: 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: fffff80002a5840f

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 fffff80002a7c469 to fffff80002a7cf00

STACK_TEXT:  
fffff880`009edce8 fffff800`02a7c469 : 00000000`0000007f 00000000`00000008 00000000`80050031 00000000`000006f8 : nt!KeBugCheckEx
fffff880`009edcf0 fffff800`02a7a932 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`009ede30 fffff800`02a5840f : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb2
fffff880`08e4d000 fffff800`02a4569c : fffff880`08e4d0e0 fffffa80`045ae7c8 00000000`00000000 00000000`00000000 : nt!RtlSidHashInitialize+0x2f
fffff880`08e4d030 fffff800`02a457df : fffffa80`045ae7c8 00000000`00000001 00000000`00000000 00000000`00000000 : nt!SepTokenFromAccessInformation+0xbc
fffff880`08e4d060 fffff880`0159cc5a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!SeAccessCheckFromState+0x9f
fffff880`08e4d750 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : NETIO+0x6c5a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
NETIO+6c5a
fffff880`0159cc5a ??              ???

SYMBOL_STACK_INDEX:  6

SYMBOL_NAME:  NETIO+6c5a

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: NETIO

IMAGE_NAME:  NETIO.SYS

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc18a

FAILURE_BUCKET_ID:  X64_0x7f_8_NETIO+6c5a

BUCKET_ID:  X64_0x7f_8_NETIO+6c5a

Followup: MachineOwner
---------
My System SpecsSystem Spec
03 Feb 2010   #3
swarfega

Windows 7 Professional 64-bit
 
 

General causes of "STOP 0x0000007F" errors might help you, it would appear to be a hardware related issue.
My System SpecsSystem Spec
.

03 Feb 2010   #4
ickymay

win7 ultimate / virtual box
 
 

Quote   Quote: Originally Posted by Aslund View Post
Hey everyone

I had a random BSOD coming up and decided that I needed a hardware upgrade too, so I changed motherboard, CPU and RAM.
The problem is that I just got a BSOD again and I am quite lost why.
On the old machine the problem seemed to start when I added a second screen to my PC, but even sticking to one screen afterward didn't help. At that time I used the iterated graphic card on the AMD 785G motherboard, but changed in to the AMD Radeon 4550 card without help.
Later I upgraded to AMD Phenom II X4 955, Kingston HyperX CL7 1333MHz and Gigabyte GA-MA790FXT-UD5P, but kept my 4 Western Digital GreenPower hard drives, one 2.5" 7200rpm Hitachi hard drive, a 550W Corsair power supply and a Creative X-Fi Elite Pro.
I guess the problem is the same, but I am not 100% sure.
The result of the minidump have I added below, thanks for your help.

Regards

Sebastian Aslund
-------------------------------------------------------------------------
Edit: I see people add the file instead, so I have added the file instead of posting the whole message.
what antivirus and firewall are you using ?

this driver for the Creative X-Fi Elite Pro
Quote:
ctac32k.sys fffff880`06800000 fffff880`068ae000 0x000ae000 0x486b3e7e 02/07/2008 08:38:22
is old and needs replacing
My System SpecsSystem Spec
03 Feb 2010   #5
Aslund

Windows 7
 
 

Jonathan_King ->
I have done a clean install, but your link is for BSOD in Vista, does it also apply to Win7?

ickymay ->
I have Zonealarm Security Suite and my creative driver should be the newest from their website :S
My System SpecsSystem Spec
03 Feb 2010   #6
Jonathan_King

Windows 7 Professional x64
 
 

It should also apply to 7.
My System SpecsSystem Spec
04 Feb 2010   #7
ickymay

win7 ultimate / virtual box
 
 

Quote   Quote: Originally Posted by Aslund View Post
Jonathan_King ->
I have done a clean install, but your link is for BSOD in Vista, does it also apply to Win7?

ickymay ->
I have Zonealarm Security Suite and my creative driver should be the newest from their website :S
well this driver is old and needs replacing or removing as it could be tipping your system over
Quote:
ctac32k.sys fffff880`06800000 fffff880`068ae000 0x000ae000 0x486b3e7e 02/07/2008 08:38:22
My System SpecsSystem Spec
04 Feb 2010   #8
Aslund

Windows 7
 
 

Hey everyone

Thanks alot for your replies.
I read that Zonealarm can cause problems with NetIO.sys, so I will try to uninstall it and put Microsoft Essentials instead while deleting the Creative driver too.

I did 6 hours Prime95 test yesterday without my PC breaking a sweat, so the hardware hsould be stable and ok.
My System SpecsSystem Spec
04 Feb 2010   #9
ickymay

win7 ultimate / virtual box
 
 

Quote   Quote: Originally Posted by Aslund View Post
Hey everyone

Thanks alot for your replies.
I read that Zonealarm can cause problems with NetIO.sys, so I will try to uninstall it and put Microsoft Essentials instead while deleting the Creative driver too.

I did 6 hours Prime95 test yesterday without my PC breaking a sweat, so the hardware hsould be stable and ok.
yup clean out zone alarm completely and let us know if your system stabilizes
My System SpecsSystem Spec
04 Feb 2010   #10
Aslund

Windows 7
 
 

So far the system runs without problems, I will give it a few days and return with the feedback.

Ps.
I uninstalled the Creative drivers and Zonealarm through the control panel, is this enough or should I mess with the registers too?
My System SpecsSystem Spec
Reply

 Periodic BSOD, even after upgrade




Thread Tools




Similar help and support threads
Thread Forum
Periodic BSOD during backups or watching videos
I've been having periodic (approximately once a week) BSOD's either while backups are occurring or while playing video games or watching videos. The most recent occurred during the early morning (around 1am) during a system backup. I use an external USB 3.0 drive and Acronis True Image 2014 for...
BSOD Help and Support
Periodic BSOD have been appearing
Hi, I bought my computer about 4 years ago and i never had problems of BSOD. Recently, frequently BSOD have been appearing and the system crash. The Diagnostic_Tool file required is atteched. I hope you can help me. Yours faithfully, Kogo
BSOD Help and Support
BSOD: Periodic d1 Crashes
The attached .dmp files show that BSOD has appeared several times in the last several weeks. But restarting to full capability has been no problem.
BSOD Help and Support
Periodic BSOD's
My system has Bluescreened 9 times in the past two monts. Attached is a zip of the last two and most common .dmp files. Can someone interpret these files and advise of a solution please?
BSOD Help and Support
periodic BSOD errors
Hi everyone, I have bought a new HP pavilion dv6 laptop Windows 7 home premium 64 bit After 2 weeks i started getting bsods every 3-4 days.Image restore of the OS didnt help.At the service centre,they suggested reinstalling thru another cd.After 20 days of doing that,the bsods started...
BSOD Help and Support
Periodic BSOD HELP PLEASE !!!
So i just did a fresh install of Windows 7 Ultimate because it crashed right after the login screen, it is only a few days later and it is crashing again not at the login screen but just periodically for no reason it always happens when im not actually using when i go to use the laptop again it is...
BSOD Help and Support


Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 08:29.
Twitter Facebook Google+ Seven Forums iOS App Seven Forums Android App