Problems with 6860FX, any help?

I bought my 6860FX maybe a couple of months ago and ive had a couple problems. Every other day i get the blue screen of death and every time i try to boot it at after i get the blue screen again. However, if i wait like an hour it will typically boot up. I had this problem before. Thinking it was a virus i formatted my hard drive and i didnt put anything from the old hard drive to the clean formatted one and is it solved the problem for awhile. Do you think this is a virus again or something wrong with the laptop top? Also my power pack lately has been humming loudly. It is so loud that i can hear it over a tv and fans in the background so i only use it when needed. If anyone has any suggestions or help it would be much appreciated.
thanks

 

as to the blue screen there is small file it dumps in C:\WINDOWS\Minidump\ with the date of of the last crash, if you post it here some people may help with finding what actually causing it.

as to the power brick its a known issue, if you'll cal gateway and tell them its SO loud and SO hot... you might talk them into a replacement.
have been done b4.

 

Alot of us have started to upgrade to the 180watt power brick, due to the system draw. its pretty close to maxing a 120watt out. So the upgrade keeps the system powered nicely and the block quite cool to the touch

Pretty much a win win situation.

As to the BSOD... no idea.
The error codes will be helpful. But have you ran a scan of your HD. if parts of it are screwing up it might be as simple as a bum drive (its rare but does happen)

 

I am not really sure if this is the error codes you need to help me. I used the windows debugger and used the analyze command. If i need to do something different please help.

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

KMODE_EXCEPTION_NOT_HANDLED (1e)
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.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff8000227a7b3, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: ffffffffffffffff, Parameter 1 of the exception

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


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

FAULTING_IP:
nt!PoIdle+143
fffff800`0227a7b3 42ff54ef20 call qword ptr [rdi+r13*8+20h]

EXCEPTION_PARAMETER1: 0000000000000000

EXCEPTION_PARAMETER2: ffffffffffffffff

READ_ADDRESS: ffffffffffffffff

CUSTOMER_CRASH_COUNT: 5

DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT

BUGCHECK_STR: 0x1E

PROCESS_NAME: System

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff80002238e77 to fffff8000225f390

STACK_TEXT:
fffffa60`0191b3a8 fffff800`02238e77 : 00000000`0000001e ffffffff`c0000005 fffff800`0227a7b3 00000000`00000000 : nt!KeBugCheckEx
fffffa60`0191b3b0 fffff800`0225f1e9 : fffffa60`0191bae8 00000000`00000000 fffffa60`0191bb90 fffffa60`005efa00 : nt! ?? ::FNODOBFM::`string'+0x29317
fffffa60`0191b9b0 fffff800`0225ddcd : fffffa80`0500e140 00000000`00000003 00000000`00000140 6f007300`62004f00 : nt!KiExceptionDispatch+0xa9
fffffa60`0191bb90 fffff800`0227a7b3 : fffffa80`040e6040 fffffa60`005f5d40 fffffa60`0191bdb0 fffff800`02262a2d : nt!KiGeneralProtectionFault+0xcd
fffffa60`0191bd20 fffff800`02269b31 : fffffa60`005ec180 00000000`000112d9 00000000`00000000 00000000`00000005 : nt!PoIdle+0x143
fffffa60`0191bd80 fffff800`024375c0 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x21
fffffa60`0191bdb0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!zzz_AsmCodeRange_End+0x4


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!PoIdle+143
fffff800`0227a7b3 42ff54ef20 call qword ptr [rdi+r13*8+20h]

SYMBOL_STACK_INDEX: 4

SYMBOL_NAME: nt!PoIdle+143

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 4812c3f7

FAILURE_BUCKET_ID: X64_0x1E_nt!PoIdle+143

BUCKET_ID: X64_0x1E_nt!PoIdle+143

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

 

Bump, can anyone help?

 

I'm looking into it.

EDIT: Found this info:

"Probably caused by : ntkrnlmp.exe witch according to Microsoft has to do with

CAUSE
This problem occurs if one or more of the processors in the computer:
•Require a microcode update that is not applied by the computer's basic input/output system (BIOS).
•Are damaged or defective.
•Are operating outside their specified ranges for temperature, power, or other conditions."

HOWEVER, some are saying it is driver related, which I tend to believe more than a faulty CPU/BIOS, which rarely fail. If it were me, Id download the latest Intel chipset drivers and Matrix Storage Manager and try an updated video card driver.

 

IMHO, his PSU shouldn't be operatng as loudly as he says it is. I couldn't hear any noise from my stock PSU (unless I put me ear close to it) even before I started underclocking.

mjaisit, does your computer still BSOD when you are running from battery? Make sure you disconnect the power supply jack from the back of your notebook when you check. Uplugging the powersupply while leaving it plugged into your notebook might still cause problems if there is a short in your PSU. Also, even if your computer works fine when isolated from the PSU, it could still be that your PSU is fine, but there is a short between the power jack and the mobo. It would however, strongly suggest that there is a power/hardware problem -- something you should be talking to a Gateway tech about.

 

You indeed make a good point. I, somehow, missed the whole howling PS. That very well could be the problem.

 

Jeez, you posted that not 5 seconds after I hit the submit button

 

LOL. This was the first post active in my subscribed threads so I checked into it. Good timing, I rectum.

 

Ok guys i updated my drivers today and so far so good. I dont think it has anything to do with PSU because i do get the BSOD while running it off just the battery. Im hoping that updating the drivers is going to help. Though i could not update the Matrix Storage Manager. It was telling me my system didnt meet the minimum requirement.

 

Either you're missing a verb between "I" and "rectum" or you meant "reckon".
Here is a list of verbs you could use:
do
did
get
like
possess
see
etc..

 

Twas intentional. Apparently people still are baffled by my sense of humor.

 

Are you joking? I really can't tell.