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: New build, Microsoft-Windows-Kernel-Power Error: 0x8000000000000002


25 Mar 2012   #1

Window 7 64bit Professional SP1
 
 
New build, Microsoft-Windows-Kernel-Power Error: 0x8000000000000002

I just finished building my system a couple weeks ago, but I am getting a blue screen again after trouble shooting the ones I could. I have gotten 5 of them in the last 5 days and they all seem to be the same one from what I can tell. The last two days, I have turned my computer on, but did not log on. Both times, sometime during the day I would come to find the BSOD.

Thanks for any help
Wes

OS: Windows 7 Professional SP1 64-bit - System Builder

Malware:ESET Smart Security V.5

Chassis: Corsair Graphite 600T Mid-Tower

PSU: Corsair AX850W 80+ Gold Plus

Motherboard: ASUS P8Z68-V PRO/GEN3, LGA 1155

CPU: Intel i7-2700K, Sandy Bridge,Quad-Core, 3.5GHz

CPU Fan: Corsair H100 Liquid CPU Cooler

Graphics: NVidia GeForce GTX 560 Ti, 1GB, DDR5, PCI-E 2.0, (x2 SLI setup)

Memory: Corsair Vengeance 16GB (4x4), DDR3, SDRAM, Dual Channel, 1600MHz

OS Hard Drive: Corsair Force 3, 240GB, Internal SATA 3, 6.0GB, SSD

Data Storage: Seagate Barracuda 3TB, 6.0GB, Internal SATA, 7200RPM, 64MB Cache

Optical Drive:LG 12x Internal Blu-ray Disc Double-Layer DVD±RW/CD-RW

Optical Drive: LG Super-Multi 24x Internal DVD±RW/CD-RW

Monitor: Dell Ultra Sharp U2410 24” Widescreen LCD

My System SpecsSystem Spec
.

26 Mar 2012   #2

Window 7 64bit Professional SP1
 
 

Bump
My System SpecsSystem Spec
26 Mar 2012   #3

Windows 7 Home Premium 64 Bit
 
 

Possible out of date drivers:
Code:
MarvinBus64	fffff880`060db000	fffff880`0611f000	Fri Sep 23 15:17:03 2005 (433470cf)	00045c12		MarvinBus64.sys
Pinnacle Marvin Bus driver; I would think this is a video capture device since it is Pinnacle.


