Not a BSOD - Random Power Offs

P

paringofthewaste

Member
Joined
Apr 11, 2013
Posts
16
Dear all,

Following a fresh Windows 7 reinstall (to cure previous BSODs on an old install), I am now getting random power offs. there is no pattern to them but they happen about once every half hour to hour.

My previous install was very old but I also discovered some hardware errors with 2 of my DIMMs as well as running a chkdsk /b (and Seagate SeaTools for DOS) on the HDD to fix some bad sectors.

The only Errrors/Criticals I could find in Event viewer were these:

Event ID 6008: The previous system shutdown at 09:43:57 on ‎11/‎04/‎2013 was unexpected.
Event ID 41: The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Any help would be greatly appreciated and please just ask if you need any log files from me.

Many thanks.
 
Hello, many thanks for the reply.

Please find the requested files zipped and attached.

Questions:

· OS - Vista/ Windows 7 ?
Windows 7 Professional.

· x86 (32-bit) or x64 ?
x64

· What was original installed OS on system?
When I bought it from Dell it was Windows Vista.

· Is the OS an OEM version (came pre-installed on system) or full retail version (YOU purchased it from retailer)?
Full Retail.

· Age of system (hardware)
Purchased from Dell in 2007. Since then have replaced Graphics Card (GeForce 560 GTX), RAM (8GB PC2-5300 4x2GB DIMMs from Komputerbay - chips are Samsung. 2 have since failed - tested with Windows Memory Tool and memtest86) and HDD (Seagate Barracuda SATA 1TB) all about 1 year ago.

· Age of OS installation - have you re-installed the OS?
Reinstalled Windows 7 yesterday

· CPU
Intel Core 2 Quad CPU @ 2.4GHz

· Video Card
GeForce 560 GTX

· MotherBoard
Brand: Foxconn LS-36

Chipset is as follows (from the manual):

Nvidia nforce 590 SLI MCP

Northbridge: C19
Southbridge: MCP55

· Power Supply - brand & wattage (if laptop, skip this one)
Dell - Ref No: NPS-750CB A Rev 02. Output Wattage 750W Max.

· System Manufacturer
Dell

· Exact model number (if laptop, check label on bottom)
Dell XPS 710
 

Attachments

Last edited:
Hello again,

I just attempted to run the Driver Verifier as per the link in your post.

This would not allow me to restart normally due to a BSOD. I tried 3 times but kept getting the same BSOD. I have atttached the minidump files below from these BSODs into a ZIP file.

I did catch the name of the file quoted on the BSOD. It was:

ctaud2k.sys

After this I rebooted into safe mode and ran verifier /reset in CMD to switch it off. I could then reboot into Windows normally which is where I'm at now.

Many thanks again.
 

Attachments

Also I have run the HDD Diagnostics and Memory Tests already (before my initial post) as follows:


With regards to HDD Diagnostics on this link:

Hard Drive Diagnostic Procedure

I have already run SeaGate SeaTools for DOS on the Long Test - this did not find any errors (it is a relatively new drive still - around 6 months old).



With regards to memory test diagnostics on this link:

Memory Diagnostics

I have run memtext86 (PassMark version) on the single 2GB DIMM in DIMM Slot 1 that I am currently using and it passed without errors.

Thanks again.
 
With regards to the Microsoft KB Article Windows Kernel event ID 41 error "The system has rebooted without cleanly shutting down first" in Windows 8, Windows Server 2012, Windows 7, or Windows Server 2008 R2

According to Event Viewer I have had 13 Event ID 41 Critical Events (Kernel-Power).

10 of these had a BugcheckCode of 0. For this the KB Articles recommends checking the following:

Overclocking: Disable overclocking to see whether the issue occurs when the system is run at the correct speed.
I am not overclocking - Dell BIOS is locked and I have no Overclocking software installed, nor have I ever used Overclocking software with this hardware.

Check the memory: Verify the memory by using a memory checker. Verify that each memory chip is the same speed and that it is configured correctly in the system.
As per my above post I have run memtest86 on the DIMM I am currently using and it came back as OK.

Power supply: Make sure that the power supply has enough wattage to appropriately handle the installed devices. If you added memory, installed a newer processor, installed additional drives, or added external devices, such devices can require more energy than the current power supply can provide consistently.
My PSU is 750W Max as listed above. I don't know if it is faulty or how to check this?

