BSOD after installing Win7Home32, different errors.

flesk · 08 Dec 2011

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 · 08 Dec 2011

Hi.

https://www.sevenforums.com/crashes-d...tructions.html

flesk · 08 Dec 2011

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.

System Information (local)
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

Crash Dump Analysis
Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

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: cng.sys (cng+0x615E)
Bugcheck code: 0x101 (0x31, 0x0, 0xFFFFFFFF807C2120, 0x1)
Error: CLOCK_WATCHDOG_TIMEOUT
file path: C:\Windows\system32\drivers\cng.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
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.

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: netr28.sys (netr28+0xAB7C)
Bugcheck code: 0x101 (0x31, 0x0, 0xFFFFFFFF807C2120, 0x1)
Error: CLOCK_WATCHDOG_TIMEOUT
file path: C:\Windows\system32\drivers\netr28.sys
product: Ralink 802.11n Wireless Adapters
company: Ralink Technology, Corp.
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: netr28.sys Ralink Technology, Corp. CLOCK_WATCHDOG_TIMEOUT

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: dxgkrnl.sys (dxgkrnl+0x8CC26)
Bugcheck code: 0x116 (0xFFFFFFFF887FC510, 0xFFFFFFFF8FE344CE, 0x0, 0x2)
Error: VIDEO_TDR_ERROR
file path: C:\Windows\system32\drivers\dxgkrnl.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
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.

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: dxgkrnl.sys (dxgkrnl+0x8CC26)
Bugcheck code: 0x116 (0xFFFFFFFF9C12F510, 0xFFFFFFFF8E0364CE, 0x0, 0x2)
Error: VIDEO_TDR_ERROR
file path: C:\Windows\system32\drivers\dxgkrnl.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
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.

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: dxgkrnl.sys (dxgkrnl+0x8CC26)
Bugcheck code: 0x116 (0xFFFFFFFF856FD008, 0xFFFFFFFF8E2234CE, 0x0, 0x2)
Error: VIDEO_TDR_ERROR
file path: C:\Windows\system32\drivers\dxgkrnl.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
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.

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: dxgkrnl.sys (dxgkrnl+0x8CC26)
Bugcheck code: 0x116 (0xFFFFFFFF84955008, 0xFFFFFFFF8D8064CE, 0x0, 0x2)
Error: VIDEO_TDR_ERROR
file path: C:\Windows\system32\drivers\dxgkrnl.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
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.

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: dxgkrnl.sys (dxgkrnl+0x8CC26)
Bugcheck code: 0x116 (0xFFFFFFFF84B46008, 0xFFFFFFFF8DA194CE, 0x0, 0x2)
Error: VIDEO_TDR_ERROR
file path: C:\Windows\system32\drivers\dxgkrnl.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
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.

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: cng.sys (cng+0x615E)
Bugcheck code: 0x101 (0x31, 0x0, 0xFFFFFFFF807C2120, 0x1)
Error: CLOCK_WATCHDOG_TIMEOUT
file path: C:\Windows\system32\drivers\cng.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
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.

panais · 08 Dec 2011

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 https://www.sevenforums.com/tutorials/160729-nvidia-amd-video-card-test-occt.html post here the results.

Run RAM - Test with Memtest86+
Leave it to run overnight.

Finish and post back.

flesk · 08 Dec 2011

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 · 08 Dec 2011

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

panais · 08 Dec 2011

The RAM - Test with Memtest86+ 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 · 09 Dec 2011

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 · 09 Dec 2011

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

flesk · 10 Dec 2011

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