BSOD - System_Service_Exception (3B)

[Whilom]

Norm - Yes a walkthough would be ideal, thanks!

Fumz - I'm not attempting to stop people from helping me, I don't know anything about RAM modules and I'm just trying to provide as much information as I can.

 

[NormCameron]

Do you have CPU-Z. It's a free download, run without an install. Run it and post me a snip of your Memory and SPD.

 

[Whilom]

Chipset
------------------------------------------------------------------------------
Northbridge  Intel P35/G33/G31 rev. A2
Southbridge  Intel 82801IB (ICH9) rev. 02
Graphic Interface PCI-Express
PCI-E Link Width x16
PCI-E Max Link Width x16
Memory Type  DDR2
Memory Size  4096 MBytes
Channels  Dual (Symmetric)
Memory Frequency 533.3 MHz (1:2)
CAS#   5.0
RAS# to CAS#  7
RAS# Precharge  7
Cycle Time (tRAS) 24
Command Rate  2T

 Memory SPD
------------------------------------------------------------------------------
DIMM #1
General
Memory type  DDR2
Module format  Regular UDIMM
Manufacturer (ID) Crucial Technology (7F7F7F7F7F9BFFFF)
Size   1024 MBytes
Max bandwidth  PC2-6400 (400 MHz)
Part number  
Serial number  801139E6
Manufacturing date Week 165/Year 165
Attributes
Number of banks  1
Data width  64 bits
Correction  None
Nominal Voltage  1.80 Volts
EPP   yes (2 profiles)
XMP   no
Timings table
Frequency (MHz)  266 333 400 
CAS#   3.0 4.0 5.0 
RAS# to CAS# delay 4 5 5 
RAS# Precharge  4 5 5 
TRAS   12 15 18 
TRC   16 20 23 
EPP profile 1 (full)
Voltage level  2.000 Volts
Address Command Rate 2T
Cycle time  2.500 ns (400.0 MHz)
tCL   4.0 clocks
tRCD   4 clocks (10.00 ns)
tRP   4 clocks (10.00 ns)
tRAS   12 clocks (30.00 ns)
tRC   24 clocks (60.00 ns)
tWR   6 clocks (15.00 ns)
EPP profile 2 (full)
Voltage level  2.000 Volts
Address Command Rate 2T
Cycle time  1.875 ns (533.3 MHz)
tCL   5.0 clocks
tRCD   5 clocks (9.00 ns)
tRP   5 clocks (9.00 ns)
tRAS   15 clocks (28.00 ns)
tRC   30 clocks (55.00 ns)
tWR   8 clocks (15.00 ns)
 
DIMM #2
General
Memory type  DDR2
Module format  Regular UDIMM
Manufacturer (ID) Crucial Technology (7F7F7F7F7F9BFFFF)
Size   1024 MBytes
Max bandwidth  PC2-6400 (400 MHz)
Part number  
Serial number  8A71CD11
Manufacturing date Week 165/Year 165
Attributes
Number of banks  1
Data width  64 bits
Correction  None
Nominal Voltage  1.80 Volts
EPP   yes (2 profiles)
XMP   no
Timings table
Frequency (MHz)  266 333 400 
CAS#   3.0 4.0 5.0 
RAS# to CAS# delay 4 5 5 
RAS# Precharge  4 5 5 
TRAS   12 15 18 
TRC   16 20 23 
EPP profile 1 (full)
Voltage level  2.000 Volts
Address Command Rate 2T
Cycle time  2.500 ns (400.0 MHz)
tCL   4.0 clocks
tRCD   4 clocks (10.00 ns)
tRP   4 clocks (10.00 ns)
tRAS   12 clocks (30.00 ns)
tRC   24 clocks (60.00 ns)
tWR   6 clocks (15.00 ns)
EPP profile 2 (full)
Voltage level  2.000 Volts
Address Command Rate 2T
Cycle time  1.875 ns (533.3 MHz)
tCL   5.0 clocks
tRCD   5 clocks (9.00 ns)
tRP   5 clocks (9.00 ns)
tRAS   15 clocks (28.00 ns)
tRC   30 clocks (55.00 ns)
tWR   8 clocks (15.00 ns)
 
DIMM #3
General
Memory type  DDR2
Module format  Regular UDIMM
Manufacturer (ID) Crucial Technology (7F7F7F7F7F9BFFFF)
Size   1024 MBytes
Max bandwidth  PC2-6400 (400 MHz)
Part number  
Serial number  801139EA
Manufacturing date Week 165/Year 165
Attributes
Number of banks  1
Data width  64 bits
Correction  None
Nominal Voltage  1.80 Volts
EPP   yes (2 profiles)
XMP   no
Timings table
Frequency (MHz)  266 333 400 
CAS#   3.0 4.0 5.0 
RAS# to CAS# delay 4 5 5 
RAS# Precharge  4 5 5 
TRAS   12 15 18 
TRC   16 20 23 
EPP profile 1 (full)
Voltage level  2.000 Volts
Address Command Rate 2T
Cycle time  2.500 ns (400.0 MHz)
tCL   4.0 clocks
tRCD   4 clocks (10.00 ns)
tRP   4 clocks (10.00 ns)
tRAS   12 clocks (30.00 ns)
tRC   24 clocks (60.00 ns)
tWR   6 clocks (15.00 ns)
EPP profile 2 (full)
Voltage level  2.000 Volts
Address Command Rate 2T
Cycle time  1.875 ns (533.3 MHz)
tCL   5.0 clocks
tRCD   5 clocks (9.00 ns)
tRP   5 clocks (9.00 ns)
tRAS   15 clocks (28.00 ns)
tRC   30 clocks (55.00 ns)
tWR   8 clocks (15.00 ns)
 
DIMM #4
General
Memory type  DDR2
Module format  Regular UDIMM
Manufacturer (ID) Crucial Technology (7F7F7F7F7F9BFFFF)
Size   1024 MBytes
Max bandwidth  PC2-6400 (400 MHz)
Part number  
Serial number  81047A8C
Manufacturing date Week 165/Year 165
Attributes
Number of banks  1
Data width  64 bits
Correction  None
Nominal Voltage  1.80 Volts
EPP   yes (2 profiles)
XMP   no
Timings table
Frequency (MHz)  266 333 400 
CAS#   3.0 4.0 5.0 
RAS# to CAS# delay 4 5 5 
RAS# Precharge  4 5 5 
TRAS   12 15 18 
TRC   16 20 23 
EPP profile 1 (full)
Voltage level  2.000 Volts
Address Command Rate 2T
Cycle time  2.500 ns (400.0 MHz)
tCL   4.0 clocks
tRCD   4 clocks (10.00 ns)
tRP   4 clocks (10.00 ns)
tRAS   12 clocks (30.00 ns)
tRC   24 clocks (60.00 ns)
tWR   6 clocks (15.00 ns)
EPP profile 2 (full)
Voltage level  2.000 Volts
Address Command Rate 2T
Cycle time  1.875 ns (533.3 MHz)
tCL   5.0 clocks
tRCD   5 clocks (9.00 ns)
tRP   5 clocks (9.00 ns)
tRAS   15 clocks (28.00 ns)
tRC   30 clocks (55.00 ns)
tWR   8 clocks (15.00 ns)

Anything else needed?

 

[NormCameron]

Can you give me the CPU-Z snip?

 

[Whilom]

The actual file?

Attached.

Or do you want screen shots?

 

[NormCameron]

Screen Shots would be better for what I want to see.

 

[Whilom]

Attached.

 

[NormCameron]

Just looking at what you sent me previously . Everything seems to be OK. I am still sure the problem is with your MOBO and 4 x 1gb sticks of RAM. Could you please try just 2 for a while to let me move on if that isn't the problem?

 

[NormCameron]

Going to bed now. See you tommorrow.

 

[Whilom]

OK - I will try that. I have also now removed the sound card.

Thank you for your suggestions, I very much appreciate them.

Could I just show you my latest crash dump, this happened a few moments ago. This is the first one to suggest hardware:

BugCheck 24, {1904aa, fffffa600d470598, fffffa600d46ff70, fffffa60010f165f}
Probably caused by : hardware ( Ntfs!NtfsCreateNewFile+cf )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
NTFS_FILE_SYSTEM (24)
    If you see NtfsExceptionFilter on the stack then the 2nd and 3rd
    parameters are the exception record and context record. Do a .cxr
    on the 3rd parameter and then kb to obtain a more informative stack
    trace.
Arguments:
Arg1: 00000000001904aa
Arg2: fffffa600d470598
Arg3: fffffa600d46ff70
Arg4: fffffa60010f165f
Debugging Details:
------------------

EXCEPTION_RECORD:  fffffa600d470598 -- (.exr 0xfffffa600d470598)
ExceptionAddress: fffffa60010f165f (Ntfs!NtfsCreateNewFile+0x00000000000000cf)
   ExceptionCode: c000001d (Illegal instruction)
  ExceptionFlags: 00000000
