Random bluescreens

this

New Member
Hello! I really hope that someone can help me with this. Have a computer that gets BSOD every now and then. But it's not the same type of bluescreen every time. Have run memtest86 +, 11 rounds without any problems. Latest BIOS is installed. Plus latest drivers. Same problem on W7 x64 and Vista x64.

Windows memory diagnostic: no errors
Harddrive test: no errors

Specs:

Phenom x4 II 920
Corsair XMS2 Xtreme TwinX DDR2 PC6400/800MHz CL5 2x2GB
Gigabyte GA-MA780G-UD3H
Corsair CMPSU-450VX
Samsung 320GB HD322HJ
Gigabyte GV-R485ZL-512H

What do you think that might be wrong?

Can give you the code to two minidump files.
 

My Computer

May not be any use, but have you removed any fonts?? I uninstalled a bunch of fonts just today and started getting BSODs out of the blue ... very annoying, as I have no idea which font was the problem and had reinstall the whole lot. I have like 100 fonts installed by various software!! I do know Vista uses several different fonts for different things v. previous versions. HTH, probably won't. :)
 

My Computer

System One

  • CPU
    Intel i7 920 2.67GHz
    Motherboard
    Gigabyte UD3R-SLI
    Memory
    6GB
    Graphics Card(s)
    Radeon HD 4800
    Sound Card
    On board
    Monitor(s) Displays
    Samsung 950p Plus
    Screen Resolution
    1280 x 1024
    Hard Drives
    Samsung HD103UJ 1Tb
    Seagate ST31000333AS 1Tb
    PSU
    No idea :)
    Case
    Thermaltake
    Cooling
    Can't remember - a good one!
    Keyboard
    Logitech cordless (basic)
    Mouse
    Logitech cordless (basic)
    Internet Speed
    Satellite 1024
Check the temps and voltages (use the bios screen).
 

My Computer

System One

  • Manufacturer/Model
    Self Built
    CPU
    I5 3570K
    Motherboard
    Gigabyte Z77-DS3H
    Memory
    4 x 4GB corsair ballistix sport DDR3 1600 Mhz
    Graphics Card(s)
    Gigabyte Geforce GTX 660 TI
    Sound Card
    creative x-fi
    Monitor(s) Displays
    Primary CiBox 22" Widescreen LCD ,Secondary Dell 22" Widescreen
    Screen Resolution
    Both 1680 x 1050
    Hard Drives
    2 x 500G HD (SATA) 1 x 2TB USB
    PSU
    Corsair HX 620W ATX2.2 Modular SLI Complient PSU
    Case
    Antec 900 Ultimate Gaming Case
    Cooling
    3 x 80mm tri led front, 120mm side 120mm back, 200mm top
    Keyboard
    Logik
    Mouse
    Technika TKOPTM2
    Internet Speed
    288 / 4000
    Other Info
    Creative Inspire 7.1 T7900 Speakers
    Trust Graphics Tablet
I will now upload the minidump files, so that you can analyze them.

Temps are fine, voltages to CPU are fine to. watched with HWmonitor.
 

Attachments

  • minidumpfiles.zip
    130.2 KB · Views: 9

My Computer

RivaTuner64.sys is from 2007 - I wonder if this is the cause.
Code:
fffff880`053ca000 fffff880`053d1000   RivaTuner64 RivaTuner64.sys Tue Jul 17 15:13:42 2007 (469D14E6)
Since the problems occur in several OS's, I'd suspect that it's either something that each installation has in common (such as RivaTuner), or a hardware problem (this presumes that all of the 3rd party software is good).

Post back if the RivaTuner isn't at fault and we'll try some other stuff. I'd suspect (after this) your video drivers or your network drivers - although there could also be a problem with your memory.

