Sign-in / Sign-up
Your question

Random locking, restarting, etc... help needed

Tags:
  • Windows 7
  • Computers
Last response: in Windows 7
July 2, 2014 7:46:35 AM

Hello,

Recently my computer running Windows 7 Professional has started to lock up and the only way to get it to recover is to turn it off with the power button and back on. Other times it would randomly restart then on reboot it wouldn't find any drives so I'd have to turn it off and turn it back on.

I did get this error once referencing rundll32.exe but have yet to see it again.

I've ran Microsoft Security Essentials, AVG, and CC Cleaner. No viruses are found. CC Cleaner found registrry issues and I had then fixed.

I'm seeing this error a lot in Event Viewer.
Session "Microsoft Security Client OOBE" stopped due to the following error: 0xC00000D

Any ideas on what I can do to get this solved?

Thank you!

More about : random locking restarting needed

July 2, 2014 10:34:25 AM

I removed the file as per the instructions. We'll see what happens.
m
0
l
Related resources
July 2, 2014 11:56:23 AM

How would I view a BSOD if I didn't catch it in time and the computer restarted? I changed to the setting to disable automatic restart.
m
0
l
a b $ Windows 7
July 2, 2014 11:59:48 AM

the dump files should be in
C:\Windows\Minidump
C:\Windows\MEMORY.DMP
m
0
l
July 2, 2014 12:46:57 PM

For some reason that file MEMORY.DMP and folder Minidump do not exist. I have click to show system file and also to show hidden files/folders.

I was able to record this on the BSOD.

STOP: 0x000000F4 (0x0000000000000003,0xFFFFFA8009E1C620,0xFFFFFA8009e1c900,0xFFFFF80003197270)

Physical memory dump FAILED with status 0xC0000010
m
0
l
July 2, 2014 1:30:35 PM

Thank you! What am I needing to look for in all these files?
m
0
l
a b $ Windows 7
July 2, 2014 2:37:03 PM

If you can boot into Windows, click Start > Run > and type sysdm.cpl
This will bring up the System Properties windows. Click on Advanced > Startup and Recovercy, click Settings > Under "System failure" check:
Write an event to the system log
Automatically restart
Write debugging information (drop-down box) select "Small memory dump (256KB)
Small dump directory: %SystemRoot%\Minidump (your PC setting probably was set at None)
Click OK twice to Exit. Restart and wait for the next BSOD happen, then restart the Computer and log back in Windows and locate the directory:
C:Windows\Minidump there should be the dump files
m
0
l
July 2, 2014 4:28:56 PM

I will double check my settings but pretty sure everything is set up to write dump files. Thank you for the instructions.

Something very interesting as well that i found. I'm running Windows off of an Crucial M4 SSD. The following might be the cause of my BSOD.

Crucial M4 SSD 2.5

Downloaded from their site Crucial.com Product Downloads - Firmware Updates

A friend found this in the M4 firmware release notes:

Correct a condition where an incorrect response to a SMART counter will cause the m4 drive to become unresponsive after 5184 hours of Power-on time. The drive will recover after a power cycle, however, this failure will repeat once per hour after reaching this point. The condition will allow the end user to successfully update firmware, and poses no risk to user or system data stored on the drive.
This firmware update is STRONGLY RECOMMENDED for drives in the field. Although the failure mode due to the SMART Power On Hours counter poses no risk to saved user data, the failure mode can become repetitive, and pose a nuisance to the end user. If the end user has not yet observed this failure mode, this update is required to prevent it from happening.

m
0
l