BSOD MRVW24C.sys

flarosie said:

I've gotten 4x BSOD errors today (1 actually happened while running the Windows NT6 BSOD thing...) and 2 complete system freezes.

This hasn't happened before today and the ONLY thing I can guess to be the culprit is Dropbox. I started transferring a ton of work files to it last night and that's when the first crash happened (according to the logs it was around 2:30am). The 3 others happened while I was actually working, along with the 2x complete freezes.

I'm running Windows 7 Professional x64, OEM, 9 days since I last re-formatted (installed Adobe CS5 for work) and this is a fairly recent build, so judging by Newegg history...software is about 9 months old.

I really need some help to get this problem fixed! Please let me know if there's any more information you need.

Thanks in advance for the help! :)

Rosie

RFosie

Hi and welcome

You have uploaded the application instead of the results try this method.





To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.

The procedure:

* Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
* Zip up the copy.
* Attach the ZIP archive to your post using the "paperclip" (file attachments) button.



To ensure minidumps are enabled:

Go to Start, in the Search Box type: sysdm.cpl, press Enter.
Under the Advanced tab, click on the Startup and Recovery Settings... button.
Ensure that Automatically restart is unchecked.
Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
OK your way out.
Reboot if changes have been made.

Thanks a bunch for the quick reply, here's the Minidump files you requested. And there's a 5th one in there since I got another BSOD error about 10 minutes ago...

Please let me know if you need anything else!

Rosie

flarosie said:

Thanks a bunch for the quick reply, here's the Minidump files you requested. And there's a 5th one in there since I got another BSOD error about 10 minutes ago...

Please let me know if you need anything else!

Rosie

All of these virtually identical and caused by your Linksys driver (MRVW24C.sys ). Reinstall the newest version available

Code:

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


Loading Dump File [C:\Users\K\Desktop\Minidump\051011-19032-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;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0xfffff800`02e5c000 PsLoadedModuleList = 0xfffff800`030a1e90
Debug session time: Tue May 10 20:58:36.322 2011 (GMT-4)
System Uptime: 0 days 1:42:43.353
Loading Kernel Symbols
...............................................................
................................................................
.........................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {8, 2, 0, fffff8800579a349}

Unable to load image \SystemRoot\system32\DRIVERS\MRVW24C.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for MRVW24C.sys
*** ERROR: Module load completed but symbols could not be loaded for MRVW24C.sys
Probably caused by : MRVW24C.sys ( MRVW24C+a349 )

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

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
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 kernel debugger is available get stack backtrace.
Arguments:
Arg1: 0000000000000008, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff8800579a349, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff8000310d0e8
 0000000000000008 

CURRENT_IRQL:  2

FAULTING_IP: 
MRVW24C+a349
fffff880`0579a349 4c8b7608        mov     r14,qword ptr [rsi+8]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  System

TRAP_FRAME:  fffff80000b9c310 -- (.trap 0xfffff80000b9c310)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000002 rbx=0000000000000000 rcx=fffffa8006983078
rdx=fffffa8006981802 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8800579a349 rsp=fffff80000b9c4a0 rbp=0000000000000000
 r8=0000000000000000  r9=0000000000000000 r10=fffff80002e5c000
r11=0000000000000002 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
MRVW24C+0xa349:
fffff880`0579a349 4c8b7608        mov     r14,qword ptr [rsi+8] ds:00000000`00000008=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002edbbe9 to fffff80002edc640

STACK_TEXT:  
fffff800`00b9c1c8 fffff800`02edbbe9 : 00000000`0000000a 00000000`00000008 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff800`00b9c1d0 fffff800`02eda860 : 00000000`00000000 fffff800`0304ee80 fffffa80`04002d80 fffffa80`068c2000 : nt!KiBugCheckDispatch+0x69
fffff800`00b9c310 fffff880`0579a349 : 00000000`00000000 00000000`00000000 fffffa80`06985138 fffffa80`068c2000 : nt!KiPageFault+0x260
fffff800`00b9c4a0 00000000`00000000 : 00000000`00000000 fffffa80`06985138 fffffa80`068c2000 fffffa80`0a01c250 : MRVW24C+0xa349


STACK_COMMAND:  kb

FOLLOWUP_IP: 
MRVW24C+a349
fffff880`0579a349 4c8b7608        mov     r14,qword ptr [rsi+8]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  MRVW24C+a349

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: MRVW24C

IMAGE_NAME:  MRVW24C.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  472551f7

FAILURE_BUCKET_ID:  X64_0xD1_MRVW24C+a349

BUCKET_ID:  X64_0xD1_MRVW24C+a349

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

I had a feeling that maybe my Wireless Router was the culprit... I uninstalled the Network adapter via Device Manager then rebooted and let Windows install the driver needed itself (see pics).

I'll leave my computer on overnight again and I'll let you know if the crashing continues or not.

Thanks!

Rosie

So far, so good!

I really think my wireless adapter and Dropbox were having some sort of conflict. I lowered the upload limit and the amount of files I was uploading overnight and woke up to my desktop...just where I left it! phew

I think I'll just need to handle my Dropbox uploads in small pieces instead of dumping everything in there all at once. I guess my wireless adapter just wasn't agreeing with the amount of work I was telling it to do as once, so it kept crashing? I don't know! But that's what my guess it.

Thanks for the help! If anything else quirky happens then I'll be back for sure, haha

Rosie

Good Luck sounds like a plan


Ken