Problems? See this thread at archive.org.
hey guys, im wondering if anyone might be willing to help me with some BSODs ive been getting after overclocking my 9800m GS?
im overclocking with setFSB and MSI afterburner to nothing too crazy (usually about 600/1500/800 or just below which usually lets me play wildstar as long as i please with about 30-40fps) but seemingly every time i walk away and am not around to see exactly waht goes down i come back to a log in screen and a recovered from error with a BSOD info in details.
ive checked through bluescreen viewer (before finding out how not as good as event viewer it is) and found that one of them was usually do to faulty ram/memory error i think it was the 1a code? anyway i ran windows mem diagnostic and nothing came up (i wasn't able to get memtest working before my patience ran out but everyone said memory diagnostic would find any memory issues as well but other than it being a memory error/ kernal-windows file issue (have recently reinstalled but can again i suppose :/
i was really hoping someone could tell me via my minidump (whocrashed txt) what i need to stabilize my OC? my temps never get much further than high 70s usually, and though the bios isn't flashed to GT any longer i have read that its not really needed considering the card will get to 1.1 with the numbers im running.
any advice would be great, or a push even in the right direction and i'd be grateful.
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
Hardware: G50VT , ASUSTeK Computer Inc. , G50VT
CPU: GenuineIntel Intel(R) Core(TM)2 Duo CPU P7450 @ 2.13GHz Intel586, level: 6
2 logical processors, active mask: 3
RAM: 4294168576 total
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Tue 9/30/2014 11:32:49 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\093014-20841-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x1A (0x8886, 0xFFFFFA80034EB220, 0xFFFFFA80034C5A50, 0x205)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Mon 9/29/2014 2:53:50 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\092914-44429-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xA (0xFFFFF89FD71FAB38, 0x2, 0x1, 0xFFFFF80002E87781)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Sun 9/28/2014 9:34:54 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\092814-53367-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xA (0x20, 0x2, 0x0, 0xFFFFF80002EB8850)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Sat 9/27/2014 10:07:17 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\092714-51027-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x1A (0x5003, 0xFFFFF70001080000, 0x18956, 0x189580003129C)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Sat 9/27/2014 10:07:17 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x1A (0x5003, 0xFFFFF70001080000, 0x18956, 0x189580003129C)
Error: MEMORY_MANAGEMENT
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
5 crash dumps have been found and analyzed. No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.
G50Vt x5 BSOD when overclocking (some soon, some after HOURS). Looking for assistance
Discussion in 'ASUS Gaming Notebook Forum' started by Viconaut, Sep 30, 2014.
