BSOD after installing Win7Home32, different errors.

[flesk]

Hello.
I have read lots of topics in here, but cant seem to find anyone similar to my problem.
Windows is all updated. MB, Mouse, Keyboard, GFX, drivers are updated.
I had this system running winXP for 2½-3 years rock solid.
It also crashes about 10 seconds within Battlefield 3, also with all settings set to low. Cant play a youtube video without crashing, 5 seconds within.
I have disconnected all I/O devises, everything that is not neccesary, isnt plugged in.
I had the system crarshing so many times, that my hdd died. I bought an ssd instead and re-installed windows.

Please help me.. dont know what to do..

system;
Win 7 32 Home retail
core2 quad 2,83 - aprox 2½-3 years old
MSI P45 Diamond - aprox 2½-3 years old
Sapphire VaporX 2GB 4870 - aprox 2½-3 years old
Corsair 750w PSU - aprox 2½-3 years old
SSD 60GB - Brand new

 

[panais]

Hi.

http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html

 

[flesk]

I have pasted the log from "who crashed"...
The dates are not right, cant even change them without system crashing.
In the last part, it says that I should update the 802.11 driver because om the crashes, but i have just only NOW installed the card, because I moved the machine to another room.

[FONT=Segoe UI, Arial]System Information (local) [/FONT]
[FONT=Segoe UI, Arial]computer name: FLESK-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Core(TM)2 Quad CPU Q9550 @ 2.83GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 2146603008 total
VM: 2147352576, free: 2007306240
[/FONT]

[FONT=Segoe UI, Arial] Crash Dump Analysis [/FONT]
[FONT=Segoe UI, Arial]Crash dump directory: C:\Windows\Minidump[/FONT]

[FONT=Segoe UI, Arial][FONT=Segoe UI, Arial]Crash dumps are enabled on your computer.
[/FONT][/FONT]

[FONT=Segoe UI, Arial]On Wed 07-12-2011 23:50:40 GMT your computer crashed
crash dump file: C:\Windows\Minidump\120711-12932-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]cng.sys[/FONT] (cng+0x615E)
Bugcheck code: 0x101 (0x31, 0x0, 0xFFFFFFFF807C2120, 0x1)
Error: [FONT=Segoe UI, Arial]CLOCK_WATCHDOG_TIMEOUT[/FONT]
file path: C:\Windows\system32\drivers\cng.sys
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: Kernel Cryptography, Next Generation
Bug check description: This indicates that an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
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.
[/FONT]

[FONT=Segoe UI, Arial]On Wed 07-12-2011 23:50:40 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]netr28.sys[/FONT] (netr28+0xAB7C)
Bugcheck code: 0x101 (0x31, 0x0, 0xFFFFFFFF807C2120, 0x1)
Error: [FONT=Segoe UI, Arial]CLOCK_WATCHDOG_TIMEOUT[/FONT]
file path: C:\Windows\system32\drivers\netr28.sys
product: [FONT=Segoe UI, Arial]Ralink 802.11n Wireless Adapters[/FONT]
company: [FONT=Segoe UI, Arial]Ralink Technology, Corp.[/FONT]
description: Ralink 802.11 Wireless Adapter Driver
Bug check description: This indicates that an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
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: netr28.sys (Ralink 802.11 Wireless Adapter Driver, Ralink Technology, Corp.).
Google query: [FONT=Segoe UI, Arial]netr28.sys Ralink Technology, Corp. CLOCK_WATCHDOG_TIMEOUT[/FONT]


[/FONT]

[FONT=Segoe UI, Arial]On Sun 04-12-2011 12:33:04 GMT your computer crashed
crash dump file: C:\Windows\Minidump\101008-13494-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]dxgkrnl.sys[/FONT] (dxgkrnl+0x8CC26)
Bugcheck code: 0x116 (0xFFFFFFFF887FC510, 0xFFFFFFFF8FE344CE, 0x0, 0x2)
Error: [FONT=Segoe UI, Arial]VIDEO_TDR_ERROR[/FONT]
file path: C:\Windows\system32\drivers\dxgkrnl.sys
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: DirectX Graphics Kernel
Bug check description: This indicates that an attempt to reset the display driver and recover from a timeout failed.
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.
[/FONT]

