2 BSODs 2 Days

Is Windows 7 . . .
- x86 (32-bit) or x64 ? 64
- the original installed OS on the system? W7
- an OEM or full retail version? Full retail
- OEM = came pre-installed on system
- Full Retail = you purchased it from retailer

- What is the age of system (hardware)? September 2009
- What is the age of OS installation (have you re-installed the OS?) Same time as above

Well I've had 2-3 sets of RAM sent back since I built this PC because it's been faulty and god knows how many BSODs. Had one yesterday at 8:25am I thought "one off" I turned pc on this morning from sleep mode (7am) and had another BSOD.

The most recent BSOD:

Code:

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

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000000000000028, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
	bit 0 : value 0 = read operation, 1 = write operation
	bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80002f19518, address which referenced memory

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


READ_ADDRESS:  0000000000000028 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!MiFindNodeOrParent+0
fffff800`02f19518 48f7412800ffffff test    qword ptr [rcx+28h],0FFFFFFFFFFFFFF00h

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  CurseClient.ex

TRAP_FRAME:  fffff880099a72d0 -- (.trap 0xfffff880099a72d0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002f19518 rsp=fffff880099a7468 rbp=0000000000000000
 r8=fffff880099a74b0  r9=0000000000000000 r10=fffffa80051528f0
r11=fffffa8004be4070 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
nt!MiFindNodeOrParent:
fffff800`02f19518 48f7412800ffffff test    qword ptr [rcx+28h],0FFFFFFFFFFFFFF00h ds:00000000`00000028=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002ed6ca9 to fffff80002ed7740

STACK_TEXT:  


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiFindNodeOrParent+0
fffff800`02f19518 48f7412800ffffff test    qword ptr [rcx+28h],0FFFFFFFFFFFFFF00h

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!MiFindNodeOrParent+0

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0xA_nt!MiFindNodeOrParent+0

BUCKET_ID:  X64_0xA_nt!MiFindNodeOrParent+0

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

And the one yesterday:

Code:

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

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000003452, The subtype of the bugcheck.
Arg2: 0000000077753000
Arg3: fffff70001080718
Arg4: 8520000128143004

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


BUGCHECK_STR:  0x1a_3452

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  chrome.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002f43073 to fffff80002ecf740

STACK_TEXT:  


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+339e3
fffff800`02f43073 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+339e3

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9

FAILURE_BUCKET_ID:  X64_0x1a_3452_nt!_??_::FNODOBFM::_string_+339e3

BUCKET_ID:  X64_0x1a_3452_nt!_??_::FNODOBFM::_string_+339e3

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

I bought a new sound card, last week? So therefore drivers, it is a: Asus Xonar DG 5.1 PCI Sound Card with built in Headphone Amp


Gigabyte GA-MA790X-UD3P AMD 790X Socket AM2+ High Def Audio ATX Motherboard
AMD Phenom II X4 955 Black Edition 3.2 GHz Socket AM3 8MB Cache Retail Boxed Processor
XFX HD 4890 1GB GDDR5 Dual DVI HDTV Out PCI-E Graphics Card
Coolermaster RealPower 700W Modular PSU - SLI Ready
Crucial 4GB (2X2GB) DDR2 800MHz/PC2-6400 Ballistix Memory CL4 2.0V
Western Digital WD1001FALS 1TB Hard Drive SATAII 7200rpm 32MB Cache - OEM Caviar Black

I also have MSE installed as the report says otherwise.

It couldn't happen at a worst time of the year could it.. xmas!

Thanks a lot

The second dump blames memory corruption, test your RAM
RAM - Test with Memtest86+


MarvinBus64.sys is most likely related to Pinnacle so i would recommend to update those drivers are well Pinnacle Systems - Product Support

Code:

MarvinBus64.sys        fffff880`05366000    fffff880`053aa000    0x00044000    0x433470cf    24/09/2005 01:17:03

Lomai said:

Hi oli

Welcome to Seven Forums.
I have requested assistance from the BSOD Crew so hang in there :)
Whatever the outcomes, wish you a Merry Christmas and Happy Holidays

Thanks, you too

yowanvista said:

The second dump blames memory corruption, test your RAM
RAM - Test with Memtest86+


MarvinBus64.sys is most likely related to Pinnacle so i would recommend to update those drivers are well Pinnacle Systems - Product Support

Code:

MarvinBus64.sys        fffff880`05366000    fffff880`053aa000    0x00044000    0x433470cf    24/09/2005 01:17:03

Thanks for really quick response :)

Stupid RAM -.- If it's faulty again I have no idea what's up with it because it will be the 4th time or something. And as it's Christmas, RMA won't exactly happen.

Trying to load up that pinnacle systems link, though site isn't loading. I actually don't need/use the software any more, I did remove it. Will remove driver now, somehow missed that

Will have a look up on what way the link suggests to test RAM, always this 1 stick or two stick at a time problem!

Ty

For reference - two previous threads with what I believe is the same system:

Windows 7 64bit Ultimate BSOD - Tech Support Forum

[SOLVED] BSOD's Once Again - Tech Support Forum

Remove that new sound card for now, it may be the problem here.

Also - run me through what hardware is still unchanged from the original system build, and exactly what you have replaced or added.

There's a few more threads over there about BSODs.

Counted 5 threads.

Aww About sound card. Should I remove drivers as well? As its only been 2 BSODs though, might not come back leaving me in a "Was it the sound card?" situation.

Everything is uncharged apart from the RAM. The RAM has been replaced with the same RAM (RMA)
The last time it happened I also looked into RAM voltages and quite sure I set them correctly as well

kcmartz said:

With Sunbelt VIPRE I haven't gottten a single virus/bsod :)

Sent From my VM Samsung Intercept via Tapatalk

Anti-viruses don't generally cause BSODs do they now?

Drivers or hardware is the main fault I would imagine

oli356 said:

There's a few more threads over there about BSODs.

Counted 5 threads.

Aww About sound card. Should I remove drivers as well? As its only been 2 BSODs though, might not come back leaving me in a "Was it the sound card?" situation.

Everything is uncharged apart from the RAM. The RAM has been replaced with the same RAM (RMA)
The last time it happened I also looked into RAM voltages and quite sure I set them correctly as well

kcmartz said:

With Sunbelt VIPRE I haven't gottten a single virus/bsod :)

Sent From my VM Samsung Intercept via Tapatalk

Anti-viruses don't generally cause BSODs do they now?

Drivers or hardware is the main fault I would imagine

Antiviruses do cause BSODs but in your case none was blamed in the dmps

oli356 said:

Drivers or hardware is the main fault I would imagine

Correct. I have actually seen VIPRE cause a few BSODs though...

Given that they appeared again after months of absence - I do have to suspect the latest bit of hardware which of course is your sound card.

reventon said:

oli356 said:

Drivers or hardware is the main fault I would imagine

Correct. I have actually seen VIPRE cause a few BSODs though...

Given that they appeared again after months of absence - I do have to suspect the latest bit of hardware which of course is your sound card.

Oh right, wouldn't think they would cause them

Well my last BSOD before this one was 18th November

Though I can't see a thread about it. (EDIT: I just remembered I was speaking with Jonathan (from the forums) when they happened.
As far as I remember a chkdsk actually stopped them and a uninstall of logmeinpro. I have 10 dumps from that date.

Done:
Removed pinnacle drivers

To do
See if graphics card drivers need updating (CCC)

Should I?
Remove sound card and drivers and see if problems arise
or
Do a memtest (would rather not considering it takes all day)
or
Both?

Thanks