Sign in with
Sign up | Sign in
Your question

Frequent BSOD- HELP!

Last response: in Graphics & Displays
Share
January 28, 2010 3:35:34 AM

Hey guys,

I'm new to this forum and excited to join this community. I am wondering if anyone has a solution to a problem I have right now. I bought a ATI 4860 video card and installed it on my computer last month. Last week I upgrade my OS from Windows Vista to Windows 7. Since then, every time I play any game a fan from my computer runs really fast then slow then fast. Starting yesterday I kept getting BSOD and got 2 more today. When I restart computer, the monitor is blank.

I took out the ATI card and put in my old NVIDIA card and then restarted my comp. The computer runs but ther monitor screen is blank and its blinking continuously. So i took out that video card too and booted off the onboard video card and the computer ran properly and i could get into the desktop and there was display on the monitor.


I was wondering if anyone can help me with this situation as I dont know what to do

Computer Specs:

Windows 7 64-bit
AMD X3
3.0GB RAM
ATI 4860 video card

More about : frequent bsod

a c 189 U Graphics card
January 28, 2010 4:37:10 AM

So, what is your PSU? brand? model?
January 28, 2010 5:21:49 AM


Well, we could starte by giving the maker and model of your mobo, ram, power supply, hard disk.
Related resources
January 28, 2010 5:29:58 AM

Hey
Sure I will give all that but my buddy was sayin that it could be the ATI video card since the Chipset on my motherboard is a NVIDIA. He said that mixing isnt good and that I have to use a NVIDIA video card. Is that true?

Motherboard: ASUS M2N68-LA
Motherboard Chipset: nVIDIA nForce 6150SE-430
BIOS Type: Award BIOS
Hard Disk: Hitachi Disk Drive (298GB)

Regarding power supply, I forgot what it is and I will have it to you first thing in the morning.
a b U Graphics card
January 28, 2010 5:43:04 AM

That's not true, you're buddy is a n00b.

Even if it ends up being a no-name PSU, find out the amp ratings per rail.

Also try cleaning out the old drivers next time, using something like Driver Cleaner Pro.
January 28, 2010 5:47:06 AM

Its not a no-name PSU, I just dont know if its a Thermaltake or a Corsair thats why Im not throwing a name. And its 500W

There were no old drivers. I installed the video card when I had Vista and it was running flawlessly. I then installed Windows 7 and the problems started
January 28, 2010 10:12:28 AM


And your RAM? 2x 1gb? DDR2 667? 800?

January 28, 2010 1:25:52 PM

RAM is 3gb
2x 1GB and 2x512MB both on DDR2 SDRAM
January 28, 2010 1:30:21 PM

whats the BSOD error stop code?

What is the driver / device it is messing up on?
January 28, 2010 1:36:33 PM

This is what I get after I finally get my computer to reset. When I get the BSOD, my computer turns off and wen i try to turn it back on, the computer will run but the monitor is blank and just blinking. After numerous resets or if I boot off onboard video card, I can get to desktop and this is what it shows me:

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.1
Locale ID: 1033

Additional information about the problem:
BCCode: 1000007e
BCP1: FFFFFFFFC0000005
BCP2: FFFFF80002AC6105
BCP3: FFFFF8800318D338
BCP4: FFFFF8800318CB90
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\010108-20280-01.dmp
C:\Users\Home\AppData\Local\Temp\WER-35209-0.sysdata.xml
January 28, 2010 1:44:27 PM

do you use the program easy file and folder protector?

could you open the C:\Windows\Minidump\010108-20280-01.dmp wih a text edior and see what it says inside? looking for sys files or things like that.
January 28, 2010 1:53:40 PM

So i tried turning on my computer right now for the first time (since last night) and once again the problem occurerd. The computer will turn on but nothing on the monitor display. I have to boot off the onboard video card if I want to see anything
January 28, 2010 1:59:16 PM

Now it wont even boot off the integrated video. I took out the video card and plugged the monitor cable on the onboard video card slot and turned on the computer but nothing on display and monitor light just blinks.
January 28, 2010 2:33:16 PM

