Multiple BSOD in Windows 7

[hulagirl]

I keep getting the BSOD in my new Windows 7 computer. Here is the latest bug file:


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


Loading Dump File [C:\Windows\Minidump\021710-141212-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16481.x86fre.win7_gdr.091207-1941
Machine Name:
Kernel base = 0x8324f000 PsLoadedModuleList = 0x83397810
Debug session time: Wed Feb 17 10:01:17.756 2010 (GMT-8)
System Uptime: 0 days 1:03:35.379
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Loading Kernel Symbols
...............................................................
................................................................
.......................................................
Loading User Symbols
Loading unloaded module list
........
Unable to load image \??\C:\Windows\system32\Drivers\SYMEVENT.SYS, Win32 error 0n2
*** WARNING: Unable to verify timestamp for SYMEVENT.SYS
*** ERROR: Module load completed but symbols could not be loaded for SYMEVENT.SYS
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, 922c50c3, 9d0c7b20, 0}

*** WARNING: Unable to verify timestamp for BHDrvx86.sys
*** ERROR: Module load completed but symbols could not be loaded for BHDrvx86.sys
***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Probably caused by : SYMEVENT.SYS ( SYMEVENT+e0c3 )

Followup: MachineOwner
---------

 

[zigzag3143]

I keep getting the BSOD in my new Windows 7 computer. Here is the latest bug file:


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


Loading Dump File [C:\Windows\Minidump\021710-141212-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16481.x86fre.win7_gdr.091207-1941
Machine Name:
Kernel base = 0x8324f000 PsLoadedModuleList = 0x83397810
Debug session time: Wed Feb 17 10:01:17.756 2010 (GMT-8)
System Uptime: 0 days 1:03:35.379
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Loading Kernel Symbols
...............................................................
................................................................
.......................................................
Loading User Symbols
Loading unloaded module list
........
Unable to load image \??\C:\Windows\system32\Drivers\SYMEVENT.SYS, Win32 error 0n2
*** WARNING: Unable to verify timestamp for SYMEVENT.SYS
*** ERROR: Module load completed but symbols could not be loaded for SYMEVENT.SYS
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, 922c50c3, 9d0c7b20, 0}

*** WARNING: Unable to verify timestamp for BHDrvx86.sys
*** ERROR: Module load completed but symbols could not be loaded for BHDrvx86.sys
***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Probably caused by : SYMEVENT.SYS ( SYMEVENT+e0c3 )

Followup: MachineOwner
---------

One question. your build number is different from MS. where did yoou get the dvd?

 

[hulagirl]

I got the whole system refurbished from Dell. I didn't put anything new in it...

 

[hulagirl]

Here is another debug file from a week ago...

 

[hulagirl]

I had another one today. Anyone have any ideas for me? Please...

 

[ickymay]

I keep getting the BSOD in my new Windows 7 computer. Here is the latest bug file:

Probably caused by : SYMEVENT.SYS ( SYMEVENT+e0c3 )

Followup: MachineOwner
---------

SYMEVENT.SYS is Part of Symantec Norton Internet Security suite so either update this or remove it to see if it solves the crashes ?

next time please upload the actual .dmp file for us to analyze

 

[hulagirl]

how do I load the actual .dmp file? It doesn't seem to be a file extension I can upload.

 

[zigzag3143]

Here is another debug file from a week ago...

Is the machine in the DOC file the same as the DMP macine because it is showing yet another build number.

From DOC
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0x82a39000 PsLoadedModuleList = 0x82b81810
Debug session time: Wed Jan 6 14:53:18.584 2010 (GMT-8)
System Uptime: 0 days 0:08:22.223


FROM DMP
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16481.x86fre.win7_gdr.091207-1941
Machine Name:
Kernel base = 0x8324f000 PsLoadedModuleList = 0x83397810
Debug session time: Wed Feb 17 10:01:17.756 2010 (GMT-8)
System Uptime: 0 days 1:03:35.379


See what I mean?

 

[hulagirl]

yes, it is the same machine... Don't know why it would do that... Here are all the dump files

 

[hulagirl]

could it be because it was refurbished?

 

[zigzag3143]

yes, it is the same machine... Don't know why it would do that... Here are all the dump files

OK
You have many different causes. Because you have different sources we must think hardware, or more specifically memory

For that you need to download memtestx86 and run it for 5 passes
for the system files run system file check
(type cmd in search>right click and run as admin>sfc /scannow

Also your frontier desktop (addinmon.exe,) is so old it desperately needs to be updated

If you are oveclocking stop

let us know how these work

Ken

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


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

Symbol search path is: SRV*d:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0x82a05000 PsLoadedModuleList = 0x82b4d810
Debug session time: Fri Jan 29 13:24:39.015 2010 (GMT-5)
System Uptime: 0 days 0:29:26.654
Loading Kernel Symbols
...............................................................
................................................................
............................................
Loading User Symbols
Loading unloaded module list
......
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: ffffff30, memory referenced.
Arg2: 00000000, value 0 = read operation, 1 = write operation.
Arg3: 82a98dda, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 00000000, (reserved)

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


READ_ADDRESS: GetPointerFromAddress: unable to read from 82b6d718
Unable to read MiSystemVaType memory at 82b4d160
 ffffff30 

FAULTING_IP: 
nt!ObReferenceObjectSafe+3
82a98dda 8b0a            mov     ecx,dword ptr [edx]

MM_INTERNAL_CODE:  0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  AddInMon.exe

CURRENT_IRQL:  0

TRAP_FRAME:  b4989754 -- (.trap 0xffffffffb4989754)
ErrCode = 00000000
eax=87b6fd00 ebx=00000000 ecx=00000000 edx=ffffff30 esi=853bed48 edi=82b45e80
eip=82a98dda esp=b49897c8 ebp=b49897e0 iopl=0         nv up ei ng nz ac pe cy
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010297
nt!ObReferenceObjectSafe+0x3:
82a98dda 8b0a            mov     ecx,dword ptr [edx]  ds:0023:ffffff30=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from 82a4b5f8 to 82a8a8e3

STACK_TEXT:  
b498973c 82a4b5f8 00000000 ffffff30 00000000 nt!MmAccessFault+0x106
b498973c 82a98dda 00000000 ffffff30 00000000 nt!KiTrap0E+0xdc
b49897c4 82c8ef6e 0064bbc0 000000b8 0064b808 nt!ObReferenceObjectSafe+0x3
b49897e0 82c42c4c 87b6fd40 99e45ebc 00000000 nt!PsGetNextProcess+0x5e
b4989880 82c393d6 00643be8 00008000 b4989cd0 nt!ExpGetProcessInformation+0x5f7
b4989d00 82c3b48c 00000005 00000000 00000000 nt!ExpQuerySystemInformation+0x1086
b4989d1c 82a4842a 00000005 00643be8 00008000 nt!NtQuerySystemInformation+0x76
b4989d1c 771664f4 00000005 00643be8 00008000 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
0012f51c 00000000 00000000 00000000 00000000 0x771664f4


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!ObReferenceObjectSafe+3
82a98dda 8b0a            mov     ecx,dword ptr [edx]

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  nt!ObReferenceObjectSafe+3

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrpamp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc007

FAILURE_BUCKET_ID:  0x50_nt!ObReferenceObjectSafe+3

BUCKET_ID:  0x50_nt!ObReferenceObjectSafe+3

Followup: MachineOwner
---------

011410-19780-01.dmp    1/14/2010 4:16:08 PM        0x00000119    0x00000002    0xc000000d    0x8e0b8af0    0x86e419d0    dxgkrnl.sys    dxgkrnl.sys+14eb        32-bit    
020810-20155-01.dmp    2/8/2010 9:21:46 AM    BUGCODE_USB_DRIVER    0x000000fe    0x00000006    0x884aa990    0x66725045    0x00000000    USBPORT.SYS    USBPORT.SYS+1025        32-bit    
012110-27970-01.dmp    1/21/2010 5:20:02 AM    DRIVER_CORRUPTED_EXPOOL    0x000000c5    0x00000004    0x00000002    0x00000001    0x82b2f067    tcpip.sys    tcpip.sys+70ff7        32-bit    
011510-18392-01.dmp    1/15/2010 11:59:10 AM    IRQL_NOT_LESS_OR_EQUAL    0x0000000a    0x000001a5    0x00000002    0x00000000    0x82ae0869    ntkrnlpa.exe    ntkrnlpa.exe+467eb        32-bit    
011510-20545-01.dmp    1/15/2010 10:19:52 AM    IRQL_NOT_LESS_OR_EQUAL    0x0000000a    0xffffffb8    0x00000002    0x00000000    0x82a3baca    ntkrnlpa.exe    ntkrnlpa.exe+467eb        32-bit    
012010-21091-01.dmp    1/20/2010 2:54:48 PM    IRQL_NOT_LESS_OR_EQUAL    0x0000000a    0x00000004    0x00000002    0x00000001    0x82aae9c6    ntkrnlpa.exe    ntkrnlpa.exe+467eb        32-bit    
021110-18642-01.dmp    2/11/2010 12:01:24 PM    KERNEL_MODE_EXCEPTION_NOT_HANDLED    0x1000008e    0xc0000005    0x8c9c0c29    0xd8183ab4    0x00000000    CLASSPNP.SYS    CLASSPNP.SYS+4c29        32-bit    
020910-25802-01.dmp    2/9/2010 4:43:14 PM    KERNEL_MODE_EXCEPTION_NOT_HANDLED    0x1000008e    0xc0000005    0x9322d438    0xb5305674    0x00000000    dlkmd.sys    dlkmd.sys+2438        32-bit    
020810-27736-01.dmp    2/8/2010 11:07:18 AM    KERNEL_MODE_EXCEPTION_NOT_HANDLED    0x1000008e    0xc0000005    0x832e2dda    0xb5b9c744    0x00000000    ntkrnlpa.exe    ntkrnlpa.exe+93dda        32-bit    
010610-30420-01.dmp    1/6/2010 2:54:30 PM    KERNEL_MODE_EXCEPTION_NOT_HANDLED    0x1000008e    0xc0000005    0x00000000    0x8fcdd8bc    0x00000000    win32k.sys    win32k.sys+ba867        32-bit    
012610-26566-01.dmp    1/26/2010 3:24:48 PM    PAGE_FAULT_IN_NONPAGED_AREA    0x00000050    0x89e19002    0x00000000    0xb80a65ba    0x00000000    ndis.sys    ndis.sys+1ca5        32-bit    
012910-23462-01.dmp    1/29/2010 9:39:58 AM    PAGE_FAULT_IN_NONPAGED_AREA    0x00000050    0x88e00000    0x00000000    0x82a877d3    0x00000000    ndis.sys    ndis.sys+2c261        32-bit    
012910-19687-01.dmp    1/29/2010 10:25:38 AM    PAGE_FAULT_IN_NONPAGED_AREA    0x00000050    0xffffff30    0x00000000    0x82a98dda    0x00000000    ntkrnlpa.exe    ntkrnlpa.exe+858e3        32-bit    
020410-45411-01.dmp    2/4/2010 12:23:54 PM    REFERENCE_BY_POINTER    0x00000018    0x00000000    0x883b2730    0x00000002    0x91868814    ntkrnlpa.exe    ntkrnlpa.exe+dcd10        32-bit

OLD DRIVERS

mdmxsdk.sys        0x9add4000    0x9add7180    0x00003180    0x449716a3    6/19/2006 4:26:59 PM                        
secdrv.SYS        0xae0cc000    0xae0d6000    0x0000a000    0x45080528    9/13/2006 8:18:32 AM

 

[hulagirl]

Not overclocking. Attached is what I get when I do the system files check.

How do I update the addinmon.exe?

Trying to run memtestx86 but having trouble creating the bootable CD

 

[hulagirl]

Ran memtest86 once (because I'm at work and need to use my computer today) and got no errors. I'll trying running additional times this weekend. But that CBS log shows some problems for sure....

Any other thoughts? Computer is under warranty...

 

[ickymay]

Ran memtest86 once (because I'm at work and need to use my computer today) and got no errors. I'll trying running additional times this weekend. But that CBS log shows some problems for sure....

Any other thoughts? Computer is under warranty...

return under warranty is always the best option if it's not too painful and they are responsible for providing a working system

did you try removing Norton and using MSE temporarily ?

 

[hulagirl]

well, I ran the memtest86 9 times last night. No errors.... So, at least that is good. Have not removed Norton yet. I only installed it last week. So, it may have been the cause of my last crash, but certainly not the previous ones.

 

[hulagirl]

Dell says I have no software support and that this is a software issue... Any other thoughts? Got two more BSOD today...

 

[ickymay]

Dell says I have no software support and that this is a software issue... Any other thoughts? Got two more BSOD today...

we need the dmp files ?

 

[hulagirl]

dmp files are in post #9

 

[ickymay]

Dell says I have no software support and that this is a software issue... Any other thoughts? Got two more BSOD today...

we have looked at your .dmp files from post 9 but we need the files from your latest two dumps you mentioned here ?

new minidumps show new things and or show a trend

 

[hulagirl]

Here are the new dmps