Overheating: Check whether the system is overheating by examining the internal temperature of the hardware.
I don't know how to do this.

Defaults: Reset the system back to the system defaults to see whether the issues occur when the system is running in its default configuration.
This is a fresh Windows 7 install.

The other 3 Criticals had the following Decimal BugcheckCode:

126
196
1

These Convert to Hexadecimals of:

7E
C4
1

Respectively.

The KB Articles advises:

"After you identify the hexadecimal value, go to support.microsoft.com, and search for the converted hexadecimal code (0x0000009f) and the word bugcheck."

I have done this for these three Hexadecimal Values but could not find anything on the website.



Many thanks again.
 
I'm late for work, this'll be quick (and I'll post more after work)

Driver verifier pointed at ctaud2k.sys
That's the Creative Audio driver

Please uninstall the Creative audio software drivers from your system.
Then download and install the latest, Win7 compatible drivers available from the Creative website
Test and see if that has fixed the BSOD's

Good luck!
 
Hi again.

I have just reinstalled the Creative Labs Audigy 2 Driver for Windows 7 Version 2.18.0017 (I have the SB0350 Audigy 2 ZS) from the below link:

Creative Worldwide Support > Audigy 2 ZS

Following this I re-enabled Driver Verifier and was now able to boot into Windows normally without a BSOD due to ctaud2k.sys as happened before.

I then ran verifier /query in CMD and have attached the output below in the .txt file.

I will leave Driver Verifier running then for the next 24 hours I suppose?

Thanks again.
 

Attachments

Hi there, thankyou for your reply.

May I reiterate that I am not getting BSODs - I am getting random power offs. Event Viewer shows the sort of Critical Errors as I have outlined in a post above.

Please could you inform me if these sorts of crashes will have .dmp files and if so where I can find them so I can collate them together and post as an attachment?



Furthermore I would like to report the following:

I ran the following two Hardware tests already, yesterday, just after my fresh reinstall:

1. Memory Diagnostics shows no errors - I ran memtest86.

2. HDD Diagnostics shows no errors - I ran Seagate SeaTools for DOS - Long Test.



3. As for malware/antivirus - this is a clean Windows 7 install as of yesterday and I Zero'd the drive prior to this using Seagate SeaTools so I'm not sure this is necessary? Furthermore, I have only installed Windows Updates or Drivers since yesterday so I would imagine its quite unlikely to be virus/malware related? The link you sent had a lot of programs. However, if you want to recommend one or two from the list to install I will happily do so and run them.

4. FurMark - I just ran the "Burn-in" Test (before you posted saying to wait for a 24hour period). My GPU Temperature Maxed out at 78 Degrees. No visual artifacts or crashes. Resolution was 1280x720, Windowed, Anti-Aliasing was Off.



One point I would like to note is as follows:

The Dell XPS 710 Manual says the system is good for PC-5300 RAM. The RAM I have installed was bought labelled as PC-5300 RAM but HWiNFO 64 reports it as PC-6400 RAM as per the attached screenshot. However - as noted above - memtest86 ran quite happily and passed. Furthermore, the BIOS seems to recognise it just fine too.

Thanks to all again.
 

Attachments

  • HWiNFO 64.JPG
    HWiNFO 64.JPG
    106.3 KB · Views: 4
  1. We understand that you were not previously getting blue screens. The power off is likely an indication of a hardware fault, but it could possibly be a driver fault, which is why Verifier was recommended to force a blue screen and help us analyze the crashes. To upload the reports from those blue screens and the reports for your power-offs, you will need to again follow the blue screen posting instructions in 24 hours.


  2. How long did you run memtest86+ for? Was it overnight? Did it complete at least 7-10 passes? It can take up to 22 passes to find errors. It should also be run after the system has been shut down (not in sleep mode) for a few hours to test the RAM when it is cold, and then again when the system has been running for a few hours to test the RAM when it is warm.

  3. You may want to check the hard disk(s) with HD Tune. HD Tune provides more diagnostic information than SeaTools does. Check Health status and run the Error Scan with HD Tune and report back.


  4. Are your malware/antivirus remarks in regard to the Event ID 41 article? I would not worry if this is a clean install and you have not gone to any questionable sites. Do know that there are BIOS level malicious items out there, but they are rare.

  5. Good news on FurMark.

  6. Provide the following information about your hardware so we can check compatibility:

    Download and install CPU-Z and Upload screenshots of the CPU, Mainboard, Memory, and SPD tabs. In the SPD tab, upload an image of each slot. To upload all screenshots, it would be best to:
    1. generate the images using the Snipping Tool,
    2. go to where the images are saved,
    3. right click in a blank area within the folder where the images are saved,
    4. create a new folder,
    5. name the folder CPUZ,
    6. select all the images,
    7. place the pointer over an image,
    8. press and hold down the left mouse button and drag the image (all images should move with it),
    9. drop the images into the CPUZ directory you created,
    10. create a compressed (zipped) folder of CPUZ
    11. upload the .zip file to the forums.


Again, hardware diagnostics should be conducted after the 24 hour period with Verifier to see if Verifier flags any more problematic drivers on the system.
 
Last edited:
Hi again - thanks for your continued help.

1. I will continue to run Verifier.

2. Regarding "reports for power-offs" - I am unsure of where these will be stored, that's all. Would it be in Windows\minidumps ?

If that is the case then for the record - not every power-off is creating a .dmp in minidumps (judging by the timestamp of the .dmp files versus when the power-offs actually occur). Some have created a .dmp, others have not.

3. On the memorytesting I used memtest86 (PassMark) not memtest86+. I don't know if they are totally different or not - sorry, as you can appreciate the names are quite simmilar and it is a bit confusing. Is this a problem? Should I use memtest86+ exclusively? I allowed for 2 passes. I can certainly leave it running longer next time.

I would just point out that I may be using incompatible memory as per my above post but I am not sure. Crucial claims PC2-6400 is "guaranteed" to work with my system, but the Dell manual only mentions PC2-5300. The RAM I have at the moment was labeled and sold as PC2-5300 but as per the above screenshot, it actually seems to be PC2-6400 (confirmed in the BIOS - speed reported is 800MHz). I have been using it for about 6 months with intermittent BSODs/crashes.

Re: XPS 710 and PC6400 DDR2 800MHz ram - XPS Club Forum - XPS Club - Dell Community

4. I will certainly use HD Tune as you suggest.

5. My malware/anti-virus remarks are in relation to this page

Hardware Diagnostics

as suggested above. As you mention though I have just done a clean reinstall and have only been to this forum, the Dell website, Windows Update etc since. As such I will leave this to one side, although noting the remote possibility of BIOS level problems.

6. I will provide the information you have asked for forthwith.

Thanks again.
 
Power-offs are often reported in the event viewer logs. Not much information is helpful in regards to the power-off itself, but other errors in the event viewer logs can be helpful in determining why the power-offs are occurring. Also, any power-offs that did create a .dmp can be helpful in analyzing and determining the cause.

First thing's first: Your power-offs may be due to a malicious item built into your pirated operating system to randomly turn off the system. I see that you have an acer/Gateway/Packard Windows installation attached to your Dell hardware.

I am afraid your installation may not be genuine. If you believe that I am in error in my analysis, please let me know. However, if you do have a pirated copy of Windows, know that our troubleshooting steps may not have any effect on the pirated operating system, so we may be wasting your time by proceeding.

Non-Genuine Windows contains security leaks and also cannot be properly updated which may result in instabilities and blue screen crashes. If you were not aware that your Windows was Non-Genuine, contact your seller or the company that provided the seller and file a complaint. Also let Microsoft know of the problem: Protect Yourself from Piracy

If you do have a pirated copy of Windows, I am sorry, but due to forum rules, we may not assist you further until you have installed a genuine version of Windows. To put the genuine Windows on, I strongly suggest you backup any important data, format your hard disk, and reinstall Windows 7 to make sure all remnants are removed of the software that you used to make Windows work before. If you do not clean re-install, you may be left with a compromised system and your identity, bank accounts, credit card information, etc. may continue to be at risk as they are now. Once you install a genuine version:

Please download and run the MGADiag tool. When it finishes, hit the copy button, and paste in your next post with [code]<MGADiag info>[/code] surrounding the MGADiag info.​


Further information about pirated software:

 
Entirely possible I suppose given that this is a second-hand machine purchased from Gumtree! Couldn't argue with the price for the components alone though. I'll keep working on it - thanks anyway.
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top