BSODs all the times (During Boot, during Windows, IRQL, Driver IRQL)

[Kangaxx1980]

System:
7 Ultimate x64 SP1
Pentium D 2,80
GeForce 7600 GT

Hi guys,
I don't know what to do.
Since yesterday I am encountering BSODs all the time.
I did a SFC but it says some files cannot be repaired. Which ones? I dunno. The result file is somewhat uninformative. (Perhaps one of you guys is able to work with it -> CBS.log (11,55 MB) - uploaded.to )
I did a memtest, no failures.
The only recent new driver I installed was NVDIA's newest graphics driver. This I uninstalled and installed an older one. But nothing.
The BSODs are different every time. Sometime IRQL, sometimes driver IRQL (sataport.sys, ntfs.sys and so on) and other things but the BlueScreenViewer says that everything was caused by ntoskrnl.exe.
Within the zip file you'll find every Minidump. Can't create System Health report because of Windows crashing about instantly.
Help would be appreciated.

 

[panais]

Hi Kangaxx1980 welcome to SF


Update your Realtek Ethernet NIC software\driver


Realtek



Finish with this step and post back with any results.

 

[Kangaxx1980]

Thank you.

The lastest driver (6.111) should allready be installed.
Realtek

 

[usasma]

NOTE: I have severe eye problems. If I do not respond to your postings, please PM another staff member for assistance.

NOTE: Please provide the following information for a more detailed response: http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html

I'd have to wonder about a hardware failure (because of the crash in the perfmon report and your description of the errors)
Try this free diagnostic: HD Diagnostic (read the details at the link) - Test ALL of the hard drives.

20 memory dumps over the last 2 days - WOW!!!
Interestingly, they're all STOP 0xA - except for 2 STOP 0x50, so all are IRQL errors (makes hardware less likely)
But, there's at least 4 different causes blamed, so hardware is a possibility IMO.

The only significantly older driver is your Realtek Network card (the driver dates from 2008). I'd suggest updating it to the latest Win7 compatible version. I'd also update the other drivers listed here:
OLDER DRIVERS PRESENT IN THE DUMP FILES
- Create a System Restore Point prior to doing any of this. DO NOT mess with the drivers themselves - leave the Windows\System32\drivers directory alone unless we specifically direct you to it!
- Please update these drivers from the device manufacturer's website - or uninstall them from your system. Reference links are included below.
- DO NOT use Windows Update or the Update Drivers function of Device Manager.
- Please feel free to post back about any drivers that you are having difficulty locating.
- Windows Update exceptions may be noted below for Windows drivers:

[font=lucida console]
vmbus.sys                   Sat Nov 20 04:57:29 2010 (4CE79B89)
winhv.sys                   Sat Nov 20 04:20:02 2010 (4CE792C2)
amdxata.sys                 Fri Mar 19 12:18:18 2010 (4BA3A3CA)
ladfGSCamd64.sys            Mon Apr 11 14:41:01 2011 (4DA34B3D) - Logitech LADF Capture Filter Drive (?Gamepanel?)
RTKVAC64.SYS                Thu Jun 18 15:37:20 2009 (4A3A9770)
LGBusEnum.sys               Mon Nov 23 20:36:48 2009 (4B0B38B0)
[LEFT][B][COLOR=Red]Rtnic64.sys                 Fri May 30 11:12:23 2008 (48401957)[/COLOR][/B]
[/LEFT]
TuneUpUtilitiesDriver64.sys Thu Sep 17 07:54:52 2009 (4AB2238C)
LGVirHid.sys                Mon Nov 23 20:36:48 2009 (4B0B38B0)
NisDrvWFP.sys               Wed Apr 06 16:08:53 2011 (4D9CC855)
nvlddmkm.sys                Wed Aug 03 05:08:32 2011 (4E391010)
drmkaud.sys                 Mon Jul 13 20:06:16 2009 (4A5BCBF8)
MpNWMon.sys                 Wed Apr 06 16:07:23 2011 (4D9CC7FB)
MpFilter.sys                Wed Apr 06 16:07:29 2011 (4D9CC801)
SDHookDrv64.sys             Thu Jan 07 10:14:06 2010 (4B45FA3E) - Spybot-S&D 2 Hook Driver
[/font]

http://www.carrona.org/dvrref.html#vmbus.sys
http://www.carrona.org/dvrref.html#winhv.sys
http://www.carrona.org/dvrref.html#amdxata.sys
http://www.carrona.org/dvrref.html#RTKVAC64.SYS
http://www.carrona.org/dvrref.html#LGBusEnum.sys
http://www.carrona.org/dvrref.html#Rtnic64.sys
http://www.carrona.org/dvrref.html#TuneUpUtilitiesDriver64.sys
http://www.carrona.org/dvrref.html#LGVirHid.sys
http://www.carrona.org/dvrref.html#NisDrvWFP.sys
http://www.carrona.org/dvrref.html#nvlddmkm.sys
http://www.carrona.org/dvrref.html#drmkaud.sys
http://www.carrona.org/dvrref.html#MpNWMon.sys
http://www.carrona.org/dvrref.html#MpFilter.sys

If this doesn't stop the BSOD's (and the hard drive passes the diagnostic test), then please run Driver Verifier according to these directions:

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff 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).

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 "Special Pool" and "Low Resource Simulation" and click "Next"
NOTE: You can use Low Resource Simulation if you'd like. From my limited experimentation it makes the BSOD's come faster.
- 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).

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

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.

If that doesn't work, post back and we'll have to see about fixing the registry entry off-line:

Delete these registry keys to stop Driver Verifier from loading (works in XP, Vista, Win7):
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDrivers
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDriverLevel

More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users

BSOD BUGCHECK SUMMARY

[font=lucida console]
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\101111-23187-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Tue Oct 11 02:48:10.196 2011 (UTC - 4:00)
System Uptime: 0 days 0:00:48.883
Probably caused by : win32k.sys ( win32k!NtGdiGetDIBitsInternal+320 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  dwm.exe
FAILURE_BUCKET_ID:  X64_0xA_win32k!NtGdiGetDIBitsInternal+320
Bugcheck code 0000000A
Arguments 00000000`00000010 00000000`00000002 00000000`00000001 fffff800`02f00f00
BiosVersion = 080012 
BiosReleaseDate = 06/21/2006
CPUID:        "Intel(R) Pentium(R) D CPU 2.80GHz"
MaxSpeed:     2800
CurrentSpeed: 2800
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\101111-24140-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Tue Oct 11 02:44:09.718 2011 (UTC - 4:00)
System Uptime: 0 days 0:00:09.406
Probably caused by : Ntfs.sys ( Ntfs!NtfsFastQueryStdInfo+55 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x50_Ntfs!NtfsFastQueryStdInfo+55
Bugcheck code 00000050
Arguments ffffe9e0`014c6507 00000000`00000001 fffff880`012a5b85 00000000`00000007
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\101011-22484-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Mon Oct 10 17:15:15.515 2011 (UTC - 4:00)
System Uptime: 0 days 0:26:14.218
Probably caused by : memory_corruption ( nt!MiReplenishPageSlist+c0 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  OptimizationWi
FAILURE_BUCKET_ID:  X64_0xA_nt!MiReplenishPageSlist+c0
Bugcheck code 0000000A
Arguments fffffa7f`ffffffe0 00000000`00000002 00000000`00000001 fffff800`02ec0f00
BiosVersion = 080012 
BiosReleaseDate = 06/21/2006
CPUID:        "Intel(R) Pentium(R) D CPU 2.80GHz"
MaxSpeed:     2800
CurrentSpeed: 2800
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\101011-23234-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Mon Oct 10 16:32:50.164 2011 (UTC - 4:00)
System Uptime: 0 days 0:05:04.867
Probably caused by : ntkrnlmp.exe ( nt!KxWaitForLockOwnerShip+12 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xA_nt!KxWaitForLockOwnerShip+12
Bugcheck code 0000000A
Arguments 00000000`0000ffdf 00000000`00000002 00000000`00000001 fffff800`02f023a2
BiosVersion = 080012 
BiosReleaseDate = 06/21/2006
CPUID:        "Intel(R) Pentium(R) D CPU 2.80GHz"
MaxSpeed:     2800
CurrentSpeed: 2800
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\101011-22937-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Mon Oct 10 13:21:58.861 2011 (UTC - 4:00)
System Uptime: 0 days 0:04:56.580
Probably caused by : memory_corruption ( nt!MiReplenishPageSlist+c0 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  MsMpEng.exe
FAILURE_BUCKET_ID:  X64_0xA_nt!MiReplenishPageSlist+c0
Bugcheck code 0000000A
Arguments fffffa7f`ffffffe0 00000000`00000002 00000000`00000001 fffff800`02eaef00
BiosVersion = 080012 
BiosReleaseDate = 06/21/2006
CPUID:        "Intel(R) Pentium(R) D CPU 2.80GHz"
MaxSpeed:     2800
CurrentSpeed: 2800
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\101011-23562-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Mon Oct 10 13:16:06.984 2011 (UTC - 4:00)
System Uptime: 0 days 0:07:06.687
Probably caused by : ntkrnlmp.exe ( nt!KxWaitForLockOwnerShip+12 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xA_nt!KxWaitForLockOwnerShip+12
Bugcheck code 0000000A
Arguments 00000000`00000020 00000000`00000002 00000000`00000001 fffff800`02f0f3a2
BiosVersion = 080012 
BiosReleaseDate = 06/21/2006
CPUID:        "Intel(R) Pentium(R) D CPU 2.80GHz"
MaxSpeed:     2800
CurrentSpeed: 2800
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\101011-30234-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Mon Oct 10 12:14:10.674 2011 (UTC - 4:00)
System Uptime: 0 days 0:04:12.377
Probably caused by : memory_corruption ( nt!MiReplenishPageSlist+c0 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  setup.exe
FAILURE_BUCKET_ID:  X64_0xA_nt!MiReplenishPageSlist+c0
Bugcheck code 0000000A
Arguments 00000000`00000010 00000000`00000002 00000000`00000001 fffff800`02f05f00
BiosVersion = 080012 
BiosReleaseDate = 06/21/2006
CPUID:        "Intel(R) Pentium(R) D CPU 2.80GHz"
MaxSpeed:     2800
CurrentSpeed: 2800
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\101011-28406-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Mon Oct 10 12:09:04.401 2011 (UTC - 4:00)
System Uptime: 0 days 0:09:37.120
Probably caused by : memory_corruption ( nt!MiReplenishPageSlist+c0 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  LCore.exe
FAILURE_BUCKET_ID:  X64_0xA_nt!MiReplenishPageSlist+c0
Bugcheck code 0000000A
Arguments 00000000`00000010 00000000`00000002 00000000`00000001 fffff800`02ea2f00
BiosVersion = 080012 
BiosReleaseDate = 06/21/2006
CPUID:        "Intel(R) Pentium(R) D CPU 2.80GHz"
MaxSpeed:     2800
CurrentSpeed: 2800
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\101011-32328-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Mon Oct 10 11:57:50.234 2011 (UTC - 4:00)
System Uptime: 0 days 0:10:07.937
Probably caused by : ntkrnlmp.exe ( nt!KxWaitForLockOwnerShip+12 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xA_nt!KxWaitForLockOwnerShip+12
Bugcheck code 0000000A
Arguments 00000000`0000ff5f 00000000`00000002 00000000`00000001 fffff800`02f033a2
BiosVersion = 080012 
BiosReleaseDate = 06/21/2006
CPUID:        "Intel(R) Pentium(R) D CPU 2.80GHz"
MaxSpeed:     2800
CurrentSpeed: 2800
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\101011-16000-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Mon Oct 10 08:13:45.360 2011 (UTC - 4:00)
System Uptime: 0 days 0:09:05.860
Probably caused by : memory_corruption ( nt!MiReplenishPageSlist+c0 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xA_nt!MiReplenishPageSlist+c0
Bugcheck code 0000000A
Arguments fffffa7f`ffffffe0 00000000`00000002 00000000`00000001 fffff800`02307f00
BiosVersion = 080012 
BiosReleaseDate = 06/21/2006
CPUID:        "Intel(R) Pentium(R) D CPU 2.80GHz"
MaxSpeed:     2800
CurrentSpeed: 2800
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\101011-18062-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Mon Oct 10 08:03:46.746 2011 (UTC - 4:00)
System Uptime: 0 days 0:13:26.433
Probably caused by : memory_corruption ( nt!MiReplenishPageSlist+c0 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  dwm.exe
FAILURE_BUCKET_ID:  X64_0xA_nt!MiReplenishPageSlist+c0
Bugcheck code 0000000A
Arguments 00000000`00000010 00000000`00000002 00000000`00000001 fffff800`02f08f00
BiosVersion = 080012 
BiosReleaseDate = 06/21/2006
CPUID:        "Intel(R) Pentium(R) D CPU 2.80GHz"
MaxSpeed:     2800
CurrentSpeed: 2800
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\101011-25953-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Mon Oct 10 07:31:57.189 2011 (UTC - 4:00)
System Uptime: 0 days 0:19:16.892
Probably caused by : ntkrnlmp.exe ( nt!KxWaitForLockOwnerShip+12 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xA_nt!KxWaitForLockOwnerShip+12
Bugcheck code 0000000A
Arguments 00000000`000000a0 00000000`00000002 00000000`00000001 fffff800`02b153a2
BiosVersion = 080012 
BiosReleaseDate = 06/21/2006
CPUID:        "Intel(R) Pentium(R) D CPU 2.80GHz"
MaxSpeed:     2800
CurrentSpeed: 2800
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\101011-17640-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Mon Oct 10 06:29:36.651 2011 (UTC - 4:00)
System Uptime: 0 days 0:07:03.370
Probably caused by : memory_corruption ( nt!MiReplenishPageSlist+c0 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  firefox.exe
FAILURE_BUCKET_ID:  X64_0xA_nt!MiReplenishPageSlist+c0
Bugcheck code 0000000A
Arguments 00000000`00000010 00000000`00000002 00000000`00000001 fffff800`02abef00
BiosVersion = 080012 
BiosReleaseDate = 06/21/2006
CPUID:        "Intel(R) Pentium(R) D CPU 2.80GHz"
MaxSpeed:     2800
CurrentSpeed: 2800
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\101011-16796-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Mon Oct 10 06:18:06.175 2011 (UTC - 4:00)
System Uptime: 0 days 0:11:43.910
Probably caused by : memory_corruption ( nt!MiInsertPageInFreeOrZeroedList+54c )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xA_nt!MiInsertPageInFreeOrZeroedList+54c
Bugcheck code 0000000A
Arguments fffffa7f`ffffffd0 00000000`00000002 00000000`00000001 fffff800`02a9c25c
BiosVersion = 080012 
BiosReleaseDate = 06/21/2006
CPUID:        "Intel(R) Pentium(R) D CPU 2.80GHz"
MaxSpeed:     2800
CurrentSpeed: 2800
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\101011-17312-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Mon Oct 10 05:50:07.803 2011 (UTC - 4:00)
System Uptime: 0 days 0:01:46.522
Probably caused by : win32k.sys ( win32k!memset+b0 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  explorer.exe
FAILURE_BUCKET_ID:  X64_0xA_win32k!memset+b0
Bugcheck code 0000000A
Arguments fffffa7f`ffffffe0 00000000`00000002 00000000`00000001 fffff800`02abbf00
BiosVersion = 080012 
BiosReleaseDate = 06/21/2006
CPUID:        "Intel(R) Pentium(R) D CPU 2.80GHz"
MaxSpeed:     2800
CurrentSpeed: 2800
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\101011-18281-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Mon Oct 10 04:10:09.675 2011 (UTC - 4:00)
System Uptime: 0 days 0:14:05.394
Probably caused by : win32k.sys ( win32k!NtGdiDdDDICreateDCFromMemory+1f4 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  thunderbird.ex
FAILURE_BUCKET_ID:  X64_0xA_win32k!NtGdiDdDDICreateDCFromMemory+1f4
Bugcheck code 0000000A
Arguments 00000000`00000010 00000000`00000002 00000000`00000001 fffff800`02af1f00
BiosVersion = 080012 
BiosReleaseDate = 06/21/2006
CPUID:        "Intel(R) Pentium(R) D CPU 2.80GHz"
MaxSpeed:     2800
CurrentSpeed: 2800
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\101011-31796-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Mon Oct 10 03:32:04.056 2011 (UTC - 4:00)
System Uptime: 0 days 0:05:34.759
Probably caused by : memory_corruption ( nt!MiReplenishPageSlist+c0 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  thunderbird.ex
FAILURE_BUCKET_ID:  X64_0xA_nt!MiReplenishPageSlist+c0
Bugcheck code 0000000A
Arguments fffffa7f`ffffffe0 00000000`00000002 00000000`00000001 fffff800`02b07f00
BiosVersion = 080012 
BiosReleaseDate = 06/21/2006
CPUID:        "Intel(R) Pentium(R) D CPU 2.80GHz"
MaxSpeed:     2800
CurrentSpeed: 2800
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\101011-18718-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Mon Oct 10 03:25:21.504 2011 (UTC - 4:00)
System Uptime: 0 days 0:09:37.223
Probably caused by : ntkrnlmp.exe ( nt!KiChainedDispatch+93 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x50_nt!KiChainedDispatch+93
Bugcheck code 00000050
Arguments fffff800`02053618 00000000`00000000 fffff800`02a8c5c3 00000000`00000000
BiosVersion = 080012 
BiosReleaseDate = 06/21/2006
CPUID:        "Intel(R) Pentium(R) D CPU 2.80GHz"
MaxSpeed:     2800
CurrentSpeed: 2800
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\101011-17421-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Mon Oct 10 03:06:03.907 2011 (UTC - 4:00)
System Uptime: 0 days 0:11:33.438
Probably caused by : ntkrnlmp.exe ( nt!KxWaitForLockOwnerShip+12 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xA_nt!KxWaitForLockOwnerShip+12
Bugcheck code 0000000A
Arguments 00000000`0000ffff 00000000`00000002 00000000`00000001 fffff800`01d153a2
BiosVersion = 080012 
BiosReleaseDate = 06/21/2006
CPUID:        "Intel(R) Pentium(R) D CPU 2.80GHz"
MaxSpeed:     2800
CurrentSpeed: 2800
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\101011-15593-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Mon Oct 10 02:51:37.189 2011 (UTC - 4:00)
System Uptime: 0 days 0:01:06.923
Probably caused by : memory_corruption ( nt!MmZeroPageThread+3c4 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xA_nt!MmZeroPageThread+3c4
Bugcheck code 0000000A
Arguments fffffa7f`ffd00010 00000000`00000002 00000000`00000001 fffff800`02a4a841
BiosVersion = 080012 
BiosReleaseDate = 06/21/2006
CPUID:        "Intel(R) Pentium(R) D CPU 2.80GHz"
MaxSpeed:     2800
CurrentSpeed: 2800
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
  [/font]

 

[Kangaxx1980]

I updated the network driver -> BSOD

I was able do generate a system health report. See attachment.

Driver scanner only found:
HID Mouse 6.1.7600.16385 -> seems to be up to date, but scanner tells me to update to 6.00.0.005 ^^
GeForce -> up to date, the most recent driver would be a beta (this I am going to install now) -> BSOD

I was able to create a Windows_NT6_BSOD_jcgriff2 folder before my system crashed again.

Now I am going to do the HDD testing. This should take a while.

 

[usasma]

Do you have a Logitech Gamepanel? I've seen errors like this on another system that had one - but there was no definite blame put on the Gamepanel. Now that I find 2 systems with it, I'd wonder if this device is starting to cause problems.

In order to rule it out, please uninstall the software and remove the device from the system.

Other free diagnostic/stress tests listed below:

H/W Diagnostics:
Please start by running these bootable hardware diagnostics:
Memory Diagnostics (read the details at the link)
HD Diagnostic (read the details at the link) - Test ALL of the hard drives.

Also, please run one of these free, independent online malware scans to ensure that your current protection hasn't been compromised: Free Online AntiMalware Resources (read the details at the link)
There are also free, bootable antivirus disks at this link: Free Online AntiMalware Resources - Bootable Disks

Then, if the above tests pass, I'd try these free stress tests:

FurMark download site: FurMark: VGA Stress Test, Graphics Card and GPU Stability Test, Burn-in Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net
FurMark Setup:
- If you have more than one GPU, select Multi-GPU during setup
- In the Run mode box, select "Stability Test" and "Log GPU Temperature"
Click "Go" to start the test
- Run the test until the GPU temperature maxes out - or until you start having problems (whichever comes first).
NOTE: Set the alarm to go off at 90ºC. Then watch the system from that point on. If the system doesn't display a temperature, watch it constantly and turn it off at the first sign of video problems. DO NOT leave it it unmonitored, it can DAMAGE your video card!!!
If the temperature gets above 100ºC, quit the test - the video card is overheating.
- Click "Quit" to exit

Prime95 download site: http://www.mersenne.org/freesoft/
Prime95 Setup:
- extract the contents of the zip file to a location of your choice
- double click on the executable file
- select "Just stress testing"
- select the "Blend" test. If you've already run MemTest overnight please run the "Small FFTs" test instead. (run all 3 if you find a problem and note how long it takes to error out with each)
- "Number of torture test threads to run" should equal the number of CPU's times 2 (if you're using hyperthreading).
The easiest way to figure this out is to go to Task Manager...Performance tab - and see the number of boxes under CPU Usage History
Then run the test for 6 to 24 hours - or until you get errors (whichever comes first).
Monitor the CPU temperature and DON'T let it exceed 85ºC. If it does, then you probably have a CPU cooling problem.
This won't necessarily crash the system - but check the output in the test window for errors.
The Test selection box and the stress.txt file describes what components that the program stresses.
More details on the use of this test: Torture test your CPU with Prime95

More Video Stress Tests:
1. Thanks to VirGnarus for finding this test: https://simtk.org/home/memtest
2. Two other video stress tests (may be more stressful than FurMark):
NOTE: I have had reports that some ISP's will block this website
Video Memory stress Test - МИРNVIDIA / Утилиты / VMT
Artifact Locator - МИРNVIDIA / Утилиты / Artifact Locator
Sorry, but I don't read the language that this website is made in.
3. Another interesting test that came to my attention: Download - OCCT Website english
USE AT YOUR OWN RISK - the program doesn't have a whole bunch of safety features to protect you from yourself!

CPU Stress Tests:
Only need to run 1 or 2 of the tests under most circumstances. I haven't used any of the tests myself, so I listed all that I was able to find.
- http://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&DwnldID=19182&lang=eng
- 7Byte : Hot CPU Tester Pro
- 7Byte : BurnIn64
- CPU Stress test - Overclock.net - Overclocking.net
- Fossil Free Online CPU Load or Stress Test.
- CPU Stability Test description, System Resources Tune-Up. Downloads List By All Time Popularity | PCWorld | PCWorld
- CPU Stress test - Overclock.net - Overclocking.net
- |MG| CPU Stability Test 6.0 Download
- LinX - A simple Linpack interface
- the test(s) suggested at this link are bootable: Headless CPU Stress Testing - Tech Support Forum

 

[usasma]

Driver scanners aren't (IMO) reliable - being only as good as those who programmed them and did the research for the updated drivers. I've been doing driver research for several years ( Driver Reference ) and still am amazed at the difficulties that this presents. Also, I don't do any programming - but I find that the research alone occupies a large amount of time - adding programming to it would leave no room for me to have a life!

So, I recommend this process:
- check driver dates from the BSOD report
- research each drive that's older - but this depends on how often the manufacturer releases updates.
- continue to research drivers up to and including those from 2011 - to see if there are newer versions available
- finally, those that don't have newer versions available may still have issues - so removing them and installing a fresh copy can help solve problems also.

 

[Kangaxx1980]

HDD testing still in progress.

Why should I use the verifier to just scan non Microsoft drivers? SATAPORT.SYS and NTFS.SYS who are to blame for some BSODs according to the bluescreen itself are Microsoft drivers?

I can't disconnect the game panel. It's part of my keyboard. G15. And without the software my G35 won't work, too.
It should have nothing to do with the BSODs. The software was installed weeks ago, but the BSODs just recently occured.

I am not able to find any information on drivers within the dumps. I neither know how to read them properly nor what to look for.

 

[usasma]

Please read Windows Internals, 5th Edition to see why you should test non-Microsoft drivers. In short, BSOD's are rarely caused by Windows drivers - and most often by 3rd party drivers. When a Microsoft driver is blamed, we assume that it's another cause that came in and then caused the Microsoft driver to crash.

In your example, both of the drivers are related to your storage sub-system. IME most storage system errors are caused by failing HDD's - although this can also be due to a bad cable, a bad hard drive controller on the motherboard, or bad/corrupted drivers for any of the devices that affect these devices.

In addition to scanning all 3rd party drivers (which rules out the 3rd party programs) you also tend to rule out/in hardware problems (and compatibility/malware issues) - which are more common than Windows driver problems also. If the BSOD's (with Driver Verifier running on all 3rd party drivers) continue without creating Driver Verifier Enabled Memory Dumps, then it's presumed that there's hardware issues, compatibility issues, malware issues, or Windows issues (in that order).

I mentioned the GamePanel simply because I'd seen another system that had BSOD issues and it also had a GamePanel installed. The drivers weren't in my database ( Driver Reference ), so I have to wonder about them until we've seen enough without problems.

Just because a driver was installed and didn't give problems back then, doesn't mean that there won't be problems in the future. If this was the case, then systems would never break down. A system is a dynamic creature, constantly changing and updating - and these changes can be cumulative and can cause BSOD's on systems that were functioning properly for a long time.

If you have another keyboard to test with, try that. If not, then download a fresh copy of the Logitech software, uninstall the current software and install the fresh copy. That will tend to overwrite any corruptions that may be present. FYI - this is just a guess on my part. I do this stuff a lot, and my hunches have paid off in the past. This won't hurt your system - and it may help. Your choice.

I posted a list of drivers that came up from the memory dumps - so you wouldn't have to figure all of this out. And, jsut below that list, is a list of links to information about those drivers - so that you can attempt to find updates for them. If you can't find updates, then post back with the names of the drivers and we'll see what we can do about finding them for you.

 

[Kangaxx1980]

Summary until now:
MemTest x86 without result
Maxtor PowerMax Full Read Scan without result
SFC had a few errors but I don't know which ones (please look into the ZIP uploaded at UL.to in the first post)

VMBus.sys: due to list on caronna.org up to date
winhv.sys: due to list on caronna.org up to date
amdxdata.sys: newer than the driver on the list on caronna.org
ladfGSCamd64.sys: Part of the Logitech driver software for G15 & G35. I am going to uninstall it and reinstall the latest version after a reboot.
RTKVAC64.SYS: due to list on caronna.org up to date
LGBusEnum.sys: due to list on caronna.org up to date (Part of Logitech software. Will be reinstalled, too)
Rtnic64.sys: Up to date since this afternoon
TuneUpUtilitiesDriver64.sys: Part of the beta software TuneUp Utilities. I am going to uninstall and reinstall the latest non beta after a reboot.
LGVirHid.sys: due to list on caronna.org up to date (Part of Logitech software. Will be reinstalled, too)
NisDrvWFP.sys: newer than the driver on the list on caronna.org
nvlddmkm.sys: NVIDIA driver. Up to date since this afternoon.
drmkaud.sys: Should be up to date because due to caronna.org updates are provided through Windows updates.
MpNWMon.sys: Part of Microsoft Security Essentials. Should be up to date because due to caronna.org updates are provided through Windows updates.
MpFilter.sys: Part of Microsoft Security Essentials. Should be up to date because due to caronna.org updates are provided through Windows updates.
SDHookDrv64.sys: Part of Spybot Search & Destroy 2 (Beta). I am going to uninstall it and install Spybot 1 (there is no driver involved within the old version).

I am going to uninstall the Logitech, Tuneup and Spybot software now and the use the verifier.

 

[Kangaxx1980]

Yesterday night I had an idea. A weeks ago I changed my power supply unit to a smaller one because my normal one did break.
I thought that perhaps I have to less power to use my PC propperly so I borrowed me another big PSU. My Windows ran the whole night, without problems. Prime did not find any error.
BUT: this morning I wanted to use my PC as normal and now again. BSOD over BSOD.
No chance to get the verifier working.

Now I am trying to do another virus scan. This time I use a Knoppix Live OS. This should be able to find everything.

 

[usasma]

Are the BSOD's happening with the old (weak) PSU? If so, borrow the big PSU and see if it stops. If it does, then it's most likely the PSU that's the problem.

 

[Kangaxx1980]

As I said. Big PSU is on duty since yesterday. After an error free night my Windows is back to old unstable behavior.

Funny:
Using the recovery console from CD -> sometimes BSOD
Using Knoppix Live CD -> sometimes system freezes

Perhaps a hardware failure at all.
But what?
CPU test = negative
HDD test = negative
RAM test = negative

 

[usasma]

Run Driver Verifier according to these instructions for a minimum of 36 hours (computer operating time):

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff 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).

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 "Special Pool" and "Low Resource Simulation" and click "Next"
NOTE: You can use Low Resource Simulation if you'd like. From my limited experimentation it makes the BSOD's come faster.
- 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).

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

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.

If that doesn't work, post back and we'll have to see about fixing the registry entry off-line:

Delete these registry keys to stop Driver Verifier from loading (works in XP, Vista, Win7):
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDrivers
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDriverLevel

More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users

Check to make sure that nothing is overheating. Wait for it to freeze with the Knoppix, unplug from the wall and open the case. Hold onto metal of case while feeling around inside the case. DO NOT TOUCH anything - only get near it - it can burn you!

Also, plug in the system and make sure that the fans are all working and that the coolers are free of dust bunnies. Check the caps on the mobo to ensure that none of them have burst.

 

[Kangaxx1980]

As I said. No chance. I can't use windows atm because of BSODs.

 

[usasma]

Try this then...

Check to make sure that nothing is overheating. Wait for it to freeze with the Knoppix, unplug from the wall and open the case. Hold onto metal of case while feeling around inside the case. DO NOT TOUCH anything - only get near it - it can burn you!

Also, plug in the system and make sure that the fans are all working and that the coolers are free of dust bunnies. Check the caps on the mobo to ensure that none of them have burst.

 

[Kangaxx1980]

Nothing is more than warm.
All four fans are working.

 

[usasma]

Did you run malware scans as I suggested earlier? If so, and if they came out clean, then there's nothing else evident.
As such I'd have to suggest that you do the following:

For testing purposes, it's best to install Windows "clean".
This is, basically, installing it the way that Microsoft intended (using drivers from Windows Update).
This procedure is for Windows 7, Vista is similar (but has 2 service packs)

You will need your installation/recovery DVD(s) before you start. Once you wipe the hard drive there's no going back!!!

1. Backup all your data.
This will wipe everything off of your hard drive, so anything that you want to keep will need to be saved elsewhere.

2. Connect the system to the internet (if the system says disconnect from the Internet, then do so).
3. Use DBAN ( DBAN Download | Darik's Boot And Nuke ) or KillDisk ( Freeware Download Active@ KillDisk ) to wipe the entire hard drive (both are free). This will also delete any recovery partitions on the system - so the intallation/recovery DVD's are essential!!!
4. Install Windows by booting from the installation/recovery DVD - DO NOT tweak any settings!!!
5. Visit Windows Update and get all updates
6. Visit Windows Update and get Service Pack 1 (usually under Important Updates). Read these notes for installing SP1: Steps to follow before you install Windows 7 Service Pack 1 from the Microsoft Download Center
7. Visit Windows Update and get any other available updates
8. Check Device Manager for any unknown/disabled devices - if there are unknown/disabled devices, fix them with the latest drivers from the device manufacturer's website (not the PC Manufacturer)
9. Download, install, and update a free antivirus so you don't get infected while testing ( Free AntiVirus ).

If the problems persist, then the problem is most likely with your hardware.

CAVEAT: If you have an Asus motherboard, check the date on the C:\Windows\System32\driver\ASACPI.sys file. 2004/2005 is a problem, 2009,2010 is OK. Updates are available at the Asus support website.

 

[Kangaxx1980]

My system allways did crash before complete scan.
I did wipe the HDD = no malware atm.
My suggestion is that my mobo is broken. I got another one and now I am trying to install a system image from earlier this month. Perhaps the whole problem is solved now. I am going to inform you of the results later this day.

 

[Kangaxx1980]

It seems to be stable now. I am doing some more tests (stressing, malware, viruses) but it seem the source of all evil was really my mobo.