Code:
  1. Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [D:\Kingston\BSODDmpFiles\wbsimpson11\032512-9126-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506 Machine Name: Kernel base = 0xfffff800`03616000 PsLoadedModuleList = 0xfffff800`0385b670 Debug session time: Sun Mar 25 21:09:33.266 2012 (UTC - 6:00) System Uptime: 0 days 2:00:20.014 Loading Kernel Symbols ............................................................... ................................................................ ................................................................ ... Loading User Symbols Loading unloaded module list .... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck A, {fffff8a008b3bf80, 2, 0, fffff80003668bce} Probably caused by : cng.sys ( cng!GatherRandomKey+294 ) Followup: MachineOwner --------- 7: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* IRQL_NOT_LESS_OR_EQUAL (a) An attempt was made to access a pageable (or completely invalid) address at an interrupt request level (IRQL) that is too high. This is usually caused by drivers using improper addresses. If a kernel debugger is available get the stack backtrace. Arguments: Arg1: fffff8a008b3bf80, memory referenced Arg2: 0000000000000002, IRQL Arg3: 0000000000000000, bitfield : bit 0 : value 0 = read operation, 1 = write operation bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status) Arg4: fffff80003668bce, address which referenced memory Debugging Details: ------------------ READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800038c5100 fffff8a008b3bf80 CURRENT_IRQL: 2 FAULTING_IP: nt!ExpGetLookasideInformation+2ce fffff800`03668bce 0fb741c0 movzx eax,word ptr [rcx-40h] CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xA PROCESS_NAME: System TRAP_FRAME: fffff88003968f30 -- (.trap 0xfffff88003968f30) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=0000000000000058 rbx=0000000000000000 rcx=fffff8a008b3bfc0 rdx=fffff88003e87350 rsi=0000000000000000 rdi=0000000000000000 rip=fffff80003668bce rsp=fffff880039690c0 rbp=000000000000080f r8=fffff80003833400 r9=0000000000000000 r10=0000000000000000 r11=0000fffffffff000 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl nz na po nc nt!ExpGetLookasideInformation+0x2ce: fffff800`03668bce 0fb741c0 movzx eax,word ptr [rcx-40h] ds:e270:fffff8a0`08b3bf80=???? Resetting default scope LAST_CONTROL_TRANSFER: from fffff800036921e9 to fffff80003692c40 STACK_TEXT: fffff880`03968de8 fffff800`036921e9 : 00000000`0000000a fffff8a0`08b3bf80 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx fffff880`03968df0 fffff800`03690e60 : 00000000`00000000 00000000`00000000 00000000`00000000 fffff800`038333f0 : nt!KiBugCheckDispatch+0x69 fffff880`03968f30 fffff800`03668bce : 00000000`00000ff4 00000000`00000000 fffff8a0`0241b170 fffff880`03969190 : nt!KiPageFault+0x260 fffff880`039690c0 fffff800`0399d028 : 00000000`00000000 00000000`00000ff4 fffff880`03969190 00000000`00000000 : nt!ExpGetLookasideInformation+0x2ce fffff880`03969150 fffff800`0399d449 : fffff8a0`0241b170 00000000`00000000 00000000`00000004 00000000`00000000 : nt!ExpQuerySystemInformation+0x15e8 fffff880`03969500 fffff800`03691ed3 : fffff8a0`02430000 fffff800`03690e7d 00000000`00000041 fffff8a0`0241b000 : nt!NtQuerySystemInformation+0x4d fffff880`03969540 fffff800`0368e470 : fffff880`018c3ef4 00000000`00020000 fffff880`03969704 fffff8a0`0241b148 : nt!KiSystemServiceCopyEnd+0x13 fffff880`039696d8 fffff880`018c3ef4 : 00000000`00020000 fffff880`03969704 fffff8a0`0241b148 fffff880`0f86b04c : nt!KiServiceLinkage fffff880`039696e0 fffff880`018c43ed : fffffa80`0d14b8d0 fffff800`0369af93 fffffa80`20206f49 00000000`00000018 : cng!GatherRandomKey+0x294 fffff880`03969aa0 fffff800`039899fd : 00000000`00000001 00000000`00000001 fffffa80`1268e1e0 fffffa80`0ca77680 : cng!scavengingWorkItemRoutine+0x3d fffff880`03969b40 fffff800`0369d001 : fffff800`03833200 fffff800`03989901 fffffa80`0ca77600 fffffa80`0ca77680 : nt!IopProcessWorkItem+0x3d fffff880`03969b70 fffff800`0392dfee : 00000000`00000000 fffffa80`0ca77680 00000000`00000080 fffffa80`0ca4c040 : nt!ExpWorkerThread+0x111 fffff880`03969c00 fffff800`036845e6 : fffff880`0376d180 fffffa80`0ca77680 fffff880`037780c0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a fffff880`03969c40 00000000`00000000 : fffff880`0396a000 fffff880`03964000 fffff880`03968e60 00000000`00000000 : nt!KxStartSystemThread+0x16 STACK_COMMAND: kb FOLLOWUP_IP: cng!GatherRandomKey+294 fffff880`018c3ef4 85c0 test eax,eax SYMBOL_STACK_INDEX: 8 SYMBOL_NAME: cng!GatherRandomKey+294 FOLLOWUP_NAME: MachineOwner MODULE_NAME: cng IMAGE_NAME: cng.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4ec48c35 FAILURE_BUCKET_ID: X64_0xA_cng!GatherRandomKey+294 BUCKET_ID: X64_0xA_cng!GatherRandomKey+294 Followup: MachineOwner ---------
  2. Loading Dump File [D:\Kingston\BSODDmpFiles\wbsimpson11\031812-9906-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506 Machine Name: Kernel base = 0xfffff800`0320a000 PsLoadedModuleList = 0xfffff800`0344f670 Debug session time: Sun Mar 18 01:16:05.598 2012 (UTC - 6:00) System Uptime: 0 days 1:19:45.442 Loading Kernel Symbols ............................................................... ................................................................ ...................................................... Loading User Symbols Loading unloaded module list ..... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 3D, {fffff80004e12f60, 0, 0, fffff8800112778e} Unable to load image mv91xx.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for mv91xx.sys *** ERROR: Module load completed but symbols could not be loaded for mv91xx.sys Probably caused by : mv91xx.sys ( mv91xx+3178e ) Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* INTERRUPT_EXCEPTION_NOT_HANDLED (3d) Arguments: Arg1: fffff80004e12f60 Arg2: 0000000000000000 Arg3: 0000000000000000 Arg4: fffff8800112778e Debugging Details: ------------------ CONTEXT: fffff80004e12f60 -- (.cxr 0xfffff80004e12f60) rax=fffffa800f85c200 rbx=fffffa800f86db60 rcx=0000000000000000 rdx=fffffa800f86db60 rsi=0000000000000000 rdi=fffffa800f87e608 rip=fffff8800112778e rsp=fffff80004e13940 rbp=fffffa800f85c748 r8=fffff88004147100 r9=0000000000000000 r10=fffffa800f87e680 r11=fffffa800f85d018 r12=0000000000000100 r13=fffffa800f879fe0 r14=fffffa800cd6eb30 r15=fffff80004e0d080 iopl=0 nv up ei ng nz ac pe cy cs=0010 ss=0000 ds=002b es=002b fs=0053 gs=002b efl=00000293 mv91xx+0x3178e: fffff880`0112778e ?? ??? Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x3D PROCESS_NAME: System CURRENT_IRQL: b LAST_CONTROL_TRANSFER: from fffffa800d37a008 to fffff8800112778e STACK_TEXT: fffff800`04e13940 fffffa80`0d37a008 : 00000000`00000000 fffffa80`0d09d060 fffff880`04147100 fffffa80`0f87e608 : mv91xx+0x3178e fffff800`04e13948 00000000`00000000 : fffffa80`0d09d060 fffff880`04147100 fffffa80`0f87e608 fffffa80`0f879fe0 : 0xfffffa80`0d37a008 FOLLOWUP_IP: mv91xx+3178e fffff880`0112778e ?? ??? SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: mv91xx+3178e FOLLOWUP_NAME: MachineOwner MODULE_NAME: mv91xx IMAGE_NAME: mv91xx.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4c778a22 STACK_COMMAND: .cxr 0xfffff80004e12f60 ; kb FAILURE_BUCKET_ID: X64_0x3D_mv91xx+3178e BUCKET_ID: X64_0x3D_mv91xx+3178e Followup: MachineOwner ---------
  1. Possible causes are Memory problems... Corrupted hard disk file system... Corrupted System Files... BIOS... Lack of Windows updates... Antivirus Software... Backup... Hardware...
  2. Caused by your Marvell MV91xx AHCI/RAID driver