Depends on how comfortable you are with getting into the machine. Try unplugging the power from the mother board and waiting till the heart beat light goes out. Then plug the power back in. Some times that fixes some issues with some things. That may get your video back.
January 28, 2010 2:47:38 PM

But that will only get the video back right? It still wont solve the issue Im having...:( 
January 28, 2010 5:12:20 PM

Will going back to Vista solve anything? His computer was perfectly fine when Vista was running. The problem only started after I installed Windows 7. Either that or the BIOS has the onboard video card enabled. But I dont know how to change that since there is no option in the BIOS
January 29, 2010 12:10:46 AM


Ok, I just simulated the error code, I think its a memory problem, hope you could try this.

Remove your 4 pcs RAM, clean the pins and sockets, re-install the ram.

If still does not work, try to isolate each RAM, by installing a Single RAM into a channel/socket, and then the other ram, until you could get what RAM was causing the problem.

Let me know...
January 29, 2010 1:16:18 AM

Vaughn2K, what error code did you simulate?

So basically put the ATI back in the slot and run with only a single RAM?
January 29, 2010 3:14:09 AM

This is what I get when I ran Windows Debugging Tool


Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\010108-20280-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (3 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02a51000 PsLoadedModuleList = 0xfffff800`02c8ee50
Debug session time: Wed Jan 27 21:14:23.585 2010 (GMT-5)
System Uptime: 0 days 3:32:30.801
Loading Kernel Symbols
...............................................................
................................................................
......................
Loading User Symbols
Loading unloaded module list
.........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff80002ac6105, fffff8800318d338, fffff8800318cb90}

Probably caused by : ntkrnlmp.exe ( nt!ExpInterlockedPopEntrySListFault16+0 )

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

0: 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: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80002ac6105, The address that the exception occurred at
Arg3: fffff8800318d338, Exception Record Address
Arg4: fffff8800318cb90, 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:
nt!ExpInterlockedPopEntrySListFault16+0
fffff800`02ac6105 498b08 mov rcx,qword ptr [r8]

EXCEPTION_RECORD: fffff8800318d338 -- (.exr 0xfffff8800318d338)
ExceptionAddress: fffff80002ac6105 (nt!ExpInterlockedPopEntrySListFault16)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT: fffff8800318cb90 -- (.cxr 0xfffff8800318cb90)
rax=000000125384001c rbx=0000000000001000 rcx=fffff80002c49b90
rdx=00fffa8002f07001 rsi=0000000000000001 rdi=0000000000000000
rip=fffff80002ac6105 rsp=fffff8800318d570 rbp=fffff8800318d5c0
r8=00fffa8002f07000 r9=0000000063416d4d r10=fffff80002c49b90
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000063416d4d
iopl=0 nv up ei pl nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010206
nt!ExpInterlockedPopEntrySListFault16:
fffff800`02ac6105 498b08 mov rcx,qword ptr [r8] ds:002b:00fffa80`02f07000=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: chrome.exe

CURRENT_IRQL: 0

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

EXCEPTION_PARAMETER1: 0000000000000000

EXCEPTION_PARAMETER2: ffffffffffffffff

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cf90e0
ffffffffffffffff

FOLLOWUP_IP:
nt!ExpInterlockedPopEntrySListFault16+0
fffff800`02ac6105 498b08 mov rcx,qword ptr [r8]

BUGCHECK_STR: 0x7E

LAST_CONTROL_TRANSFER: from fffff80002bf24b1 to fffff80002ac6105

STACK_TEXT:
fffff880`0318d570 fffff800`02bf24b1 : 00000000`00000000 00000000`0000000e 00000000`00000001 00000000`00040004 : nt!ExpInterlockedPopEntrySListFault16
fffff880`0318d580 fffff800`02ad5860 : 00000000`00001000 fffff800`02c50880 00000000`00000000 655d2ac6`00000000 : nt!MiAllocatePoolPages+0xa1
fffff880`0318d6d0 fffff800`02bf5bfe : 00000000`00000000 00000000`00000000 00000000`00000000 fffff800`02c50880 : nt!ExpAllocateBigPool+0xb0
fffff880`0318d7c0 fffff800`02bc7a24 : fffffa80`00040004 00000000`00001000 00000000`00000000 00000000`00000000 : nt!ExAllocatePoolWithTag+0x82e
fffff880`0318d8b0 fffff800`02bc7bf6 : fffffa80`02afb000 00000000`00006485 fffff680`0009f5e8 00000000`00000000 : nt!MiAllocateAccessLog+0xb4
fffff880`0318d8e0 fffff800`02b2b1d8 : 00000003`00000000 c8500000`a6549867 00000000`00000000 00000000`00006485 : nt!MiLogPageAccess+0x46
fffff880`0318d930 fffff800`02b43a0e : fffffa80`060249c8 fffff880`00000001 00000000`00000001 fffff880`0318dbb0 : nt! ?? ::FNODOBFM::`string'+0x21846
fffff880`0318dae0 fffff800`02ad76e2 : 00000000`000031cf 00000000`00000000 fffffa80`00000000 00000000`00000004 : nt! ?? ::FNODOBFM::`string'+0x49926
fffff880`0318db80 fffff800`02ad796f : 00000000`00000008 fffff880`0318dc10 00000000`00000001 fffffa80`00000000 : nt!MmWorkingSetManager+0x6e
fffff880`0318dbd0 fffff800`02d66166 : fffffa80`025d9680 00000000`00000080 fffffa80`024d6040 00000000`00000001 : nt!KeBalanceSetManager+0x1c3
fffff880`0318dd40 fffff800`02aa1486 : fffff800`02c3be80 fffffa80`025d9680 fffff800`02c49c40 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`0318dd80 00000000`00000000 : fffff880`0318e000 fffff880`03188000 fffff880`0318d710 00000000`00000000 : nt!KxStartSystemThread+0x16


SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt!ExpInterlockedPopEntrySListFault16+0

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc600

STACK_COMMAND: .cxr 0xfffff8800318cb90 ; kb

FAILURE_BUCKET_ID: X64_0x7E_nt!ExpInterlockedPopEntrySListFault16+0

BUCKET_ID: X64_0x7E_nt!ExpInterlockedPopEntrySListFault16+0

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






Looking from this I can see that ntkrnlmp.exe is causing the problem. But what the hell is that?
January 29, 2010 12:52:43 PM

vaughn2k said:
"Vaughn2K, what error code did you simulate?

So basically put the ATI back in the slot and run with only a single RAM? "

- the BCCODE

- Run each Single RAM to check which one is faulty...

- Yup, either you have a BIOS problem or one of your four RAMs are faulty.

http://support.microsoft.com/kb/318729

http://superuser.com/questions/31410/blue-screen-error-...




So I ran MemTest 86+ for 10 hours and I got 10 passes and no errors. Does that mean my RAM is fine?
a c 271 U Graphics card
January 29, 2010 1:20:22 PM

@ flyingdutchman7588, do you have google chrome installed?

a c 271 U Graphics card
January 29, 2010 1:28:38 PM

flyingdutchman7588 said:
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: chrome.exe

CURRENT_IRQL: 0

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

I would try un installing chrome to see if that made the problem go away.
January 29, 2010 2:00:42 PM

Oh ok. Also What is that VISTA_DRIVER_FAULT??
I have no traces of Windows Vista on the PC since I did a fresh clean install of Windows 7
a c 271 U Graphics card
January 29, 2010 2:05:37 PM

W7 and Vista are pretty much the same thing, think of W7 as Vista SP3.
January 29, 2010 3:24:23 PM

I have attached two files here

The first one shows the driver version of the ATI video card. Is that the most recent version because I cannot find the latest version anywhere on google. When I go to the ATI website it tells me to download 10.1 Catalyst Control Centre which is what I have

The second one shows ATI Overdrive UI and if you look at Fan Control, the slider is at 50% but the fan picture on the right isnt spinning and is showing 0%. The video card on my fan is running though. Any ideas?



January 29, 2010 6:03:45 PM

any ideas?

Also does the PSU have to do with anything?

I have a Thermaltake TR2 430W PSU
February 1, 2010 5:50:17 AM

I am not sure if the MEMTEST86 can detect the problem. Had an experience before and replacing the RAM just made the problem go away.

Did you still try to remove the 2pcs 512MB? or tried running only 1gb then 2 gb?
!