Jump to content

Archived

This topic is now archived and is closed to further replies.

MarkW

BSOD - help required.

Recommended Posts

I have recently begun to experience very intermittently a BSOD that seems to be around the ntoskrnl.exeI understand that this may be related to keyboard ground wire issues but not sure. So far crashes have only occured while flying in the sim.Any help requested.==================================================Dump File : 011112-25318-01.dmpCrash Time : 1/11/2012 7:32:02 PMBug Check String : Bug Check Code : 0x00000101Parameter 1 : 00000000`00000031Parameter 2 : 00000000`00000000Parameter 3 : fffff880`033d7180Parameter 4 : 00000000`00000003Caused By Driver : ntoskrnl.exeCaused By Address : ntoskrnl.exe+7cc40File Description : NT Kernel & SystemProduct Name : Microsoft® Windows® Operating SystemCompany : Microsoft CorporationFile Version : 6.1.7601.17640 (win7sp1_gdr.110622-1506)Processor : x64Crash Address : ntoskrnl.exe+7cc40Stack Address 1 : Stack Address 2 : Stack Address 3 : Computer Name : Full Path : C:\Windows\Minidump\011112-25318-01.dmpProcessors Count : 4Major Version : 15Minor Version : 7601Dump File Size : 262,144====================================================================================================Dump File : 103011-16146-01.dmpCrash Time : 10/30/2011 4:09:23 PMBug Check String : SYSTEM_SERVICE_EXCEPTIONBug Check Code : 0x0000003bParameter 1 : 00000000`c0000005Parameter 2 : fffff880`0120375cParameter 3 : fffff880`0a61ade0Parameter 4 : 00000000`00000000Caused By Driver : Ntfs.sysCaused By Address : Ntfs.sys+b0aacFile Description : Product Name : Company : File Version : Processor : x64Crash Address : ntoskrnl.exe+7cc40Stack Address 1 : Stack Address 2 : Stack Address 3 : Computer Name : Full Path : C:\Windows\Minidump\103011-16146-01.dmpProcessors Count : 4Major Version : 15Minor Version : 7601Dump File Size : 262,144====================================================================================================Dump File : 122811-14788-01.dmpCrash Time : 12/28/2011 8:39:39 AMBug Check String : Bug Check Code : 0x00000101Parameter 1 : 00000000`00000031Parameter 2 : 00000000`00000000Parameter 3 : fffff880`009ea180Parameter 4 : 00000000`00000001Caused By Driver : ntoskrnl.exeCaused By Address : ntoskrnl.exe+7cc40File Description : NT Kernel & SystemProduct Name : Microsoft® Windows® Operating SystemCompany : Microsoft CorporationFile Version : 6.1.7601.17640 (win7sp1_gdr.110622-1506)Processor : x64Crash Address : ntoskrnl.exe+7cc40Stack Address 1 : Stack Address 2 : Stack Address 3 : Computer Name : Full Path : C:\Windows\Minidump\122811-14788-01.dmpProcessors Count : 4Major Version : 15Minor Version : 7601Dump File Size : 262,144====================================================================================================Dump File : 123111-14991-01.dmpCrash Time : 12/31/2011 2:39:19 PMBug Check String : Bug Check Code : 0x00000101Parameter 1 : 00000000`00000031Parameter 2 : 00000000`00000000Parameter 3 : fffff880`031d7180Parameter 4 : 00000000`00000003Caused By Driver : igdkmd64.sysCaused By Address : igdkmd64.sys+3c59cFile Description : Product Name : Company : File Version : Processor : x64Crash Address : ntoskrnl.exe+7cc40Stack Address 1 : Stack Address 2 : Stack Address 3 : Computer Name : Full Path : C:\Windows\Minidump\123111-14991-01.dmpProcessors Count : 4Major Version : 15Minor Version : 7601Dump File Size : 262,144==================================================

Share this post


Link to post
Share on other sites
Guest firehawk44

The common denominator for your crashes was the Crash Address: ntoskrnl.exe+7cc40. Based on the following link, this indicates there is something wrong with your system memory - http://www.sevenforums.com/crashes-debugging/190800-solved-random-bsod-around-ntoskrnl-exe-7cc40.html. See how much memory is being reported by your system. Probably one or more sticks of memory has gone bad. When I first built my system, I had several BSOD's with just 'ntoskrnl.exe' reported as the bad file/module. The solution I found was to check the voltages/frequencies on my BIOS memory settings. I adjusted those settings (believe I lowered the voltage to 1.5) and the issue when away. I was frustrated because I had done several memory stability testing and none of the tests reported anything wrong. Then I started up FSX....Best regards,Jim

Share this post


Link to post
Share on other sites

Jim,Thanks for your insight on this. When I built my system I followed NickN's instructions and ran 7 cycles of memtest one strip at a time. The memory passed with flying colours. I have the memory timings at default in the bios so I cannot understand why this would be the cause of the problem. In any regard I will double check my settings and re-run the mem test. thanks again.Mark.

Share this post


Link to post
Share on other sites
Jim,Thanks for your insight on this. When I built my system I followed NickN's instructions and ran 7 cycles of memtest one strip at a time. The memory passed with flying colours. I have the memory timings at default in the bios so I cannot understand why this would be the cause of the problem. In any regard I will double check my settings and re-run the mem test. thanks again.Mark.
Mark,Memory is prone to failing over the course of a PC's lifetime. Recheck each stick, one at a time, at stock settings.Memory isn't necessarily the culprit given the ntoskrnl.exe crash address. The crash could be related to the CPU overclock as well. What voltage are you using all around? I'd be interested in knowing your BIOS settings.Is the crash random in FSX, or does it happen around all scenery?

Share this post


Link to post
Share on other sites
Guest firehawk44
I have the memory timings at default in the bios
Mark, I know you have an ASROCK MB and I have an ASUS MB but I was told ASUS has a very difficult time setting the correct memory frequencies/timings/voltages through their BIOS. Perhaps ASROCK doesn't handle memory settings properly too. If I were you I would seriously look at the settings and make sure they are correct. I have mine set to the XMP 1600 Profile and lowered the voltage to 1.5 as I was having issues with the recommended 1.65 voltage. My system has been very stable since doing that.Best regards,Jim

Share this post


Link to post
Share on other sites

×
×
  • Create New...