Crashing daily (The computer has rebooted from a bugcheck)

So I've had Windows 7 Build 7000 32-bit installed over Vista Business w/SP1 since MS released it. I'm very pleased and happy with it's performance aside from two annoying things.

(1) I am not able to use Macdrive 7. The ONLY app I have that will no longer run or install. This is something I just have to accept until it's resolved.

(2) Windows 7 crashes and restarts on me, usually daily. Sometimes it's even been twice in a day.

For the first few days, it happened while I was sitting in front of it. It would throw up the BSOD, pointing to "nwifi.sys". Since then, I'm either asleep or just present at the time. I finally decided to look at the Event Log and see just what the hell is going on.

Here's the neccessary portion for those that might be able to help.

Level: Critical
Date/Time: 1/20/2009, 5:22:11 PM
Source: Kernel-Power
Event ID: 41
Task Category: (63)
Message: The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.


Level: Error
Date/Time: 1/20/2009, 5:22:54 PM
Source: EventLog
Event ID: 6008
Task Category: None
Message: The previous system shutdown at 5:20:18 PM on ‎1/‎20/‎2009 was unexpected.


I then have eight entries as "Information" that pertain to startup. Followed by:

Level: Error
Date/Time: 1/20/2009, 5:22:55 PM
Source: BugCheck
Event ID: 1001
Task Category: None
Message: The computer has rebooted from a bugcheck. The bugcheck was: 0x00000116 (0x86796510, 0x91408eb0, 0x00000000, 0x00000002). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 012009-44148-01.


Does anyone have any input on this by chance? Help would be appreciated. I would love to get around this crashing. Thanks!

Yes I get the exact same BSOD about once a day while doing nothing at all.
I was getting constant DHCPv6 can't connect server errors in my event log. I went into network management and unchecked that one which seems to have ended those errors.

I'am not sure if those errors were causing the Kernel-Power ID 41 BSOD's or not. Maybe you can look at your event error's log and see if you have the same problem. I recall seeing the bugcheck error's at one time also but I'am not sure if that is connected with the problem or not.
Getting these also when viewing event history.
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000000a (0xfffffa7fffffe7e0, 0x0000000000000002, 0x0000000000000000, 0xfffff80002896f19). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 011809-24507-01.



I'am using Nvidia 780i reference board. And the 64bit Windows 7 latest build.

I'm getting the exact same critical event, but in a different scenario.

I'm using:
Windows 7 x64 Build 7000

Equipment is as follows:

Gigabyte GA-MA770-DS3P Motherboard
(which includes a built-in Realtek ALC888 sound card and Realtek Gigabit Ethernet)

AMD Phenom X3 8750 Triple-Core 2.4Ghz (overlocked to 2.8Ghz, although i've tried using the "optimized" settings and get the same BSoD)

(1) Pinnacle PCTV HD PCI Card (wow, was that a mistake! why does best buy carry this thing?)

(1) eVGA GeForce 8600GT 1GB DDR Video Card (using Microsoft-update-provided driver)

(2) Corsair PC6400 DDR2 DIMM's

(1) Seagate 500GB SATA2 HD (where the OS is installed, formatted as a dynamic, MBR drive)

(1) Seagate 1TB SATA2 HD (storage, formatted as dynamic GPT drive)

(1) Western Digital 500GB SATA2 HD (currently with nothing on it)

(1) Lite-On Blu-Ray Drive

(1) Samsung DVD-RW Drive

I also have four fans in there keeping things nice and cool, or at least they should be.

Here's the initial line of the BSoD:

IRQL_NOT_LESS_OR_EQUAL

The rest never stays on long enough for me to read it.

When I check the logs, here is the recurring critical event:

- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331C3B3A-2005-44C2-AC5E-77220C37D6B4}" />

<EventID>41</EventID>

<Version>2</Version>

<Level>1</Level>

<Task>63</Task>

<Opcode>0</Opcode>

<Keywords>0x8000000000000002</Keywords>

