Find your solution!

virtualQ · 03-Jun-2009, 10:32 AM #1

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.

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? I suspect the motherboard, but it could also be a software problem even though I have the latest drivers.

Please tell me if you need more info. I'm currently running a hard drive test.
I have also analyzed one of the minidumpfiles which said that it was the driver win32k.sys that was the problem. But just as I said it is different drivers almost every time.

ashwinsharma2100 · 03-Jun-2009, 02:22 PM #2

It may be because of RAM.
check using windows diagnostic. it is a memory diagnostic tool.
actually this problem is emerging very common.
Do one thing
When did the problem begin? Have you tried a System Restore to a date when things worked?

*A look at the minidump files may help:*

I can run a debugging utility on the dump files if you do this:

1 > create a new folder on the desktop and call it "dumpcheck" or whatever you like
2 > navigate to *c:\windows\minidump *and copy the last few minidump files to that folder. *this assumes 'c' is your boot drive, if it is not, subsitute accordingly
3 > close the folder and right click on it and select *Send to* Compressed (zipped) Folder.
4 > use the "manage attachments" in the "advanced" reply window to upload that zip file here as an attachment.

This might point us to a non Microsoft driver causing the error, if one exists for it.

>>>>>>>

*Have you also tested startups in Safe Mode (both with and without Networking Support)?

virtualQ · 03-Jun-2009, 02:49 PM #3

Hi!
Okej, But I have run memtest as I said, wouldn't it test the same as windows memory diagnostic?

I have analysed a minidump with windbg, but can post the file if you have some other software to analyze it.

The code I got from windbg:

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`028e0125 498b08 mov rcx,qword ptr [r8]

CONTEXT: fffff88006d76260 -- (.cxr 0xfffff88006d76260)
rax=0000031dc4740006 rbx=fffff88006d76d00 rcx=fffffa80053c8d50
rdx=12152125175e2101 rsi=0000000000000004 rdi=00000000000000d8
rip=fffff800028e0125 rsp=fffff88006d76c40 rbp=fffffa80053c8d50
r8=12152125175e2100 r9=000000007fffffff r10=fffffa80053c8d50
r11=fffff900c1ff6010 r12=0000000000000000 r13=fffff88006d76e70
r14=fffff900c239b590 r15=0000000000000000
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`028e0125 498b08 mov rcx,qword ptr [r8] ds:002b:12152125`175e2100=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x3B

PROCESS_NAME: msnmsgr.exe

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff960000e24e5 to fffff800028e0125

STACK_TEXT:
fffff880`06d76c40 fffff960`000e24e5 : 00000000`00000000 fffff960`000b5d85 fffff900`c0081054 fffff900`c2061420 : nt!ExpInterlockedPopEntrySListFault16
fffff880`06d76c50 00000000`00000000 : fffff960`000b5d85 fffff900`c0081054 fffff900`c2061420 00000000`00000000 : win32k+0xb24e5

FOLLOWUP_IP:
win32k+b24e5
fffff960`000e24e5 ?? ???

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: win32k+b24e5

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: win32k

IMAGE_NAME: win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4a0a3ad0

STACK_COMMAND: .cxr 0xfffff88006d76260 ; kb

FAILURE_BUCKET_ID: X64_0x3B_win32k+b24e5

BUCKET_ID: X64_0x3B_win32k+b24e5

Followup: MachineOwner

EDIT: I will also stress that this computer is entirely new. So it has just been running for a month. But the problems was occurring from the very start when I had Vista x64 installed. We gave up and installed Windows 7 x64 but the problems remained.

virtualQ · 05:56 PM

I got one more BSOD today. Can somenone please help me with this problem!
EDIT: memory diagnostic tool came out with no errors.

Here is the debugger info:

EXCEPTION_RECORD: fffff880072353d8 -- (.exr 0xfffff880072353d8)
ExceptionAddress: fffff80002b91bb0 (nt!FsRtlNotifyFilterReportChange+0x0000000000000124)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 0000000000000000
Attempt to read from address 0000000000000000