Here's a summary of the dump files. As you can see, they're all over the place with errors:
Code:
.
Built by: 7100.0.amd64fre.winmain_win7rc.090421-1700
Debug session time: Tue Jun 16 11:22:07.577 2009 (GMT-4)
System Uptime: 0 days 0:27:04.465
BugCheck 50, {ffffffffffffff8e, 1, fffff80002dae214, 0}
Probably caused by : hardware ( nt!ExDestroyHandle+4 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  lsass.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7100.0.amd64fre.winmain_win7rc.090421-1700
Debug session time: Thu Jun 18 07:37:51.075 2009 (GMT-4)
System Uptime: 0 days 1:37:59.963
BugCheck 7F, {8, 80050031, 6f8, fffff80002da7c9c}
Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  SUPERAntiSpywa
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7100.0.amd64fre.winmain_win7rc.090421-1700
Debug session time: Sun Jun 21 15:48:52.978 2009 (GMT-4)
System Uptime: 0 days 3:37:41.690
BugCheck 119, {7000000, fffffa8005544010, fffffa80065db100, fffffa8004e3a0c0}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : dxgmms1.sys ( dxgmms1!VidSchiCheckConditionDeviceCommand+8c )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  Wow.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7100.0.amd64fre.winmain_win7rc.090421-1700
Debug session time: Sun Jun 21 19:53:13.400 2009 (GMT-4)
System Uptime: 0 days 4:03:31.290
BugCheck 50, {fffff9010a6cee54, 1, fffff960000eba09, 5}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : win32k.sys ( win32k+5ba09 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  dwm.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7100.0.amd64fre.winmain_win7rc.090421-1700
Debug session time: Mon Jun 22 13:06:17.587 2009 (GMT-4)
System Uptime: 0 days 17:12:24.460
BugCheck 50, {fffff9010855e0e4, 1, fffff960000fba09, 5}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : win32k.sys ( win32k+5ba09 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  firefox.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7100.0.amd64fre.winmain_win7rc.090421-1700
Debug session time: Mon Jun 22 19:14:32.743 2009 (GMT-4)
System Uptime: 0 days 6:07:35.242
BugCheck A, {0, 2, 0, fffff80002a9cdea}
Probably caused by : ntkrnlmp.exe ( nt!KeSetEvent+233 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  Wow.exe
 

My Computer

Thank for the summary!

Rivatuner can't be the problem because it was installed much later than the problems began. Really think that it is something about the network or video driver. Can tell ya that the video driver stops working every now and then. W7 says it has a adress error or something like that. I think it might be a good idea to try to run the computer with just one stick of memory.
 

My Computer

im going to take a stab at this , but im no expert , one crashdump seems to point to Direct X . one to WOW im assuming this is world of warcraft? and one to DWM which im thinking is windows desktop manager (one to firefox but i dont know how that got in there ;) )

all of these are graphics related , but all diffearnt , so im thinking maybe update Direct X , GPU drivers?

maybe faulty hardware?? which i cant help with from crash dump analysis

H2S04 will be back soon , he knows what hes doing with these things ;)
 

My Computer

System One

  • Manufacturer/Model
    Custom Build
    CPU
    Intel Q9550 @ 4Gig / Titan Fenir
    Motherboard
    XFX 780i
    Memory
    4GB OCZ PC2-8500C5 DDR2
    Graphics Card(s)
    Gainward GTX260/216 SLI
    Sound Card
    Creative X-FI Xtreme Gamer
    Monitor(s) Displays
    Dell UltraSharp 2209WA 22"
    Screen Resolution
    1680x1050
    Hard Drives
    western digital raptor 10000rpm sata
    PSU
    OCZ Modstream 700w
    Cooling
    Titan Fenir
    Keyboard
    Razer Reclusa
    Mouse
    Logitech G5 Gamer
    Internet Speed
    8mb
Well, you can update the network driver and the video driver to see if it fixes things. With the video drivers I recommend that you uninstall the current drivers before installing the fresh copy that you'd download.

Also, try opening up your case and pointing a house fan into it. Try it for a day and see if you get any BSOD's (you're averaging one every 6 or so hours of uptime, with the longest interval being 17 hours).
 

My Computer

The latest network driver is already installed and the video driver is the latest one from Gigabytes place. But there is probably much later drivers at AMD's place.

I dont know about the fan, because none of the sensors is showing too high temps. But maybe you know that there aren't sensors to all components and that it could be a heat problem with one of those.

It really feels like it's some hardware related problem. But in that case the only part I suspect is the motherboard. Because the video card was running just fine on an other computer when I did RMA on it. It was actually when I built the computer and the problems began. This computer never did work without any problem from the start. Memory is going through plenty of tests and so is the harddrive.
 

My Computer

Back
Top