[FONT=Segoe UI, Arial]On Mon 13-10-2008 22:48:51 GMT your computer crashed
crash dump file: C:\Windows\Minidump\101408-12854-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]dxgkrnl.sys[/FONT] (dxgkrnl+0x8CC26)
Bugcheck code: 0x116 (0xFFFFFFFF9C12F510, 0xFFFFFFFF8E0364CE, 0x0, 0x2)
Error: [FONT=Segoe UI, Arial]VIDEO_TDR_ERROR[/FONT]
file path: C:\Windows\system32\drivers\dxgkrnl.sys
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: DirectX Graphics Kernel
Bug check description: This indicates that an attempt to reset the display driver and recover from a timeout failed.
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.
[/FONT]

[FONT=Segoe UI, Arial]On Mon 13-10-2008 22:46:49 GMT your computer crashed
crash dump file: C:\Windows\Minidump\101408-13665-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]dxgkrnl.sys[/FONT] (dxgkrnl+0x8CC26)
Bugcheck code: 0x116 (0xFFFFFFFF856FD008, 0xFFFFFFFF8E2234CE, 0x0, 0x2)
Error: [FONT=Segoe UI, Arial]VIDEO_TDR_ERROR[/FONT]
file path: C:\Windows\system32\drivers\dxgkrnl.sys
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: DirectX Graphics Kernel
Bug check description: This indicates that an attempt to reset the display driver and recover from a timeout failed.
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.
[/FONT]

[FONT=Segoe UI, Arial]On Fri 10-10-2008 00:12:17 GMT your computer crashed
crash dump file: C:\Windows\Minidump\101408-9469-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]dxgkrnl.sys[/FONT] (dxgkrnl+0x8CC26)
Bugcheck code: 0x116 (0xFFFFFFFF84955008, 0xFFFFFFFF8D8064CE, 0x0, 0x2)
Error: [FONT=Segoe UI, Arial]VIDEO_TDR_ERROR[/FONT]
file path: C:\Windows\system32\drivers\dxgkrnl.sys
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: DirectX Graphics Kernel
Bug check description: This indicates that an attempt to reset the display driver and recover from a timeout failed.
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.
[/FONT]

[FONT=Segoe UI, Arial]On Fri 10-10-2008 00:01:05 GMT your computer crashed
crash dump file: C:\Windows\Minidump\101008-22947-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]dxgkrnl.sys[/FONT] (dxgkrnl+0x8CC26)
Bugcheck code: 0x116 (0xFFFFFFFF84B46008, 0xFFFFFFFF8DA194CE, 0x0, 0x2)
Error: [FONT=Segoe UI, Arial]VIDEO_TDR_ERROR[/FONT]
file path: C:\Windows\system32\drivers\dxgkrnl.sys
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: DirectX Graphics Kernel
Bug check description: This indicates that an attempt to reset the display driver and recover from a timeout failed.
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.
[/FONT]

[FONT=Segoe UI, Arial]On Thu 09-10-2008 23:08:59 GMT your computer crashed
crash dump file: C:\Windows\Minidump\101008-15100-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]cng.sys[/FONT] (cng+0x615E)
Bugcheck code: 0x101 (0x31, 0x0, 0xFFFFFFFF807C2120, 0x1)
Error: [FONT=Segoe UI, Arial]CLOCK_WATCHDOG_TIMEOUT[/FONT]
file path: C:\Windows\system32\drivers\cng.sys
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: Kernel Cryptography, Next Generation
Bug check description: This indicates that an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
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.
[/FONT]

 

[panais]

Download and install the new version of Driver Sweeper.


Download the most recent software\driver for your ati AMD Graphics Drivers & Software.

Uninstall ati software\driver,restart in safe mode,run driver sweeper,choose only AMD-Display andclean,restart in normal mode.


Install the new ati software\driver,restart.

Update DirectX.


Read very carefully the instructions and run http://www.sevenforums.com/tutorials/160729-nvidia-amd-video-card-test-occt.html post here the results.




Run http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html
Leave it to run overnight.



Finish and post back.

 

[flesk]

So far, i´ve updated the directx and the driver, as you said so, although it was the same version.

It says something about, it cant run "gpu memtest" cause I need at least GF8 or higher...

It is now running a gpu test for an hour..


Memtest; I do not rely on the system running for a whole night, an hour tops. But i´ll give it a try, is there a log in the memtest if it shuts down?

 

[flesk]

here´s the result of the gpu test, as mentioned before, Im not allowed to do the gpu memtest...

 

[panais]

The http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html is for the system memory ram and not for the gpu.

Download http://memtest.org/download/4.20/memtest86+-4.20.iso.gz burn it in cd,restart,boot from cd and let the the memtest to run.

It will check the memory ram sticks.

 

[flesk]

Thank you for the help so far.
memtest;
I have ran the test with 14 passes, no errors.




This I cant run, because of the limitation of the video card, or so it says...

Test 2: Video Memory Test
OCCT GPU Memtest, based on Nvidia CUDA runs a Memtest-like test on your GPU Memory. It is aimed at detecting manufacturing errors on the GPU memory



NOW, what to do???

 

[panais]

Did you had\have again any new crash\bsod?

 

[flesk]

it still crashes.
Is the problem only related to the video card?
Would it be solved, if I buy a new one??

I think one of the crashes was related to the cpu..

 

[panais]

Upload the new minidmps.

 

[flesk]

Here it is.
I didn´t have a BSOD, they do accour at random times, but i provocked it to "hang" until I restarted. That by playing a youtube video. At 3 attempts, the longest "survivor" did 30 seconds, and then it "crashed".

 

[writhziden]

For testing purposes, please uninstall Kaspersky and run Microsoft Security Essentials

I am unable to read the dmp files... This is what I get in case anyone else out there can help me out with this problem:



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


Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\flesk\Windows_NT6_BSOD_jcgriff2\120711-12932-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16841.x86fre.win7_gdr.110622-1503
Machine Name:
Kernel base = 0x82a51000 PsLoadedModuleList = 0x82b99830
Debug session time: Wed Dec 7 16:50:40.847 2011 (UTC - 7:00)
System Uptime: 0 days 0:01:06.549
Loading Kernel Symbols
...............................................................
................................................................
..............
Loading User Symbols
Loading unloaded module list
.....

And then it just stops...

 

[panais]

Here it is.
I didn´t have a BSOD, they do accour at random times, but i provocked it to "hang" until I restarted. That by playing a youtube video. At 3 attempts, the longest "survivor" did 30 seconds, and then it "crashed".

You have the error STOP 0x101: CLOCK_WATCHDOG_TIMEOUT

 

[flesk]

What you're looking for will be in one of the following categories:

a) BIOS bug
b) a driver whose activity is causing the target processor to lock up
c) a hardware defect (temperature, voltage, dust, RFI, outright borkedness...)
- H2SO4

a) updated to (newest) version 1.5 from 2008-10-10
b) the system hangs in a clean windows install, but also with all drivers updated.
c) NOT temperature... NOT dust.... the rest I do not know about...
cant find a "tlb" in the BIOS.


What to do from here ?
Thank you so far

 

[writhziden]

Could you replace the graphics card with a friend's card or another card you own? This would determine whether it is the graphics card or another hardware issue.

 

[writhziden]

Any update on your stability crashes? Let us know if you still need help.

 

[flesk]

Well, sorry for the late response.



I have now bought a new GFX;
ASUS ENGTX560 TI DC2 TOP/2DI/2GD5

I changed the case to coolermaster haf932 with ekstra 20mm intake


Now in Battlefield 3 the game still freezes, but it doesn´t make the entire system shut down. I can go the task manager and shut down the game, no system faillure !



Company of heroes shut down twice in a row with a "error" that I cant see, cause I have to "kill" it in task manager....

Any other suggestions...

 

[writhziden]

Check RAM compatibility:

• Download and install CPU-Z and Upload screenshots of the CPU, Mainboard, Memory, and SPD tabs. In the SPD tab, upload an image of each slot.

Also, please fill in your system specs in your profile and not in a post in this thread: http://www.sevenforums.com/tutorials/180324-system-info-see-your-system-specs.html

 

[flesk]

Thank you for the response.
I have filled out the blanks.
Here is the screenshots.

Best regards
Flemming