Sign in with
Sign up | Sign in
Your question

New Build, BSOD problems

Tags:
  • Blue Screen
  • Crash
  • Computers
  • Windows 7
Last response: in Windows 7
Share
October 2, 2012 5:52:54 PM

I just Built this computer last week and have been getting BSOD periodicaly, mostly when I play a game. But a few times just while sitting on the Desktop. Much help would be appriciated.

Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Wed 10/3/2012 8:43:16 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\100312-17924-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71ED0)
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 Wed 10/3/2012 8:43:16 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ndis.sys (ndis!NdisReleaseReadWriteLock+0x9D)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\ndis.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NDIS 6.20 driver
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 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 Mon 10/1/2012 3:23:58 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\100112-14695-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0x50 (0xFFFFF800023D7270, 0x0, 0xFFFFF80002B87AAE, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 invalid system memory has been referenced.
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.

More about : build bsod problems

a b $ Windows 7
October 2, 2012 5:54:47 PM

Most likely a memory fault.

Download memtest86 and run at least 3 full test cycles.
m
0
l
October 2, 2012 6:21:53 PM

Alright, thank you. Currently running it now. Used the bootable USB one. It says So far I have 6400 errors on Test #3.
m
0
l
Related resources
October 2, 2012 6:29:31 PM

thatchackguy said:
Alright, thank you. Currently running it now. Used the bootable USB one. It says So far I have 6400 errors on Test #3.


You shouldn't be getting any errors unless you are running a memory that is incompatible to the mobo. Try with one stick in modules. If you get any errors post here. Make sure that the memory is seated well in the modules before starting the memtest.
m
0
l
October 2, 2012 6:48:42 PM

guhati said:
You shouldn't be getting any errors unless you are running a memory that is incompatible to the mobo. Try with one stick in modules. If you get any errors post here. Make sure that the memory is seated well in the modules before starting the memtest.




My motherboard is the Asus M5 A99FX Pro r2.0 and I'm using 2 4gb gskill sniper ram 1600MHz. I don't know why the wouldn't be compatible. And the test is still running, I already planed on doing 1 stick at a time.
m
0
l
a b $ Windows 7
October 2, 2012 7:10:28 PM

Clearly a RAM problem. Looks like one or more of the sticks is defective. Isolate which one is bad, then RMA for a replacement.

Happens from time to time.
m
0
l
October 2, 2012 11:46:58 PM

gamerk316 said:
Clearly a RAM problem. Looks like one or more of the sticks is defective. Isolate which one is bad, then RMA for a replacement.

Happens from time to time.




So after I have I let it run for these past 5 hours I have yet to get any errors like I did the first time. I even ran one stick at a time and got nothing So far.
m
0
l
October 3, 2012 1:30:00 AM

And now a new BSOD problem. Ugh... :pfff: 
These errors happend while playing Dirt3, I was able to recreaat the crash a few times, I also tried to play Skyrim, managed to make it 10min before it BSOD again. A few days ago my computer crashed while trying to play minecraft aswell. Whats in common is that before the crash the game will jerk/freeze and start runing okay again before it finally fails.



On Thu 10/4/2012 4:20:06 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\100312-12807-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x1EA5F)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0x40000000, 0xFFFFF88005BFF6C8, 0xFFFFF88005BFEF20)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
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 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 Thu 10/4/2012 4:20:06 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1!VidMmInterface+0xD19F)
Bugcheck code: 0x7E (0xFFFFFFFFC0000005, 0x40000000, 0xFFFFF88005BFF6C8, 0xFFFFF88005BFEF20)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
Bug check description: This bug check indicates that a system thread generated an exception that the error handler did not catch.
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 Thu 10/4/2012 4:06:12 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\100312-12495-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0x50 (0xFFFFF89FA91D51F0, 0x0, 0xFFFFF8800121E0EF, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 invalid system memory has been referenced.
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.



m
0
l
a b $ Windows 7
October 3, 2012 1:45:15 AM

When you ran the RAM tests did you:

1. Run 3 cycles on each stick in each of the 4 slots?
2. Run 3 cycles on both sticks in alternate pairs of slots?
3. Swap the order of the sticks and repeat test 2?

I'm still betting faulty RAM but it could also be a motherboard issue. You aren't overclocking are you?
m
0
l
October 3, 2012 2:00:48 AM

ex_bubblehead said:
When you ran the RAM tests did you:

1. Run 3 cycles on each stick in each of the 4 slots?
2. Run 3 cycles on both sticks in alternate pairs of slots?
3. Swap the order of the sticks and repeat test 2?

I'm still betting faulty RAM but it could also be a motherboard issue. You aren't overclocking are you?





I ran both sticks for 3 cycles in 2 diffrents slots with no problems. Ran both sticks in the first slot for 3 cyles with no problems. I guess I'll try alternating slots now.



Walked away form my computer for a few miniuts and cae back to this, was just sitting on the desktop.

On Thu 10/4/2012 4:55:28 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\100312-12012-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x20CF7)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF880053BFCF7, 0xFFFFF88005BE96A8, 0xFFFFF88005BE8F00)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
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 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.
m
0
l
a b $ Windows 7
October 3, 2012 2:34:23 PM

