Jump to content

Welcome to Geeks to Go - Register now for FREE

Need help with your computer or device? Want to learn new tech skills? You're in the right place!
Geeks to Go is a friendly community of tech experts who can solve any problem you have. Just create a free account and post your question. Our volunteers will reply quickly and guide you through the steps. Don't let tech troubles stop you. Join Geeks to Go now and get the support you need!

How it Works Create Account
Photo

Tremendous Windows 7 Boot problems


  • Please log in to reply

#76
iammykyl

iammykyl

    Tech Staff

  • Technician
  • 7,659 posts
Gday.
Please start the computer in safe mode with networking.
Download Who Crashed from the link. Scroll down to,
WhoCrashed 5.00Comprehensible crash dump analysis tool<br style="font-family: 'Segoe UI', Arial; font-size: small;">for Windows 8.1/8/7/Vista/XP/2012/2008/2003 (x86 and x64)


This program checks for any drivers which may have been causing your computer to crash....<br style="color: rgb(13, 41, 117); font-size: 13px; line-height: 19px; background-color: rgb(242, 242, 242);"><br style="color: rgb(13, 41, 117); font-size: 13px; line-height: 19px; background-color: rgb(242, 242, 242);">Click on the file you just downloaded and run it.
Put a tick in Accept then click on Next
Put a tick in the Don't create a start menu folder then click Next
Put a tick in Create a Desktop Icon then click on Install and make sure there is a tick in Launch Whocrashed before clicking Finish
Click Analyze
It will want to download the Debugger and install it Say Yes
WhoCrashed will create report but you have to scroll down to see it
Copy and paste it into your next reply

http://www.resplendence.com/downloads
  • 0

Advertisements


#77
Colorado7

Colorado7

    Member

  • Topic Starter
  • Member
  • PipPip
  • 55 posts
Sorry I've been busy the last couple of days. Here is the report.

System Information (local)
--------------------------------------------------------------------------------

computer name: JOHN-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
Hardware: ASUSTeK Computer INC., M4A87TD EVO
CPU: AuthenticAMD AMD Phenom™ II X6 1090T Processor AMD586, level: 16
6 logical processors, active mask: 63
RAM: 8588009472 total
VM: 2147352576, free: 1961660416




--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

No valid crash dumps have been found on your computer

--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

Crash dumps are enabled but no valid crash dumps have been found. It may be that there are problems which prevent crash dumps from being written out. Check out the following article for possible causes: If crash dumps are not written out.

In case your computer does experience sudden reboots it is likely these are caused by malfunctioning hardware, power failure or a thermal issue. To troubleshoot a thermal issue, check the temperature using your BIOS setup program, check for dust in CPU and motherboard fans and if your computer is portable make sure it's located on a hard surface. Otherwise it's suggested you contact the support department of the manufacturer of your system or test your system with a memory test utility for further investigation.

Check out the following articles for more information: Troubleshooting sudden resets and shut downs.

Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.


  • 0

#78
iammykyl

iammykyl

    Tech Staff

  • Technician
  • 7,659 posts
That result was good but actually hoping for a consistent driver error.
Sorry but I just about run out of idias. The only direction we have not looked at is display . You could try a DVI cable or a different monitor or suitable TV.
  • 0

#79
Colorado7

Colorado7

    Member

  • Topic Starter
  • Member
  • PipPip
  • 55 posts
Thanks but I've already tried.
  • 0

#80
Colorado7

Colorado7

    Member

  • Topic Starter
  • Member
  • PipPip
  • 55 posts
So that's it? No more suggestions?
  • 0

#81
iammykyl

iammykyl

    Tech Staff

  • Technician
  • 7,659 posts
Yes, two thanks to Phillpower2.
To see if any error messages are displayed I would suggest that Colorado7 disables the automatic restart in Windows 7, details here
You could also have Colorado7 download and run the new Samsung SSD utility tool to see if that helps,Magician 4.3

I would try both in safe mode with networking.
  • 0

#82
Colorado7

Colorado7

    Member

  • Topic Starter
  • Member
  • PipPip
  • 55 posts
Automatic restarts disabled, Samsung Magician 4.3 installed. Fingers crossed.
  • 0

#83
Colorado7

Colorado7

    Member

  • Topic Starter
  • Member
  • PipPip
  • 55 posts
No luck, it still crashed while I was AFK for about 4 hours. Seems it crashed about mid-way through.

But, the event viewer shows information!

Take a look at this.

http://imgur.com/Ah9P2Ki

It shows detailed information. Usually it just shows 0 0 0 0 0 for all those values. It's not something I can analyze myself, but maybe you can.

Edited by Colorado7, 17 December 2013 - 05:02 AM.

  • 0

#84
phillpower2

phillpower2

    Mechanised Mod

  • Global Moderator
  • 24,780 posts
It would appear that the computer and Windows are still shutting down unexpectedly.

Couple of things for you to do;

Please provide an updated list of the hardware that is connected to the computer at present.

Tell us from where you have obtained your Windows 7 OS media.

Run DriverView and then copy/paste the results into your next reply, see here

Finally;
To see if we can identify any driver conflicts please refer to the copy/paste details below provided courtesy of jcgriff2 :thumbsup:

1. Create a Windows System Restore Point -
Vista - START | type rstrui - create a restore point
Windows 7 - START | type create | select "Create a Restore Point"

2. Run the Driver Verifier -
Go to START | type verifier | make these selections -

