Crash every 30 mins

[furydeath]

Out of no where to day mi computer starts BSOD on me every 25-30. I can't find any thing that says why ether. Been working just fine all this time and now i can hardly use it more then 30 mins. The only errors i can find on the event viewer are:

The Server service depends on the Security Accounts Manager service which failed to start because of the following error:
The service cannot be started, either because it is disabled or because it has no enabled devices associated with it.

and

The Computer Browser service depends on the Server service which failed to start because of the following error:
The dependency service or group failed to start.

And then the crash it's self with is just, The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

 

[JMH]

Hello furydeath...

We DO require the DMP files 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.



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 drop down box (the 256kb varies).
*Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
*OK.
Reboot if changes have been made.

 

[furydeath]

OK i knew i needed something hopefully i can get this before it crashes again.

K hopefully this is it said one was Dennie so hopeful wont need that one xD


Edit: now that i look at em probably only need the one dated today.

 

[furydeath]

i did find a new error in the last one that just happen

The computer has rebooted from a bugcheck. The bugcheck was: 0x1000007e (0xffffffffc0000005, 0xfffff880043cef00, 0xfffff88005bab668, 0xfffff88005baaed0). A dump was saved in: C:\Windows\Minidump\Minidump\080911-15366-01.dmp. Report Id: 080911-15366-01.

 

[furydeath]

Also did the one thing it asks to have done with the System Health Report and stuff.

 

[furydeath]

well 11 crashes later still no clue why.

 

[furydeath]

Now I'm crashing every 10 mins. anyone know a way to skip that would you like to start in safe mode cause if it's going to do this all night now at least it can save me 2 mins starting up 5 times an hour?

 

[furydeath]

ran memtest for 2 passes came up with 4 error how do you tell what stick it is tho in memetest?

I'm just testing the old way right now to see if that what it is saddly =(

 

[zigzag3143]

ran memtest for 2 passes came up with 4 error how do you tell what stick it is tho in memetest?

I'm just testing the old way right now to see if that what it is saddly =(

Furydeath

My sincere apologies for the extended wait.

Before you even worry about memory there are a few things I noticed in the crash dumps that might fix the problem without having to replace the ram.

There is a simple test to run that may take under an hour that will give us valuable information.

It is called a system file check and it is run the verify (and repair if possible) operating system files.. It is run like this

To do this type cmd in search, then right click to run as administrator, then
SFC /SCANNOW

Read here for more information http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

Let us know the results from the report at the end.

Also of note

1-old drivers that should be updated.

RTCore64.sys    5/25/2005 2:39:12 AM        fffff880`0810f000    fffff880`08115000    0x00006000    0x42941d90                        
mcdbus.sys    2/24/2009 6:34:07 AM        fffff880`04253000    fffff880`0428f880    0x0003c880    0x49a3cd1f                        
gdrv.sys    3/12/2009 11:22:29 PM        fffff880`080fc000    fffff880`08105000    0x00009000    0x49b9d175                        
RTKVHD64.sys    6/16/2009 6:12:51 AM        fffff880`0523b000    fffff87f`053ebe80    0xffffffff001b0e80    0x4a377023

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

2-You also should update your ESET product as yours is over two years old and vulnerable to malware.

 

[furydeath]

D'oh i just took out ram it works fine with one stick in and i just switch them when i saw this so if it works ok on this one i'll give this post a go.

I have done ton's of them scan cause my windows is kinda crapped out as it is so know there will be something already in it.

 

[furydeath]

Well looks like its not the ram working a ton better with only one stick in lol now to see what happen with two again.

 

[furydeath]

So i took one stick out it was working fine now, i swtich the sticks and it was working fine, so then i put both back in and it's working fine for an hour. :| so now if the real test maybe it was them solar storms someone told me about lol.

 

[MvdB]

Happy for you that it seems to be better but I would still strongly advice to follow up all of Zigzags' advice. Not doing so is bound to cause problems in the future, even if your system seems more stable now....