BSOD

[Bendocherty]

Hi, I recently had BSOD problems, but they seemed to be fixed. However I have had another one which i have uploaded. Any suggestions please

 

[Bendocherty]

http://www.sevenforums.com/crashes-debugging/125770-bsod-just-after-start-up.html - link to the other problems I have had in the last 2 weeks

and I forgot to put the html perfmon report file in the zip so Iv attached it seperate

 

[wish]

Hello,
Your single dump have PAGE_FAULT_IN_NONPAGED_AREA (0x50) = can be caused by driver or bad memory.

Start troubleshooting by removing AVG and replace it with MSE because MSE could running better in kernel windows.
http://www.microsoft.com/security_essentials/

And update your Realtek Fast Ethernet NIC driver

Rtnicxp.sys  Fri May 30 08:12:11 2008

Then we'll see if the problem persist, enable driver verifier.
http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

Log

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

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffffde8, memory referenced.
Arg2: 00000000, value 0 = read operation, 1 = write operation.
Arg3: 828c23cc, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 00000000, (reserved)

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


READ_ADDRESS: GetPointerFromAddress: unable to read from 82971718
Unable to read MiSystemVaType memory at 82951160
 fffffde8 

FAULTING_IP: 
nt!RtlpCopyLegacyContextX86+18
828c23cc 8b88b4000000    mov     ecx,dword ptr [eax+0B4h]

MM_INTERNAL_CODE:  0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  chrome.exe

CURRENT_IRQL:  0

TRAP_FRAME:  9d43f7fc -- (.trap 0xffffffff9d43f7fc)
ErrCode = 00000000
eax=fffffd34 ebx=0001003f ecx=00010001 edx=9d63e3b0 esi=00010001 edi=9d43fb8c
eip=828c23cc esp=9d43f870 ebp=9d43f87c iopl=0         nv up ei pl zr na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00210246
nt!RtlpCopyLegacyContextX86+0x18:
828c23cc 8b88b4000000    mov     ecx,dword ptr [eax+0B4h] ds:0023:fffffde8=????????
Resetting default scope

EXCEPTION_RECORD:  9d43fce0 -- (.exr 0xffffffff9d43fce0)
ExceptionAddress: 6427cd94
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 00000000
   Parameter[1]: d068204a
Attempt to read from address d068204a

LAST_CONTROL_TRANSFER:  from 8284f638 to 8288e903

STACK_TEXT:  
9d43f7e4 8284f638 00000000 fffffde8 00000000 nt!MmAccessFault+0x106
9d43f7e4 828c23cc 00000000 fffffde8 00000000 nt!KiTrap0E+0xdc
9d43f87c 828c6b90 0001003f 9d43f8a4 828c691f nt!RtlpCopyLegacyContextX86+0x18
9d43f888 828c691f 00000001 fffffd34 001feaf0 nt!RtlpCopyLegacyContext+0x1d
9d43f8a4 828c6510 00000001 001feaf0 00000001 nt!RtlpCopyExtendedContext+0x5b
9d43fcc4 8284d036 9d43fce0 00000000 9d43fd34 nt!KiDispatchException+0x338
9d43fd2c 8284cfea 001feb34 6427cd94 badb0d00 nt!CommonDispatchException+0x4a
9d43fd34 6427cd94 badb0d00 00333000 00000000 nt!Kei386EoiHelper+0x192
WARNING: Frame IP not in any known module. Following frames may be wrong.
9d43fd38 badb0d00 00333000 00000000 00000000 0x6427cd94
9d43fd3c 00333000 00000000 00000000 00000000 0xbadb0d00
9d43fd40 00000000 00000000 00000000 00000000 0x333000


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!RtlpCopyLegacyContextX86+18
828c23cc 8b88b4000000    mov     ecx,dword ptr [eax+0B4h]

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  nt!RtlpCopyLegacyContextX86+18

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrpamp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c3fac

FAILURE_BUCKET_ID:  0x50_nt!RtlpCopyLegacyContextX86+18

BUCKET_ID:  0x50_nt!RtlpCopyLegacyContextX86+18

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

 

[Bendocherty]

Hi, iv installed MSE, unistalled AVG, and installed Driver Verifier. Would you like any info from driver verifier?

With the driver however, I tried navigating myself through the downloads page on the realtek website but im not sure what driver I need at all. In Device manager, its under network adaptors and then its called realtek RTL8139/810x Family Fast Ethernet NIC.

Any help will be excellent

 

[Tews]

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

upload any new .dmp files that driver verifier creates...

 

[Bendocherty]

Followed your instructions, cheers for the help btw

Another dmp file (it may have the previous one in it as well

Also, MSE found an error so I just clicked clean computer. I presumed this was the correct thing to do, but I wasnt sure if I should leave it all so driver verifier detects the errors for now?

 

[Tews]

Your .dmp file is blaming mcdbus.sys (MagicDisc) as the cause of your crash.... I suggest that you uninstall it for now and see if that resolves your problem ... Also, disable driver verifier for the time being...

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

DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
A device driver attempting to corrupt the system has been caught.  This is
because the driver was specified in the registry as being suspect (by the
administrator) and the kernel has enabled substantial checking of this driver.
If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA will
be among the most commonly seen crashes.
Arguments:
Arg1: 00000081, MmMapLockedPages called without MDL_MAPPING_CAN_FAIL
Arg2: 8b187a68, MDL address.
Arg3: 0000008a, MDL flags.
Arg4: 00000000, 0.

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

*** WARNING: Unable to verify timestamp for mcdbus.sys
*** ERROR: Module load completed but symbols could not be loaded for mcdbus.sys

BUGCHECK_STR:  0xc4_81

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

PROCESS_NAME:  System

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 82b7cf1f to 82924d10

STACK_TEXT:  
873279a8 82b7cf1f 000000c4 00000081 8b187a68 nt!KeBugCheckEx+0x1e
873279c8 82b89edb 8b187a68 a2d7efe0 9a3def68 nt!VerifierBugCheckIfAppropriate+0x30
873279e0 8c9d033f 8b187a68 00000000 9a3def68 nt!VerifierMmMapLockedPages+0x3e
WARNING: Stack unwind information not available. Following frames may be wrong.
87327c40 849f1f3a 7dce6500 87327cac 87327c84 mcdbus+0x1533f
87327c5c 849ef6f7 82319cc0 00000000 00000018 cdrom!RequestHandleGetDriveGeometry+0x40
87327cb0 849efa37 82319cc0 7dcf4b50 8227d448 cdrom!RequestProcessSerializedIoctl+0x518
87327cc4 82f63042 7dd82bb0 93afafe0 8227d448 cdrom!IoctlWorkItemRoutine+0x4b
87327ce0 82f630aa 822794c8 87327d00 82a68815 Wdf01000!FxWorkItem::WorkItemHandler+0xad
87327cec 82a68815 822794c8 8227d448 847e8020 Wdf01000!FxWorkItem::WorkItemThunk+0x19
87327d00 828b5f3b 93afafe0 00000000 847e8020 nt!IopProcessWorkItem+0x23
87327d50 82a566d3 00000001 a77ff34e 00000000 nt!ExpWorkerThread+0x10d
87327d90 829080f9 828b5e2e 00000001 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19


STACK_COMMAND:  kb

FOLLOWUP_IP: 
mcdbus+1533f
8c9d033f ??              ???

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  mcdbus+1533f

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: mcdbus

IMAGE_NAME:  mcdbus.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  49a3cf05

FAILURE_BUCKET_ID:  0xc4_81_VRF_mcdbus+1533f

BUCKET_ID:  0xc4_81_VRF_mcdbus+1533f

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

 

[wish]

Follow Tews advice to uninstall Magic Disc.

Hi, iv installed MSE, unistalled AVG, and installed Driver Verifier. Would you like any info from driver verifier?

With the driver however, I tried navigating myself through the downloads page on the realtek website but im not sure what driver I need at all. In Device manager, its under network adaptors and then its called realtek RTL8139/810x Family Fast Ethernet NIC.

Any help will be excellent

For your Realtek NIC driver, at the website navigate to :
Communication Network ICs -> Network Interface controller -> 10/100 Fast Ethernet -> PCI -> software

After update make sure the Realtek driver stamped 2010 at device manager.

 

[Bendocherty]

Follow Tews advice to uninstall Magic Disc.

For your Realtek NIC driver, at the website navigate to :
Communication Network ICs -> Network Interface controller -> 10/100 Fast Ethernet -> PCI -> software

After update make sure the Realtek driver stamped 2010 at device manager.

Iv unistalled Magic Disc. What you suggest I use as a cd virtual device, or should I just burn my ISO files im using to discs instead?

I followed your directions to the driver, chose the windows 7 one and installed it, however it doesnt have a 2010 driver stamp, it has

Driver date: 23/07/2009
Driver Version: 6.111.723.2009

I ran the driver update thing again incase it had to get a driver to update to the newest driver but it says that the driver is installed. Is this the latest driver?

Thanks

Ben

 

[wish]

Alright maybe 2009 is the latest driver for your Realtek. It's a year newer than your first attach (2008).
For Magic Disc software, just uninstall it for few days to see if the BSOD have gone.

 

[Bendocherty]

Alright maybe 2009 is the latest driver for your Realtek. It's a year newer than your first attach (2008).
For Magic Disc software, just uninstall it for few days to see if the BSOD have gone.

Brilliant, done that, hopefully no more bsods. Magicdisc uninstalled