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: Random crashes on new built computer


10 Sep 2010   #1

Windows 7 64bit
 
 
BSOD recurring often now

BSOD is happening frequently more and more now on my new rebuilt pc. Just today, clicking uninstall on avg antivirus caused it and a few hrs later closing internet explorer caused it. Any help would be much appreciated. Thanks.

Windows 7 Professional 64 bit (retail upgrade version)
Clean install on new pc
Age of system - 2 weeks
Age of OS - 1 week
PC specs:
evga p55 le
wd 500 blue
gt240 512mb
corsair 4gb xms3


My System SpecsSystem Spec
.

11 Sep 2010   #2

Windows 7 64bit
 
 

Most recent error
Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.48
Locale ID: 1033
Additional information about the problem:
BCCode: 3b
BCP1: 00000000C0000005
BCP2: FFFFF80002FC1D90
BCP3: FFFFF88006F625B0
BCP4: 0000000000000000
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1
Files that help describe the problem:
C:\Windows\Minidump\091110-22109-01.dmp
C:\Users\Anthony\AppData\Local\Temp\WER-38281-0.sysdata.xml
Read our privacy statement online:
Windows 7 Privacy Statement - Microsoft Windows
If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt
My System SpecsSystem Spec
11 Sep 2010   #3
Microsoft MVP

 
 

No clearcut answers from the BSOD's - but there may be the start of a hardware problem.
So, let's start with these free diagnostics:
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)
If all of the above diagnostics pass, please run 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/Windows 7 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, Windows 7):
        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
Once Driver Verifier is done (a maximum of 36 hours continuous operation), then try these free stress tests if nothing else was revealed:
Quote:
Quote:
FurMark download site: FurMark: VGA Stress Test, Graphics Card and GPU Stability 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.
BSOD BUGCHECK SUMMARY
Code:

Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sat Sep 11 06:29:13.040 2010 (UTC - 4:00)
System Uptime: 0 days 1:53:09.071
BugCheck 3B, {c0000005, fffff80002fc1d90, fffff88006f625b0, 0}
Probably caused by : ntkrnlmp.exe ( nt!ObDereferenceSecurityDescriptor+20 )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  iexplore.exe
จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sat Sep 11 03:28:38.506 2010 (UTC - 4:00)
System Uptime: 0 days 0:01:51.538
BugCheck 18, {fffffa800495e080, fffffa800669f6c0, 1, 4000}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+463ba )
BUGCHECK_STR:  0x18
PROCESS_NAME:  consent.exe
จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Fri Sep 10 03:17:30.522 2010 (UTC - 4:00)
System Uptime: 0 days 3:45:21.553
BugCheck 1A, {41790, fffffa80041840a0, ffff, 0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+33906 )
BUGCHECK_STR:  0x1a_41790
PROCESS_NAME:  SC2.exe
จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Tue Sep  7 23:43:11.274 2010 (UTC - 4:00)
System Uptime: 0 days 0:01:50.321
BugCheck A, {4000, 2, 0, fffff80002c856a6}
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for ataport.SYS - 
Probably caused by : CLASSPNP.SYS ( CLASSPNP!TransferPktComplete+2f8 )
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ``
  
  
 
 
My System SpecsSystem Spec
.


27 Sep 2010   #4

Windows 7 64bit
 
 

Update: Computer is pretty unstable, crashes every 5 or so mins it seems. Memory and HD passed. Will prob try driver verifier next. Here are the latest dmp files. Thanks.
My System SpecsSystem Spec
27 Sep 2010   #5
Microsoft MVP

 
 

I'll wait for the results from Driver Verifier
My System SpecsSystem Spec
29 Sep 2010   #6

Windows 7 64bit
 
 

These were the crash files when running driver verifier.
My System SpecsSystem Spec
29 Sep 2010   #7
Microsoft MVP

 
 

Driver Verifier points to what's most likely a hardware problem.
10 memory dumps
6 different BSOD error messages
blaming 7 different causes.

