BSOD at random time at ntoskrnl.exe (nt+0x75C40) and ntkrnlmp.exe (nt

CyberAxe · 19 Feb 2013

I have a client who's had a repeating BSOD and I need help with a debug please. - I reloaded the system about 2 months ago. Windows is updated but I'm sure the hardware drivers are outdated. I also added Ram but the system was runnning great for a month.

One user said when they started Internet.

The computer has rebooted from a bugcheck. The bugcheck was: 0x0000003b (0x00000000c0000005, 0xfffff80002bcc2dc, 0xfffff8800416d120, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 021913-19890-01.

Whocrashed
-------------------------------------------------
System Information (local)
</B>
computer name: VET01
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 3200569344 total
VM: 2147352576, free: 1958760448

Crash Dump Analysis
</B>
Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Tue 2/19/2013 1:32:03 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\021913-19890-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C40)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002BCC2DC, 0xFFFFF8800416D120, 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 that cannot be identified at this time.

On Tue 2/19/2013 1:32:03 PM 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, 0xFFFFF80002BCC2DC, 0xFFFFF8800416D120, 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 that cannot be identified at this time.

On Sat 2/16/2013 5:49:10 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\021513-30201-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C10)
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 that cannot be identified at this time.

On Sat 2/16/2013 5:47:09 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\021513-33384-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C40)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002B792DC, 0xFFFFF88004FB9F60, 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 that cannot be identified at this time.

Dsprague · 20 Feb 2013

PLease update the following drivers:

Code:

atikmdag  Fri Apr 24 06:51:57 2009 can be updated here http://support.amd.com/us/Pages/AMDSupportHub.aspx

e1e6232e           Fri Jun 05 15:08:41 2009 can be updated here Intel Download Center

Updates the Bios from the computer manufactureres web page (if an update is available):

Code:

BIOS Release Date             07/21/2011

last i Notice that all the ram in the system seems to be running at different frequencies which can cause all sorts of odd problems, when adding memory to a computer( at least this is my policy) it is best to make sure that the ram matches aall other ram in the computer for specs or it can cause issues.

Code:

[Memory Device (Type 17) - Length 27 - Handle 0035h]
  Physical Memory Array Handle  0033h
  Memory Error Info Handle      [Not Provided]
  Total Width                   64 bits
  Data Width                    64 bits
  Size                          1024MB
  Form Factor                   09h - DIMM
  Device Set                    01h
  Device Locator                XMM1
  Bank Locator                  [String Not Specified]
  Memory Type                   13h - Specification Reserved
  Type Detail                   0080h - Synchronous
  Speed                         667MHz
  Manufacturer                  JEDEC ID:7F 7F 7F 7F 7F F7 00 00
  Serial Number                         
  Asset Tag Number              [String Not Specified]
  Part Number

Code:

[Memory Device (Type 17) - Length 27 - Handle 0036h]
  Physical Memory Array Handle  0033h
  Memory Error Info Handle      [Not Provided]
  Total Width                   64 bits
  Data Width                    64 bits
  Size                          1024MB
  Form Factor                   09h - DIMM
  Device Set                    01h
  Device Locator                XMM2
  Bank Locator                  [String Not Specified]
  Memory Type                   13h - Specification Reserved
  Type Detail                   0080h - Synchronous
  Speed                         800MHz
  Manufacturer                  JEDEC ID:CE 00 00 00 00 00 00 00
  Serial Number                         
  Asset Tag Number              [String Not Specified]
  Part Number                   M3 78T2953EZ3-CF7

Code:

[Memory Device (Type 17) - Length 27 - Handle 0037h]
  Physical Memory Array Handle  0033h
  Memory Error Info Handle      [Not Provided]
  Total Width                   64 bits
  Data Width                    64 bits
  Size                          1024MB
  Form Factor                   09h - DIMM
  Device Set                    02h
  Device Locator                XMM3
  Bank Locator                  [String Not Specified]
  Memory Type                   13h - Specification Reserved
  Type Detail                   0080h - Synchronous
  Speed                         800MHz
  Manufacturer                  JEDEC ID:CE 00 00 00 00 00 00 00
  Serial Number                         
  Asset Tag Number              [String Not Specified]
  Part Number                   M3 78T2953EZ3-CF7

CyberAxe · 21 Feb 2013

lol, yeah on the ram I had a box of old ram I just put in anything that would work to get it up.

I'll have to look at that, it was my first bet as to the BSOD but it's all I have. This client is strapped for cash but all their computers had less than 1mb ram.

Thank you, I'll do as advised and see what happens.