computer keeps on resetting, kernel-power error, ID 41

[jamesw68]

for past few days, PC keeps on resetting every hour or so

Running windows 7 x64 and the age of system (hardware) is 10 months.
i5 760 with amd hd6870. All the requested files should be attached, any help very much appreciated.

I had corrupt windows install after a graphics card driver upgrade that caused similar problems in March/April, reinstalled windows from scratch and no problem for 5 months. A scannow run revealed no problems.

Went back to a restore point from 21st Oct and changed anti virus from mse to avg. No change.

 

[zigzag3143]

for past few days, PC keeps on resetting every hour or so

Running windows 7 x64 and the age of system (hardware) is 10 months.
i5 760 with amd hd6870. All the requested files should be attached, any help very much appreciated.

I had corrupt windows install after a graphics card driver upgrade that caused similar problems in March/April, reinstalled windows from scratch and no problem for 5 months. A scannow run revealed no problems.

Went back to a restore point from 21st Oct and changed anti virus from mse to avg. No change.

No DMP's included in upload. Try this method.

We do need the DMP file as it contains the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.

You may be able to get the DMP files without crashing by booting into safe mode (F8) with networking.

To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.

The procedure:

* Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
* Zip up the copy.
* Attach the ZIP archive to your post using the "paperclip" (file attachments) button.
*If the files are too large please upload them to a file sharing service like "Rapidshare" and put a link to them in your reply.


To ensure minidumps are enabled:

* Go to Start, in the Search Box type: sysdm.cpl, press Enter.
* Under the Advanced tab, click on the Startup and Recovery Settings... button.
* Ensure that Automatically restart is unchecked.
* Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
* Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
* OK your way out.
* Reboot if changes have been made.

 

[jamesw68]

it was set to kernal memory dump not small memory dump. Changed settings, restarted and waiting for failure.

 

[zigzag3143]

it was set to kernal memory dump not small memory dump. Changed settings, restarted and waiting for failure.

No worries just have to wait for a crash. If you can upload the kernel dmp

 

[jamesw68]

there was no kernal dump file. It has now crashed 4 times and no minidump files are being produced. last time changed location to C:\dumps from %systemroot%\minidump.

Still no dmp file. Any ideas

 

[PsylockeSmythe]

I had this same issue for a few days after I built my latest computer. It turns out for me; the motherboard was undervolting the ram. When set on auto; the motherboard was only supplying 1.44volts; and the memory wanted 1.5volts.

By slowly adjusting the voltage being supplied to the ram; I was able to find a voltage that made the ram happy and the kernel-power error ID 41 to stop. For me; that means I've got it set on 1.524 and the motherboard is reporting it at 1.504volts.

So my suggest is check your voltage settings in the bios. I would also check the voltage for the CPU; because that could also be causing this problem.

Psy

 

[zigzag3143]

there was no kernal dump file. It has now crashed 4 times and no minidump files are being produced. last time changed location to C:\dumps from %systemroot%\minidump.

Still no dmp file. Any ideas

Check to see if anything is logged in event viewer


There are several ways to find what the problem is. The best is to go into event viewer (type eventvwr in search). Event viewer (local) and look for errors listed in the last day, week, etc. Then go to the windows log>application tab. Finally the windows Logs>system tabs.

You want to look for all errors (they have red in the left column ).

When you find them you want to look for critical errors that say app hang, app crash, or anything that relates to the problem.

When you find them please note the event ID, and the source codes and tell us what they are.