Windows 7 Forums

Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: Freezing because of an unexpected error event id 6008

14 Dec 2011   #1
leche

Windows 7 Ultimate x64
 
 
Freezing because of an unexpected error event id 6008

Dear Friends i have a problem with my pc.This is the pc
OS
Windows 7 Ultimate x64
CPU
AMD Phenom II X4 955 3.2 Ghz
Motherboard
Gigabyte MA785GT-UD3H ver 1.1
Memory
4 gb 1600Mhz (2x2gb) G.Skill Ripjaws F3-12800CL8D-4GBRM
Graphics Card(s)
HIS Radeon HD5750 iCooler IV 1Gb 128Bit GDDR5
Sound Card
Onboard
Monitor(s) Displays
Philips 190C 19" LCD
Screen Resolution
N/A
Hard Drives
Western Digital Caviar Black (WD7501AAL89 3.5" 750GB SATA
PSU
600W thermaltake PSU
Case
Thermaltake V3 Black Edition with 600w psu
Cooling
Sunbeam Core Contact Freezer 120mm CPU fan +120mm case fan
My computer sometimes freezes.I send it to service but they werent able to find any errors.So now i understood that the pc creates an error when it is working under pressure, when playing game for example.The screen goes dark firstly, after sound freezes and there isnt any errors.I had to reset and after that it doesnt give an errors too.And when i looked event viewer i saw theese errors.




System

- Provider


[ Name] EventLog


- EventID 6008


[ Qualifiers] 32768



Level 2


Task 0


Keywords 0x80000000000000

- TimeCreated


[ SystemTime] 2011-12-14T20:32:26.000000000Z



EventRecordID 4164


Channel System


Computer Baris-PC


Security
- EventData


22:31:15


‎14.‎12.‎2011










3366










DB070C0003000E0016001F000F00D200DB070C0003000E0014001F000F00D200600900003C00000001000000600900000000 0000B00400000100000000000000
Binary data:

In Words
0000: 000C07DB 000E0003 001F0016 00D2000F
0008: 000C07DB 000E0003 001F0014 00D2000F
0010: 00000960 0000003C 00000001 00000960
0018: 00000000 000004B0 00000001 00000000

In Bytes
0000: DB 07 0C 00 03 00 0E 00 .......
0008: 16 00 1F 00 0F 00 D2 00 .......
0010: DB 07 0C 00 03 00 0E 00 .......
0018: 14 00 1F 00 0F 00 D2 00 .......
0020: 60 09 00 00 3C 00 00 00 `...<...
0028: 01 00 00 00 60 09 00 00 ....`...
0030: 00 00 00 00 B0 04 00 00 .......
0038: 01 00 00 00 00 00 00 00 ........


And this one


- System

- Provider


[ Name] Microsoft-Windows-Kernel-Power


[ Guid] {331C3B3A-2005-44C2-AC5E-77220C37D6B4}



EventID 41


Version 2


Level 1


Task 63


Opcode 0


Keywords 0x8000000000000002

- TimeCreated


[ SystemTime] 2011-12-14T20:32:20.674414300Z



EventRecordID 4169


Correlation

- Execution


[ ProcessID] 4


[ ThreadID] 8



Channel System


Computer Baris-PC

- Security


[ UserID] S-1-5-18

- EventData

BugcheckCode 0

BugcheckParameter1 0x0

BugcheckParameter2 0x0

BugcheckParameter3 0x0

BugcheckParameter4 0x0

SleepInProgress false

PowerButtonTimestamp 0

So i cant understand anything about the error.What can i do to fix this error?What is the problem exactly?Sorry for poor english.Thanks for everything already now.


My System SpecsSystem Spec
.
15 Dec 2011   #2
JMH

Win 7 Ultimate 64-bit. SP1.
 
 

There are many reasons why a PC " behaves" this way.

These annoying " gliches" may be caused by an overloaded hard drive, overworked CPU, Malware, running 2 AV 's, unnecessary data, Browser addons or you may have unnecessary programs running in the background etc....


* Have you experienced a BSOD?


FYI.


windows 7 rc error event id 6008


unexpected shutdown "event id=6008" - Microsoft Answers


http://www.sevenforums.com/crashes-d...id-6008-a.html


Troubleshooting steps for you to try -

* If you are overclocking STOP.

*Make sure all intake/exhausts vents are clean along with all fans.
Get some temp monitoring software for cpu, gpu.

* Have you a System Restore Point PRIOR to the problem presenting that you could roll back to?

*How long have you had this problem for?

*Have you SP1 installed?

* What Anti Virus Program came preinstalled on your computer?
How did you get rid of it?

* Please list ALL the Security Programs currently used.

* Run a Disk Check.

Disk Check



My System SpecsSystem Spec
15 Dec 2011   #3
leche

Windows 7 Ultimate x64
 
 

Quote:
There are many reasons why a PC " behaves" this way.

These annoying " gliches" may be caused by an overloaded hard drive, overworked CPU, Malware, running 2 AV 's, unnecessary data, [COLOR=#3485BD ! important][COLOR=#3485BD ! important]Browser[/COLOR][/COLOR] addons or you may have unnecessary programs running in the background etc....


* Have you experienced a BSOD?


FYI.


windows 7 rc error event id 6008


unexpected shutdown "event id=6008" - Microsoft Answers


EventID: 6008


Troubleshooting steps for you to try -

* If you are overclocking STOP.

*Make sure all intake/exhausts vents are clean along with all fans.
Get some temp monitoring software for cpu, gpu.

* Have you a System Restore Point PRIOR to the problem presenting that you could roll back to?

*How long have you had this problem for?

*Have you SP1 [COLOR=#3485BD ! important][COLOR=#3485BD ! important]installed[/COLOR][/COLOR]?

* What Anti Virus Program came preinstalled on your computer?
How did you get rid of it?

* Please list ALL the Security Programs currently used.

* Run a Disk Check.

Disk Check
i have ecperienced a few times BSOD.

I am not overclocking

All fans clean and air circulation good.it have given that errors from the days i bought it.

SP1 is installed.

There asnt any security progeams on it, i use kaspersky internet security 2012

I checked te disk there is no errors.
My System SpecsSystem Spec
.

15 Dec 2011   #4
JMH

Win 7 Ultimate 64-bit. SP1.
 
 

IF you have any 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.

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:

Quote:
* 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:
Quote:
* 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.
My System SpecsSystem Spec
16 Dec 2011   #5
leche

Windows 7 Ultimate x64
 
 

Dear friends, i had read a comment about this situation before i wrote here.It said that the reason of the problem might be Win7's power settings.And he advised to change Win7 power settings (to high power) in control panel.So i tried it, and changed a option in bios what changes cpu's voltage when it overheated.Now i have been forcing the pc by some games and graphic softwares.Up to know (since yestarday) there isn't any errors.After a few days test, i will tell about the situation in this topic.
My System SpecsSystem Spec
16 Dec 2011   #6
leche

Windows 7 Ultimate x64
 
 

No.Unfortunately i saw the same error.But i have found the dump file.And now i will paste all of informations from it.



Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Baris\Desktop\WD-20111216-2344.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0xfffff800`03063000 PsLoadedModuleList = 0xfffff800`032a0e70
Debug session time: Fri Dec 16 23:44:58.501 2011 (UTC + 2:00)
System Uptime: 0 days 1:32:05.796
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
................................................................
.........................
Loading User Symbols
Mini Kernel Dump does not contain unloaded driver list
Unable to load image watchdog.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for watchdog.sys
*** ERROR: Module load completed but symbols could not be loaded for watchdog.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 117, {fffffa80081df010, fffff88004607ba8, 0, 0}

*** WARNING: Unable to verify timestamp for mssmbios.sys
*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
Unable to load image dxgkrnl.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for dxgkrnl.sys
*** ERROR: Module load completed but symbols could not be loaded for dxgkrnl.sys
Unable to load image atikmpag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for atikmpag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
Probably caused by : atikmpag.sys ( atikmpag+7ba8 )

Followup: MachineOwner
---------

1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

VIDEO_TDR_TIMEOUT_DETECTED (117)
The display driver failed to respond in timely fashion.
(This code can never be used for real bugcheck).
Arguments:
Arg1: fffffa80081df010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88004607ba8, The pointer into responsible device driver module (e.g owner tag).
Arg3: 0000000000000000, The secondary driver specific bucketing key.
Arg4: 0000000000000000, Optional internal context dependent data.

Debugging Details:
------------------

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************

ADDITIONAL_DEBUG_TEXT:
Use '!findthebuild' command to search for the target build information.
If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.

FAULTING_MODULE: fffff80003063000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 4e68f2d9

FAULTING_IP:
atikmpag+7ba8
fffff880`04607ba8 ?? ???

DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_TIMEOUT

TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b


BUGCHECK_STR: 0x117

CURRENT_IRQL: 0

STACK_TEXT:
fffff880`0275d490 fffffa80`056d28c0 : fffff880`058748a0 fffffa80`081df010 fffffa80`063c1010 fffff880`04607ba8 : watchdog+0xa577
fffff880`0275d498 fffff880`058748a0 : fffffa80`081df010 fffffa80`063c1010 fffff880`04607ba8 00000000`00000000 : 0xfffffa80`056d28c0
fffff880`0275d4a0 fffffa80`081df010 : fffffa80`063c1010 fffff880`04607ba8 00000000`00000000 00000000`00000000 : dxgkrnl+0x1f8a0
fffff880`0275d4a8 fffffa80`063c1010 : fffff880`04607ba8 00000000`00000000 00000000`00000000 fffffa80`00000b70 : 0xfffffa80`081df010
fffff880`0275d4b0 fffff880`04607ba8 : 00000000`00000000 00000000`00000000 fffffa80`00000b70 00000000`00000000 : 0xfffffa80`063c1010
fffff880`0275d4b8 00000000`00000000 : 00000000`00000000 fffffa80`00000b70 00000000`00000000 00000000`00000000 : atikmpag+0x7ba8


STACK_COMMAND: kb

FOLLOWUP_IP:
atikmpag+7ba8
fffff880`04607ba8 ?? ???

SYMBOL_STACK_INDEX: 5

SYMBOL_NAME: atikmpag+7ba8

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: atikmpag

IMAGE_NAME: atikmpag.sys

BUCKET_ID: WRONG_SYMBOLS

Followup: MachineOwner
---------


So what does it mean?might it be a hardware problem?
My System SpecsSystem Spec
16 Dec 2011   #7
JMH

Win 7 Ultimate 64-bit. SP1.
 
 

leche,
Unfortunately that is no help what so ever to you or us.
We need to do the DMP analysis.{ Refer my post 4 for the instructions.
Each step needs to be carefully followed.}

If you are having trouble translating, have you someone more fluent in English to assist you?

Until we receive the DMP files all else is speculation...


Please also update to SP1 ASAP!
My System SpecsSystem Spec
17 Dec 2011   #8
leche

Windows 7 Ultimate x64
 
 

Quote:

leche,
Unfortunately that is no help what so ever to you or us.
We need to do the DMP analysis.{ Refer my post 4 for the instructions.
Each step needs to be carefully followed.}

If you are having trouble translating, have you someone more fluent in English to assist you?

Until we receive the DMP files all else is speculation...


Please also update to SP1 ASAP!
Dear JMH, My english is enough to understand, but the problem is that i have done what you wrote to create dump files, but i can't find it now.The bsod doesnt seems always.The display goes black and sound hangs.And the pc hangs hard.It show bsod for a few time.But Many of errors have not given any bsod.I did what you said.But After the crash i couldn't find any folder like minidump in Windows folder.So i searched .dmp files in Windows and found a file which is called "WD-20111216-2344.dmp" in "C:\Windows\LiveKernelReports\WATCHDOG" so i thought this is the file we needed, because it was create the time when pc crashed.Is it enough if i posted the file you?Or what can i do about it?
My System SpecsSystem Spec
17 Dec 2011   #9
zigzag3143

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by leche View Post
Quote:

leche,
Unfortunately that is no help what so ever to you or us.
We need to do the DMP analysis.{ Refer my post 4 for the instructions.
Each step needs to be carefully followed.}

If you are having trouble translating, have you someone more fluent in English to assist you?

Until we receive the DMP files all else is speculation...


Please also update to SP1 ASAP!
Dear JMH, My english is enough to understand, but the problem is that i have done what you wrote to create dump files, but i can't find it now.The bsod doesnt seems always.The display goes black and sound hangs.And the pc hangs hard.It show bsod for a few time.But Many of errors have not given any bsod.I did what you said.But After the crash i couldn't find any folder like minidump in Windows folder.So i searched .dmp files in Windows and found a file which is called "WD-20111216-2344.dmp" in "C:\Windows\LiveKernelReports\WATCHDOG" so i thought this is the file we needed, because it was create the time when pc crashed.Is it enough if i posted the file you?Or what can i do about it?
Leche

We can glean very little information from the winDbg output in your post and since we cant get a dmp file the most likely causes of your crash (and its is only for ths one only) is a memory issue (probably caused by a driver (perhaps your directX)




These crashes were caused by memory corruption (probably a driver). Please run these two tests to verify your memory and find which driver is causing the problem.

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



1-Memtest.
Quote:
*Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86+ - Advanced Memory Diagnostic Tool

*Boot from the CD, and leave it running for at least 5 or 6 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.

Any errors are indicative of a memory problem.

If a known good stick fails in a motherboard slot it is probably the slot.

RAM - Test with Memtest86+



2-Driver verifier

Quote:
I'd suggest that you first backup your data 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).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

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 "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).

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.
Driver Verifier - Enable and Disable


Further Reading
Using Driver Verifier to identify issues with Windows drivers for advanced users
My System SpecsSystem Spec
17 Dec 2011   #10
JMH

Win 7 Ultimate 64-bit. SP1.
 
 

As well as the considered advice from zigzag 3143 please carefully read...

Quote:

It's not a true crash, in the sense that the bluescreen was initiated only because the combination of video driver and video hardware was being unresponsive, and not because of any synchronous processing exception".

Since Vista, the "Timeout Detection and Recovery" (TDR) components of the OS video subsystem have been capable of doing some truly impressive things to try to recover from issues which would have caused earlier OSs like XP to crash.


As a last resort, the TDR subsystem sends the video driver a "please restart yourself now!" command and waits a few seconds.


If there's no response, the OS concludes that the video driver/hardware combo has truly collapsed in a heap, and it fires off that stop 0x116 BSOD.


If playing with video driver versions hasn't helped, make sure the box is not overheating.


Try removing a side panel and aiming a big mains fan straight at the motherboard and GPU.


Run it like that for a few hours or days - long enough to ascertain whether cooler temperatures make a difference.


If so, it might be as simple as dust buildup and subsequently inadequate cooling.


I would download cpu-z and gpu-z (both free) and keep an eye on the video temps.


STOP 0x116: VIDEO_TDR_ERROR troubleshooting

If all else fails..

Repair Install

Clean Install Windows 7






My System SpecsSystem Spec
Reply

 Freezing because of an unexpected error event id 6008




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
Event ID 6008
Every time I shutdown or restart on boot Event Viewer writes an administrative error in the log "Source: EventLog Event ID: 6008 The previous system shutdown at <time> on <date> was unexpected." I do of course shut down properly, i.e... Start> Shutdown or Restart. I've done a good deal of...
BSOD Help and Support
Event Viewer - Event ID 6008 [Troubleshooting]
Hello, First time ever I am posting a thread like this, never thought I would have to. Anyway, the issue is described below. Randomly my computer decides to shutdown and restart unexpectedly.
BSOD Help and Support
Event Viewer ID 6008
Hi Folks, Everytime my Laptop was shutdown from 28 Oct. (I used the 'Shutdown' button in the start menu everytime.) I have got the same message in Event Viewer ID 6008 as in text. - Log Name: System Source: EventLog Date: 23/11/2011 02:36:51 Event ID: 6008 Task...
Performance & Maintenance
Event Error 6008
I get an Event Error 6008 on my desktop that I personally built. When the weather was cooler the computer ran fine. Now that it is summer time (I live in CA and its about 100 outside and 80ish in the house) it shuts down when I'm running high resource stuff such as games and multi-tasking if I...
Hardware & Devices
Event ID 6008 Help.
About a month ago I built a new pc. Everything was running at great temps(no overclock). I use HW Monitor to look at the temps. I ran Memtest86 for about 3-4hrs with no errors and ran Prime95 for about 6-7hrs and never went above 55C on stock cooling(no failures). In the span of two weeks, I...
BSOD Help and Support
Windows 7 Hang Event 6008, Need some help
Hi, I have recently encounter computer hangs and sound jammed when im asleep playing music from the computer. After getting help from another forum, i updated on my realtek audio and network drivers and finally, it was the first time that my computer could continue to run after i woke up,...
BSOD Help and Support


Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 22:13.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App