Make sure your Marvell driver is up to date. If it is up to date, re-install it. It may be corrupted. You can find the driver at ASUS - Motherboards- ASUS P8Z68-V PRO/GEN3 under SATA for your OS.
My System SpecsSystem Spec
.


26 Mar 2012   #4

Window 7 64bit Professional SP1
 
 

I have updated every driver in the world. I have tested my memory, did a burn in of the system. BIOS is up to date and it was doing it with the original BIOS and the updated. The Marvell seems to be the key in all of this since the beginning. What is the latest driver, becuase I have them all. I have unistalled it, moved the hard drives off of the port to them, yet it still comes up. What do I do. Thanks for telling that any given peice of my system could be doing it, but it really helps none.

Wes
My System SpecsSystem Spec
26 Mar 2012   #5

Window 7 64bit Professional SP1
 
 

Pinnacle is my HD video editting software. The MV91xx was coming up way before then. It has been an issue since I first loaded the system with the OS and virus software only. The other thing is, the last two BSODs occured at the login screen from a fresh boot. I hadnt even logged on.
My System SpecsSystem Spec
26 Mar 2012   #6

Windows 7 Home Premium 64 Bit
 
 

Is your SSD firmware up to date? Chipset Drivers? Have you tried using a different controller than the Marvell 91XX controllers?

Also, how did you test the memory?
My System SpecsSystem Spec
26 Mar 2012   #7

Window 7 64bit Professional SP1
 
 

I do not have the my drives hooked up the the Marvell controllers on the motherboard anymore. That was how I had them initially, but now have them in the 2 x Intell 6.0GB controllers, yet I am still getting MV91xx causing issues. I Ran MemTest for several hours and everything came up fine.

Only thing I have not done is the SSD Firmware. Will give that a try
My System SpecsSystem Spec
27 Mar 2012   #8

Window 7 64bit Professional SP1
 
 

ok, so i have the latest Corsair FW of 1.3.3 which is the latest on the web
My System SpecsSystem Spec
27 Mar 2012   #9

Windows 7 Home Premium 64 Bit
 
 

I do not understand your previous post. Did you have to update the firmware, or did you have it up to date all along?

If you continue to have problems with the updated firmware, the best step would be to replace your SSD with an HDD and see if you still have crashes. Your SSD could be bad, or there may be an incompatibility with it and your system.
My System SpecsSystem Spec
27 Mar 2012   #10

Window 7 64bit Professional SP1
 
 

I had the latest firmware for my SSD. It is already at 1.3.3 and I did not have to update it. Initially, I have the SSD and HDD both in the Marvell 6.0GB controller, but seeing that the MV91xx was coming up alot, I moved them off the Marvell controller over to the Intel 6.0GB controllers, yet the mv91xx still continues to show up in the BSODs. I have version 1.0.0.1051 driver for my Marvell, which I beleive is from AMD. CHecked the ASUS site and the lastest they had was the 1.0.0.1045, so I reverted back to that version last night.

I have the lastest BIOS for my board, but that has not resolved it either since I did that last weekend.

I have seen many folks talking about how the Marvell does not like SSDs and they seem to have the same type of issues with it.
My System SpecsSystem Spec
Reply

 New build, Microsoft-Windows-Kernel-Power Error: 0x8000000000000002




Thread Tools



Similar help and support threads for2: New build, Microsoft-Windows-Kernel-Power Error: 0x8000000000000002
Thread Forum
bsod Microsoft-Windows-Kernel-Power Event ID: 41 BSOD Help and Support
Solved Kernel Power ID 41, (0x8000000000000002) BSOD when gaming. BSOD Help and Support
Solved event 41 kernel power 0x8000000000000002 BSOD Help and Support
Windows 7 64bit Kernel Power ID 41, (0x8000000000000002) Randomly BSOD Help and Support
Solved BSOS at ranfom Microsoft-Windows-Kernel-Power 0x8000000000000002 BSOD Help and Support
Microsoft-Windows-Kernel-Power, EventID 41 BSOD Help and Support
Microsoft-Windows-Kernel-Power Issue 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 06:59 AM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33