PC keeps crashing/rebooting

[fecalpheliac]

Hi,

I recently installed Windows 7 and now my PC has become almost unusable.

A bit of background: I had XP before, and it crashed quite often when doing something that required relatively intensive graphics (gaming).

Anyway, my PC reboots pretty much every time during start up. It used to be that I could let it reboot a few times and then it would run fine (until the next morning). Today, it's been rebooting many times over (stops at the Windows splash screen). The 2 times that it did boot, I used the PC for about 5 min before it BSOD'd (various different stop codes).

WHAT can I do? I thought it was my graphics card because of the crashing while gaming. Cleaning it out and applying new thermal grease did solve this issue, but it doesn't affect the crashing on boot at all

Thanks

[jdeb]

System specs please...

1. Attempt to boot in Safe Mode.
If you can boot the system properly in Safe Mode (press F8 at startup), there's a good chance whatever is wrong revolves around a device driver. Safe Mode loads its own set of fail-safe drivers, which are minimally functional, but more importantly, stable.

2. Disable the auto-reboot function
Automatic Restart Windows 7 - How To Disable the Automatic Restart on System Failure in Windows 7

3. Note any crash messages once auto-reboot is disabled.

[EzyStvy]

Google the STOP Codes....

[fecalpheliac]

Thanks.

As luck would have it, it just booted OK. I disabled automatic restart and will write down the error message I get at the next BSOD.

The problem is that the stop codes have been different every time up to now...

[jdeb]

Download and install WhoCrashed. It will read your dump files and hopefully isolate the hardware or driver issue(s)

Resplendence Software - WhoCrashed, automatic crash dump analyzer

Let us know

[fecalpheliac]

Thanks, I've installed it and here is the analysis:







--------------------------------------------------------------------------------
Welcome to WhoCrashed HOME EDITION v 3.02
--------------------------------------------------------------------------------

...

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

computer name: DESKTOP-PC
windows version: Windows 7 , 6.1, build: 7600
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Core(TM)2 CPU 6700 @ 2.66GHz Intel586, level: 6
2 logical processors, active mask: 3
RAM: 3220299776 total
VM: 2147352576, free: 2005925888



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

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Mon 9/19/2011 10:16:51 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: unknown_module_04e0c108.sys (Unloaded_Unknown_Module_04e0c108+0x597D2E49)
Bugcheck code: 0x7E (0xFFFFFFFFC0000005, 0xFFFFFFFF92D7DBB5, 0xFFFFFFFF80EA09E8, 0xFFFFFFFF80EA05C0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Bug check description: This bug check indicates that a system thread generated an exception that the error handler did not catch.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: unknown_module_04e0c108.sys .
Google query: unknown_module_04e0c108.sys SYSTEM_THREAD_EXCEPTION_NOT_HANDLED




On Mon 9/19/2011 8:47:25 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\091911-38703-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x38B5B)
Bugcheck code: 0xD1 (0x5, 0x2, 0x0, 0xFFFFFFFF949F93CD)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Mon 9/19/2011 7:19:54 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\091911-29515-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x8B2B2)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF8BC912B2, 0xFFFFFFFF8DBCC91C, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\tcpip.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: TCP/IP Driver
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.



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

3 crash dumps have been found and analyzed. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

unknown_module_04e0c108.sys

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.


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.

[jdeb]

system specs please

check device manager for errors.

BIOS version


7E may be related to video driver and / or anti virus software
8E may be related to BIOS
D1 is probably your antivirus software

again, need system spec, motherboard, video, ram, hard drive, power supply. third party software, etc.

[fecalpheliac]

some system info from above plus extra:

windows version: Windows 7 , 6.1, build: 7600
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Core(TM)2 CPU 6700 @ 2.66GHz Intel586, level: 6
2 logical processors, active mask: 3
RAM: 3220299776 total
VM: 2147352576, free: 2005925888
GFX: ATI 1900XTX


BTW I also just installed the following hotfix from Microsoft, so far so good:
Error message on a blue screen on a computer that is running Windows 7 or Windows Server 2008 R2: "STOP: 0x0000000A"

[jdeb]

O.K. I guess you figured it all out. Those specs only tell me your CPU and vaguely your video card. You have three separate issues and I doubt a hotfix is going to fix all or any of them.

[fecalpheliac]

ok, what else can I give you?

[glc]

Is this a name brand computer or custom build? If it's name brand, brand and model. If it's custom, brands and models of the components.