Random lockups and freezing

No DMP's inc.


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.

If you are overclocking STOP

We could also use some system information, which you can get easily by running msinfo32. To do that go to start>run>type msinfo32>enter

When it is finished running go to file>save>name it and upload to us here.

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.

Thanks for replying, JMH

I posted the attachment as required by the BSOD posting instructions, but for my issue my system just freezes instantly and doesn't BSOD, which might be the reason why no dump files were in the zip file.

I am not overclocking any of my hardware. I've never done it and I don't plan to..

System information from msinfo32 is already included in the zip file on the first post.

\Windows\Minidump folder does not exist.

Just unchecked Automatic Restart and changed Write Debugging Information to Small memory dump (256 kB)

* There are several reasons that may prevent you from having a DMP file in the usual places.

If you control panel is not configured for small dump you probably will then find it in C:\windows and it will be called MEMORY.dmp. It will overwrite every crash.

Other reasons are if you have UAC turned off, if you have a small page file, or a page file on a different HD than the OS.


* Please provide us with your Event Viewer administrative logs by following these steps:

Click Start Menu
Type eventvwr into Search programs and files (do not hit enter)
Right click eventvwr.exe and click Run as administrator
Expand Custom Views
Click Administrative Events
Right click Administrative Events
Save all Events in Custom View As...
Save them in a folder where you will remember which folder and save as Errors.evtx
Go to where you saved Errors.evtx
Right click Errors.evtx -> send to -> compressed (zipped) folder
Upload the .zip file here.

@JMH:

MEMORY.dmp does not exist in C:\Windows either.

I do have UAC turned off, my page file is of 4087 MB and on the OS drive.

Event Viewer logs are attached. Kernel-Power events are most likely due to me manually restarting the PC after it locks up.

You need to have UAC turned on to get .dmp files... JMH was telling you they will not be generated if UAC is turned off.

The most frequent event viewer errors are network related. You also have a corrupt "firmware" that needs re-installing/upgrading and what ever disk issue you were having in February seems to have resolved itself.

Since networking is involved I would re-install the Realtek driver with newest available.

zigzag3143 said:

The most frequent event viewer errors are network related. You also have a corrupt "firmware" that needs re-installing/upgrading and what ever disk issue you were having in February seems to have resolved itself.

Since networking is involved I would re-install the Realtek driver with newest available.

Could you point out this firmware to me? I can't seem to find the one you mean in the Event Viewer.

Also I can't seem to find the proper Realtek driver for my device. Windows Update reports that it is already updated, so I tried looking manually.

I've found this, Realtek , the RTL8168D driver, but my driver is of RTL8167, so I'm unsure if I can use that.

Code:

Log Name:      System
Source:        Microsoft-Windows-HAL
Date:          4/5/2012 1:01:33 PM
Event ID:      12
Task Category: None
Level:         Error
Keywords:      (1)
User:          N/A
Computer:      Desktop
Description:
The platform firmware has corrupted memory across the previous system power transition.  Please check for updated firmware for your system.

There seems to be missing information as to which firmware. Please provide the compressed (zipped) version of the LocaleMetaData folder that is saved in the same location as your .evtx file you saved last time, or create a new version of both and compress (zip) both together in a folder to upload here. The following steps may be helpful:

1. Click Start Menu
2. Type eventvwr into Search programs and files (do not hit enter)
3. Right click eventvwr.exe and click Run as administrator
4. Expand Custom Views
5. Click Administrative Events
6. Right click Administrative Events
7. Save all Events in Custom View As...
8. Save them in a folder where you will remember which folder and save as Errors.evtx
9. When asked, save the display information in English.
10. Go to where you saved Errors.evtx
11. Create a new folder by right clicking in a blank area within the folder Errors.evtx is saved in. You could also click New Folder at the top of the directory under the directory path box.
12. Name the new folder Errors.
13. Place Errors.evtx and the LocaleMetaData folder into the new Errors folder.
14. Right click the Errors folder -> send to -> compressed (zipped) folder
15. Upload the .zip file here.

For the Realtek: GIGABYTE - Motherboard - Socket 1156 - GA-P55-US3L (rev. 2.3) -> Downloads -> Choose your OS: Windows 7 64bit -> LAN ->

Code:

Realtek LAN Driver	7.049.0927.2011	3.48 MB	2012/03/21

You may have uninstall the current version and install the new one. To do so, download the above driver first and save it in a known place. Then do the following steps:

1. Click Start Menu
2. Right Click My Computer/Computer
3. Click Manage
4. Click Device Manager from the list on the left
5. Expand Network adapters
6. Right click the Realtek Ethernet device
7. Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
8. Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
9. Restart your computer only if Windows asks you to.
10. Install the latest driver for the device.

Alternatively:

1. Login as an adminstrative user.
2. Click Start Menu
3. Click Control Panel
4. Click Hardware and Sound
5. Click Device Manager (the last link under Devices and Printers)
6. Expand Network adapters
7. Right click the Realtek Ethernet device
8. Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
9. Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
10. Restart your computer only if Windows asks you to.
11. Install the latest driver for the device.

Alright, uploaded a fresh errors.evtx with LocaleMetaData in the zip. A full lock up occured at around 2:46 pm (At least, that was shown on the clock)

No events were shown in between my reboot and the previous event at 5:41 am, which is the HAL firmware issue mentioned.

I've updated my LAN driver as instructed (after compiling errors.zip)