CONTEXT: fffff88007234c30 -- (.cxr 0xfffff88007234c30)
rax=0000000000000000 rbx=fffffa80040b8660 rcx=000000000000007a
rdx=fffffa8004a756a8 rsi=fffff8a00148d960 rdi=0000000000000000
rip=fffff80002b91bb0 rsp=fffff88007235610 rbp=fffffa8003fe8010
r8=fffff8a00983c340 r9=fffff8a00983c340 r10=fffffa8004a75180
r11=0000000000000010 r12=fffff8a006bc3358 r13=fffffa80048fd830
r14=000000000000001c r15=0000000000000001
iopl=0 nv up ei ng nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010282
nt!FsRtlNotifyFilterReportChange+0x124:
fffff800`02b91bb0 663938 cmp word ptr [rax],di ds:002b:00000000`00000000=????
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: NULL_DEREFERENCE

PROCESS_NAME: svchost.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_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_PARAMETER1: 0000000000000000

EXCEPTION_PARAMETER2: 0000000000000000

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002aba0e0
0000000000000000

FOLLOWUP_IP:
Ntfs!NtfsReportDirNotify+24c
fffff880`012193ac 488b9424d8000000 mov rdx,qword ptr [rsp+0D8h]

FAULTING_IP:
nt!FsRtlNotifyFilterReportChange+124
fffff800`02b91bb0 663938 cmp word ptr [rax],di

BUGCHECK_STR: 0x24

LAST_CONTROL_TRANSFER: from fffff880012193ac to fffff80002b91bb0