By far the most common sub-system mentioned in the memory dumps is the video sub-system, so I'd try these free stress tests to see if they make the video card act up. If the system won't stay on long enough to try them, then I'd suggest trying another video card (if you purchase one, make sure that the store has a good return policy):
Quote:
Quote:
FurMark download site: FurMark: VGA Stress Test, Graphics Card and GPU Stability 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.
BSOD BUGCHECK SUMMARY
Code:

Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Wed Sep 29 02:23:11.892 2010 (UTC - 4:00)
System Uptime: 0 days 0:08:11.048
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+704c88 )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0x116
PROCESS_NAME:  System
Bugcheck code 00000116
Arguments fffffa80`0593f010 fffff880`105bec88 ffffffff`c000009a 00000000`00000004
จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Wed Sep 29 02:14:33.815 2010 (UTC - 4:00)
System Uptime: 0 days 0:08:07.846
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+704c88 )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0x116
PROCESS_NAME:  System
Bugcheck code 00000116
Arguments fffffa80`0606c010 fffff880`105d6c88 ffffffff`c000009a 00000000`00000004
จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Wed Sep 29 02:06:06.593 2010 (UTC - 4:00)
System Uptime: 0 days 0:00:12.640
Probably caused by : HDAudBus.sys ( HDAudBus!GetDeviceCapabilities+1a0 )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
Bugcheck code 1000007E
Arguments ffffffff`c0000005 00000001`0357cc16 fffff880`03368d48 fffff880`033685b0
จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Wed Sep 29 01:46:11.594 2010 (UTC - 4:00)
System Uptime: 0 days 0:08:12.641
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+29dd23 )
DEFAULT_BUCKET_ID:  NULL_DEREFERENCE
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
Bugcheck code 1000007E
Arguments ffffffff`c0000005 fffff880`10168d23 fffff880`03e688e8 fffff880`03e68150
จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Tue Sep 28 15:08:48.296 2010 (UTC - 4:00)
System Uptime: 0 days 0:00:12.328
Probably caused by : CI.dll ( CI!MFIsHashInGRL+ac )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
Bugcheck code 0000000A
Arguments 00000000`00000006 00000000`00000002 00000000`00000000 fffff800`030ef2b3
จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Tue Sep 28 14:53:10.294 2010 (UTC - 4:00)
System Uptime: 0 days 0:01:24.341
Probably caused by : Ntfs.sys ( Ntfs!NtfsFlushVolume+436 )
DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE
PROCESS_NAME:  MsMpEng.exe
BUGCHECK_STR:  0x24
Bugcheck code 00000024
Arguments 00000000`001904fb fffff880`093db1f8 fffff880`093daa60 fffff800`03073920
จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Tue Sep 28 14:50:51.036 2010 (UTC - 4:00)
System Uptime: 0 days 0:08:05.067
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+704c88 )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0x116
PROCESS_NAME:  System
Bugcheck code 00000116
Arguments fffffa80`060b34e0 fffff880`10594c88 ffffffff`c000009a 00000000`00000004
จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Tue Sep 28 14:39:26.854 2010 (UTC - 4:00)
System Uptime: 0 days 0:01:36.010
BugCheck D1, {0, 2, 1, fffff880018f7b46}
Probably caused by : cdrom.sys ( cdrom!DeviceEvtIoInCallerContext+62 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
Bugcheck code 000000D1
Arguments 00000000`00000000 00000000`00000002 00000000`00000001 fffff880`018f7b46
จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Sep 27 15:40:03.000 2010 (UTC - 4:00)
System Uptime: 0 days 0:00:11.031
Probably caused by : rdyboost.sys ( rdyboost!ST_STORE<SMD_TRAITS>::StDmCurrentRegionSet+9b )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
Bugcheck code 0000000A
Arguments 00000000`00000000 00000000`00000002 00000000`00000001 fffff800`030ac2a3
จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Sep 27 15:36:37.234 2010 (UTC - 4:00)
System Uptime: 0 days 0:00:27.265
Probably caused by : fltmgr.sys ( fltmgr!TreeUnlinkMulti+51 )
BUGCHECK_STR:  0x1E_c0000005
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  svchost.exe
Bugcheck code 0000001E
Arguments ffffffff`c0000005 fffff880`010e3141 00000000`00000000 00000000`00000120
จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ``
  
  
My System SpecsSystem Spec
06 May 2011   #8

Windows 7 64bit
 
 
new video card

new video card, same results...sighs...
My System SpecsSystem Spec
06 May 2011   #9
Microsoft MVP

 
 

Well, since it's a hardware problem and it isn't the video - we'll have to try this procedure: Hardware Troubleshooting Via System Stripdown
My System SpecsSystem Spec
Reply

 Random crashes on new built computer




Thread Tools



Similar help and support threads for2: Random crashes on new built computer
Thread Forum
Built new computer, getting video crashes randomly. Graphic Cards
'Random' crashes with new built computer BSOD Help and Support
Random BLSC 0x50 New Computer, New Install; Random Program Crashes. BSOD Help and Support
Newly built computer, crashes while playing a certain game Hardware & Devices
Solved Computer crashes at random and won't boot Hardware & Devices
Random BSOD's on self built computer BCCode 50,1a and 24 so far BSOD Help and Support

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 10:37 AM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33