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: Bsod help

09 Nov 2010   #1
kennedy1

Windows 7 64 Bit
 
 
Bsod help

Hello,

I am consistently getting BSOD while using my computer. Never set off by any one thing, it seems to happen randomly, surfing Internet, scanning documents, typing in Open Office. Never really associated with one thing.

System Specs are as follows:
OS: Windows 7 64 Bit
Motherboard: MSI NF980-G65 AM3 NVIDIA nForce 980a SLI HDMI ATX AMD
Processor: AMD Phenom II X4 955 Black Edition Deneb 3.2GHz
Memory: 8gigs: G.SKILL 4GB (2 x 2GB) 240-Pin DDR3 SDRAM DDR3 1600 (PC3 12800)
Hard Drive: Western Digital Caviar Green WD10EADS 1TB 32MB Cache SATA 3.0Gb/s
GPU: SAPPHIRE Vapor-X Radeon HD 4870 2GB 256-bit GDDR5 PCI Express 2.0 x16 HDCP Ready CrossFireX

Any help is greatly appreciated this is driving me nuts!


My System SpecsSystem Spec
09 Nov 2010   #2
usasma
Microsoft MVP

 
 

I suggest starting all troubleshooting with the following diagnostic tests. They'll save you a lot of time and heartache if there is a hardware failure, and you'll have the disks on hand in case you need them in the future:
Quote:
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)

