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: omg just about every boot up ntoskrnl.exe bsod

05 Feb 2013   #1
wagne5a2

windows 7 64
 
 
omg just about every boot up ntoskrnl.exe bsod

so just about on every boot up my desktop loads then blue screen This has only been happening since I upgraded from windows 7 32 to windows 7 64. not idea how to fix this. I tried the repair disk and nothing changed.


Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Tue 2/5/2013 4:01:31 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\020513-38641-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0)
Bugcheck code: 0xC1 (0xFFFFF9802AEF0FC0, 0xFFFFF9802AEF02BC, 0xFB4048, 0x32)
Error: SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that the driver wrote to an invalid section of the special pool.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.




My System SpecsSystem Spec
.
05 Feb 2013   #2
wagne5a2

windows 7 64
 
 

Microsoft (R) Windows Debugger Version 6.2.9200.20512 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Windows\Minidump\020513-38641-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Machine Name:
Kernel base = 0xfffff800`03c4d000 PsLoadedModuleList = 0xfffff800`03e89e70
Debug session time: Tue Feb 5 09:01:31.446 2013 (UTC - 7:00)
System Uptime: 0 days 0:01:35.772
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
................................................................
..........................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck C1, {fffff9802aef0fc0, fffff9802aef02bc, fb4048, 32}
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
Probably caused by : ntoskrnl.exe ( nt+705c0 )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION (c1)
Special pool has detected memory corruption. Typically the current thread's
stack backtrace will reveal the guilty party.
Arguments:
Arg1: fffff9802aef0fc0, address trying to free
Arg2: fffff9802aef02bc, address where one bit is corrupted
Arg3: 0000000000fb4048, (reserved)
Arg4: 0000000000000032, caller is freeing an address where nearby bytes within the same page have a single bit error
Debugging Details:
------------------
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
My System SpecsSystem Spec
05 Feb 2013   #3
wagne5a2

windows 7 64
 
 

*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
ADDITIONAL_DEBUG_TEXT:
You can run '.symfix; .reload' to try to fix the symbol path and load symbols.
MODULE_NAME: nt
FAULTING_MODULE: fffff80003c4d000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 503f857d
BUGCHECK_STR: 0xC1_32
SPECIAL_POOL_CORRUPTION_TYPE: 32
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff80003d4cc63 to fffff80003cbd5c0
STACK_TEXT:
fffff800`00b9c148 fffff800`03d4cc63 : 00000000`000000c1 fffff980`2aef0fc0 fffff980`2aef02bc 00000000`00fb4048 : nt+0x705c0
fffff800`00b9c150 00000000`000000c1 : fffff980`2aef0fc0 fffff980`2aef02bc 00000000`00fb4048 00000000`00000032 : nt+0xffc63
fffff800`00b9c158 fffff980`2aef0fc0 : fffff980`2aef02bc 00000000`00fb4048 00000000`00000032 fffff800`04150adc : 0xc1
fffff800`00b9c160 fffff980`2aef02bc : 00000000`00fb4048 00000000`00000032 fffff800`04150adc 00000000`00000001 : 0xfffff980`2aef0fc0
fffff800`00b9c168 00000000`00fb4048 : 00000000`00000032 fffff800`04150adc 00000000`00000001 fffff800`03dc3ba3 : 0xfffff980`2aef02bc
fffff800`00b9c170 00000000`00000032 : fffff800`04150adc 00000000`00000001 fffff800`03dc3ba3 fffffa80`00000003 : 0xfb4048
fffff800`00b9c178 fffff800`04150adc : 00000000`00000001 fffff800`03dc3ba3 fffffa80`00000003 fffffa80`059a7460 : 0x32
fffff800`00b9c180 00000000`00000001 : fffff800`03dc3ba3 fffffa80`00000003 fffffa80`059a7460 00000000`00000246 : nt+0x503adc
fffff800`00b9c188 fffff800`03dc3ba3 : fffffa80`00000003 fffffa80`059a7460 00000000`00000246 fffff800`04150dfe : 0x1
fffff800`00b9c190 fffffa80`00000003 : fffffa80`059a7460 00000000`00000246 fffff800`04150dfe fffff800`00b9c1b0 : nt+0x176ba3
fffff800`00b9c198 fffffa80`059a7460 : 00000000`00000246 fffff800`04150dfe fffff800`00b9c1b0 fffff800`00b97000 : 0xfffffa80`00000003
fffff800`00b9c1a0 00000000`00000246 : fffff800`04150dfe fffff800`00b9c1b0 fffff800`00b97000 00000000`00000001 : 0xfffffa80`059a7460
fffff800`00b9c1a8 fffff800`04150dfe : fffff800`00b9c1b0 fffff800`00b97000 00000000`00000001 fffff800`03e73a60 : 0x246
fffff800`00b9c1b0 fffff800`00b9c1b0 : fffff800`00b97000 00000000`00000001 fffff800`03e73a60 fffffa80`03c5d1e0 : nt+0x503dfe
fffff800`00b9c1b8 fffff800`00b97000 : 00000000`00000001 fffff800`03e73a60 fffffa80`03c5d1e0 fffff800`03ce2b92 : 0xfffff800`00b9c1b0
fffff800`00b9c1c0 00000000`00000001 : fffff800`03e73a60 fffffa80`03c5d1e0 fffff800`03ce2b92 00000000`00000040 : 0xfffff800`00b97000
fffff800`00b9c1c8 fffff800`03e73a60 : fffffa80`03c5d1e0 fffff800`03ce2b92 00000000`00000040 00000000`00000001 : 0x1
fffff800`00b9c1d0 fffffa80`03c5d1e0 : fffff800`03ce2b92 00000000`00000040 00000000`00000001 00000000`00000000 : nt+0x226a60
fffff800`00b9c1d8 fffff800`03ce2b92 : 00000000`00000040 00000000`00000001 00000000`00000000 00000000`00000000 : 0xfffffa80`03c5d1e0
fffff800`00b9c1e0 00000000`00000040 : 00000000`00000001 00000000`00000000 00000000`00000000 00000000`00000040 : nt+0x95b92
fffff800`00b9c1e8 00000000`00000001 : 00000000`00000000 00000000`00000000 00000000`00000040 fffff800`03db2efb : 0x40
fffff800`00b9c1f0 00000000`00000000 : 00000000`00000000 00000000`00000040 fffff800`03db2efb fffff980`2aef0000 : 0x1

STACK_COMMAND: kb
FOLLOWUP_IP:
nt+705c0
fffff800`03cbd5c0 48894c2408 mov qword ptr [rsp+8],rcx
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt+705c0
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: ntoskrnl.exe
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner
---------
My System SpecsSystem Spec
.