STACK_TEXT:
fffff880`07235610 fffff880`012193ac : fffffa80`048fd830 fffffa80`04a756a8 fffff8a0`0983c340 fffff8a0`0028001c : nt!FsRtlNotifyFilterReportChange+0x124
fffff880`07235750 fffff880`012e16b4 : fffff8a0`00000000 fffff8a0`0983c3a8 fffff880`06123490 fffff8a0`0983c340 : Ntfs!NtfsReportDirNotify+0x24c
fffff880`07235820 fffff880`012c2ea4 : fffffa80`05dcce40 fffff880`06123490 fffffa80`05dcce40 fffff8a0`06699a01 : Ntfs!NtfsCreateNewFile+0xb34
fffff880`07235b50 fffff880`01214b9d : fffffa80`05dcce40 fffffa80`03fe8010 fffff880`06123490 fffffa80`03aefb00 : Ntfs!NtfsCommonCreate+0xef4
fffff880`07235d30 fffff800`0288c207 : fffff880`06123400 00000000`00000000 00000000`00000000 00000000`00000000 : Ntfs!NtfsCommonCreateCallout+0x1d
fffff880`07235d60 fffff800`0288c1c1 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KySwitchKernelStackCallout+0x27
fffff880`061232d0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSwitchKernelStackContinue

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: Ntfs!NtfsReportDirNotify+24c

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: Ntfs

IMAGE_NAME: Ntfs.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 49ee8de7

STACK_COMMAND: .cxr 0xfffff88007234c30 ; kb

FAILURE_BUCKET_ID: X64_0x24_Ntfs!NtfsReportDirNotify+24c

BUCKET_ID: X64_0x24_Ntfs!NtfsReportDirNotify+24c

Followup: MachineOwner

Lee_BNY · 04-Jun-2009, 08:29 PM #5

Hi there

When do the BSOD occur? before the boot process or after?
Any beep codes during the boot process?
When was the last time the system was working properly?
Where there any outages/upgrades/maintenance did to the machine?

virtualQ · 05-Jun-2009, 06:29 AM #6

Hi Lee!

It's a brand new computer so the system was built with this specs from the beginning. The bluescreens was occurring from the start. There is none problem during the boot process. The BSOD's occur usually at very random times. The system have with other words never worked properly.

Lee_BNY · 02:59 PM

Virtual

"Access violation in svchost looks like a virus."

Open up Task Manager,
go to Processes tab, and sort by CPU %.

See if an svchost is spiking hard (over 80%)

If it is... google "svchost cpu" and find a good reference for removing what's causing the problem.
Had that issue a while back... I'ts not just the svchost.

All agree?

virtualQ · 05-Jun-2009, 08:24 PM #8

No there is no such svchost process that take so much cpu time. But I will do a virus scan with malwarebytes and se if it finds something. But since I had this problem from the start, it rather feels like a hardware error. I will test to run this computer with one stick of 1GB memory and see if it solves the problem. Otherwise I'll come back to this thread again.

Lee_BNY · 16-Jun-2009, 10:51 AM #9

Did you ever get your issue fixed?

virtualQ · 16-Jun-2009, 03:26 PM **#10**

I thought it was fixed since I hadn't any bluescreens in a week. But today I got a bluescreen. I will upload the debugged code so that someone can analyze it.

virtualQ · 25-Jun-2009, 01:37 PM **#11**

Here are the dumpfiles to the latest BSOD's. Hope someone is willing to analyze them.

virtualQ · 02-Jul-2009, 10:41 AM **#12**

I know that there are people that is capable of helping me with this prob.

Please give me som advice

**Rollin' Rog** · 11:09 AM

My gander at the variety of bugchecks you have there is that they are all consistent with hardware faults -- either ram or display memory. If not bad or mismatched, then overclocked.

I see RivaTuner64.sys in the trapframe of the last, which suggests you have overclocking drivers loaded if not actually being used.

Make sure everything is set to defaults.

I also see this in the trapframe of the fault when you are playing WOW >> ISODrv64.sys; I don't know if or how it is being used.

virtualQ · 02-Jul-2009, 11:14 AM **#14**

Hi!
Yes, the errors seems to be related to hardware errors. BUT the frustrating part is that memory have been tested with memtest with no errors. It ran 11 rounds. And windows memory diagnostic also came out clean. We have tested the computer running only one stick of memory but it still did BSOD.

The Graphic card was in for RMA but came back because they couldn't find any errors. So the problem is probably very very tiny.

**Rollin' Rog** · 03-Jul-2009, 12:08 PM **#15**

What about the overclocking question?

Is the motherboard SLI enabled? If so, disable that at the BIOS level.

If home built -- do look for possible overheating issues. You might want to monitor with something like "speedfan" and look for any rise of more than 30c from a completely cold boot.

http://www.majorgeeks.com/download337.html

If there is any chance you can try a clean install with a 32 bit version of Windows, I would recommend that too. Some of these issues seem to be more common on 64 bit Vista and probably Win7 as well.

If you can't resolve this, consider RMA'ing the motherboard as well.

And test with a "Clean Boot" >>

Run msconfig and select the "Services" tab. Check "Hide Microsoft Services" and then disable the rest. Also uncheck "load startup group" on the general page.

Now restart and test the issue at hand

If no problems, run msconfig and recheck half the disabled items on the Services tab. Test again. If the problem recurs, UNcheck half the items you just checked to narrow down the culprit.

If the problem didn't occur, check the other half, so all the Services are enabled -- proceed to do this on the startup tab as well.

Get the idea? You want to isolate the problem to a specific startup if possible.

Note: if you already have items unchecked under msconfig > startups and are in “selective” startup mode – you should note what these are before beginning. They will need to be de-selected again.

http://support.microsoft.com/kb/929135 << written for Vista but apples equally to XP

Tag Cloud
adware audio bios blue screen boot bsod computer connection crash dell desktop driver email error excel firefox freeze google hard drive hardware hijackthis install internet laptop linux malware network no sound outlook problem recovery router screen server slow sound speakers spyware startup trojan usb video virus vista webcam windows windows 7 windows vista windows xp wireless

Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)

Search
Search for: