System reboots itself

[fredoz]

What I have: - Windows 7 32 bit SP1
-AMD Athlon 64 Dual Core 3800+
-2 GIG RAM
-NVIDIA Quadro FX-450

What's happening:
The computer reboots itself. I've checked processor for heat sink problems, thinking this is an hardware issue.
I've attached required files. Any help is greatly appreciated.

 

[JMH]

Hello fredoz & welcome,
FYI...
There is no obvious attachment in your post.

 

[fredoz]

I edited my post and attachments should be there.

 

[JMH]

Please answer all the questions below.
Note I have not time to examine your attachment ATM.

> Have you used a Registry Cleaner / Optimizer?

> What troubleshooting methods have you tried thus far?

> What alterations /downloads etc have you made/done to your computer between now & when it ran normally?

> Have you a System Restore point created prior to when you troubles began?

> Have you a recent back up { on an external hard drive} in case of need?

> Have you a Win7 disk?

> Have you had any BSOD's?

> Are you overclocking?

 

[fredoz]

> Have you used a Registry Cleaner / Optimizer?
Yes

> What troubleshooting methods have you tried thus far?
Thinking it might be a hardware problem, I cleaned the CPU die where it makes contact with the heat sink. I applied new Arctic Silver compound


> What alterations /downloads etc have you made/done to your computer between now & when it ran normally?
Other than installing Win 7 in place of XP, none. Even before this was an intermittent problem. Now with Win 7 it seems to be more pronounced.

> Have you a System Restore point created prior to when you troubles began?
No.

> Have you a recent back up { on an external hard drive} in case of need?
Yes.

> Have you a Windows 7 disk?
Yes.

> Have you had any BSOD's?
Two, I think.

> Are you overclocking?
No.

 

[JMH]

> Your use of a Registry Cleaner / Optimizer may have indeed been a contributing factor to your current glitches..

Current accepted wisdom with Win 7 is to NOT use a cleaner.

If you ever think your Registry needs to be cleaned, repaired, boosted, tuned-up, cured, tweaked, fixed, or optimized it shouldn't.

In other words, injudicious use of "Registry cleaners" CAN & DOES cause problems.

> > Re your recent back up....was your system stable at that point?

> > > Re BSOD's

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

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.

 

[Lantz]

If you went from Windows XP to Windows 7 you probably did a clean install correct? If so and you had that problem before and it persists it probably isn't the registry. Also, have you checked your system's temperature to see if it's overheating?

 

[fredoz]

__Current accepted wisdom with Win 7 is to NOT use a cleaner.

I had this problem with XP as well, just not so frequently





__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.

I edited my original post and uploaded the files you requested.




Regarding overheating: how does one check for that?

 

[JMH]

> Please remove your Zone Alarm at least to test.
Make sure the inbuilt Firewall is turned on.

http://download.zonealarm.com/bin/free/support/cpes_clean.exe


> Asacpi.sys

The pre 2009 version of this driver is a known BSOD cause.

Please visit this link: Asus tek computer inc. -support- drivers and download p7p55d le

ASUSTeK Computer Inc. -Support- Drivers and Download P7P55D LE
ASUSTeK Computer Inc. - Motherboards- ASUS P5K-VM

