Random BSOD's

[tomatpasser]

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

 

[usasma]

Nothing much to blame in these dumps. Please run Driver Verifier according to these instructions:

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:

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

[font=lucida console]
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
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
  [/font]

 

[tomatpasser]

Thanks, i'll do that when i get back from school

 

[tomatpasser]

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

Uploading the dumps

 

[usasma]

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:

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:

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

[font=lucida console]
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
[COLOR=Red]Probably caused by :[/COLOR] 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
[COLOR=Red]Probably caused by :[/COLOR] Ntfs.sys ( Ntfs!NtfsCommonCleanup+2653 )
DEFAULT_BUCKET_ID:  [COLOR=Black]VERIFIER_ENABLED_VISTA_MINIDUMP[/COLOR]
PROCESS_NAME:  System
BUGCHECK_STR:  0x24
Bugcheck code 00000024
Arguments 00000000`001904fb fffff880`077a4b38 fffff880`077a43a0 fffff800`02add4b4
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
  [/font]

 

[tomatpasser]

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.

 

[usasma]

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/Detail_Desc.aspx?agr=Y&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:

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

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.

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

[font=lucida console]
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
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
  [/font]

 

[tomatpasser]

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

 

[usasma]

Memory test needs to run at least 3 passes - overnight is better

 

[tomatpasser]

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.

 

[usasma]

Although I'm not familiar with SSD's, this entry in the crystaldiskinfo.txt file is of concern (in RED at the bottom of the quote box):

----------------------------------------------------------------------------
CrystalDiskInfo 3.8.0 (C) 2008-2010 hiyohiyo
Crystal Dew World : Crystal Dew World
----------------------------------------------------------------------------

OS : Windows 7 Home Premium Edition [6.1 Build 7600] (x64)
Date : 2010/10/07 16:42:32

-- Controller Map ----------------------------------------------------------
- ATA Channel 1 (1) [ATA]
+ Standard Dual Channel PCI IDE Controller [ATA]
- ATA Channel 0 (0)
- ATA Channel 1 (1)
+ Standard Dual Channel PCI IDE Controller [ATA]
+ ATA Channel 0 (0)
- ST31500341AS ATA Device
+ ATA Channel 1 (1)
- PIONEER DVD-RW DVR-216D ATA Device
- KINGSTON SNV425S2128GB ATA Device
+ ANFYODE7 IDE Controller [SCSI]
- WLUHYLW 2N4XYJSD SCSI CdRom Device

-- Disk List ---------------------------------------------------------------
(1) ST31500341AS : 1500.3 GB [0-0-1, pd1]
(2) KINGSTON SNV425S2128GB : 128.0 GB [1-1-0, pd1]

----------------------------------------------------------------------------
(1) ST31500341AS
----------------------------------------------------------------------------
Model : ST31500341AS
Firmware : CC1H
Serial Number : 9VS145XM
Disk Size : 1500.3 GB (8.4/137.4/1500.3)
Buffer Size : Unknown
Queue Depth : 32
# of Sectors : 2930275055
Rotation Rate : 7200 RPM
Interface : Serial ATA
Major Version : ATA8-ACS
Minor Version : ATA8-ACS version 4
Transfer Mode : SATA/300
Power On Hours : 3690 hours
Power On Count : 929 count
Temparature : 39 C (102 F)
Health Status : Caution
Features : S.M.A.R.T., AAM, 48bit LBA, NCQ
APM Level : ----
AAM Level : FE00h [ON]

2 instances of this error in the results.txt file:

FATAL ERROR: Rounding was 0.5, expected less than 0.4
Hardware failure detected, consult stress.txt file.

Here's an extract from the stress.txt file:

WHAT TO DO IF A PROBLEM IS FOUND?
---------------------------------

The exact cause of a hardware problem can be very hard to find.

If you are not overclocking, the most likely cause is an overheating CPU
or memory DIMMs that are not quite up to spec. Another possibility is
you might need a better power supply. Try running MotherBoard monitor
and browse the forums above to see if your CPU is running too hot.
If so, make sure the heat sink is properly attached, fans are operational,
and air flow inside the case is good. For isolating memory problems, try
swapping memory DIMMs with a co-worker's or friend's machine. If the errors
go away, then you can be fairly confidant that memory was the cause of
the trouble. A power supply problem can often be identified by a significant
drop in the voltages when prime95 starts running. Once again the overclocker
forums are a good resource for what voltages are acceptable.

If you are overclocking then try increasing the core voltage, reduce the
CPU speed, reduce the front side bus speed, or change the memory timings
(CAS latency). Also try asking for help in one of the forums above - they
may have other ideas to try.

The point here is that I wouldn't try any of it until I fix the SSD issue - as it can be the cause of the problem.

 

