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 BSOD's

19 Sep 2010   #1
tomatpasser

Windows 7 64-bit
 
 
Random BSOD's

I've been having random BSOD's for like half a year. It might have started when i installed Win7, I'm not sure if i had them too before when i had Windows XP.
My pc:
Win7 64-bit
Gigabyte GA-MA770T-UD3P motherboard
AMD Phenom II X4 955 Processor
ATI Radeon 4900 display card
8gb ram, not sure which model/manufacturer.

128gb Kingston SSDNow V-Series: Boot disk + programs
1,5tb
not sure which model/manufacturer: Other stuff

Just got my ssd this week and installed win7 fresh on it, i used my big harddrive as boot disk before where i also had crashes, so i don't think it's the hdd that's the problem.

I followed the instructions for the forum and attached the zip file.
Looked at the crashed myself with winDbg and one of them said audiodg.exe was causing it. I'm not an expert tho

Thanks in advance.

tomatpasser



My System SpecsSystem Spec
.
19 Sep 2010   #2
usasma
Microsoft MVP

 
 

Nothing much to blame in these dumps. Please run Driver Verifier according to these instructions:
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: Using Driver Verifier to identify issues with Windows drivers for advanced users
BSOD BUGCHECK SUMMARY
Code:

Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sun Sep 19 07:18:32.689 2010 (UTC - 4:00)
System Uptime: 0 days 0:34:44.000
Probably caused by : ntkrnlmp.exe ( nt!KiIpiSendRequest+1d5 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  audiodg.exe
Bugcheck code 0000000A
Arguments fffff808`02cb18f8 00000000`0000000c 00000000`00000000 fffff800`02a87925
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sun Sep 19 06:43:21.805 2010 (UTC - 4:00)
System Uptime: 0 days 1:56:11.901
Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )
BUGCHECK_STR:  0x1E_0
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
Bugcheck code 0000001E
Arguments 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
  
  
My System SpecsSystem Spec
19 Sep 2010   #3
tomatpasser

Windows 7 64-bit
 
 

Thanks, i'll do that when i get back from school
My System SpecsSystem Spec
.

22 Sep 2010   #4
tomatpasser

Windows 7 64-bit
 
 

I've gotten two bsod┤s with verifier running so far.

Uploading the dumps
My System SpecsSystem Spec
22 Sep 2010   #5
usasma
Microsoft MVP

 
 

Don't forget to turn Driver Verifier off (see the instructions above).

Some very odd memory dumps.

Neither blames a 3rd party driver - so Driver Verifier is saying that the 3rd party drivers are probably OK. That leaves either hardware problems (most likely) or Windows problems. Compatibility problems are also possible - but not as likely as that would be issues with 3rd party stuff.

Since hardware is the most likely, and NTFS.sys is cited in one of the dumps - I'd start with this:
Quote:
CHKDSK /R /F:
Run CHKDSK /R /F from an elevated (Run as adminstrator) Command Prompt. Please do this for each hard drive on your system.
When it tells you it can't do it right now - and asks you if you'd like to do it at the next reboot - answer Y (for Yes) and press Enter. Then reboot and let the test run. It may take a while for it to run, but keep an occasional eye on it to see if it generates any errors. See "CHKDSK LogFile" below in order to check the results of the test.

Elevated Command Prompt:
Go to Start and type in "cmd.exe" (without the quotes)
At the top of the Search Box, right click on Cmd.exe and select "Run as administrator"

CHKDSK LogFile:
Go to Start and type in "eventvwr.msc" (without the quotes) and press Enter
Expand the Windows logs heading, then select the Application log file entry.
Double click on the Source column header.
Scroll down the list until you find the Chkdsk entry (wininit for Win7) (winlogon for XP).
Copy/paste the results into your next post.
Then I'd use the hard drive diagnostic in this procedure:
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: Wed Sep 22 13:42:13.340 2010 (UTC - 4:00)
System Uptime: 0 days 1:02:30.057
Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )
BUGCHECK_STR:  0x1E_0
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  System
Bugcheck code 0000001E
Arguments 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Tue Sep 21 02:22:31.771 2010 (UTC - 4:00)
System Uptime: 0 days 0:01:07.488
Probably caused by : Ntfs.sys ( Ntfs!NtfsCommonCleanup+2653 )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  System
BUGCHECK_STR:  0x24
Bugcheck code 00000024
Arguments 00000000`001904fb fffff880`077a4b38 fffff880`077a43a0 fffff800`02add4b4
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
  
  
My System SpecsSystem Spec
04 Oct 2010   #6
tomatpasser

Windows 7 64-bit
 
 

Sorry it took me a while to get those things done

Zipped the chdsk test of c: and d: drive and some new crashdumps.
The Seagate harddisk test showed no problems, but i couldn't find a test tool for my Kingston SSD.
My System SpecsSystem Spec
04 Oct 2010   #7
usasma
Microsoft MVP

 
 

Chkdsk did find issues on your C: drive. Is that your SSD?
Did the system pass the memory test?

