View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0004000 | DarkRadiant | General | public | 31.12.2014 16:51 | 11.01.2015 17:49 |
Reporter | Assigned To | ||||
Priority | none | Severity | trivial | Reproducibility | N/A |
Status | closed | Resolution | no change required | ||
Platform | Win32 | OS | Windows | OS Version | 7 sp1 |
Product Version | 2.0.2 | ||||
Summary | 0004000: 2.0.2 pre4 causing BSOD: Win7Sp1 | ||||
Description | While using DR I have randomly beeing getting BSOD, so Ran memtest and found no faults. Did a quick analyse of the memory dump via BSOD view and WhoCrashed and both came upo with a generic error - MEMORY_MANAGMENt, kernal crash. So I downloaded and installed windows debug tools to get a more detailed explaination and to my suprise it was DR that caused the BSOD. | ||||
Additional Information | BUGCHECK_STR: 0x1a_41201 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: DarkRadiant.ex CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from fffff8000431a9fe to fffff800042bebc0 STACK_TEXT: fffff880`0b39f7e8 fffff800`0431a9fe : 00000000`0000001a 00000000`00041201 fffff680`000fbd00 00000000`00000001 : nt!KeBugCheckEx fffff880`0b39f7f0 fffff800`042d86c4 : 00000000`00000080 fffff680`000fbd20 00000000`1f79b000 00000000`00000080 : nt! ?? ::FNODOBFM::`string'+0x13702 fffff880`0b39f830 fffff800`045b7d4a : 00000000`00000000 00000000`00000000 fffffa80`0d3e2620 00000000`00000004 : nt!MiCommitExistingVad+0x2c4 fffff880`0b39f8d0 fffff800`042bde53 : ffffffff`ffffffff fffffa80`11ddb3e0 00000000`00000000 00000000`0012a388 : nt!NtAllocateVirtualMemory+0x134a fffff880`0b39fa70 00000000`775e143a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 00000000`0012a368 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x775e143a STACK_COMMAND: kb FOLLOWUP_IP: nt! ?? ::FNODOBFM::`string'+13702 fffff800`0431a9fe cc int 3 SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+13702 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 531590fb FAILURE_BUCKET_ID: X64_0x1a_41201_nt!_??_::FNODOBFM::_string_+13702 BUCKET_ID: X64_0x1a_41201_nt!_??_::FNODOBFM::_string_+13702 Followup: MachineOwner --------- | ||||
Tags | No tags attached. | ||||
I doubt that DarkRadiant itself causes the BSOD, I couldn't write code to do that even if I wanted to... Driver faults are what they are: driver faults, even if DarkRadiant is the application that was last active when it fails. While I doubt that I can do anything about it, do you still have the minidump file for me to loook at? |
|
Ok this hasn't happened for a while now, so will have to keep this on the back burner. When it happens again I will add a link to the dump file. |
|
This can be closed, as it was a local machine issue. | |
Date Modified | Username | Field | Change |
---|---|---|---|
31.12.2014 16:51 |
|
New Issue | |
31.12.2014 17:06 | greebo | Note Added: 0007286 | |
31.12.2014 17:06 | greebo | Status | new => feedback |
04.01.2015 14:44 |
|
Note Added: 0007298 | |
04.01.2015 14:44 |
|
Status | feedback => new |
04.01.2015 14:45 |
|
Note Edited: 0007298 | |
04.01.2015 16:58 | greebo | Status | new => acknowledged |
11.01.2015 16:04 |
|
Note Added: 0007335 | |
11.01.2015 16:05 |
|
Priority | normal => none |
11.01.2015 16:05 |
|
Severity | crash => trivial |
11.01.2015 16:05 |
|
Resolution | open => no change required |
11.01.2015 16:06 |
|
Reproducibility | sometimes => N/A |
11.01.2015 16:06 |
|
Product Version | 2.0.1 => 2.0.2 |
11.01.2015 16:06 |
|
Fixed in Version | => 2.0.2 |
11.01.2015 17:49 | greebo | Status | acknowledged => closed |
11.01.2015 17:49 | greebo | Fixed in Version | 2.0.2 => |