[tomatpasser]

Although I'm not familiar with SSD's, this entry in the crystaldiskinfo.txt file is of concern (in RED at the bottom of the quote box):

----------------------------------------------------------------------------
CrystalDiskInfo 3.8.0 (C) 2008-2010 hiyohiyo
Crystal Dew World : Crystal Dew World
----------------------------------------------------------------------------

OS : Windows 7 Home Premium Edition [6.1 Build 7600] (x64)
Date : 2010/10/07 16:42:32

-- Controller Map ----------------------------------------------------------
- ATA Channel 1 (1) [ATA]
+ Standard Dual Channel PCI IDE Controller [ATA]
- ATA Channel 0 (0)
- ATA Channel 1 (1)
+ Standard Dual Channel PCI IDE Controller [ATA]
+ ATA Channel 0 (0)
- ST31500341AS ATA Device
+ ATA Channel 1 (1)
- PIONEER DVD-RW DVR-216D ATA Device
- KINGSTON SNV425S2128GB ATA Device
+ ANFYODE7 IDE Controller [SCSI]
- WLUHYLW 2N4XYJSD SCSI CdRom Device

-- Disk List ---------------------------------------------------------------
(1) ST31500341AS : 1500.3 GB [0-0-1, pd1]
(2) KINGSTON SNV425S2128GB : 128.0 GB [1-1-0, pd1]

----------------------------------------------------------------------------
(1) ST31500341AS
----------------------------------------------------------------------------
Model : ST31500341AS
Firmware : CC1H
Serial Number : 9VS145XM
Disk Size : 1500.3 GB (8.4/137.4/1500.3)
Buffer Size : Unknown
Queue Depth : 32
# of Sectors : 2930275055
Rotation Rate : 7200 RPM
Interface : Serial ATA
Major Version : ATA8-ACS
Minor Version : ATA8-ACS version 4
Transfer Mode : SATA/300
Power On Hours : 3690 hours
Power On Count : 929 count
Temparature : 39 C (102 F)
Health Status : Caution
Features : S.M.A.R.T., AAM, 48bit LBA, NCQ
APM Level : ----
AAM Level : FE00h [ON]

2 instances of this error in the results.txt file:

The health status: caution is actually for my normal disk, if you look further down in the crystaldiskinfo.txt it shows the ssd as in good health..

----------------------------------------------------------------------------
(2) KINGSTON SNV425S2128GB
----------------------------------------------------------------------------
Model : KINGSTON SNV425S2128GB
Firmware : D100309a
Serial Number : 07WA50002440
Disk Size : 128.0 GB (8.4/128.0/128.0)
Buffer Size : Unknown
Queue Depth : 1
# of Sectors : 250069680
Rotation Rate : ---- (SSD)
Interface : Serial ATA
Major Version : ATA8-ACS
Minor Version : ----
Transfer Mode : SATA/300
Power On Hours : 140 hours
Power On Count : 73 count
Temparature : 39 C (102 F)
Health Status : Good
Features : S.M.A.R.T., APM, 48bit LBA, TRIM
APM Level : 0000h [OFF]
AAM Level : ----

 

[usasma]

See, I told you I wasn't familiar with SSD's!
Seriously tho', there's an issue with your other HDD - so I'd suggest disconnecting it to prevent further problems from affecting your system.

Then, once it's removed (both the power and the data cables), then rerun Prime95 to see if you get the errors again.

 

[tomatpasser]

I haven't had time to try to do this before now. Do i just take the cables out of my normal hdd or do i completely take the hdd out and remove the cables from the mb too?

 

[usasma]

Sorry for the delay - I've been sick and then the neighbor nicked our cable with his lawnmower.

I'd disconnect the data cable from the motherboard, and the power cable (from the PSU) from the drive. This'll rule out any problems with the data cable also.

 

[tomatpasser]

ok, i've had it disconnected now. I still get blue screens.

So that means it's something else.. got any ideas?

 

[usasma]

Zip up and post the memory dumps that happened with the drive disconnected. We'll see what they say and move on from there.

 

[tomatpasser]

ok this is weird.. i don't have any files in the C:/Windows/Minidump folder.. i deleted all the files before i removed the harddisk so the dumps with and without harddisk wouldn't get mixed.

It has crashed three times since i did this, so there should be 3 files right? :huh:

 

[usasma]

There's many different reasons for a BSOD not being captured. When does the crash occur (in relation to the boot process - before/after the Windows Splash Screen, before/after the Windows logon/desktop, etc?

When the next one occurs, please capture this info from the screen:
How To Find Bsod Error Messages

 

[tomatpasser]

i just had a bsod, the only thing i managed to see before my pc restarted was "0x1E"

I found this in the event viewer: