Tech Support Forum banner
Status
Not open for further replies.

BSOD STOP: 7E on New Build

7K views 23 replies 3 participants last post by  WrongtownReilly 
#1 ·
Hi All,

I'm having trouble with seemingly random BSOD's on my new build. The specs are as follows;

MoBo: Gigabyte PA67A-UD3-B3
CPU: Intel Core i7 2600 3.4GHz
GPU: Asus Nvidia GT440
Memory: 2x Crucial 4GB DDR3 PC3-10600
PCI: Belkin Firewire 800 Card
OS: Windows 7 Home Premium 64-Bit


The BSOD seems to be happening at random and the screen shows the following code:

STOP: 0x0000007E (0xFFFFFDFFFC0000005, 0xFFFFF80003113349, 0XFFFFF880009A9998, 0xFFFFF880009A9200


I'm also occasionally getting a message saying my display adaptor has stopped working but has recovered which may point to the graphics card as the culprit.

I've tried memtest on the RAM and also sfc /scannow but neither have returned any errors. I've also updated my Bios and downloaded the latest graphics drivers from the NVidia website.

I have attached the .dmp file from the latest crash in case this helps track down the issue. I've looked at it in WinDBG but I'm not sure how to interpret this:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\050711-14461-01.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 \SystemRoot\system32\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 (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Machine Name:
Kernel base = 0xfffff800`0305c000 PsLoadedModuleList = 0xfffff800`03299e50
Debug session time: Sat May 7 13:20:15.292 2011 (UTC + 1:00)
System Uptime: 0 days 2:47:16.213
*********************************************************************
* 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 \SystemRoot\system32\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
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff80003113349, fffff880009a9998, fffff880009a9200}

***** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 : ntoskrnl.exe ( nt+b7349 )

Followup: MachineOwner
---------
I seem to be missing the correct symbols to display most of this information!

Can anyone suggest a possible solution to this? This is happening regularly and is the cause of much frustration!

Thanks,
Reilly
 

Attachments

See less See more
#3 ·
Please provide this info: http://www.techsupportforum.com/for...-instructions-windows-7-and-vista-452654.html

Try this free stress test on your video card:
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!!!
- Click "Quit" to exit
The memory dumps don't point to anything specific - so I'd suggest running 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 "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: Using Driver Verifier to identify issues with Windows drivers for advanced users
Please uninstall the Gigabyte EasyTune software and see if that helps. This is just a hunch on my part.

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:
Code:
[font=lucida console]
amdxata.sys      Fri Mar 19 12:18:18 2010 (4BA3A3CA) - Windows will update this if it's available.
speedfan.sys     Sat Dec 18 06:03:51 2010 (4D0C9517)
aswSP.SYS        Mon Apr 18 13:17:56 2011 (4DAC7244)
AppleCharger.sys Mon Jan 10 04:57:29 2011 (4D2AD809)
Rt64win7.sys     Fri Dec 24 02:30:25 2010 (4D144C11)
nusb3hub.sys     Thu Nov 18 20:34:24 2010 (4CE5D420)
gdrv.sys         Thu Mar 12 23:22:29 2009 (49B9D175)
cpuz_x64.sys     Tue Dec 02 08:51:19 2008 (49353D57)
HECIx64.sys      Tue Sep 21 12:59:04 2010 (4C98E458)
nusb3xhc.sys     Thu Nov 18 20:34:25 2010 (4CE5D421)
nvlddmkm.sys     Thu Apr 07 23:22:12 2011 (4D9E7F64)
[/font]
http://www.carrona.org/dvrref.html#amdxata.sys
http://www.carrona.org/dvrref.html#speedfan.sys
http://www.carrona.org/dvrref.html#aswSP.SYS
http://www.carrona.org/dvrref.html#AppleCharger.sys
http://www.carrona.org/dvrref.html#Rt64win7.sys
http://www.carrona.org/dvrref.html#nusb3hub.sys
http://www.carrona.org/dvrref.html#gdrv.sys
http://www.carrona.org/dvrref.html#HECIx64.sys
http://www.carrona.org/dvrref.html#nusb3xhc.sys
http://www.carrona.org/dvrref.html#nvlddmkm.sys
BSOD BUGCHECK SUMMARY
Code:
[font=lucida console]
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Sat May  7 08:20:15.292 2011 (UTC - 4:00)
System Uptime: 0 days 2:47:16.213
Probably caused by : memory_corruption ( nt!MmZeroPageThread+3d4 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
FAILURE_BUCKET_ID:  X64_0x7E_nt!MmZeroPageThread+3d4
Bugcheck code 1000007E
Arguments ffffffff`c0000005 fffff800`03113349 fffff880`009a9998 fffff880`009a9200
BiosVersion = F3
BiosReleaseDate = 03/31/2011
CPUID:        "Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3395
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Sat May  7 05:22:37.370 2011 (UTC - 4:00)
System Uptime: 0 days 0:23:27.291
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+40e0b )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  AvastSvc.exe
FAILURE_BUCKET_ID:  X64_0x50_nt!_??_::FNODOBFM::_string_+40e0b
Bugcheck code 00000050
Arguments ffffea80`08d960f0 00000000`00000001 fffff800`030cd80c 00000000`00000007
BiosVersion = F3
BiosReleaseDate = 03/31/2011
CPUID:        "Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3391
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Sat May  7 04:54:02.016 2011 (UTC - 4:00)
System Uptime: 0 days 0:03:38.937
Probably caused by : memory_corruption ( nt!MmZeroPageThread+3d4 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
FAILURE_BUCKET_ID:  X64_0x7E_nt!MmZeroPageThread+3d4
Bugcheck code 1000007E
Arguments ffffffff`c0000005 fffff800`030bd349 fffff880`009a9998 fffff880`009a9200
BiosVersion = F3
BiosReleaseDate = 03/31/2011
CPUID:        "Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3391
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Fri May  6 06:44:36.475 2011 (UTC - 4:00)
System Uptime: 0 days 0:52:41.397
Probably caused by : memory_corruption ( nt!MmZeroPageThread+3d4 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
FAILURE_BUCKET_ID:  X64_0x7E_nt!MmZeroPageThread+3d4
Bugcheck code 1000007E
Arguments ffffffff`c0000005 fffff800`030bb349 fffff880`009a9998 fffff880`009a9200
BiosVersion = F2
BiosReleaseDate = 02/22/2011
CPUID:        "Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3391
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Wed May  4 15:10:57.054 2011 (UTC - 4:00)
System Uptime: 0 days 1:11:36.975
Probably caused by : memory_corruption ( nt!MmZeroPageThread+3d4 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
FAILURE_BUCKET_ID:  X64_0x7E_nt!MmZeroPageThread+3d4
Bugcheck code 1000007E
Arguments ffffffff`c0000005 fffff800`03115349 fffff880`009a9998 fffff880`009a9200
BiosVersion = F2
BiosReleaseDate = 02/22/2011
CPUID:        "Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3395
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
  [/font]
 
#5 ·
Hi again, everyone.

I had to leave the new build project aside for a while because of work commitments but I'm back on it today and trying to solve this issue. Thanks for the replies on this so far.

Dai: There is a 500w Coolermaster PSU in the system

As Usasma suggested I ran the graphics card benchmark however there was no BSOD as a result of this.

This morning I activated Driver Verifier and started the computer as normal. A few minutes later there was a BSOD (at the time I was running Futuremark Benchmarking software). I had to use Windows Startup Repair to recover to a system restore point before I could boot back to windows.

I have attached the resulting dump file to this post. I haven't yet dealt with the list of older drivers in Usasma's post.

Does this new dump shed any more light on the cause of the BSOD's? Thanks for your help so far guys.
 

Attachments

#7 ·
#8 ·
The Verifier Enabled Memory Dump blames the Windows kernel.
Since you set the verifier to verify 3rd party drivers, this indicates that none of the 3rd party drivers failed due to Driver Verifier. As such we presume that 3rd party drivers aren't at fault.

That leaves (basically) Windows or hardware (although there are some compatibility issues and some malware issues that could cause this - but they are less likely).

Here's some hardware tests to run - but also continue the PSU discussion with dai as that's a distinct possibility at this point.

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:
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)
If you find hardware issues, here's a link to the hardware forums: Hardware Support - Tech Support Forum

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)
If you find malware, here's a link on how to post in the Security Center: NEW INSTRUCTIONS - Read This Before Posting For Malware Removal Help - Tech Support Forum
 
#9 ·
Forgot to post the BSOD summary:
BSOD BUGCHECK SUMMARY
Code:
[font=lucida console]
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\062811-19500-01.dmp]
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Tue Jun 28 07:26:42.853 2011 (UTC - 4:00)
System Uptime: 0 days 0:00:14.696
Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xA_VRF_nt!KiPageFault+260
Bugcheck code 0000000A
Arguments 00000000`000001f0 00000000`00000002 00000000`00000000 fffff800`0309d605
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
  [/font]
 
#10 ·
Memtest, Hard Disk scan (Sea-Tools) and a few of those malware checks returned no errors or issues.

It may be worth pointing out that the Memtest ran overnight which is the longest the machine has ever run without error although I guess that could be because the other hardware was under less strain during this time.
 
#11 ·
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!!!
- Click "Quit" to exit
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 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).
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):
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!
 
#12 ·
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!!!
- Click "Quit" to exit
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 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).
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):
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!
 
#15 ·
What test were you running with Prime95? (Blend, Small FFT or Large FFT)
Were there any errors displayed in Prime95?
Have you tried running it again to see if it's able to force another BSOD?

Were there any problems noted with Furmark? What temperature did the video card get to? Have you tried running it again to see if it's able to force another BSOD?

Please uninstall the Gigabyte EasyTune software and see if that helps. There are traces of it's driver (gdrv.sys) in the memory dump file(s) - and it's sometimes a problem with some Win7 systems.

Other than that the memory dumps don't reveal very much. Try the different Prime95 tests and see which takes the longest (and the shortest) to cause problems (and document the problems). Check on the temps when running Furmark also.

BSOD BUGCHECK SUMMARY
Code:
[font=lucida console]
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\063011-14523-01.dmp]
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Thu Jun 30 11:41:41.038 2011 (UTC - 4:00)
System Uptime: 0 days 0:22:38.866
Probably caused by : memory_corruption ( nt!MmZeroPageThread+3c4 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
FAILURE_BUCKET_ID:  X64_0x7E_nt!MmZeroPageThread+3c4
Bugcheck code 1000007E
Arguments ffffffff`c0000005 fffff800`03047841 fffff880`009a9898 fffff880`009a90f0
BiosVersion = F3
BiosReleaseDate = 03/31/2011
CPUID:        "Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3391
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\063011-17924-01.dmp]
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Thu Jun 30 11:15:31.925 2011 (UTC - 4:00)
System Uptime: 0 days 5:25:14.753
Probably caused by : win32k.sys ( win32k!xxxRealSleepThread+257 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  speedfan.exe
FAILURE_BUCKET_ID:  X64_0xA_win32k!xxxRealSleepThread+257
Bugcheck code 0000000A
Arguments ffffea80`083a6bf0 00000000`00000002 00000000`00000000 fffff800`030def95
BiosVersion = F3
BiosReleaseDate = 03/31/2011
CPUID:        "Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3391
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
  [/font]
 
#16 ·
I was running a Small FTT's test as I had successfully run memtest overnight and had no errors. There were no errors that I saw however I was not at the computer when the BSOD occurred. I had been checking in on it every 10 minutes or so and there had been no error messages. I will run another Prime95 test now to see if I can force another BSOD.

Similarly the FurMark test had no on-screen errors. I ran the test again this morning and it ran for about an hour or so before another BSOD. The temperature of the graphics card had been varying from 57 to 60 C. I have attached the crash dump from the BSOD to this post along with the logs generated by FurMark.

I uninstalled EasyTune earlier this morning before running the second FurMark test.
 
#19 · (Edited)
Youre going to have to run all 3 Pimr95 tests. The length of time it takes to make an error in each test will help determine what's causing the error. Since Furmark also ceases I'd have to suspect the kobo first and the CPU next (depending on the type of CPU)

I'll try to get online this PM. Am visiting my new grandson in Wilmington NC. Internet very sketchy at the hotel here
 
#21 ·
Hi All,

I've been experimenting with the machine over the weekend, specifically running Prime95 tests with one stick of RAM at a time (I currently have 2 4GB sticks).

Interestingly with one of the sticks in on its own, Prime95 fails after around 40 minutes. I also got a couple of BSODs during tests too. But with the other stick in on its own, the tests run without crashing. I haven't been able to do a 24-hour test with Prime95 on the *good* stick yet. This will be my next task!

Does this sound like bad RAM stick? Or perhaps a bad slot on the MoBo? As I mentioned in an earlier post I was able to run Memtest overnight with both sticks and had no errors reported. I'll do an overnight test on the bad stick and see what I come up with.

Happy 4th of July USA-ers :smile:
 
#22 ·
Memtest tests memory, Prime95 tests CPU, mobo memory functions, and memory.

Chances are good that the "bad" stick is bad - as long as the "good" stick doesn't error out in the same slot.

Although MemTest is the recommended memory test utility around here - I've seen memory errors in Prime95 that weren't picked up by MemTest (and were fixed by replacing the "bad" stick).
 
Status
Not open for further replies.
You have insufficient privileges to reply here.
Top