NumberParameters: 0
CONTEXT:  fffffa600d46ff70 -- (.cxr 0xfffffa600d46ff70)
rax=fffffa600d470bf0 rbx=fffffa60019bf0b0 rcx=fffffa8007aabe50
rdx=fffffa800513f810 rsi=fffff8800015abd0 rdi=fffffa60019bf0b8
rip=fffffa60010f165f rsp=fffffa600d4707d0 rbp=fffffa800513f810
 r8=fffff8800015abd0  r9=fffff8800ac39f60 r10=0000000010000000
r11=fffffa600d470b28 r12=fffffa600d470bd8 r13=0000000000000000
r14=fffffa8007aabe50 r15=0000000000000000
iopl=0         nv up ei ng nz ac po cy
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010297
Ntfs!NtfsCreateNewFile+0xcf:
fffffa60`010f165f 60              ???
Resetting default scope
CUSTOMER_CRASH_COUNT:  2
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x24
PROCESS_NAME:  System
CURRENT_IRQL:  0
ERROR_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION}  Illegal Instruction  An attempt was made to execute an illegal instruction.
LAST_CONTROL_TRANSFER:  from fffffa60010e4f88 to fffffa60010f165f
MISALIGNED_IP: 
Ntfs!NtfsCreateNewFile+cf
fffffa60`010f165f 60              ???
STACK_TEXT:  
fffffa60`0d4707d0 fffffa60`010e4f88 : fffffa80`07aabe50 fffffa60`019bf0b0 fffffa80`07aabe50 fffff880`0ddccb01 : Ntfs!NtfsCreateNewFile+0xcf
fffffa60`0d470b30 fffffa60`0102b10d : fffffa80`07aabe50 fffffa80`0513f810 fffffa60`019bf0b0 fffffa80`036afb03 : Ntfs!NtfsCommonCreate+0x988
fffffa60`0d470d30 fffff800`01ea4697 : fffffa60`019bf020 00000000`044ffa58 00000000`77432f00 00000000`00000000 : Ntfs!NtfsCommonCreateCallout+0x1d
fffffa60`0d470d60 fffff800`01ea464e : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxSwitchKernelStackCallout+0x27
fffffa60`019bef40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSwitchKernelStackContinue

FOLLOWUP_IP: 
Ntfs!NtfsCreateNewFile+cf
fffffa60`010f165f 60              ???
SYMBOL_STACK_INDEX:  0
SYMBOL_NAME:  Ntfs!NtfsCreateNewFile+cf
FOLLOWUP_NAME:  MachineOwner
IMAGE_NAME:  hardware
DEBUG_FLR_IMAGE_TIMESTAMP:  0
STACK_COMMAND:  .cxr 0xfffffa600d46ff70 ; kb
MODULE_NAME: hardware
FAILURE_BUCKET_ID:  X64_IP_MISALIGNED_Ntfs.sys
BUCKET_ID:  X64_IP_MISALIGNED_Ntfs.sys
Followup: MachineOwner

Many thanks again,

- W

 

[Whilom]

Going to bed now. See you tommorrow.

Ok, no problem! Thank you! See you tomorrow.

 

[NormCameron]

Hi Whilom, how did you get on?

 

[Whilom]

Well, I spoke to a guy from Crucial who suggested some changes... I couldn't actually make those changes because I didn't have a clue how to do them in the BIOS - but one thing I did manage to do was to change my RAM to run at 800MHz... This change has changed my timing from 5-7-7-24 to 5-5-5-18 (which is very close to what they're supposed to be I believe). Now, I don't know anything about timings or what they mean... But I ran Memtest86 overnight again and there were no errors!

Could the incorrect timing of RAM or the incorrect MHz setting of RAM cause BSOD and also Memtest to show errors? If it can then I might have found the cause - fingers crossed!

 

[NormCameron]

Every chance that is the case. Got mine crossed too. Keep me posted. If you need help on changing BIOS setting let me know.

 

[Bare Foot Kid]

Hello Whilom.

I too hope you've found your solution!















Later Ted

 

[NormCameron]

Whilom, I've been having a look at the crash dump you sent me and while I am not certain, it seems to relate to a memory leak which ties in with what we've been looking at.

 

[mikeface]

Whilom when u tested each stick of ram individually, did you use the same ram slot? if so, i would try a stick of ram that tested good on each slot individually and test it that way. I have come across motherboards with bad ram slots. that could cause you errors when testing all sticks of ram together