Also, please run one of these free, independent online malware scans to ensure that your current protection hasn't been compromised: Malware (read the details at the link)
BSOD BUGCHECK SUMMARY
Code:

Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Tue Nov  9 11:11:17.015 2010 (UTC - 5:00)
System Uptime: 0 days 0:22:04.421
Probably caused by : win32k.sys ( win32k!HMAssignmentUnlock+10 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  mmc.exe
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff960`001b6444 fffff880`07acc040 00000000`00000000
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Tue Nov  9 01:15:43.937 2010 (UTC - 5:00)
System Uptime: 0 days 4:15:15.343
Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+233 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  soffice.bin
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff800`02dc10bf fffff880`059fdf30 00000000`00000000
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Nov  8 20:59:52.960 2010 (UTC - 5:00)
System Uptime: 0 days 0:17:42.367
Probably caused by : ntkrnlmp.exe ( nt!ExFreePoolWithTag+43 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
Bugcheck code 1000007E
Arguments ffffffff`c0000005 fffff800`02dee0f3 fffff880`031bd8e8 fffff880`031bd150
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Nov  8 17:22:24.769 2010 (UTC - 5:00)
System Uptime: 0 days 3:47:25.113
Probably caused by : memory_corruption ( nt!MmUnmapViewInSystemCache+d2 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
BUGCHECK_STR:  0x34
Bugcheck code 00000034
Arguments 00000000`00050830 fffff880`0319a4f8 fffff880`03199d60 fffff800`02cab782
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sat Nov  6 17:20:08.351 2010 (UTC - 5:00)
System Uptime: 0 days 0:24:19.695
Probably caused by : ntkrnlmp.exe ( nt!CmpDereferenceNameControlBlockWithLock+aa )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
Bugcheck code 1000007E
Arguments ffffffff`c0000005 fffff800`02f77bd2 fffff880`031a8968 fffff880`031a81d0
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Thu Nov  4 17:25:41.738 2010 (UTC - 5:00)
System Uptime: 0 days 0:16:58.144
Probably caused by : ntkrnlmp.exe ( nt!ObpLookupDirectoryEntry+16a )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  gnotify.exe
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff800`02f7da4a fffff880`05be1c50 00000000`00000000
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Thu Nov  4 17:07:54.367 2010 (UTC - 5:00)
System Uptime: 0 days 1:04:36.710
Probably caused by : ntkrnlmp.exe ( nt!ExAllocatePoolWithTag+53d )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  AEI.exe
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff800`02db590d fffff880`08ffe910 00000000`00000000
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Thu Nov  4 16:01:59.672 2010 (UTC - 5:00)
System Uptime: 0 days 0:26:55.079
Probably caused by : Ntfs.sys ( Ntfs!NtfsFindStartingNode+4b9 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  svchost.exe
BUGCHECK_STR:  0x24
Bugcheck code 00000024
Arguments 00000000`001904fb fffff880`0841d848 fffff880`0841d0b0 fffff880`012f0d49
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Tue Nov  2 17:08:43.471 2010 (UTC - 5:00)
System Uptime: 0 days 0:03:45.877
Probably caused by : Ntfs.sys ( Ntfs!NtfsCommonCleanup+872 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  svchost.exe
BUGCHECK_STR:  0x24
Bugcheck code 00000024
Arguments 00000000`001904fb fffff880`06f1f5b8 fffff880`06f1ee20 fffff800`02ca590c
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Tue Nov  2 17:04:23.676 2010 (UTC - 5:00)
System Uptime: 0 days 0:06:49.020
Probably caused by : ntkrnlmp.exe ( nt!ExpInterlockedPopEntrySListFault16+0 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  SearchProtocol
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff800`02cc4905 fffff880`03af79b0 00000000`00000000
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Tue Nov  2 16:52:16.800 2010 (UTC - 5:00)
System Uptime: 0 days 1:47:22.191
Probably caused by : Ntfs.sys ( Ntfs!NtfsOpenAttribute+3a7 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  mpnex10.exe
BUGCHECK_STR:  0x24
Bugcheck code 00000024
Arguments 00000000`001904fb fffff880`0625b3f8 fffff880`0625ac60 fffff880`012f4bf7
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Wed Oct 27 13:45:00.610 2010 (UTC - 5:00)
System Uptime: 0 days 3:40:19.000
Probably caused by : fileinfo.sys ( fileinfo!FIStreamFillStreamInfo+83 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
BUGCHECK_STR:  0x24
Bugcheck code 00000024
Arguments 00000000`001904fb fffff880`03185528 fffff880`03184d90 fffff880`010f7493
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
  
  
My System SpecsSystem Spec
10 Nov 2010   #3
kennedy1

Windows 7 64 Bit
 
 

Thanks,
I will try that....
This all seems really complicated, is there any more straightforward way to look at the crash logs and see what is causing it?

I will attempt to runs these diagnostics and report back.

Thanks again.

Quote   Quote: Originally Posted by usasma View Post
I suggest starting all troubleshooting with the following diagnostic tests. They'll save you a lot of time and heartache if there is a hardware failure, and you'll have the disks on hand in case you need them in the future:
Quote:
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)

Also, please run one of these free, independent online malware scans to ensure that your current protection hasn't been compromised: Malware (read the details at the link)
BSOD BUGCHECK SUMMARY
Code:

Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Tue Nov  9 11:11:17.015 2010 (UTC - 5:00)
System Uptime: 0 days 0:22:04.421
Probably caused by : win32k.sys ( win32k!HMAssignmentUnlock+10 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  mmc.exe
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff960`001b6444 fffff880`07acc040 00000000`00000000
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Tue Nov  9 01:15:43.937 2010 (UTC - 5:00)
System Uptime: 0 days 4:15:15.343
Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+233 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  soffice.bin
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff800`02dc10bf fffff880`059fdf30 00000000`00000000
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Nov  8 20:59:52.960 2010 (UTC - 5:00)
System Uptime: 0 days 0:17:42.367
Probably caused by : ntkrnlmp.exe ( nt!ExFreePoolWithTag+43 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
Bugcheck code 1000007E
Arguments ffffffff`c0000005 fffff800`02dee0f3 fffff880`031bd8e8 fffff880`031bd150
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Nov  8 17:22:24.769 2010 (UTC - 5:00)
System Uptime: 0 days 3:47:25.113
Probably caused by : memory_corruption ( nt!MmUnmapViewInSystemCache+d2 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
BUGCHECK_STR:  0x34
Bugcheck code 00000034
Arguments 00000000`00050830 fffff880`0319a4f8 fffff880`03199d60 fffff800`02cab782
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sat Nov  6 17:20:08.351 2010 (UTC - 5:00)
System Uptime: 0 days 0:24:19.695
Probably caused by : ntkrnlmp.exe ( nt!CmpDereferenceNameControlBlockWithLock+aa )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
Bugcheck code 1000007E
Arguments ffffffff`c0000005 fffff800`02f77bd2 fffff880`031a8968 fffff880`031a81d0
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Thu Nov  4 17:25:41.738 2010 (UTC - 5:00)
System Uptime: 0 days 0:16:58.144
Probably caused by : ntkrnlmp.exe ( nt!ObpLookupDirectoryEntry+16a )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  gnotify.exe
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff800`02f7da4a fffff880`05be1c50 00000000`00000000
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Thu Nov  4 17:07:54.367 2010 (UTC - 5:00)
System Uptime: 0 days 1:04:36.710
Probably caused by : ntkrnlmp.exe ( nt!ExAllocatePoolWithTag+53d )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  AEI.exe
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff800`02db590d fffff880`08ffe910 00000000`00000000
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Thu Nov  4 16:01:59.672 2010 (UTC - 5:00)
System Uptime: 0 days 0:26:55.079
Probably caused by : Ntfs.sys ( Ntfs!NtfsFindStartingNode+4b9 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  svchost.exe
BUGCHECK_STR:  0x24
Bugcheck code 00000024
Arguments 00000000`001904fb fffff880`0841d848 fffff880`0841d0b0 fffff880`012f0d49
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Tue Nov  2 17:08:43.471 2010 (UTC - 5:00)
System Uptime: 0 days 0:03:45.877
Probably caused by : Ntfs.sys ( Ntfs!NtfsCommonCleanup+872 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  svchost.exe
BUGCHECK_STR:  0x24
Bugcheck code 00000024
Arguments 00000000`001904fb fffff880`06f1f5b8 fffff880`06f1ee20 fffff800`02ca590c
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Tue Nov  2 17:04:23.676 2010 (UTC - 5:00)
System Uptime: 0 days 0:06:49.020
Probably caused by : ntkrnlmp.exe ( nt!ExpInterlockedPopEntrySListFault16+0 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  SearchProtocol
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff800`02cc4905 fffff880`03af79b0 00000000`00000000
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Tue Nov  2 16:52:16.800 2010 (UTC - 5:00)
System Uptime: 0 days 1:47:22.191
Probably caused by : Ntfs.sys ( Ntfs!NtfsOpenAttribute+3a7 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  mpnex10.exe
BUGCHECK_STR:  0x24
Bugcheck code 00000024
Arguments 00000000`001904fb fffff880`0625b3f8 fffff880`0625ac60 fffff880`012f4bf7
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Wed Oct 27 13:45:00.610 2010 (UTC - 5:00)
System Uptime: 0 days 3:40:19.000
Probably caused by : fileinfo.sys ( fileinfo!FIStreamFillStreamInfo+83 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
BUGCHECK_STR:  0x24
Bugcheck code 00000024
Arguments 00000000`001904fb fffff880`03185528 fffff880`03184d90 fffff880`010f7493
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
  
  
My System SpecsSystem Spec
10 Nov 2010   #4
kennedy1

Windows 7 64 Bit
 
 

Ran MemTest and the computer passed with no errors.
My System SpecsSystem Spec
10 Nov 2010   #5
usasma
Microsoft MVP

 
 

The "ffffffff`c0000005" thing is telling us that there was an error accessing memory. Since you passed MemTest, then the problem has to be elsewhere. The most likely thing is a problem with a 3rd party driver - but it's not the only possibility by a long shot!

Unfortunately, there's no easy way to do this - but you can take a few shortcuts if you'd like:
- first, backup your stuff.
- then wipe your hard drive with KillDisk or DBAN (free)
- install Windows
- get all Windows updates
- install an antivirus
- DO NOT install anything else!!!
- check Device Manager for any missing drivers, install only those drivers and only those from the device manufacturer's website.
- test for further BSOD's

If that fixes it, then you can start adding your programs to see if they cause the issue.

Please let us know the results of the hard drive diagnostic. If that passes, then I'd suggest running Driver Verifier according to these directions:
Quote:
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 "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:
Code:
Delete these registry keys (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: http://support.microsoft.com/?kbid=244617&sd=RMVP
My System SpecsSystem Spec
10 Nov 2010   #6
kennedy1

Windows 7 64 Bit
 
 

Thank you !!
I actually have to run MemTest for more then just 1 pass...Sorry, amateur hour here, but I thought since it 'finished' with no errors I was all set. Will re-rerun it for hours later and see the results.

As I listed I have a Sapphire Radeon HD 4870 graphics card, with it's own drivers...perhaps this is a problem with that particular card?

When I tried to run the HD diagnostic tool via the links provided, I kept getting an 'Error accessing licensing file...' I called Western Digital Support and they indicated that was an uncommon error that has to do with my MOBO / Bios and the way things are accessed...Over my head. They suggested running the Windows hard drive utility to see...

Is there a test I can run on the GPU, (i.e. a benchmark to stress it and see if it can complete the test)?

Also, I have a 500W Antec Power Supply....Maybe this is too low?

Thanks a million this is really driving me crazy...
My System SpecsSystem Spec
10 Nov 2010   #7
usasma
Microsoft MVP

 
 

The Western Digital test is a bit unpredicatable - so I recommend using either the Seagate Seatools or the Hitachi Drive Fitness Test (DFT).

Use these free stress tests for your video card:
Quote:
Quote:
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).
- Click "Quit" to exit
Quote:
Prime95 download site: Free Software - GIMPS
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 you may want to 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).
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.
Quote:
Two other video stress tests (may be more stressful than FurMark):
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.
My System SpecsSystem Spec
Reply

 Bsod help




Thread Tools



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 09:22 PM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App