also @ TechSpot: Latest Office 2010 beta available to members of MSDN and TechNet
Welcome to the TechSpot OpenBoards. Please read the FAQ if you have any questions. Login to participate.

Go Back   TechSpot OpenBoards > Operating Systems & Software > Windows OS > BSOD Help & Support

Kernel Power 41 Event

Reply
Bookmark Thread Tools
  #1  
Old 6 Days Ago
Newcomer, in training
 
Member since: Oct 2009, 13 posts
Kernel Power 41 Event

I keep getting a Kernel Power Critical error 41 at random times.

I am running a i5 750 with a MSI P55-CD53 mobo. 8gbs of Corsiar XMS DDR3. Nvidia GTX 260 with a Earthwatts 700.

Here are my minidumps.
Attached Files
File Type: zip minidumps.zip (59.2 KB, 1 views)

Last edited by bigsugardaddy1; 6 Days Ago at 02:57 PM..
Reply With Quote
  #2  
Old 6 Days Ago
Newcomer, in training
 
Member since: Oct 2009, 13 posts
No takers? I can provide more dumps if necessary. This has been going on since I upgraded to 7.
Reply With Quote
To remove this ad, sign in. To register for a new account, click here.
  
  #3  
Old 6 Days Ago
Route44's Avatar
TechSpot Evangelist
 
Location: The Socialist Republic of New Jersey
Member since: Sep 2006, 5,144 posts
Your first error is 0x0000001E: KMODE_EXCEPTION_NOT_HANDLED
The Windows kernel detected an illegal or unknown processor instruction. A Stop 0x1E condition can be caused by invalid memory and access violations similar to those that generate Stop 0xA errors.

0xA errors are caused by either hardware or drivers attempting to address a higher IRQ Level than they should and thus resulting in system crashes.

Unfortunantly the minidump cited the probable cause as a Windows OS driver and usually they are too general to be of much help.


Your second error is 0x3B: SYSTEM_SERVICE_EXCEPTION
This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.This error has been linked to excessive paged pool usage and may occur due to user-mode graphics drivers crossing over and passing bad data to the kernel code.

This minidump cited the probable cause as memory corruption. However, I gather from the information you supplied that you weren't getting BSODs prior to upgrading to Windows 7.

If you can access your BIOS please check what the motherboard has set your memory's voltage to and compare it to Corsair's design specs for your XMS. Is there a descrepency? Often what is recorded as memory corruption is actually a voltage issue.
Reply With Quote
  #4  
Old 6 Days Ago
Newcomer, in training
 
Member since: Oct 2009, 13 posts
1.65 is the spec and I can only put it at 1.647 or 1.651.
Reply With Quote
  #5  
Old 6 Days Ago
Route44's Avatar
TechSpot Evangelist
 
Location: The Socialist Republic of New Jersey
Member since: Sep 2006, 5,144 posts
Quote:
Originally Posted by bigsugardaddy1 View Post
1.65 is the spec and I can only put it at 1.647 or 1.651.
That is fine and 1.651 would be the preferred unless the BIOS has it set at exactly 1.65. What was your BIOS showing the voltage at? Does it have it set within this range?
Reply With Quote
  #6  
Old 6 Days Ago
Newcomer, in training
 
Member since: Oct 2009, 13 posts
1.653 is the bios voltage when I am booted up.
Reply With Quote