First build crashing

[BoSox07]

Hello,

I am hoping someone can give me advice with trouble shooting. I just finished building my first machine and loaded Windows 7.

CPU – Intel E8400 3G
MB - GIGABYTE GA-EP43-UD3L 775 P43 R
RAM – Corsair 4GB (2 x 2GB) 240-Pin DDR2
GPU – BFGTECH GeForce GTX-275
PSU – Corsair 550W
HD – 80G and 500G

Everything seemed fine as I was loading software, updating drivers and configuring. Then I started getting random crashes the crashes became consistent as whenever the machine is pushed. It will either blue screen or just freeze and I will have to physically push the power button to restart it. I downloaded a stress test and temp monitoring software to help diagnose.

CPU and GPU temps are 97*F and 120*F at idle. Ran the stress text at 100% and temps topped out at 127*F for the CPU and 140*F GPU just before crash. If I run the stress test just on RAM it passes, on CPU and GPU fails, just CPU fails, just GPU fails.

Blue screens error messages are inconsistent so far the only error messages I was able to retrieve were:
CNG.SYS
SRTSP.SYS
CLASSNP.SYS
IRQL_NOT_LESS_OR_EQUAL
PAGE_FAULT_IN_NONPAGED_AREA

I hope I provided enough information. I have a feeling it’s a hardware issue but temp seem to be in normal range. Any suggestion would greatly be appreciated.

 

[nate42nd]

That seems WAY too hot. I would use some different thermal paste and check all heatsink connections and fans.

 

[BoSox07]

All fan are working. two case fans, CPU fan and GPU fan.

You really think that's to hot? CPU is only 48C.

 

[TGSoldier]

That seems WAY too hot. I would use some different thermal paste and check all heatsink connections and fans.

Those temps seem fine to me.. He said Fahrenheit, not Celsius..

 

[Tews]

Welcome to the forums!

Please upload the .dmp files for analysis ... Please type event viewer in the search box .. open the application section and see if there are any critical errors listed... please post them here if there are..

 

[tewas]

That sounds like memory issue. Run memtest, it might find the problem.
Also check storage drivers, for some reason default windows drivers does not always work, especially with Intel matrix storage.

 

[Antman]

Then I started getting random crashes the crashes became consistent as whenever the machine is pushed

So, you are attempting to overclock?

 

[zigzag3143]

BoSox07

Please go to c:\windows\minidump zip the dump file (*.dmp) and upload it to us for debugging. If its not in minidump search *.dmp for it.

KEn

 

[BoSox07]

Tews – Thank you.

I will retrieve the dump files and post them when I get home tonight

tewas – I ran stress test for 15 minutes at 100% on the RAM and it passed. Is that not an accurate test?

Antman – No, I am not overclocking.

 

[TGSoldier]

15minutes is not good enough... More like a couple hours.. Overnight when you are sleeping..

15 minutes is definitely not enough.

 

[nate42nd]

That seems WAY too hot. I would use some different thermal paste and check all heatsink connections and fans.

Those temps seem fine to me.. He said Fahrenheit, not Celsius..

Oh, sorry.....that's my bad. I didn't read it well enough. Temps are fine. Sorry.

 

[BoSox07]

All,

Attached are the dumps. Thanks for your help.

 

[TGSoldier]

Did you install your drivers from manufacturers site or did you let windows install them?

 

[Antman]

What efforts have you made regarding driver updates?

 

[BoSox07]

Updated motherboard drivers from Gigabyte site and Video card drivers from NVIDIA site. All others through Windows.

 

[zigzag3143]

bump

Bosox

the last of the dumps definately points to a hardware problem. Im analysing the others now.


Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\091009-21169-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*d:\symbols*Symbol information
Executable search path is:
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0x82a56000 PsLoadedModuleList = 0x82b9e810
Debug session time: Thu Sep 10 00:47:32.859 2009 (GMT-4)
System Uptime: 0 days 0:15:24.342
Loading Kernel Symbols
...............................................................
................................................................
.............................................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 10000050, {8c2d3cd0, 8, 8c2d3cd0, 0}


Could not read faulting driver name
Probably caused by : hardware

Followup: MachineOwner
---------
*** Possible invalid call from 8b8937bd ( Ntfs!NtfsNonCachedUsaWrite+0x7 )
*** Expected target 8b893cd0 ( Ntfs!_SEH_prolog4+0x0 )

0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: 8c2d3cd0, memory referenced.
Arg2: 00000008, value 0 = read operation, 1 = write operation.
Arg3: 8c2d3cd0, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 00000000, (reserved)

Debugging Details:
------------------


Could not read faulting driver name

WRITE_ADDRESS: GetPointerFromAddress: unable to read from 82bbe718
Unable to read MiSystemVaType memory at 82b9e160
8c2d3cd0

FAULTING_IP:
+6416952f00c7df40
8c2d3cd0 ?? ???

MM_INTERNAL_CODE: 0

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x50

PROCESS_NAME: System

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from 8b8937c2 to 8c2d3cd0

POSSIBLE_INVALID_CONTROL_TRANSFER: from 8b8937bd to 8b893cd0

STACK_TEXT:
WARNING: Frame IP not in any known module. Following frames may be wrong.
8d92b1b0 8b8937c2 8b8c0eb8 00000024 8b897fa9 0x8c2d3cd0
8d92b2d0 8b89985f 8d92b2e0 8619f690 0120070a Ntfs!NtfsNonCachedUsaWrite+0xc
8d92b474 82a924bc 86920028 8619f690 8619f690 Ntfs!NtfsFsdWrite+0x2e1
8d92b48c 8b5b320c 8678fed8 8619f690 00000000 nt!IofCallDriver+0x63
8d92b4b0 8b5b33cb 8d92b4d0 8678fed8 00000000 fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x2aa
8d92b4e8 82a924bc 8678fed8 8619f690 8619f690 fltmgr!FltpDispatch+0xc5
8d92b500 82a8a749 8d92b540 00000000 8d92b7a4 nt!IofCallDriver+0x63
8d92b514 82af0aff 86893038 8678fed8 8d92b5e0 nt!IoSynchronousPageWrite+0x19d
8d92b644 82af1f85 8d6a5db0 8d6a5e00 86893e68 nt!MiFlushSectionInternal+0x828
8d92b6ac 82ae5841 00891404 0000a000 00000005 nt!MmFlushSection+0xc2
8d92b740 8b8931e7 86891404 8d92b7ec 0000a000 nt!CcFlushCache+0x156
8d92b814 8b90b38c 8d63c008 2d0f8e89 00000000 Ntfs!LfsFlushLfcb+0x478
8d92b868 8b90b437 0163c008 2d0f8e89 00000000 Ntfs!LfsFlushToLsnPriv+0x1a7
8d92b8ac 82af4d9b 8c7c8158 2d0f8e89 00000000 Ntfs!LfsFlushToLsn+0x87
8d92b948 82ae592f 868a3d00 00000000 00000001 nt!CcAcquireByteRangeForWrite+0xa6f
8d92b9ec 8b90411c 868a3c48 00000000 00000000 nt!CcFlushCache+0x244
8d92ba3c 8b90824b 85e29170 8c6fdbe8 00000000 Ntfs!NtfsFlushBootCritical+0x57
8d92bab0 8b90876b 85e29170 85eb9340 061ed07d Ntfs!NtfsCommonFlushBuffers+0x449
8d92bb18 82a924bc 86920028 85eb9340 85eb9340 Ntfs!NtfsFsdFlushBuffers+0xf7
8d92bb30 8b5b320c 8678fed8 85eb9340 00000000 nt!IofCallDriver+0x63
8d92bb54 8b5b33cb 8d92bb74 8678fed8 00000000 fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x2aa
8d92bb8c 82a924bc 8678fed8 85eb9340 85eb9340 fltmgr!FltpDispatch+0xc5
8d92bba4 82c93eee 85eb9340 876ca370 00000000 nt!IofCallDriver+0x63
8d92bbc4 82c74e5a 8678fed8 876ca370 00000000 nt!IopSynchronousServiceTail+0x1f8
8d92bc30 82a9942a 87798a20 8d92bcc8 8d92bcd0 nt!NtFlushBuffersFile+0x1d7
8d92bc30 82a97341 87798a20 8d92bcc8 8d92bcd0 nt!KiFastCallEntry+0x12a
8d92bcb0 82c53d13 800001a8 8d92bcc8 859ef920 nt!ZwFlushBuffersFile+0x11
8d92bcd0 82cf0832 8c61d008 00000000 00000000 nt!CmpFileFlush+0x5a
8d92bd00 82ac3f2b 00000000 00000000 859ef920 nt!CmpLazyFlushWorker+0x35
8d92bd50 82c6466d 00000001 bc98c096 00000000 nt!ExpWorkerThread+0x10d
8d92bd90 82b160d9 82ac3e1e 00000001 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19


STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: hardware

IMAGE_NAME: hardware

DEBUG_FLR_IMAGE_TIMESTAMP: 0

BUCKET_ID: CPU_CALL_ERROR

Followup: MachineOwner
---------
*** Possible invalid call from 8b8937bd ( Ntfs!NtfsNonCachedUsaWrite+0x7 )
*** Expected target 8b893cd0 ( Ntfs!_SEH_prolog4+0x0 )

0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: 8c2d3cd0, memory referenced.
Arg2: 00000008, value 0 = read operation, 1 = write operation.
Arg3: 8c2d3cd0, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 00000000, (reserved)

Debugging Details:
------------------


Could not read faulting driver name

WRITE_ADDRESS: GetPointerFromAddress: unable to read from 82bbe718
Unable to read MiSystemVaType memory at 82b9e160
8c2d3cd0

FAULTING_IP:
+6416952f00c7df40
8c2d3cd0 ?? ???

MM_INTERNAL_CODE: 0

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x50

PROCESS_NAME: System

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from 8b8937c2 to 8c2d3cd0

POSSIBLE_INVALID_CONTROL_TRANSFER: from 8b8937bd to 8b893cd0

STACK_TEXT:
WARNING: Frame IP not in any known module. Following frames may be wrong.
8d92b1b0 8b8937c2 8b8c0eb8 00000024 8b897fa9 0x8c2d3cd0
8d92b2d0 8b89985f 8d92b2e0 8619f690 0120070a Ntfs!NtfsNonCachedUsaWrite+0xc
8d92b474 82a924bc 86920028 8619f690 8619f690 Ntfs!NtfsFsdWrite+0x2e1
8d92b48c 8b5b320c 8678fed8 8619f690 00000000 nt!IofCallDriver+0x63
8d92b4b0 8b5b33cb 8d92b4d0 8678fed8 00000000 fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x2aa
8d92b4e8 82a924bc 8678fed8 8619f690 8619f690 fltmgr!FltpDispatch+0xc5
8d92b500 82a8a749 8d92b540 00000000 8d92b7a4 nt!IofCallDriver+0x63
8d92b514 82af0aff 86893038 8678fed8 8d92b5e0 nt!IoSynchronousPageWrite+0x19d
8d92b644 82af1f85 8d6a5db0 8d6a5e00 86893e68 nt!MiFlushSectionInternal+0x828
8d92b6ac 82ae5841 00891404 0000a000 00000005 nt!MmFlushSection+0xc2
8d92b740 8b8931e7 86891404 8d92b7ec 0000a000 nt!CcFlushCache+0x156
8d92b814 8b90b38c 8d63c008 2d0f8e89 00000000 Ntfs!LfsFlushLfcb+0x478
8d92b868 8b90b437 0163c008 2d0f8e89 00000000 Ntfs!LfsFlushToLsnPriv+0x1a7
8d92b8ac 82af4d9b 8c7c8158 2d0f8e89 00000000 Ntfs!LfsFlushToLsn+0x87
8d92b948 82ae592f 868a3d00 00000000 00000001 nt!CcAcquireByteRangeForWrite+0xa6f
8d92b9ec 8b90411c 868a3c48 00000000 00000000 nt!CcFlushCache+0x244
8d92ba3c 8b90824b 85e29170 8c6fdbe8 00000000 Ntfs!NtfsFlushBootCritical+0x57
8d92bab0 8b90876b 85e29170 85eb9340 061ed07d Ntfs!NtfsCommonFlushBuffers+0x449
8d92bb18 82a924bc 86920028 85eb9340 85eb9340 Ntfs!NtfsFsdFlushBuffers+0xf7
8d92bb30 8b5b320c 8678fed8 85eb9340 00000000 nt!IofCallDriver+0x63
8d92bb54 8b5b33cb 8d92bb74 8678fed8 00000000 fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x2aa
8d92bb8c 82a924bc 8678fed8 85eb9340 85eb9340 fltmgr!FltpDispatch+0xc5
8d92bba4 82c93eee 85eb9340 876ca370 00000000 nt!IofCallDriver+0x63
8d92bbc4 82c74e5a 8678fed8 876ca370 00000000 nt!IopSynchronousServiceTail+0x1f8
8d92bc30 82a9942a 87798a20 8d92bcc8 8d92bcd0 nt!NtFlushBuffersFile+0x1d7
8d92bc30 82a97341 87798a20 8d92bcc8 8d92bcd0 nt!KiFastCallEntry+0x12a
8d92bcb0 82c53d13 800001a8 8d92bcc8 859ef920 nt!ZwFlushBuffersFile+0x11
8d92bcd0 82cf0832 8c61d008 00000000 00000000 nt!CmpFileFlush+0x5a
8d92bd00 82ac3f2b 00000000 00000000 859ef920 nt!CmpLazyFlushWorker+0x35
8d92bd50 82c6466d 00000001 bc98c096 00000000 nt!ExpWorkerThread+0x10d
8d92bd90 82b160d9 82ac3e1e 00000001 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19


STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: hardware

IMAGE_NAME: hardware

DEBUG_FLR_IMAGE_TIMESTAMP: 0

BUCKET_ID: CPU_CALL_ERROR

Followup: MachineOwner
---------
*** Possible invalid call from 8b8937bd ( Ntfs!NtfsNonCachedUsaWrite+0x7 )
*** Expected target 8b893cd0 ( Ntfs!_SEH_prolog4+0x0 )

0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: 8c2d3cd0, memory referenced.
Arg2: 00000008, value 0 = read operation, 1 = write operation.
Arg3: 8c2d3cd0, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 00000000, (reserved)

Debugging Details:
------------------


Could not read faulting driver name

WRITE_ADDRESS: GetPointerFromAddress: unable to read from 82bbe718
Unable to read MiSystemVaType memory at 82b9e160
8c2d3cd0

FAULTING_IP:
+6416952f00c7df40
8c2d3cd0 ?? ???

MM_INTERNAL_CODE: 0

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x50

PROCESS_NAME: System

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from 8b8937c2 to 8c2d3cd0

POSSIBLE_INVALID_CONTROL_TRANSFER: from 8b8937bd to 8b893cd0

STACK_TEXT:
WARNING: Frame IP not in any known module. Following frames may be wrong.
8d92b1b0 8b8937c2 8b8c0eb8 00000024 8b897fa9 0x8c2d3cd0
8d92b2d0 8b89985f 8d92b2e0 8619f690 0120070a Ntfs!NtfsNonCachedUsaWrite+0xc
8d92b474 82a924bc 86920028 8619f690 8619f690 Ntfs!NtfsFsdWrite+0x2e1
8d92b48c 8b5b320c 8678fed8 8619f690 00000000 nt!IofCallDriver+0x63
8d92b4b0 8b5b33cb 8d92b4d0 8678fed8 00000000 fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x2aa
8d92b4e8 82a924bc 8678fed8 8619f690 8619f690 fltmgr!FltpDispatch+0xc5
8d92b500 82a8a749 8d92b540 00000000 8d92b7a4 nt!IofCallDriver+0x63
8d92b514 82af0aff 86893038 8678fed8 8d92b5e0 nt!IoSynchronousPageWrite+0x19d
8d92b644 82af1f85 8d6a5db0 8d6a5e00 86893e68 nt!MiFlushSectionInternal+0x828
8d92b6ac 82ae5841 00891404 0000a000 00000005 nt!MmFlushSection+0xc2
8d92b740 8b8931e7 86891404 8d92b7ec 0000a000 nt!CcFlushCache+0x156
8d92b814 8b90b38c 8d63c008 2d0f8e89 00000000 Ntfs!LfsFlushLfcb+0x478
8d92b868 8b90b437 0163c008 2d0f8e89 00000000 Ntfs!LfsFlushToLsnPriv+0x1a7
8d92b8ac 82af4d9b 8c7c8158 2d0f8e89 00000000 Ntfs!LfsFlushToLsn+0x87
8d92b948 82ae592f 868a3d00 00000000 00000001 nt!CcAcquireByteRangeForWrite+0xa6f
8d92b9ec 8b90411c 868a3c48 00000000 00000000 nt!CcFlushCache+0x244
8d92ba3c 8b90824b 85e29170 8c6fdbe8 00000000 Ntfs!NtfsFlushBootCritical+0x57
8d92bab0 8b90876b 85e29170 85eb9340 061ed07d Ntfs!NtfsCommonFlushBuffers+0x449
8d92bb18 82a924bc 86920028 85eb9340 85eb9340 Ntfs!NtfsFsdFlushBuffers+0xf7
8d92bb30 8b5b320c 8678fed8 85eb9340 00000000 nt!IofCallDriver+0x63
8d92bb54 8b5b33cb 8d92bb74 8678fed8 00000000 fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x2aa
8d92bb8c 82a924bc 8678fed8 85eb9340 85eb9340 fltmgr!FltpDispatch+0xc5
8d92bba4 82c93eee 85eb9340 876ca370 00000000 nt!IofCallDriver+0x63
8d92bbc4 82c74e5a 8678fed8 876ca370 00000000 nt!IopSynchronousServiceTail+0x1f8
8d92bc30 82a9942a 87798a20 8d92bcc8 8d92bcd0 nt!NtFlushBuffersFile+0x1d7
8d92bc30 82a97341 87798a20 8d92bcc8 8d92bcd0 nt!KiFastCallEntry+0x12a
8d92bcb0 82c53d13 800001a8 8d92bcc8 859ef920 nt!ZwFlushBuffersFile+0x11
8d92bcd0 82cf0832 8c61d008 00000000 00000000 nt!CmpFileFlush+0x5a
8d92bd00 82ac3f2b 00000000 00000000 859ef920 nt!CmpLazyFlushWorker+0x35
8d92bd50 82c6466d 00000001 bc98c096 00000000 nt!ExpWorkerThread+0x10d
8d92bd90 82b160d9 82ac3e1e 00000001 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19


STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: hardware

IMAGE_NAME: hardware

DEBUG_FLR_IMAGE_TIMESTAMP: 0

BUCKET_ID: CPU_CALL_ERROR

Followup: MachineOwner
---------
*** Possible invalid call from 8b8937bd ( Ntfs!NtfsNonCachedUsaWrite+0x7 )
*** Expected target 8b893cd0 ( Ntfs!_SEH_prolog4+0x0 )


Hope this helps. I also have given the link to this thread to someone who is a guru at debugging dump files. I suspect a memory problem from the write error

Ken

 

[BoSox07]

Would it be the RAM chipset or the motherboard?

Thanks,

Dave

 

[johngalt]

Three questions:

1. When you say the machine is pushed - are you referring to physically moving the machine?
2. The temps defintiely look normal - but when you say you updated the drivers, did you use windows 7 specific drivers?
3. When you say it was at 127 deg F before the drach, was this with the stress testing?

I have a feeling that 550W may be cutting it close on that system with that video card. Have you used the eXtreme Power Supply Calculator Lite v2.5 to see how much powe you need?

 

[zigzag3143]

Would it be the RAM chipset or the motherboard?

Thanks,

Dave

Bosox

I have taken quick looks at 5 of the dumps and it appears they are all caused by hardware. Not drivers, I would first check the ram, removing all but 1 memory stick. then I would check the rest of the hardware unplugging anything not critical like usb drives, bluetooth, anything else you dont need.

Im assuming someone has asked you to look in event viewer (tyep event in search) windows log>application tab for errors. I wlso would look in device manager for any unknow devices.

Hope this helps

Ken

 

[BoSox07]

johngalt,

1. Pushed meaning worked harder than just simple internet surfing. Games etc..
2. From Gigabyte and NVIDIA yes
3. Yes during stress testing at idle it bounces between 97-100 deg F
4. I will try your Power Supply Calculator


Ken,

Someone from another forum also suggested running test on just one memory stick. So last night I disconnected the 500G HD and DVD drive and ran test on the RAM sticks. The mother board has four memory slots yellow red yellow red. I tested one stick at a time in each yellow slot. For each stick I ran a15 minute 100% stress test on CPU, RAM, video and then all three at the same time.

Interesting with one stick didn’t matter which one the machine performed as expected no blue screen crashes or lock ups. Put both sticks back in still with the HD and DVD drives disconnected, ran the same test and each one passed. Although when just surfing the internet or flipping though the monitoring software the machine would periodically freeze and locks up but not blue screening.

Not sure what kind of clues this gives.

I have not looked at the event viewer. Device Manager did not show any errors

Thanks,

Dave