Jimbo Posted October 19, 2011 Share Posted October 19, 2011 My M18X has started throwing up the dreaded BSOD, always with error code 0x0000003B, any ideas as it's driving me bugshit! Also (randomly) been playing RAGE, worked perfectly for 3hrs+ on first playing, ever since it crashes within 3 mins of starting. Not sure if it's related, but it sure is annoying. Link to comment Share on other sites More sharing options...
Founder Michael Posted October 19, 2011 Founder Share Posted October 19, 2011 have you tried whocrashed tho analyze the memory dump ? Link to comment Share on other sites More sharing options...
Founder StamatisX Posted October 19, 2011 Founder Share Posted October 19, 2011 Is that with or without OC? Link to comment Share on other sites More sharing options...
Jimbo Posted October 19, 2011 Author Share Posted October 19, 2011 With CPU OC, but just started out of nowhere without me changing anything. No GPU OC. Happens on integrated and dedicated.Will try whocrashed, thanks. Link to comment Share on other sites More sharing options...
Founder StamatisX Posted October 19, 2011 Founder Share Posted October 19, 2011 Did you install any new GPU drivers in the meanwhile? Do you run the game as an admin or as user? Link to comment Share on other sites More sharing options...
Jimbo Posted October 19, 2011 Author Share Posted October 19, 2011 No new drivers. I don't specifically run things as admin (generally). Link to comment Share on other sites More sharing options...
Founder StamatisX Posted October 19, 2011 Founder Share Posted October 19, 2011 Try to run the game as admin then and see if you get the same crashes 1 Link to comment Share on other sites More sharing options...
Jimbo Posted October 19, 2011 Author Share Posted October 19, 2011 (edited) @StamatisX You may be a deity - I totally didn't expect that to work, and it works flawlessly. Just played for 1hr+ with no hiccups. Thanks and +rep. Edited October 19, 2011 by Jimbo Link to comment Share on other sites More sharing options...
Founder StamatisX Posted October 19, 2011 Founder Share Posted October 19, 2011 hehe glad it worked! Link to comment Share on other sites More sharing options...
Jimbo Posted October 20, 2011 Author Share Posted October 20, 2011 (edited) Game not crashing but still getting BSOD all the time. Thinking of resetting my OC in the hopes it will help. Tried reinstalling the GPU drivers more than once, with the whole driversweeper + CC song and dance. Readout from Whocrashed (sorry for the length). And yes, I did blatantly steal the system name from someone else, it just seemed so fitting. My desktop is Starbase. EDIT: ROFLMAO @ Unintended smileys, they seem so appropriate! System Information (local) computer name: MOTHERSHIP windows version: Windows 7 Service Pack 1, 6.1, build: 7601 windows dir: C:\Windows CPU: GenuineIntel Genuine Intel® CPU 0 @ 2.40GHz Intel586, level: 6 8 logical processors, active mask: 255 RAM: 8570875904 total VM: 2147352576, free: 1949917184 Crash Dump Analysis Crash dump directory: C:\Windows\Minidump Crash dumps are enabled on your computer. On Thu 10/20/2011 5:44:46 AM GMT your computer crashed crash dump file: C:\Windows\Minidump\102011-16489-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40) Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80003567047, 0xFFFFF8800E44A0B0, 0x0) Error: SYSTEM_SERVICE_EXCEPTION 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 an exception happened while executing a routine that transitions from non-privileged code to privileged code. 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 which cannot be identified at this time. On Thu 10/20/2011 5:44:46 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: 0x3B (0xC0000005, 0xFFFFF80003567047, 0xFFFFF8800E44A0B0, 0x0) Error: SYSTEM_SERVICE_EXCEPTION Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code. 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 which cannot be identified at this time. On Thu 10/20/2011 4:46:33 AM GMT your computer crashed crash dump file: C:\Windows\Minidump\102011-13993-01.dmp This was probably caused by the following module: atikmdag.sys (atikmdag+0x2FC888) Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF88004F41888, 0xFFFFF8800B793F68, 0xFFFFF8800B7937C0) Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M file path: C:\Windows\system32\drivers\atikmdag.sys product: ATI Radeon Family company: ATI Technologies Inc. description: ATI Radeon Kernel Mode Driver Bug check description: This indicates that a system thread generated an exception which the error handler did not catch. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: atikmdag.sys (ATI Radeon Kernel Mode Driver, ATI Technologies Inc.). Google query: atikmdag.sys ATI Technologies Inc. SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M On Thu 10/20/2011 4:04:52 AM GMT your computer crashed crash dump file: C:\Windows\Minidump\102011-14695-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40) Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80003585047, 0xFFFFF88008DF40B0, 0x0) Error: SYSTEM_SERVICE_EXCEPTION 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 an exception happened while executing a routine that transitions from non-privileged code to privileged code. 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 which cannot be identified at this time. On Thu 10/20/2011 3:35:45 AM GMT your computer crashed crash dump file: C:\Windows\Minidump\102011-15256-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40) Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF800032B2187, 0x0, 0xFFFFFFFFFFFFFFFF) Error: KMODE_EXCEPTION_NOT_HANDLED 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 kernel-mode program generated an exception which the error handler did not catch. 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 which cannot be identified at this time. On Wed 10/19/2011 10:53:18 AM GMT your computer crashed crash dump file: C:\Windows\Minidump\101911-19375-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40) Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800035D4608, 0xFFFFF880044A20F0, 0x0) Error: SYSTEM_SERVICE_EXCEPTION 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 an exception happened while executing a routine that transitions from non-privileged code to privileged code. 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 which cannot be identified at this time. On Wed 10/19/2011 8:54:08 AM GMT your computer crashed crash dump file: C:\Windows\Minidump\101911-25974-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40) Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800035C14C8, 0xFFFFF8800D9EBDA0, 0x0) Error: SYSTEM_SERVICE_EXCEPTION 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 an exception happened while executing a routine that transitions from non-privileged code to privileged code. 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 which cannot be identified at this time. On Wed 10/19/2011 5:31:02 AM GMT your computer crashed crash dump file: C:\Windows\Minidump\101911-16692-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40) Bugcheck code: 0x9F (0x3, 0xFFFFFA80070336F0, 0xFFFFF80000B9C3D8, 0xFFFFFA800A2DC010) Error: DRIVER_POWER_STATE_FAILURE file path: C:\Windows\system32\ntoskrnl.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state. 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 which cannot be identified at this time. On Tue 10/18/2011 6:44:51 PM GMT your computer crashed crash dump file: C:\Windows\Minidump\101911-17565-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40) Bugcheck code: 0x9F (0x3, 0xFFFFFA800B060910, 0xFFFFF80004B003D8, 0xFFFFFA800BE2ABD0) Error: DRIVER_POWER_STATE_FAILURE file path: C:\Windows\system32\ntoskrnl.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state. 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 which cannot be identified at this time. On Mon 10/17/2011 1:18:32 PM GMT your computer crashed crash dump file: C:\Windows\Minidump\101811-21309-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x328147) Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80003588147, 0xFFFFF880037850A8, 0xFFFFF88003784900) Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M 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 system thread generated an exception which the error handler did not catch. 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 which cannot be identified at this time. On Mon 10/17/2011 10:30:48 AM GMT your computer crashed crash dump file: C:\Windows\Minidump\101711-18158-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40) Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800035A0F88, 0xFFFFF88008813F40, 0x0) Error: SYSTEM_SERVICE_EXCEPTION 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 an exception happened while executing a routine that transitions from non-privileged code to privileged code. 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 which cannot be identified at this time. On Fri 10/7/2011 6:56:25 AM GMT your computer crashed crash dump file: C:\Windows\Minidump\100711-19983-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40) Bugcheck code: 0x9F (0x3, 0xFFFFFA800AF14060, 0xFFFFF80004B0D3D8, 0xFFFFFA80076CFE10) Error: DRIVER_POWER_STATE_FAILURE file path: C:\Windows\system32\ntoskrnl.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state. 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 which cannot be identified at this time. On Sat 9/24/2011 11:44:20 PM GMT your computer crashed crash dump file: C:\Windows\Minidump\092511-21262-01.dmp This was probably caused by the following module: ntfs.sys (Ntfs+0x5A88) Bugcheck code: 0x24 (0x1904FB, 0xFFFFF88008BBAB18, 0xFFFFF88008BBA370, 0xFFFFF80003098FC6) Error: NTFS_FILE_SYSTEM file path: C:\Windows\system32\drivers\ntfs.sys product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT File System Driver Bug check description: This indicates a problem occurred in the NTFS file system. The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time. On Fri 9/23/2011 12:08:04 PM GMT your computer crashed crash dump file: C:\Windows\Minidump\092311-18532-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC10) Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0) Error: KMODE_EXCEPTION_NOT_HANDLED 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 kernel-mode program generated an exception which the error handler did not catch. 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 which cannot be identified at this time. On Fri 9/23/2011 12:01:37 PM GMT your computer crashed crash dump file: C:\Windows\Minidump\092311-17815-01.dmp This was probably caused by the following module: win32k.sys (win32k+0x206549) Bugcheck code: 0x3B (0xC0000005, 0xFFFFF96000296549, 0xFFFFF88002A8D400, 0x0) Error: SYSTEM_SERVICE_EXCEPTION file path: C:\Windows\system32\win32k.sys product: Microsoft® Windows® Operating System company: Microsoft Corporation description: Multi-User Win32 Driver Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code. 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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time. Conclusion 16 crash dumps have been found and analyzed. Only 15 are included in this report. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers: atikmdag.sys (ATI Radeon Kernel Mode Driver, ATI Technologies Inc.) If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems. Read the topic general suggestions for troubleshooting system crashes for more information. Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further. Edited October 20, 2011 by Jimbo Link to comment Share on other sites More sharing options...
GetFound Posted October 20, 2011 Share Posted October 20, 2011 Jimbo, have you updated your OCZ firmware yet? I was getting daily BSOD's before I updated. I thought it was video at first because of the crash logs, but turned out otherwise.http://forum.techinferno.com/alienware-m18x/1211-ocz-vertex-3-vertex-3-max-iops-firmware-update-bsod-fix.html Link to comment Share on other sites More sharing options...
Jimbo Posted October 20, 2011 Author Share Posted October 20, 2011 Not even using an SSD at the moment, still stuck on the 750gb I ordered as a "backup" drive. Link to comment Share on other sites More sharing options...
mw86 Posted October 20, 2011 Share Posted October 20, 2011 (edited) Not even using an SSD at the moment, still stuck on the 750gb I ordered as a "backup" drive. Jimbo those ATi blah blah blah errors are from the modded drivers in my experience.... try going to rage preview drivers version 2. 11.10 version 2... they seem to work perfect for me and are made for mobile not modded. Brightness works etc. Install them after a clean install using driversweeper, ccleaner(registry clean) and install those drivers with restarts in between. Then disable ulps the manual way... so your sure they all were disabled... since in my experience the sapphire trixx option to disable ulps for me has glitched sometimes forcing lowest clocks like 100/150 etyc on my secondary and primary cards once... so avoid the hassle just registry edit the ulps options... next download RBEeditor and use gpuz to extract your vbios files. Open inside RBE one by one and go to the seconds tab and set your safe 24/7 overclock in all the power profiles... don't forget to put the 1.1volts under all the clokcs too. Now save the bin files and enter the button in RBE that says Winflash/or Atiflash and hit flash on your primary... next close the tab... open the next bios file do the same and renter the winflash/atiflash button and select the second card and hit flash... tell it to restart this time around when it asks and when you boot up... the cards will be at the clocks 24/7 and they wont stutter in anything... video , games anything... they run much better like this since they don't keep bouncing around to their low power clocks which actually causes instability or stuttering in a select few things. I flashed mine to 830/1100 and survived 3 hours of furmark at 1080p with all options on and 8x antialiasing with my top temp being 81c at end and the rest all mid 70s to low 70s... next for benching and not gaming your system will be as configured and now you can still use trixx to work on benching and just restarts or hit reset and clocks are back to your 24/7 ones... cool? If you need help let me know I can post a pic of this if you want... I'd send you a copy of my already modified vbios files but you don't have 6970m you have 6990M. the driver i use right now http://support.amd.com/us/kbarticles/Pages/GPU122AMDCat1110PreDriverV2.aspx Edited October 20, 2011 by mw86 Link to comment Share on other sites More sharing options...
mw86 Posted October 20, 2011 Share Posted October 20, 2011 My M18X has started throwing up the dreaded BSOD, always with error code 0x0000003B, any ideas as it's driving me bugshit!Also (randomly) been playing RAGE, worked perfectly for 3hrs+ on first playing, ever since it crashes within 3 mins of starting. Not sure if it's related, but it sure is annoying. I missed the error number in your OP here... read this about bsod error codes seems if you were overclocking the cpu you may need to raise the flex at your clocks... also if the chip is getting hot it will also require higher flex... 000x3b is voltage mostly... http://forum.techinferno.com/off-topic/1124-general-overclocking-advice-record-breaking-benchmarks.html#post13080 Link to comment Share on other sites More sharing options...
mw86 Posted October 22, 2011 Share Posted October 22, 2011 Not even using an SSD at the moment, still stuck on the 750gb I ordered as a "backup" drive. still getting bsod's? or is "solved" Link to comment Share on other sites More sharing options...
Jimbo Posted October 22, 2011 Author Share Posted October 22, 2011 @mw86 Sorry mate, meant to update just wanted to be sure the problem was gone. It has indeed been fixed by raising flex from 7 to 9, damn mobile CPU overclocking. + rep for the help (EDIT: Or not, still have to spread the love more.)RAGE still crashes fairly often but it's manageable now, every 30-40 mins instead of every 3-4. Link to comment Share on other sites More sharing options...
mw86 Posted October 23, 2011 Share Posted October 23, 2011 Hmmmmm no worry im full on rep and others are much deservering to. Glad you bsod went away. if at 45x you may need about +9 where you are now upto 15 flex depending on max workload ad every chip is different. more amps and watts will need more volts too. the chip runs great with enough volts just gets warmer... for reference Alienware M17x R2 has +75mv in bios and +150mv.... 25flex the max of the stock m18x bios is just shy of +100mv. but 99 flex is almost +386mv which is unlocked bios limits.... no we are cooking with oil so to say Link to comment Share on other sites More sharing options...
Recommended Posts