BSoD Kernal Power
I have been getting BSoD multiple times a day over the last couple months. My system dump provides the following info. Any help on the cause would be appreciated.
-
System
-
Provider
[
Name]
Microsoft-Windows-Kernel-Power
[
Guid]
{331C3B3A-2005-44C2-AC5E-77220C37D6B4}
EventID
41
Version
2
Level
1
Task
63
Opcode
0
Keywords
0x8000000000000002
-
TimeCreated
[
SystemTime]
2012-05-07T04:17:48.289208300Z
EventRecordID
211354
Correlation
-
Execution
[
ProcessID]
4
[
ThreadID]
8
Channel
System
Computer
feng-HP
-
Security
[
UserID]
S-1-5-18
-
EventData
BugcheckCode
268435582
BugcheckParameter1
0xffffffffc0000005
BugcheckParameter2
0x0
BugcheckParameter3
0xfffff880033c4488
BugcheckParameter4
0xfffff880033c3ce0
SleepInProgress
false
PowerButtonTimestamp
0
May 7th, 2012 12:41am
Follow the Knowledge Base article here
http://support.microsoft.com/kb/2028504/en-us
Regards
Milos
Free Windows Admin Tool Kit Click here and download it now
May 7th, 2012 12:57am
Hi,
Could you upload *.dump file on SkyDrive and let us analyze for you? Or you may check it yourself.
The log file will be %systemroot%\Minidump which is normally C:\windows\Minidump
The following steps may be performed:
1. Shut down the system, unplug it from power and wait at least several seconds.
2. Turn on the system, run sfc /scannow(without quotes) command.
3. Run an antivirus and scan the whole system.
4. Run the Windows Update to install all the latest service pack and hotfixes applicable to that system.
5. Update the drivers to the latest.
6. Have a hardware troubleshooting and check it again.
Here is a similar discussion and one article can be referred to.
BSoD kernel 41
http://social.technet.microsoft.com/Forums/en-us/w7itprogeneral/thread/326c6a5e-a585-4509-9700-5e7a6ecdeeed
How to read the small memory dump files that Windows creates for debugging
http://support.microsoft.com/kb/315263
Hope that helps.Ivan-Liu
TechNet Community Support
May 8th, 2012 4:32am
Thank you guys for the help! The links were very useful. I think I am dealing with more than one type of error at this time. Last night I was able to step through the HDD check, memory check, Windows Updates, and driver updates. I
believe that helped resolve/alleviate the condition I posted about above. Today there was another critical error that did not have a BugcheckCode listed.
Here is the latest minidump
https://skydrive.live.com/redir.aspx?cid=7087eac6aa2030da&resid=7087EAC6AA2030DA!105&parid=7087EAC6AA2030DA!101&authkey=!AAFztiD-3LtafGE
I will continue to pursue some of your other suggestions.
Free Windows Admin Tool Kit Click here and download it now
May 9th, 2012 1:11am
Hi,
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x7E
CURRENT_IRQL: 0
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: Wdf01000+35216
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: Wdf01000
IMAGE_NAME: Wdf01000.sys
STACK_COMMAND: .cxr 0xfffff880031bcce0 ; kb
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner
---------------------------------------------------------------------
We find that the Bugcheck 0x7E and Wdf01000.sys may be the reason cause this issue.
Wdf01000.sys is the driver of some program, please reinstall it. If this issue persists, you'd better uninstall the related program and device for further testing.
Here is one related discussion can be referred to.
wdf01000.sys blue screen
http://www.techsupportforum.com/forums/f299/wdf01000-sys-blue-screen-470167.html
Ivan-Liu
TechNet Community Support
May 10th, 2012 4:02am
*******************************************************************************
*
*
* Bugcheck Analysis
*
*
*
*******************************************************************************
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: fffff880031bd488, Exception Record Address
Arg4: fffff880031bcce0, Context Record Address
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
FAULTING_IP:
+16
00000000`00000000 ?? ???
EXCEPTION_RECORD: fffff880031bd488 -- (.exr 0xfffff880031bd488)
ExceptionAddress: 0000000000000000
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000008
Parameter[1]: 0000000000000000
Attempt to execute non-executable address 0000000000000000
CONTEXT: fffff880031bcce0 -- (.cxr 0xfffff880031bcce0)
rax=fffff880085d25c8 rbx=0000000000000000 rcx=fffffa805689ea30
rdx=fffffa805673a580 rsi=fffffa805673a580 rdi=fffffa80568839c0
rip=0000000000000000 rsp=fffff880031bd6c8 rbp=0000000000000000
r8=000000000000006c r9=fffff88000dcf370 r10=0000000000000004
r11=fffff880031bd800 r12=0000000000000009 r13=fffffa80568fb160
r14=0000000000000001 r15=fffffa80568e6d00
iopl=0 nv up ei ng nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010286
00000000`00000000 ?? ???
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 0
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
EXCEPTION_PARAMETER1: 0000000000000008
EXCEPTION_PARAMETER2: 0000000000000000
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800032b1100
0000000000000000
FOLLOWUP_IP:
cdrom!DeviceSendSrbSynchronously+568
fffff880`0121a470 8b442454 mov eax,dword ptr [rsp+54h]
FAILED_INSTRUCTION_ADDRESS:
+52842faf03acdeec
00000000`00000000 ?? ???
BUGCHECK_STR: 0x7E
LAST_CONTROL_TRANSFER: from fffff88000d7b216 to 0000000000000000
STACK_TEXT:
fffff880`031bd6c8 fffff880`00d7b216 : 00000000`0009296f 00000000`ffffffff 00000202`84000058 00000148`120a20fe : 0x0
fffff880`031bd6d0 fffff880`00d7de3c : fffffa80`568839c0 00000000`00000000 00000000`00000000 fffffa80`03a6c870 :
Wdf01000!FxRequestContext::ReleaseAndRestore+0xee
fffff880`031bd700 fffff880`00d7dda8 : 00000000`00000001 0a000000`00020070 0000013a`00000000 00000000`00000000 : Wdf01000!FxRequestBase::~FxRequestBase+0x64
fffff880`031bd730 fffff880`00d4abb4 : fffffa80`568839c0 fffff880`031bd7d0 00000000`00000001 fffffa80`568fb160 : Wdf01000!FxRequestBase::`vector deleting destructor'+0x14
fffff880`031bd760 fffff880`00da60fb : fffffa80`568839c0 00000000`00000000 00000000`00000000 00000000`00000000 : Wdf01000!FxObject::SelfDestruct+0x14
fffff880`031bd790 fffff880`00d7ae8a : fffffa80`568839c0 fffffa80`00000000 fffffa80`568e6d00 00000000`00000001 : Wdf01000!FxObject::FinalRelease+0x33
fffff880`031bd7f0 fffff880`00da8896 : fffffa80`568839c0 00000000`00000000 00000000`00000000 fffffa80`56883901 : Wdf01000!FxRequest::Release+0x52
fffff880`031bd830 fffff880`00da8159 : fffffa80`568839c0 0000057f`fb391600 0000057f`fb391600 00000000`00000000 : Wdf01000!FxObject::DeleteWorkerAndUnlock+0xf2
fffff880`031bd890 fffff880`00da3085 : 0000057f`a977c638 0000057f`fb3916e8 00000000`00000000 fffffa80`03a6cb30 : Wdf01000!FxObject::DeleteObject+0x1a9
fffff880`031bd8f0 fffff880`0121a470 : fffffa80`568839c0 00000000`00000000 00000000`00000001 00000000`00000000 : Wdf01000!imp_WdfObjectDelete+0x101
fffff880`031bd940 fffff880`0121a5e7 : 0000057f`fbf0c7e8 00000000`00000000 fffff880`031bdaa0 fffff880`00000008 : cdrom!DeviceSendSrbSynchronously+0x568
fffff880`031bda70 fffff880`0121c73c : fffffa80`04c6e910 fffffa80`040f3b80 fffff880`031bdbc0 00000000`00000001 : cdrom!MediaReadCapacity+0x8f
fffff880`031bdb30 fffff880`01217090 : 00000000`00000028 00000000`00000000 fffffa80`5453b0c0 00000000`00000001 : cdrom!RequestHandleGetDriveGeometry+0x50
fffff880`031bdb70 fffff880`00d866fb : 00000000`00000000 00000000`00000000 fffffa80`040e9b80 fffff800`0321f2b8 : cdrom!RequestProcessSerializedIoctl+0x868
fffff880`031bdc50 fffff800`03375783 : fffffa80`040f4550 00000000`00000000 fffffa80`036eb040 fffffa80`036eb040 : Wdf01000!FxWorkItem::WorkItemThunk+0x113
fffff880`031bdc80 fffff800`03089361 : fffff800`032e8900 fffff8a0`036ec501 fffff800`0321f200 fffffa80`036eb040 : nt!IopProcessWorkItem+0x23
fffff880`031bdcb0 fffff800`03319fda : 00000000`00000000 fffffa80`036eb040 00000000`00000080 fffffa80`03669890 : nt!ExpWorkerThread+0x111
fffff880`031bdd40 fffff800`030709c6 : fffff880`02f63180 fffffa80`036eb040 fffff880`02f6dfc0 00800000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`031bdd80 00000000`00000000 : fffff880`031be000 fffff880`031b8000 fffff880`031bd530 00000000`00000000 : nt!KxStartSystemThread+0x16
SYMBOL_STACK_INDEX: a
SYMBOL_NAME: cdrom!DeviceSendSrbSynchronously+568
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: cdrom
IMAGE_NAME: cdrom.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4ce79298
STACK_COMMAND: .cxr 0xfffff880031bcce0 ; kb
FAILURE_BUCKET_ID: X64_0x7E_NULL_IP_cdrom!DeviceSendSrbSynchronously+568
BUCKET_ID: X64_0x7E_NULL_IP_cdrom!DeviceSendSrbSynchronously+568
Followup: MachineOwner
-------------------------------------------------------------------
Bug Check Code 0x1000007e: http://msdn.microsoft.com/en-us/library/windows/hardware/ff557196%28v=vs.85%29.aspx
Start like Ivan mentioned.
If this does not help, you can try proceeding like that:
Update all possible driversUninstall all unused programsRun chkdsk /r /f and sfc /scannowPerform a clean boot: http://support.microsoft.com/kb/929135Disable temporary all security softwares you haveRun memtest86+ to check your RAM. If an error was detected then replace the faulty RAM or contact your manufacturer Technical Support for assistance
You can also contact Microsoft CSS for assistance.
This
posting is provided "AS IS" with no warranties or guarantees , and confers no rights.
Microsoft
Student Partner 2010 / 2011
Microsoft
Certified Professional
Microsoft
Certified Systems Administrator: Security
Microsoft
Certified Systems Engineer: Security
Microsoft
Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration
Microsoft
Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration
Microsoft
Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration
Microsoft
Certified Technology Specialist: Windows 7, Configuring
Microsoft
Certified Technology Specialist: Designing and Providing Volume Licensing Solutions to Large Organizations
Microsoft
Certified IT Professional: Enterprise Administrator
Microsoft Certified IT Professional: Server Administrator
Microsoft Certified Trainer
Free Windows Admin Tool Kit Click here and download it now
May 11th, 2012 12:37pm
Is the error occurring during the boot process or later?
You have a number of programmes dating before Windows 7 which may not be compatible. Would be please run the Windows 7 Upgrade Advisor and upload a copy of the report top your Sky Drive posting a link here:
http://windows.microsoft.com/upgradeadvisorHope this helps, Gerry
May 11th, 2012 2:49pm
Is the error occurring during the boot process or later?
You have a number of programmes dating before Windows 7 which may not be compatible. Would be please run the Windows 7 Upgrade Advisor and upload a copy of the report top your Sky Drive posting a link here:
http://windows.microsoft.com/upgradeadvisorHope this helps, Gerry
Free Windows Admin Tool Kit Click here and download it now
May 11th, 2012 2:49pm