[SERVER-16854] Production MongoDB 2.6.2 Server Crashes Frequently- please help!! Created: 14/Jan/15  Updated: 14/Jan/15  Resolved: 14/Jan/15

Status: Closed
Project: Core Server
Component/s: Stability
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: srini eadha Assignee: Unassigned
Resolution: Done Votes: 0
Labels: Windows
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Windows Server 2012 Standard


Operating System: Windows
Steps To Reproduce:

This happens unexpectedly at random times, but frequently.

Participants:

 Description   

Environment: Windows 2012 Server
Drive: SSD
MongoDB Server version: 2.6.2

Frequently getting BLUE screen and system rebooting unexpectedly,
The mongodb.exe process causing this issue, following is the memory dump analysis, please check the Process _Name

 
*******************************************************************************
*                                                                             *
*                        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: 0000000000000002, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff88000b74a38, address which referenced memory
 
Debugging Details:
------------------
 
 
READ_ADDRESS:  0000000000000002 
 
CURRENT_IRQL:  2
 
FAULTING_IP: 
storport!RaidUnitCompleteRequest+f8
fffff880`00b74a38 807f0228        cmp     byte ptr [rdi+2],28h
 
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
 
BUGCHECK_STR:  AV
 
PROCESS_NAME:  mongod.exe
 
ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre
 
DEVICE_OBJECT: fffffa8035317504
 
DRIVER_OBJECT: 0000000060cca35d



 Comments   
Comment by srini eadha [ 14/Jan/15 ]

Thank you Kaloian for looking in to this issue.

I will check again with the SSD driver we are using, but I found few folks reported about the issue related to windows virtual memory issues that caused BLUE screen, any insight on virtual memory setting for SSD drive ?

Thanks,
Srini

Comment by Kaloian Manassiev [ 14/Jan/15 ]

Hi Srini,

From the Windows crash report, this seems to be caused by a bug in the disk driver. This is not a MongoDB issue - it just so happens that mongod.exe is the process accessing the disk at the time.

Please make sure you have the latest driver for your disk subsystem and that your hardware is healthy.

-Kal.

Generated at Thu Feb 08 03:42:29 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.