<TimeCreated SystemTime="2009-01-29T22:45:52.732852800Z" />

<EventRecordID>20235</EventRecordID>

<Correlation />

<Execution ProcessID="4" ThreadID="8" />

<Channel>System</Channel>

<Computer>USER</Computer>

<Security UserID="S-1-5-18" />

</System>


- <EventData>
<Data Name="BugcheckCode">10</Data>

<Data Name="BugcheckParameter">0xd8</Data>

<Data Name="BugcheckParameter">0xf</Data>

<Data Name="BugcheckParameter">0x0</Data>

<Data Name="BugcheckParameter">0xfffff80001e826f9</Data>

<Data Name="SleepInProgress">false</Data>

<Data Name="PowerButtonTimestamp">0</Data>

</EventData>


</Event>




I've run a search on IRQL_NOT_LESS_OR_EQUAL and have gathered that this likely has something to do with a driver/program that is attempting to address a memory space that it's not allowed/able to. Unfortunately I can't seem to figure out what that is. At some point I came across an article that discussed corruption of pagefile.sys, so I went into the registry to ensure that it was being refreshed upon reboot. At first I thought that worked, but it apparently didn't. I've tried uninstalling programs, etc., to no avail.

Usually this happens when i'm attemping to burn an image to a DVD or doing some serious multi-tasking, like working in Photoshop, burning a DVD, and running the Zune software all at the same time.

Solved!

This problem was solved by me. The BSOD's when moving files accross the LAN was my clue. I realized that anytime Ram was being used over a certain percentage that the crashing would begin. So I summized that Windows 7 puts more stress on the memory controller and the north bridge than Vista does. Although my system did BSOD when doing other things also or even when doing nothing at all.

I simply raised the voltage of the MCP,FSB,and Ram voltage,just one notch up for each and this problem went away almost like magic perminately and forever.

This same system was completely stable using Vista64 on another partition. Not one BSOD since making these simple bios adjustments,it's been over a week now.

The bios adjustments outlined here have already fixed this problem on another computer right here on this forum. Link below.
http://www.sevenforums.com/general-discussion/1194-windows-7-crash-2.html

Solved a different way

I had the same problem with Vista64 and Win7x64 on a machine that has been rock stable for 2 years with Vista x32 and several weeks with Win7 x32...I just reduced my overclock a bit and the problem went away. I suspect you are right...x64 is putting a lot more stress on certain components.

I also eliminated the IPv6 errors by disabling the IP Helper service...disabling it on the individual network devices does not work because there are several ghost devices which try to use IPv6.

chevell said:

This problem was solved by me. The BSOD's when moving files accross the LAN was my clue. I realized that anytime Ram was being used over a certain percentage that the crashing would begin. So I summized that Windows 7 puts more stress on the memory controller and the north bridge than Vista does. Although my system did BSOD when doing other things also or even when doing nothing at all.

I simply raised the voltage of the MCP,FSB,and Ram voltage,just one notch up for each and this problem went away almost like magic perminately and forever.

This same system was completely stable using Vista64 on another partition. Not one BSOD since making these simple bios adjustments,it's been over a week now.

The bios adjustments outlined here have already fixed this problem on another computer right here on this forum. Link below.
http://www.sevenforums.com/general-discussion/1194-windows-7-crash-2.html

Click to expand...

Hi,

Glad you sorted it - did you send feedback to MS ?

SIW2

bummpr said:

I had the same problem with Vista64 and Win7x64 on a machine that has been rock stable for 2 years with Vista x32 and several weeks with Win7 x32...I just reduced my overclock a bit and the problem went away. I suspect you are right...x64 is putting a lot more stress on certain components.

I also eliminated the IPv6 errors by disabling the IP Helper service...disabling it on the individual network devices does not work because there are several ghost devices which try to use IPv6.

Click to expand...

Where is this IP Helper you speak of. Disabling in network connections stopped the IPv6 errors in their tracks for me.

I wasn't about to reduce a stable overclock just to make an OP system happy. Although I did try reducing it once it had no effect until I went in and raised the voltages in bios.

Yes I sent feed back. I'am the chevell above, sorry I signed in with the wrong name and for some reason it worked.

You can disable the "IPHelper" service by going into Administrative Tools - Services. Personally I like to keep my admin tools handy from the start menu (by default, Win7 does not have that enabled, I had to add it through start menu personalization). You can access it from the control panel under the extended control panel options.

Going through that process will pull up a list of all services, will show you what's running ("started"), what can/will start automatically, what will start on demand (manual), and what is disabled. I actually think that I solved my problems by shutting down some unnecessary components - in combination with completely gutting my pagefile.sys files - i'd had one on several drives, and instead, i'm just using one on the primary drive now and I have windows managing it. I'm also using a flash drive for ReadyBoost. I was also having some major problems with the windows indexing service (i.e. it magically stopped indexing, so when I ran searches it came up with nothing), but I was able to fix that by rebuilding the index - and keeping said index to a minimal number of items, i.e. start menu, my documents, etc.

As far as IPHelper goes - I have not disabled that, although I had been getting the errors related to IPv6 DHCP that everyone else was talking about, too. I don't think that's what was causing my BSoD, but i'm sure fixing that will probably improve performance. I really wish that DLink would enable IPv6 DHCP distribution in a firmware update for my router; I think that might help issues like this. Even in Vista i've run into errors where it keeps searching for a router-issued IPv6 address, to no avail.

For those out there who are overclocking, are you manually setting your voltages, and if so, are you doing that in lieu of having your BIOS automatically adjust your voltages? I have a pretty recent Gigabyte board and ever since I switched over to auto-management of power, it seems to be running pretty stable - and that's with my board overclocked from stock 2.4ghz to 2.86ghz (I have a black edition phenom, so i'm mainly using the multiplier clock to raise the ghz - I still have the stock heatsink on there so i'm not pushing it to the limit just yet).

I'll keep everyone posted if I face another BSoD, but it's pretty safe to say that I think this is all related to memory and power issues.

Oh - I almost forgot to mention one VERY important thing - and I think that this very well might be what **completely fixed my issue.** I manually re-enabled hibernation (don't know how it was disabled to begin with) from the command prompt. Ever since I did this, I have yet to have a BSoD. (I've had a few freezing issues, mainly related to things like burning lightscribe labels, but none of the Kernel-Power issues).

To do this:
1) Run the command prompt as administrator (it's under Accessories, right click and "Run as Adminstrator".
2) Type the following:
powercfg -h on

Literally my system has been stable since I did that. Shutting off some unnecessary services helps too, but I honestly believe that doing the above solved all of my problems. I *never* actually ALLOW my computer to hibernate, *however*, I think that my computer was trying to initiate some sort of sleep-oriented command (why, i'll never know) which caused this to be an issue.

Sorry for being so verbose, I just know how much of a pain it is to agonize over these issues for nights and nights on end, so hopefully this will help some people out there!

thanks

I'v had this very issue since first building my WIN7 box. I'm going to try these solutions right now, but I wanted to say thanks, as this is the first helpful conversation on this issue that I have found.
promytius.

Hi,

i was wondering if anybody resolved this issue in one definite way.. i tried the suggestions listed to no avail.. the issue is exactly the same as listed here. i'd appreciate input, thanks!

Hi Chevell,
I have the same problem right now and I'm wondering if your solution has been working allright? Also - Isn't it dangerous to encrease the voltage for the equipment or is this something that normally can be done? Can updating bios help?
I'm a bit new to this and so I feel I need to know more. Hope you can help me with this. I would appreciate it a lot.
Best regards/
Chris

chevell said:

This problem was solved by me. The BSOD's when moving files accross the LAN was my clue. I realized that anytime Ram was being used over a certain percentage that the crashing would begin. So I summized that Windows 7 puts more stress on the memory controller and the north bridge than Vista does. Although my system did BSOD when doing other things also or even when doing nothing at all.

I simply raised the voltage of the MCP,FSB,and Ram voltage,just one notch up for each and this problem went away almost like magic perminately and forever.

This same system was completely stable using Vista64 on another partition. Not one BSOD since making these simple bios adjustments,it's been over a week now.

The bios adjustments outlined here have already fixed this problem on another computer right here on this forum. Link below.
http://www.sevenforums.com/general-discussion/1194-windows-7-crash-2.html

Click to expand...

yes, a good question, and also.. do all three, memory.. FSB and CPU voltage have to be increased or only one will do the trick?

Getting same error

This same problem has been occuring for me, usually after attempting to come out of sleep. I thought it was hibernation related, but after turning that feature off using the power management settings, it kept happening.

Just tried the command prompt directions given in an earlier post for turning hibernation back on through the command prompt. I'll that for now.

Well I managed to go four days without a crash after doing the command prompt instructions to turn on hibernation, but then got a hard stop today again. No BSOD, but the PC froze complete for a good 5 minutes so I forced a reboot by holding down the power key.
Here's what my event viewer log looks like. All the same type of event.
TechSmith | Screencast.com, online video sharing, Even Viewer 2010-07-31_0959
I'm not too keen on monkeying with voltages and the like. Does anyone else have any ideas for what can be done to fix this problem?

TheUSMarshall said:

Oh - I almost forgot to mention one VERY important thing - and I think that this very well might be what **completely fixed my issue.** I manually re-enabled hibernation (don't know how it was disabled to begin with) from the command prompt. Ever since I did this, I have yet to have a BSoD. (I've had a few freezing issues, mainly related to things like burning lightscribe labels, but none of the Kernel-Power issues).

To do this:
1) Run the command prompt as administrator (it's under Accessories, right click and "Run as Adminstrator".
2) Type the following:
powercfg -h on

Literally my system has been stable since I did that. Shutting off some unnecessary services helps too, but I honestly believe that doing the above solved all of my problems. I *never* actually ALLOW my computer to hibernate, *however*, I think that my computer was trying to initiate some sort of sleep-oriented command (why, i'll never know) which caused this to be an issue.

Sorry for being so verbose, I just know how much of a pain it is to agonize over these issues for nights and nights on end, so hopefully this will help some people out there!

Click to expand...

Wow, I owe you a beer. I have had this issue for so long! I even went so far as to completely format my hard drive, reinstall Windows 7. Literally tried everything from swapping power supplies, adding after market coolers to both my cpu and vga card, swapping memory sticks to no avail.

Your command prompt suggestion to enable hibernation fixed my system completely. Have been stable for weeks!

Obviously some sort of bug with Windows 7 and the hibernation feature.

Thanks for sharing your suggestion with fellow Windows 7 users!

To TheUSMarshall - thanks from me, too.

I am the System Admin/Internal Support person for a small software development company in NZ.

We bought a brand new laptop from Dell with 64bit Windows 7 Home Premium installed on it, and it had the rebooting-randomly-with-no-warning-event-ID-41 problem. After a month or so we logged a support call with Dell. They replaced the mainboard and hard disk, but the problem was still present.

We had set the power options to never hibernate and never sleep while on battery, so the situation seemed to be similar.

I found your post and tried it:

powercfg -h on

The problem went away that day!

As usual, Microsoft's web site was absolutely no help at all. There was no inkling of anything like this on their web site (or I couldn't find it, which amounts to the same thing). You would think they would have some clues about their own OS!

Help

I tried the fix that TheUSMarshall said to do. That did not work, does anyone else know how to fix this issue.

Thanks.

Just started for me

After installing Windows 7 SP 1, my system dies every time it sleeps. The computer has rebooted from a bugcheck. The bugcheck was: 0x000000a0 (0x0000000000000009, 0xffffffffc000000e, 0x0000000000000001, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 030211-83928-01. What causes this?

Tried US Marshall's "powercfg -h on"
Sorry but didn't solve it for me.
Going to try out CHEVELL or CHEV65 ideas and bump the voltage.