05 Feb 2013   #4
Dsprague

Microsoft Community Contributor Award Recipient

Windows 7 enterprise 64 bit, Windows 7 Pro 64 bit ,Windows 8 64bit
 
 

My System SpecsSystem Spec
05 Feb 2013   #5
wagne5a2

windows 7 64
 
 

okay
My System SpecsSystem Spec
05 Feb 2013   #6
Dsprague

Microsoft Community Contributor Award Recipient

Windows 7 enterprise 64 bit, Windows 7 Pro 64 bit ,Windows 8 64bit
 
 

Ok first things first, please updated to Service Pack 1:

Learn how to install Windows 7 Service Pack 1 (SP1)

second it seems that at least some of your problems are being caused by McAfee please uninstall it using this tool:

McAfee removal tool

Then replace it with MSE and Mbam

Tip: Uncheck the box to start a free trial with Mbam when installing
My System SpecsSystem Spec
05 Feb 2013   #7
wagne5a2

windows 7 64
 
 

so I tried the system readiness tool to fix this issue with no aval
Pc would not install windows 7 sp1 got this error

ERROR_SXS_COMPONENT_STORE_CORRUPT(0x80073712)
My System SpecsSystem Spec
05 Feb 2013   #8
Dsprague

Microsoft Community Contributor Award Recipient

Windows 7 enterprise 64 bit, Windows 7 Pro 64 bit ,Windows 8 64bit
 
 

Open an elevated command prompt and run the following command then try to update again:

Code:
SFC /SCANNOW
My System SpecsSystem Spec
05 Feb 2013   #9
wagne5a2

windows 7 64
 
 

sorry bro still will not install sp1 :/
My System SpecsSystem Spec
05 Feb 2013   #10
Dsprague

Microsoft Community Contributor Award Recipient

Windows 7 enterprise 64 bit, Windows 7 Pro 64 bit ,Windows 8 64bit
 
 

Please download and run Memtest86+ for 8+ passes:

RAM - Test with Memtest86+

Tip: do this overnight it will take quite some time
My System SpecsSystem Spec
Reply

 omg just about every boot up ntoskrnl.exe bsod




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
BSOD on boot, ntoskrnl.exe
Recently, I have been having random BSODs on booting after the Windows 7 boot animation. There have been 4 different types of BSOD, those being SYSTEM_THREAD_EXCEPTION_NOT_HANDLED, BAD_POOL_CALLER, BAD_POOL_HEADER, and DRIVER_CORRUPTED_EXPOOL. Looking at BlueScreenView, they were all related to...
BSOD Help and Support
BSOD on first boot then okay! (NTOSKRNL.exe)
The Title says it all! Custom built PC and removed a hard drive from my old PC to the new one and upgraded all the drivers but however when i do my first boot of the day the computer will BSOD however when it reboots it will then work and i have no BSODs at all. I have ran BlueScreenView and that...
BSOD Help and Support
BSOD every boot - PAGE_FAULT_IN_NONPAGED_AREA (ntoskrnl.exe)
Hello 7forums, this is my first post. I read the posting guidelines, hope I've got in most of what is needed below. Since last friday on the 26th of october my computer is blue screening every time I use it. The computer BSODs immediatelly after the Windows loading screen on 100 % of all boots....
BSOD Help and Support
BSOD's on cold boot, ntoskrnl.exe, ntfs.sys
It is my first post at SevenForums.com, so hello everyone! I thought I would figure it out on my own, but I was wrong. For a couple of weeks I've been struggling with bsods, which occur mainly on cold boot, 3 to 4 times before everything stabilizes. I've already tested my ram with memtest and...
BSOD Help and Support
BSOD on every second or third boot (ntoskrnl.exe)
Hello there, another problem with my new PC... About every second or third time I boot my PC, I'm getting a blue screen. As I said, I don't get it every time I boot, sometimes I can do a single boot without this BSOD, sometimes I can go two boots without it. It happens about 10 seconds after...
BSOD Help and Support
BSOD on first boot ntoskrnl.exe
Hi everyone, ended up here after googling my problem and found some threads with similiar but not the exact same circumstances. Always, without fault, on the first boot I get a BSOD after windows have finished starting up. Every boot after that works like a charm but if I leave it off for a half...
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 10:46.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App