1. Select 2nd option - "Create custom settings (for code developers)"
2. Select 2nd option - "Select individual settings from a full list"
3. Check these boxes -▪ Special Pool
▪ Pool Tracking
▪ Force IRQL checking
▪ Deadlock Detection
▪ Security Checks (new as of Windows 7)
▪ Concurrency Stress Test (new as of Windows 8)
▪ DDI compliance checking (new as of Windows 8)
▪ Miscellaneous Checks4. Select last option - "Select driver names from a list"
5. Click on the Provider heading - sorts list by Provider
6. Check ALL boxes where "Microsoft" IS NOT the Provider
7. Click on Finish
8. Re-boot*** IMPORTANT - PLEASE READ:

- If the Driver Verifier (DV) finds a violation, it will result in a BSOD

- After re-start, you may not be able to log on to normal Windows
... • Boot into SAFEMODE - tap the F8 key repeatedly during boot-up
... • Select "System Restore"
... • Choose the restore point that you created in step #1

- For Driver Verifier status
--- select last option, 1st screen -or-
--- type verifier /query (in a cmd/DOS screen)
- To turn Driver Verifier off - verifier /reset then re-boot

- The Driver Verifier needs to run as long as possible - even if the status screen appears clear.
- All future BSOD dumps must be VERIFIER_ENABLED_MINIDUMPs - otherwise the dump(s) are of no use

If your system does BSOD while the Driver Verifier is running, please retrieve the dump file from c:\windows\minidump and attach it to your next reply.
  • 0

#85
Colorado7

Colorado7

    Member

  • Topic Starter
  • Member
  • PipPip
  • 55 posts
I haven't posted here in forever - but that's because I think I have found the solution!

If this is the solution I am really pissed, but here goes.

As I've mentioned before, my PC would crash when I play games that require a lot of resources, especially Rome 2 Total War, but also Dota 2. However I recently started playing Football Manager 2014, and it's not GPU intensive whatsoever. What it is though, is CPU and RAM intensive. Rome 2 and Dota 2 are much more GPU intensive, especially Rome 2. I would crash in Dota 2 and Rome 2, but never ever in FM 2014.

As I've done many times before, I've checked the temps for CPU and GPU. They are no where near dangerous levels by any stretch of the imagination. GPU will reach 50-60 Celsius during playing, while CPU is a little cooler.

So why would the PC crash during GPU intensive games but not during CPU/RAM intensive games?

Well, that's what I just figured out. I think.

It turns out it's the automatic fan level of the GPU that is the problem!
Yes, that's right. While my GPU would get hotter to 50-60 Celsius, the GPU fan would not increase enough or barely at all. That's why my GPU thought it was overheating and the PC shuts down because it believes it's a danger when it's in fact not. During load of heavy games my GPU fan, which was set to automatic, would only go up to about 40-50 % load, or sometimes even less. If it's idle or I am just running Dota 2 in the background (if I am alt-tabbed) the GPU fan runs at about the lowest setting there is, 35 %. Consider the fact that the GPU is factory overclocked, and GPU fan not doing enough work. That's the root of the friggin problem. Take a look at this. These are the default values for my GPU card, with GPU Mhz at 1111, and Memory Clock at 7010.

http://i.imgur.com/kS3hSaI.png

What has fixed the problem so far at least, is to manually ramp up the fan speed when I play Dota 2 or other GPU intensive games. And I have also lowered the clock to the lowest possible value. This has been 100 % stable, and I've run Dota 2 for about 18 hours one day. That day I was just running it to test, and no crashes or anything.

I have however, crashed twice, that was when I forgot to manually turn the fan speed from automatic to manual. It's annoying, but I have to do it every time the computer powers up - I tried saving a default profile with the GPU at the lowest values, and manually turning up the fan. That has been 100 % stable. I would assume that I can overclock the card as long as I turn up the fan, at least to a certain threshold.

So what the actual [bleep]. I mean, I don't really like to curse but a problem like this causing so much trouble and no information to find anywhere on the internet. The 'automatic' fan setting is a [bleep]ing joke and I am sure a lot of people had this problem too. I feel sorry I wasted not only my time, but your time when it turns out the problem is so simple yet so hidden. I'm sure there's thousands of other people having the same problem. So, I assume the problem is with the GPU Tweak program made by Asus, and nothing with the GPU itself. This system has been running stable now. Take a look at the event viewer.

http://i.imgur.com/5BNsP7U.png

Red = Uncontrolled Crash before I applied fix
Blue = Controlled Crash after fix, or rather, me forgetting to manually toggle Fan higher.
Yellow = Uncontrolled Crash, this event turned up after I started up the PC. It was not in game but rather a problem I never saw, but it turned up in event viewer. Basically, it was a boot that seemingly went normal, but somehow the event turned up in event viewer.

The yellow problem, I am not even sure if that is a problem or what is going on there. It seems a fluke more than an actual problem.

But at the end of the day, my PC is running 100 % stable in games now, for very long sessions. Thank you everyone for your help, I really can't thank you enough, and merry christmas.

Edited by Colorado7, 26 December 2013 - 05:29 AM.

  • 0

Advertisements


#86
iammykyl

iammykyl

    Tech Staff

  • Technician
  • 7,659 posts
Gday.
Not a problem, just glad you managed to find the problem and come up with a work around.
You could try reinstalling the Asus module or see if there is an update.
Good luck.
  • 0






Similar Topics

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP