[FAQ] PC auto restart/Blue Screen (BSOD), All questions go here please.
|
|
 May 8 2008, 01:01 PM
Return to original view | Post
#1
|
 
Junior Member
270 posts Joined: Oct 2006  
|
need help for someone to view this minidump for me pls.. i can't turn on my pc for more than 10 minutes, so can't install windbg..
http://aidil.irix.googlepages.com/Minidump.rar This post has been edited by irix: May 8 2008, 01:02 PM |
|
|
May 8 2008, 02:47 PM
Return to original view | Post
#2
|
|
Junior Member
270 posts Joined: Oct 2006
|
QUOTE(spikeee @ May 8 2008, 02:20 PM) seems to me like there's a critical error with your memory. ok.. i have 2 sticks of ram.. i've tested 3 times with Memtest86+... one test for each ram and both rams installed in third test..Your minidump shows a memory corruption KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e) This is a very common bugcheck. Usually the exception address pinpoints the driver/function that caused the problem. Always note this address as well as the link date of the driver/image that contains this address. Some common problems are exception code 0x80000003. This means a hard coded breakpoint or assertion was hit, but this system was booted /NODEBUG. This is not supposed to happen as developers should never have hardcoded breakpoints in retail code, but ... If this happens, make sure a debugger gets connected, and the system is booted /DEBUG. This will let us see why this breakpoint is happening.  first test: 1 stick only - passed 100% without any errors second test: another stick - passed 100% without any errors third test: both sticks running in dual channel - passed 100% without errors for the third test, i ran it for an hour and still no errors reported.. did vista just screws up my RAM? i'm sure there's no problem with any of my memory sticks.. UPDATED: I ran windbg at my friend's pc.. this is what i got from the latest minidump: CODE MODULE_NAME: nt FAULTING_MODULE: 81c00000 nt DEBUG_FLR_IMAGE_TIMESTAMP: 471ea39c WRITE_ADDRESS: unable to get nt!MmSpecialPoolStart unable to get nt!MmSpecialPoolEnd unable to get nt!MmPoolCodeStart unable to get nt!MmPoolCodeEnd c423e42c CURRENT_IRQL: 2 FAULTING_IP: nt+770bc 81c770bc ?? ??? CUSTOMER_CRASH_COUNT: 4 DEFAULT_BUCKET_ID: WRONG_SYMBOLS BUGCHECK_STR: 0xA LAST_CONTROL_TRANSFER: from 81c770bc to 81c8fd84 STACK_TEXT: WARNING: Stack unwind information not available. Following frames may be wrong. 883d3ac8 81c770bc badb0d00 00000000 8487e8c8 nt+0x8fd84 883d3b50 824a03f9 841fea70 883d3bb4 883d3b84 nt+0x770bc 883d3b60 82518af1 841fea70 00000000 85608238 Ntfs+0xc3f9 883d3b84 824a02d9 845ba008 883d3bb4 883d3bbe Ntfs+0x84af1 883d3bd8 82538479 845ba008 856080d8 a3f1f948 Ntfs+0xc2d9 883d3c28 824ad3be 845ba008 00000028 01f1fbd8 Ntfs+0xa4479 883d3c50 82534217 845ba008 a3f1fa38 a3f1fbd8 Ntfs+0x193be 883d3cb0 8251933a 845ba008 a3f1fa38 a3f1f948 Ntfs+0xa0217 883d3d44 81c78fa0 00000000 00000000 83a7bad0 Ntfs+0x8533a 883d3d7c 81e254e0 00000000 883d8680 00000000 nt+0x78fa0 883d3dc0 81c9159e 81c78ea3 00000000 00000000 nt+0x2254e0 00000000 00000000 00000000 00000000 00000000 nt+0x9159e STACK_COMMAND: kb FOLLOWUP_IP: nt+770bc 81c770bc ?? ??? SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: nt+770bc FOLLOWUP_NAME: MachineOwner IMAGE_NAME: ntkrnlpa.exe BUCKET_ID: WRONG_SYMBOLS Followup: MachineOwner This post has been edited by irix: May 8 2008, 07:04 PM |
|
|
May 9 2008, 12:07 PM
Return to original view | Post
#3
|
|
Junior Member
270 posts Joined: Oct 2006
|
alright.. made another test last night.. tested both rams in dual channel, errors start to appear after 3-4 hours..
is there other factors which causes this problem? like mobo or cpu temperature? |
| Change to: |  0.0505sec
 0.77
 7 queries
 GZIP Disabled
Time is now: 2nd December 2025 - 09:04 PM |
Quote