Try these tests for the SSD:
Crystal Dew World
Samsung SSD | Samsung SSD FAQ (dunno if it'll work with your drive - but it's free, so it's worth a shot)
http://downloadcenter.intel.com/Deta...&DwnldID=18455 (dunno if it'll work with your drive - but it's free, so it's worth a shot)

The dump files still say hardware to me. Try these free stress tests also:
Quote:
Quote:
FurMark download site: http://www.ozone3d.net/benchmarks/fur/
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: 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 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 - http://nvworld.ru/utilities/vmt/
Artifact Locator - http://nvworld.ru/utilities/alocator/
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: Sun Oct  3 05:53:07.650 2010 (UTC - 4:00)
System Uptime: 0 days 2:12:57.549
Probably caused by : Ntfs.sys ( Ntfs!NtfsFlushVolume+449 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
Bugcheck code 1000007E
Arguments ffffffff`c0000005 fffff880`01288b69 fffff880`0318c458 fffff880`0318bcc0
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Fri Oct  1 06:55:10.342 2010 (UTC - 4:00)
System Uptime: 0 days 0:31:06.043
Probably caused by : ntkrnlmp.exe ( nt!KeSetEvent+124 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  csrss.exe
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff800`02a917b4 fffff880`029e3cb0 00000000`00000000
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Thu Sep 30 15:41:09.033 2010 (UTC - 4:00)
System Uptime: 0 days 1:24:20.735
Probably caused by : ntkrnlmp.exe ( nt!KiInsertTimerTable+13b )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  plugin-contain
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff800`02a8214b fffff880`0a051f80 00000000`00000000
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Sep 27 15:23:50.658 2010 (UTC - 4:00)
System Uptime: 0 days 0:01:07.359
Probably caused by : tcpip.sys ( tcpip!TcpGetIsn+7b )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  wmpnetwk.exe
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff880`0186d69b fffff880`09524980 00000000`00000000
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
  
  
My System SpecsSystem Spec
04 Oct 2010   #8
tomatpasser

Windows 7 64-bit
 
 

Yes, c: drive is my ssd.
The memory test showed no errors after 1 pass.

I'll post back when i've run the stress tests.
Thank you so far
My System SpecsSystem Spec
05 Oct 2010   #9
usasma
Microsoft MVP

 
 

Memory test needs to run at least 3 passes - overnight is better
My System SpecsSystem Spec
10 Oct 2010   #10
tomatpasser

Windows 7 64-bit
 
 

Ok i tried Memtest with 3 passes, still nothing.

FurMark didn't make it crash even after a while, the gpu was max on 87 degrees celcius.

Posting logs from Crystal Dew and Prime95.
Looks like prime95 found something.

The samsung and intel ssd tools didn't work with my ssd.

Haven't tried those last two tests yet.
My System SpecsSystem Spec
Reply

 Random BSOD's




Thread Tools




Similar help and support threads
Thread Forum
Random BSOD after start and Random stuck on windows logo screen
Heyy.. So yesterday due to a sudden power outage (happens allot here), my windows started behaving erratically. First when the power came on my windows 7 ultimate 64 bit, was stuck on windows logo. i waited for about 20 mins and it was still stuck. The HDD read activity light on my casing was...
BSOD Help and Support
Random BSOD problems in the past 2 days. Random errors at random times
Three days ago my water cooling failed (got up to 77C while gaming is when I noticed the problem as my CPU should not go over 62C). I decided to install an aftermarket heatsink instead of a new water cooling system ,and add a few more fans just to make sure my whole motherboard was getting plenty...
BSOD Help and Support
BSOD at seemingly random times, memory dump blaming random drivers
I've been plagued by odd problems since making this custom build about a month ago, but the latest is the increasing frequency of BSODs. They never occur at load (gaming with high end specs), but often occur at shutdown (forcing a restart before I can then actually shut down). I normally boot into...
BSOD Help and Support
Random BSOD at random moments on Toshiba L500 laptop; graphics card?
My GF has had a Toshiba L500 laptop for 4 years now. It's a great model and it worked well...till now. It started about two weeks ago, with 1 blue screen every 1-2 days. I haven't reinstalled her windows for about a year, so i figured that was the problem. Four days ago it started blue...
BSOD Help and Support
Random BSOD with random error code at random moment
Hello Ok now i'm out of solution so i come here hoping that someone could help me I always had bsod hapening randomly but not like the this week I got 2 bsod/day when i'm playing, when i'm staring at my monitor or even when i'm sleeping with random error code like 0x1e, 0x24, 0x3b, 0x4a or 0xa...
BSOD Help and Support
BSOD doing random things (Google Chrome, minecraft, random times)
I have finally had it up to here with the BSODs, so I really need help. I ran a windows memtest and it detected no errors. I just finished updating to SP1 with pretty much most updates too. The BSODs I get the most are: Driver IRQL not less or Equal System Service Exception and these two I...
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 12:52.
Twitter Facebook Google+ Seven Forums iOS App Seven Forums Android App