thatchackguy said:
So after I have I let it run for these past 5 hours I have yet to get any errors like I did the first time. I even ran one stick at a time and got nothing So far.


Could be one of two things them:

1: A RAM slot failed. This can happen, but is still pretty rare.

2: When using four sticks of RAM, the memory controller/RAM/northbridge is not receiving consistent voltage, leading to RAM errors and BSOD's. [Can happen with some budget boards/PSU's]

Clearly the RAM subsystem though.
m
0
l
October 4, 2012 12:54:54 AM

Well after running memtest86 with each stick in diffrent slots and combinations, I have yet to get any errors. I ran MemOK and it says my RAM checks out aswell.
m
0
l
a b $ Windows 7
October 4, 2012 12:10:32 PM

I'm leaning toward Mobo/PSU then.

It looks like the RAM sticks themselves are good, but when you test all four together, you get failures. This indicates that the RAM probably isn't receiving stable voltage when four sticks are installed.

As a test, if you run with only two sticks, I assume no BSODs come up? If so, then I'm almost certain the mobo/PSU is at fault.
m
0
l
October 4, 2012 5:26:36 PM

Well I decided to try and install Windows 8 development preview. I get a ntoskernel.executive error and can't install it.
m
0
l
October 4, 2012 6:43:48 PM

Clear your CMOS and run at default.


BTW, what are the system specs?
m
0
l
a b $ Windows 7
October 4, 2012 7:34:26 PM

thatchackguy said:
Well I decided to try and install Windows 8 development preview. I get a ntoskernel.executive error and can't install it.


Which again makes sense if the RAM has a problem. I have no doubt theres a problem SOMEWHERE in the memory subsystem (confirmed by memtest with all four sticks in), I'm just not sure WHY yet.
m
0
l
October 4, 2012 10:03:18 PM

RussK1 said:
Clear your CMOS and run at default.


BTW, what are the system specs?



My specs are. Mobo: Asus M5 A99FX Pro R2.0
CPU: AMD Phenom 2 965 BE
PSU: 700w OCZ
GPU: Asus 2gb 7850
RAM: 2 4gb gskill sniper

m
0
l
October 5, 2012 3:55:35 AM

thatchackguy said:
My specs are. Mobo: Asus M5 A99FX Pro R2.0
CPU: AMD Phenom 2 965 BE
PSU: 700w OCZ
GPU: Asus 2gb 7850
RAM: 2 4gb gskill sniper


What mode are you in? Ganged or unganged. And is the ram set to specs... speed, timings and voltage?
m
0
l
!