Scroll down to the utilities category, then scroll down to the "atk0110 driver for windowsxp/vista/windows 7 32&64-bit" (it's about the 12th item down).

Download and install it.

Go to c:\windows\system32\drivers to check and make sure that the asacpi.sys file is date stamped from 2009 or 2010 (notbefore).

 

[zigzag3143]

What I have: - Windows 7 32 bit SP1
-AMD Athlon 64 Dual Core 3800+
-2 GIG RAM
-NVIDIA Quadro FX-450

What's happening:
The computer reboots itself. I've checked processor for heat sink problems, thinking this is an hardware issue.
I've attached required files. Any help is greatly appreciated.

In addition to doing the items JMH has suggested please update the following drivers

ASACPI.sys    8/12/2004 9:52:52 PM           
nvmpu401.sys    4/13/2005 2:34:22 PM      
AsIO.sys    12/21/2005 3:55:21 AM   
nvm62x32.sys    10/17/2008 4:00:39 PM   
AGRSM.sys    11/10/2008 9:56:37 AM        
ssmdrv.sys    5/5/2009 5:05:18 AM    
nvlddmkm.sys    5/14/2009 3:32:27 PM       
RTKVAC.SYS    6/18/2009 2:36:37 PM

How To Find Drivers:

- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.

- - The most common drivers are listed on this page: Driver Reference Driver Reference
- - Driver manufacturer links are on this page: Drivers and Downloads

Re; Overheating there are several good utilities to check temps including cpu-z, everest,aida, etc.

 

[fredoz]

So I replaced the Asacpi.sys with the one with the newer date. No crashes whatsoever yesterday. 3 crashes this morning. Obviously there's something else going on here.

 

[JMH]

> Did you remove Zone Alarm for testing purposes?

>Have you followed zigzags instructions?

 

[fredoz]

I followed your directions. Removed Zone Alarm. Aisa 64 tells me I have Asus Motherboard Name A8N5X, not P5K-VM as you indicated. I have already updated to the drivers you suggested. Now, does that mean I have updated to the wrong drivers? When I went to Asus A8N5X download section I only saw drivers for Vista, none for Win7. And when I tried to run the ACPI driver utility it told me "does not support this operating system WNT_6.1_32MCE."

Also I used Speedfan to record temperatures. The only item it shows as hot is the GPU, with a reading of 61 C.

I just find it very odd that I can run this computer one day with no problems at all and then the next day I get 4 crashes on the row.

 

[JMH]

So I replaced the Asacpi.sys with the one with the newer date. No crashes whatsoever yesterday. 3 crashes this morning. Obviously there's something else going on here.

Upload the latest crashes for analysis as per my Post 6.

 

[fredoz]

Ok. Here's last minidump file: Windows_NT6_BSOD_jcgriff

 

[JMH]

**** Delighted to see you updated all of your drivers as per zigzags recommendation.
Well done to you!
****

These crashes were caused by memory corruption (probably a driver).

If you are overclocking anything reset to default before running this test.
In other words STOP!!!

Pleas run this test...

Driver verifier

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Special Pool", "Force Pending I/O Requests" and "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

If that doesn't work, post back and we'll have to see about fixing the registry entry off-line:

Delete these registry keys to stop Driver Verifier from loading (works in XP, Vista, Win7):
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDrivers
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDriverLevel

Using Driver Verifier to identify issues with Windows drivers for advanced users

 

[fredoz]

Ok. Turned off the Driver verifier and got BSD. Here's the minidump file.

 

[zigzag3143]

Ok. Turned off the Driver verifier and got BSD. Here's the minidump file.

FINALLY. The most recent was verified and related to Vusbbus.sys with description Virtual USB bus driver is a driver file from company AlexVel belonging to product Virtual USB bus driver.


I would remove it at least to test.

If you have not I would also run malwarebytes.


Please download the free version of Malwarebytes.
Update it immediately.
Do a full system scan
Let us know the results at the end.



Malwarebytes : Download free malware, virus and spyware tools to get your computer back in shape!

 

[fredoz]

i removed Vusbbus.sys from system 32 folder, rebooted the computer, downloaded Malwarebytes and installed it. The computer crashed while Malwarebytes was scanning. I attached the last minidump.

 

[zigzag3143]

i removed Vusbbus.sys from system 32 folder, rebooted the computer, downloaded Malwarebytes and installed it. The computer crashed while Malwarebytes was scanning. I attached the last minidump.

Zone alarm is gone asacpi has been updated but these still remain.

giveio.sys    4/3/1996 9:33:25 PM    0x89032000    0x89032680        0x00000680    0x316334f5                        
mbmiodrvr.sys    4/10/2004 9:42:35 AM    0x8d98e000    0x8d98eb80        0x00000b80    0x407807db                        
[COLOR=Red]nvmpu401.sys    4/13/2005 2:34:22 PM    0x941eb000    0x941ed800        0x00002800    0x425d743e                        
AsIO.sys    12/21/2005 3:55:21 AM    0x8ecd6000    0x8ecd7440        0x00001440    0x43a91879[/COLOR]                        
hardlock.sys    11/9/2006 6:48:42 AM    0x9e827000    0x9e8d0600        0x000a9600    0x4553159a                        
nvm62x32.sys    10/17/2008 4:00:39 PM    0x8fb15000    0x8fb69c80        0x00054c80    0x48f8fcf7                        
AGRSM.sys    11/10/2008 9:56:37 AM    0x8fa00000    0x8fb06000        0x00106000    0x49184ba5                        
ssmdrv.sys    5/5/2009 5:05:18 AM    0x8d933000    0x8d938a00        0x00005a00    0x4a000f5e                        
RTKVAC.SYS    6/18/2009 2:36:37 PM    0x8f401000    0x8f7fa200        0x003f9200    0x4a3a9745

How To Find Drivers:

- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.

- - The most common drivers are listed on this page: Driver Reference Driver Reference
- - Driver manufacturer links are on this page: Drivers and Downloads