Blue Screens

[GBear]

I sometimes get very random blue screens ranging from when I'm gaming or when I'm just watching a video. I'm not sure what I should do and the other topic about blue screens somewhat inspired me to post my problem here.

 

[Panzer Grenadier Ulrich]

I would say that your Graphics card is overheating. What card do you have?

And you are probably really lucky that is hasn't burnt out

 

[iOprah]

Can You get temps from your video card? I might suggest adding more fans or more powerful ones, if you can, that is if heat is a problem. Also make sure your computers well ventilated. If its not that it could be another hardware error, maybe the HID inputs? I use to have a laptop that would give me bluescreens every so often because of the touchpad driver...

 

[GBear]

I've got an Antec 900 and a eVGA 8800GT. The temps range around 55-65C

 

[iOprah]

Thats a bit hot, most average around 45-50c Is this a custom build? Is it well ventilated?

 

[aknightwhosezni]

these sound like BSOD's due to memory... do they have a reference number or are they so fast that you cant see them? I would be more inclined to say that your memory or drivers are the problem because it only happens when there is memory intensive work going on... rarely are video cards themselves cause for BSOD's (in my experience) unless they aren't getting sufficient power / bad drivers(8800 has a dedicated pcie plug on the back [maybe two?]) 65 degrees may be high for a CPU but thats about on par for the geForce 8XXX series cards (idle) 71-76 degrees under load...

 

[iOprah]

Yeah if you can get the information of the BSOD that would be helpful, maybe take a picture?

 

[s14sh3r]

Here's the bugcheck analysis of your minidump:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {c0000005, b2026833, b84fbc68, b84fb964}

Probably caused by : kmixer.sys ( kmixer!MxCleanupRequest+23 )

Followup: MachineOwner
---------

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: b2026833, The address that the exception occurred at
Arg3: b84fbc68, Exception Record Address
Arg4: b84fb964, Context Record Address

Debugging Details:
------------------


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
kmixer!MxCleanupRequest+23
b2026833 8b412c          mov     eax,dword ptr [ecx+2Ch]

EXCEPTION_RECORD:  b84fbc68 -- (.exr 0xffffffffb84fbc68)
ExceptionAddress: b2026833 (kmixer!MxCleanupRequest+0x00000023)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 00000000
   Parameter[1]: 0000002c
Attempt to read from address 0000002c

CONTEXT:  b84fb964 -- (.cxr 0xffffffffb84fb964)
eax=00000000 ebx=88cc5710 ecx=00000000 edx=88cc5700 esi=88b1f2e8 edi=88cc5858
eip=b2026833 esp=b84fbd30 ebp=b84fbd3c iopl=0         nv up ei pl zr na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010246
kmixer!MxCleanupRequest+0x23:
b2026833 8b412c          mov     eax,dword ptr [ecx+2Ch] ds:0023:0000002c=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_PARAMETER1:  00000000

EXCEPTION_PARAMETER2:  0000002c

READ_ADDRESS:  0000002c 

FOLLOWUP_IP: 
kmixer!MxCleanupRequest+23
b2026833 8b412c          mov     eax,dword ptr [ecx+2Ch]

BUGCHECK_STR:  0x7E

DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE

LAST_CONTROL_TRANSFER:  from b203738f to b2026833

STACK_TEXT:  
b84fbd3c b203738f 88cc5710 88cc5710 b84fbd64 kmixer!MxCleanupRequest+0x23
b84fbd4c b2026943 88cc5710 88d451d8 8a413e38 kmixer!MxCompleteRequest+0xf
b84fbd64 b74657ee 8a413d90 88d451b8 80564820 kmixer!FreeDeadIrps+0x43
b84fbd7c 8053877d 88d451b8 00000000 8a5b7020 ks!WorkerThread+0x45
b84fbdac 805cff70 88d451b8 00000000 00000000 nt!ExpWorkerThread+0xef
b84fbddc 805460ee 8053868e 00000000 00000000 nt!PspSystemThreadStartup+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  kmixer!MxCleanupRequest+23

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: kmixer

IMAGE_NAME:  kmixer.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  480254b3

STACK_COMMAND:  .cxr 0xffffffffb84fb964 ; kb

FAILURE_BUCKET_ID:  0x7E_kmixer!MxCleanupRequest+23

BUCKET_ID:  0x7E_kmixer!MxCleanupRequest+23

Followup: MachineOwner
---------

The problem is with kmixer.sys. This is Kernel Mode Audio Mixer. You may have a corrupted kmixer.sys file.

I would try reinstalling the audio drivers first. If that doesn't fix it, do this:

Go to Start > Run> and type in "sfc /scannow" without the quotation marks and hit enter. It takes a little while to run, so be paient. It may ask you for your windows cd, so have it handy in case you need it.

 

[GBear]

Well, my CPU temps are really cool. Q6600 OC'd to 3.0GHz runs around 21-25C idle

I'll try that for now s14sh3r, thanks

 

[Panzer Grenadier Ulrich]

do you sometimes get stars (static) appear on your screen before it blue screens?

 

[aknightwhosezni]

Well, my CPU temps are really cool. Q6600 OC'd to 3.0GHz runs around 21-25C idle

I'll try that for now s14sh3r, thanks

sweet, i have my q6600 at 3.43

 

[GBear]

do you sometimes get stars (static) appear on your screen before it blue screens?

No I don't.

 

[Panzer Grenadier Ulrich]

No I don't.

Typically if a graphics card is burning out or over heating the screen goes fuzzy and you slowly lose colour, so I dont think its your card, I have no idea what it is then. :confused1: Sorry, good luck

 

[s14sh3r]

Hey GBear, thought I'd check in and see how the comp is doing.

 

[GBear]

Oh, I found out what the problem was. A lot of people on the eVGA forums were having the same problem. It seems that I need to update my BIOS.

 

[s14sh3r]

Oh, I found out what the problem was. A lot of people on the eVGA forums were having the same problem. It seems that I need to update my BIOS.

Glad you got it fixed

 

[GBear]

Glad you got it fixed

Not too sure yet. I'll see what happens in the next few days.