Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: Computer crashing regular sometimes bsod sometimes straight to reboot


24 Dec 2010   #1

Windows 7 Home Premium 64 bit
 
 
Computer crashing regular sometimes bsod sometimes straight to reboot

Hi Hope I have got the post ok with the correct attachments and right information. Apologies if it is wrong.

System information:

- 64 bit version of Windows 7 Home Premium - Windows 7 was the original installed OS on the system when it was purchased new (about 10 months ago) so i guess this makes it OEM.
- Intel Core i5 Processor 650 (3.20GHz, 4MB)
- 6144MB (2x2GB) (2x1GB)1067MHz DDR3 Dual Channel Memory
- Graphics - 1GB Nvidia GeForce GTS 240
- 2TB Dual Hard Drive Raid 0 "Stripe" (2x1TB - 7200rpm)


The problem:

The computer has been crashing randomly for the last 2 or 3 months (the problem may have been here longer but i hardly used it over the summer so i dont know) but i am only getting a blue screen with error messages about half the time, the other times it is just crashing then rebooting. The blue screen error message seems to vary each time.

It isn't crashing with any particular programme opening it seems to be random. It was even sometimes crashing before logging in and then sometimes crashing after 3 or 4 hours of use. I've tried various virus scan programs and nothing came up and as it was happening randomly im not sure if it is a particular program that is causing it or not. I eventually phoned up dell technical support and they had me run some memory test and that seemed to be ok, so then i went about updating all the drivers but that didn't fix things (and it was a really struggle updating the drivers because the computer kept crashing!) Eventually did a system restore. That sort of improved it, i havent crashed immediately upon logging in since i done that. But i'm still crashing frequently. (i went whole years with xp and vista without the amount of bsods i seem to get most days!). I'm really stuck here and not sure what to do so really appreciate any help.

happy holidays.

My System SpecsSystem Spec
.

24 Dec 2010   #2

Windows 7 Ultimate 32 bit
 
 

Hi Anna and welcome to the forum. I looked at your three most recent dumps. Two of them blame memory corruption and the third indicates memory corruption.

The dumps show that McAfee was heavily involved the crashes. McAfee is a known and notorious cause of BSOD's on some Win 7 systems. I recommend that you completely uninstall it using this removal tool: Tool. Download and install Microsoft Security Essentials in its place. MSE will not cause conflicts and BSOD's. Make sure Windows Firewall is turned on.

I find an obsolete driver loaded on your system. Out of date drivers can and do cause memory corruption and BSOD's. Update this driver through the link provided. If there is no update, the Blackberry software is obsolete. Uninstall it.
Quote:
RimSerial_AMD64.sys Mon Nov 24 12:01:01 2008 - Virtual Serial Port driver for Blackberry. Research In Motion - Products.
Uninstall McAfee and take care of the above driver. Reboot and see how your system does. Please post back and let us know. If you get another BSOD after doing the above, upload it and we will go from there.
Code:
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`0304b000 PsLoadedModuleList = 0xfffff800`03288e50
Debug session time: Wed Dec 15 15:24:43.468 2010 (GMT-5)
System Uptime: 0 days 0:01:42.998
Loading Kernel Symbols
...............................................................
................................................................
.......................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {ffffffffc0000005, fffff800030eb903, 0, 21}

Probably caused by : memory_corruption ( nt!MiCheckForConflictingNode+13 )

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

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

KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff800030eb903, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000021, Parameter 1 of the exception

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
nt!MiCheckForConflictingNode+13
fffff800`030eb903 483b4820        cmp     rcx,qword ptr [rax+20h]

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000021

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800032f30e0
 0000000000000021 

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x1E

PROCESS_NAME:  wmpnetwk.exe

CURRENT_IRQL:  0

EXCEPTION_RECORD:  fffff8800ac4b438 -- (.exr 0xfffff8800ac4b438)
ExceptionAddress: fffff800030eb903 (nt!MiCheckForConflictingNode+0x0000000000000013)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: 0000000000000021
Attempt to read from address 0000000000000021

TRAP_FRAME:  fffff8800ac4b4e0 -- (.trap 0xfffff8800ac4b4e0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000001 rbx=0000000000000000 rcx=0000000000002276
rdx=0000000000002277 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800030eb903 rsp=fffff8800ac4b678 rbp=fffff8800ac4b920
 r8=fffffa800b4be4a8  r9=0000000000000002 r10=0000000002277fff
r11=0000000000000011 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
nt!MiCheckForConflictingNode+0x13:
fffff800`030eb903 483b4820        cmp     rcx,qword ptr [rax+20h] ds:00000000`00000021=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800030f5a39 to fffff800030bb740

STACK_TEXT:  
fffff880`0ac4ac68 fffff800`030f5a39 : 00000000`0000001e ffffffff`c0000005 fffff800`030eb903 00000000`00000000 : nt!KeBugCheckEx
fffff880`0ac4ac70 fffff800`030bad82 : fffff880`0ac4b438 fffffa80`0b4be060 fffff880`0ac4b4e0 00000000`00001000 : nt!KiDispatchException+0x1b9
fffff880`0ac4b300 fffff800`030b98fa : 00000000`00000000 fffffa80`0b4be060 0000002b`0227ae00 0000ffff`00001fa0 : nt!KiExceptionDispatch+0xc2
fffff880`0ac4b4e0 fffff800`030eb903 : fffff800`033bd384 fffff8a0`0215e5a0 fffff880`0ac4b600 00000000`000007ff : nt!KiPageFault+0x23a
fffff880`0ac4b678 fffff800`033bd384 : fffff8a0`0215e5a0 fffff880`0ac4b600 00000000`000007ff 00000000`00000030 : nt!MiCheckForConflictingNode+0x13
fffff880`0ac4b680 fffff800`030ba993 : ffffffff`ffffffff fffff880`0ac4bad8 00000000`00000000 fffff880`0ac4ba78 : nt!NtAllocateVirtualMemory+0x2a4
fffff880`0ac4b830 fffff800`030b6f30 : fffff800`033a4ad7 fffff880`0ac4bb78 00000000`00000000 fffff880`0ac4bc20 : nt!KiSystemServiceCopyEnd+0x13
fffff880`0ac4ba38 fffff800`033a4ad7 : fffff880`0ac4bb78 00000000`00000000 fffff880`0ac4bc20 fffff800`0309ff48 : nt!KiServiceLinkage
fffff880`0ac4ba40 fffff800`030d6b1e : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`02276000 : nt!MiCheckForUserStackOverflow+0x15f
fffff880`0ac4bac0 fffff800`030b982e : 00000000`00000001 00000000`00000000 00000000`0227f001 000007fe`fe63b898 : nt!MmAccessFault+0x171e
fffff880`0ac4bc20 00000000`7779592d : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
00000000`02278b50 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7779592d


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiCheckForConflictingNode+13
fffff800`030eb903 483b4820        cmp     rcx,qword ptr [rax+20h]

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  nt!MiCheckForConflictingNode+13

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0x1E_nt!MiCheckForConflictingNode+13

BUCKET_ID:  X64_0x1E_nt!MiCheckForConflictingNode+13

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

Debug session time: Wed Dec 22 14:21:41.457 2010 (GMT-5)
System Uptime: 0 days 22:49:02.597
Loading Kernel Symbols
...............................................................
................................................................
.......................
Loading User Symbols
Loading unloaded module list
.............
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 4E, {99, 1a0c67, 0, 5bb68}

Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )

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

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

PFN_LIST_CORRUPT (4e)
Typically caused by drivers passing bad memory descriptor lists (ie: calling
MmUnlockPages twice with the same list, etc).  If a kernel debugger is
available get the stack trace.
Arguments:
Arg1: 0000000000000099, A PTE or PFN is corrupt
Arg2: 00000000001a0c67, page frame number
Arg3: 0000000000000000, current page state
Arg4: 000000000005bb68, 0

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


BUGCHECK_STR:  0x4E_99

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  vdsldr.exe

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff8000311738c to fffff80003087740

STACK_TEXT:  
fffff880`0aa206f8 fffff800`0311738c : 00000000`0000004e 00000000`00000099 00000000`001a0c67 00000000`00000000 : nt!KeBugCheckEx
fffff880`0aa20700 fffff800`030f99f7 : fffffa80`0c898548 fffff800`0318dabb 00000000`00000000 00000000`00001000 : nt!MiBadShareCount+0x4c
fffff880`0aa20740 fffff800`0305bc23 : fffffa80`0c8981b0 00000000`00000057 fffff700`01080fc8 fffff680`003b6680 : nt! ?? ::FNODOBFM::`string'+0x3223e
fffff880`0aa207d0 fffff800`0305a68a : fffffa80`0c8981b0 fffffa80`00000000 00000000`00000010 fffffa80`00000000 : nt!MiDeleteAddressesInWorkingSet+0x307
fffff880`0aa21080 fffff800`0336cdcf : fffffa80`0b7d5540 00000000`00000001 00000000`00000000 fffffa80`05fe2b60 : nt!MmCleanProcessAddressSpace+0x96
fffff880`0aa210d0 fffff800`0334485b : 00000000`c0000005 00000000`00000001 000007ff`fffdd000 00000000`00000000 : nt!PspExitThread+0x92f
fffff880`0aa21190 fffff800`03086993 : fffffa80`0c8981b0 fffff800`c0000005 ffffe571`803173b0 fffffa80`05fe2b60 : nt!NtTerminateProcess+0x25b
fffff880`0aa21210 fffff800`03082f30 : fffff800`030c1dbc fffff880`0aa21b78 fffff880`0aa218e0 fffff880`0aa21c20 : nt!KiSystemServiceCopyEnd+0x13
fffff880`0aa213a8 fffff800`030c1dbc : fffff880`0aa21b78 fffff880`0aa218e0 fffff880`0aa21c20 00000000`00000000 : nt!KiServiceLinkage
fffff880`0aa213b0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchException+0x53b


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiBadShareCount+4c
fffff800`0311738c cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!MiBadShareCount+4c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0x4E_99_nt!MiBadShareCount+4c

BUCKET_ID:  X64_0x4E_99_nt!MiBadShareCount+4c

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

Debug session time: Fri Dec 24 13:32:19.820 2010 (GMT-5)
System Uptime: 1 days 23:09:08.350
Loading Kernel Symbols
...............................................................
................................................................
........................
Loading User Symbols
Loading unloaded module list
.................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 35, {fffffa800ae9fc10, 0, 0, 0}

Probably caused by : intelppm.sys ( intelppm!MWaitIdle+19 )

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

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

NO_MORE_IRP_STACK_LOCATIONS (35)
A higher level driver has attempted to call a lower level driver through
the IoCallDriver() interface, but there are no more stack locations in the
packet, hence, the lower level driver would not be able to access its
parameters, as there are no parameters for it.  This is a disasterous
situation, since the higher level driver "thinks" it has filled in the
parameters for the lower level driver (something it MUST do before it calls
it), but since there is no stack location for the latter driver, the former
has written off of the end of the packet.  This means that some other memory
has probably been trashed at this point.
Arguments:
Arg1: fffffa800ae9fc10, Address of the IRP
Arg2: 0000000000000000
Arg3: 0000000000000000
Arg4: 0000000000000000

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


CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x35

PROCESS_NAME:  System

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff800030e124a to fffff88000dd4c61

STACK_TEXT:  
fffff800`00b9cc98 fffff800`030e124a : 00000000`002f9097 fffffa80`09a7f2d0 fffff800`0324de80 00000000`00000000 : intelppm!MWaitIdle+0x19
fffff800`00b9cca0 fffff800`030dbebc : fffff800`0324de80 fffff800`00000001 00000000`00000001 fffff880`00000000 : nt!PoIdle+0x53a
fffff800`00b9cd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x2c


STACK_COMMAND:  kb

FOLLOWUP_IP: 
intelppm!MWaitIdle+19
fffff880`00dd4c61 c3              ret

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  intelppm!MWaitIdle+19

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: intelppm

IMAGE_NAME:  intelppm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc0fd

FAILURE_BUCKET_ID:  X64_0x35_intelppm!MWaitIdle+19

BUCKET_ID:  X64_0x35_intelppm!MWaitIdle+19

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

0: kd> lmtsmn
start             end                 module name
fffff880`044d5000 fffff880`04513000   1394ohci 1394ohci.sys Mon Jul 13 20:07:12 2009 (4A5BCC30)
fffff880`00f23000 fffff880`00f7a000   ACPI     ACPI.sys     Mon Jul 13 19:19:34 2009 (4A5BC106)
fffff880`0183f000 fffff880`018c9000   afd      afd.sys      Mon Jul 13 19:21:40 2009 (4A5BC184)
fffff880`0452a000 fffff880`04540000   AgileVpn AgileVpn.sys Mon Jul 13 20:10:24 2009 (4A5BCCF0)
fffff880`01271000 fffff880`0127c000   amdxata  amdxata.sys  Tue May 19 13:56:59 2009 (4A12F2EB)
fffff880`05863000 fffff880`059e0000   athrx    athrx.sys    Fri Oct 23 21:49:44 2009 (4AE25D38)
fffff880`04104000 fffff880`0410b000   Beep     Beep.SYS     Mon Jul 13 20:00:13 2009 (4A5BCA8D)
fffff880`019c3000 fffff880`019d4000   blbdrive blbdrive.sys Mon Jul 13 19:35:59 2009 (4A5BC4DF)
fffff880`06365000 fffff880`06383000   bowser   bowser.sys   Mon Jul 13 19:23:50 2009 (4A5BC206)
fffff960`006b0000 fffff960`006d7000   cdd      cdd.dll      unavailable (00000000)
fffff880`040d1000 fffff880`040fb000   cdrom    cdrom.sys    Mon Jul 13 19:19:54 2009 (4A5BC11A)
fffff880`069db000 fffff880`069e8980   cfwids   cfwids.sys   Wed Oct 06 16:00:36 2010 (4CACD564)
fffff880`00c00000 fffff880`00cc0000   CI       CI.dll       Mon Jul 13 21:32:13 2009 (4A5BE01D)
fffff880`01801000 fffff880`01831000   CLASSPNP CLASSPNP.SYS Mon Jul 13 19:19:58 2009 (4A5BC11E)
fffff880`00d20000 fffff880`00d7e000   CLFS     CLFS.SYS     Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`01661000 fffff880`016d4000   cng      cng.sys      Mon Jul 13 19:49:40 2009 (4A5BC814)
fffff880`059ed000 fffff880`059fd000   CompositeBus CompositeBus.sys Mon Jul 13 20:00:33 2009 (4A5BCAA1)
fffff880`0619a000 fffff880`061a8000   crashdmp crashdmp.sys Mon Jul 13 20:01:01 2009 (4A5BCABD)
fffff880`019a5000 fffff880`019c3000   dfsc     dfsc.sys     Mon Jul 13 19:23:44 2009 (4A5BC200)
fffff880`01996000 fffff880`019a5000   discache discache.sys Mon Jul 13 19:37:18 2009 (4A5BC52E)
fffff880`0104c000 fffff880`01062000   disk     disk.sys     Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`06051000 fffff880`06073000   drmk     drmk.sys     Mon Jul 13 21:01:25 2009 (4A5BD8E5)
fffff880`061a8000 fffff880`061bb000   dump_dumpfve dump_dumpfve.sys Mon Jul 13 19:21:51 2009 (4A5BC18F)
fffff880`03eb4000 fffff880`040bc000   dump_iaStor dump_iaStor.sys Fri Oct 02 15:58:50 2009 (4AC65B7A)
fffff880`0618e000 fffff880`0619a000   Dxapi    Dxapi.sys    Mon Jul 13 19:38:28 2009 (4A5BC574)
fffff880`042b1000 fffff880`043a5000   dxgkrnl  dxgkrnl.sys  Thu Oct 01 21:00:14 2009 (4AC5509E)
fffff880`043a5000 fffff880`043eb000   dxgmms1  dxgmms1.sys  Mon Jul 13 19:38:32 2009 (4A5BC578)
fffff880`063c8000 fffff880`063fe000   fastfat  fastfat.SYS  Mon Jul 13 19:23:28 2009 (4A5BC1F0)
fffff880`012c8000 fffff880`012dc000   fileinfo fileinfo.sys Mon Jul 13 19:34:25 2009 (4A5BC481)
fffff880`0127c000 fffff880`012c8000   fltmgr   fltmgr.sys   Mon Jul 13 19:19:59 2009 (4A5BC11F)
fffff880`016e5000 fffff880`016ef000   Fs_Rec   Fs_Rec.sys   Mon Jul 13 19:19:45 2009 (4A5BC111)
fffff880`00d98000 fffff880`00dd2000   fvevol   fvevol.sys   Fri Sep 25 22:34:26 2009 (4ABD7DB2)
fffff880`04185000 fffff880`041cf000   fwpkclnt fwpkclnt.sys Mon Jul 13 19:21:08 2009 (4A5BC164)
fffff880`05851000 fffff880`0585e000   GEARAspiWDM GEARAspiWDM.sys Mon May 18 08:17:04 2009 (4A1151C0)
fffff800`0301a000 fffff800`03063000   hal      hal.dll      Mon Jul 13 21:27:36 2009 (4A5BDF08)
fffff880`04267000 fffff880`0428b000   HDAudBus HDAudBus.sys Mon Jul 13 20:06:13 2009 (4A5BCBF5)
fffff880`043eb000 fffff880`043fc000   HECIx64  HECIx64.sys  Thu Sep 17 15:54:16 2009 (4AB293E8)
fffff880`060c5000 fffff880`060de000   HIDCLASS HIDCLASS.SYS Mon Jul 13 20:06:21 2009 (4A5BCBFD)
fffff880`060de000 fffff880`060e6080   HIDPARSE HIDPARSE.SYS Mon Jul 13 20:06:17 2009 (4A5BCBF9)
fffff880`060b7000 fffff880`060c5000   hidusb   hidusb.sys   Mon Jul 13 20:06:22 2009 (4A5BCBFE)
fffff880`0629d000 fffff880`06365000   HTTP     HTTP.sys     Mon Jul 13 19:22:16 2009 (4A5BC1A8)
fffff880`0142b000 fffff880`01434000   hwpolicy hwpolicy.sys Mon Jul 13 19:19:22 2009 (4A5BC0FA)
fffff880`01069000 fffff880`01271000   iaStor   iaStor.sys   Fri Oct 02 15:58:50 2009 (4AC65B7A)
fffff880`06079000 fffff880`060b7000   IntcDAud IntcDAud.sys Sat Sep 26 10:42:55 2009 (4ABE286F)
fffff880`00dd2000 fffff880`00de8000   intelppm intelppm.sys Mon Jul 13 19:19:25 2009 (4A5BC0FD)
fffff880`05800000 fffff880`05851000   k57nd60a k57nd60a.sys Thu Aug 06 07:44:32 2009 (4A7AC220)
fffff880`04400000 fffff880`0440f000   kbdclass kbdclass.sys Mon Jul 13 19:19:50 2009 (4A5BC116)
fffff880`060e9000 fffff880`060f7000   kbdhid   kbdhid.sys   Mon Jul 13 20:00:20 2009 (4A5BCA94)
fffff800`00bb1000 fffff800`00bbb000   kdcom    kdcom.dll    Mon Jul 13 21:31:07 2009 (4A5BDFDB)
fffff880`0441e000 fffff880`04461000   ks       ks.sys       Wed Mar 03 23:32:25 2010 (4B8F37D9)
fffff880`015dd000 fffff880`015f7000   ksecdd   ksecdd.sys   Mon Jul 13 19:20:54 2009 (4A5BC156)
fffff880`01400000 fffff880`0142b000   ksecpkg  ksecpkg.sys  Fri Dec 11 01:03:32 2009 (4B21E0B4)
fffff880`06073000 fffff880`06078200   ksthunk  ksthunk.sys  Mon Jul 13 20:00:19 2009 (4A5BCA93)
fffff880`038d6000 fffff880`038eb000   lltdio   lltdio.sys   Mon Jul 13 20:08:50 2009 (4A5BCC92)
fffff880`03892000 fffff880`038b5000   luafv    luafv.sys    Mon Jul 13 19:26:13 2009 (4A5BC295)
fffff880`00cc8000 fffff880`00d0c000   mcupdate_GenuineIntel mcupdate_GenuineIntel.dll Mon Jul 13 21:29:10 2009 (4A5BDF66)
fffff880`06831000 fffff880`0684cc80   mfeapfk  mfeapfk.sys  Wed Oct 06 15:56:26 2010 (4CACD46A)
fffff880`060f7000 fffff880`06123800   mfeavfk  mfeavfk.sys  Wed Oct 06 15:56:49 2010 (4CACD481)
fffff880`06124000 fffff880`0618d780   mfefirek mfefirek.sys Wed Oct 06 15:59:47 2010 (4CACD533)
fffff880`012dc000 fffff880`0135ac80   mfehidk  mfehidk.sys  Wed Oct 06 15:55:49 2010 (4CACD445)
fffff880`018df000 fffff880`018ef900   mfenlfk  mfenlfk.sys  Wed Oct 06 15:56:13 2010 (4CACD45D)
fffff880`03e00000 fffff880`03e43200   mfewfpk  mfewfpk.sys  Wed Oct 06 15:56:04 2010 (4CACD454)
fffff880`0451b000 fffff880`0452a000   modem    modem.sys    Mon Jul 13 20:10:48 2009 (4A5BCD08)
fffff880`06000000 fffff880`0600e000   monitor  monitor.sys  Mon Jul 13 19:38:52 2009 (4A5BC58C)
fffff880`0440f000 fffff880`0441e000   mouclass mouclass.sys Mon Jul 13 19:19:50 2009 (4A5BC116)
fffff880`061e2000 fffff880`061ef000   mouhid   mouhid.sys   Mon Jul 13 20:00:20 2009 (4A5BCA94)
fffff880`00d7e000 fffff880`00d98000   mountmgr mountmgr.sys Mon Jul 13 19:19:54 2009 (4A5BC11A)
fffff880`06383000 fffff880`0639b000   mpsdrv   mpsdrv.sys   Mon Jul 13 20:08:25 2009 (4A5BCC79)
fffff880`0639b000 fffff880`063c8000   mrxsmb   mrxsmb.sys   Sat Feb 27 02:52:19 2010 (4B88CF33)
fffff880`06200000 fffff880`0624e000   mrxsmb10 mrxsmb10.sys Sat Feb 27 02:52:28 2010 (4B88CF3C)
fffff880`0624e000 fffff880`06271000   mrxsmb20 mrxsmb20.sys Sat Feb 27 02:52:26 2010 (4B88CF3A)
fffff880`04169000 fffff880`04174000   Msfs     Msfs.SYS     Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`00f83000 fffff880`00f8d000   msisadrv msisadrv.sys Mon Jul 13 19:19:26 2009 (4A5BC0FE)
fffff880`01367000 fffff880`013c5000   msrpc    msrpc.sys    Mon Jul 13 19:21:32 2009 (4A5BC17C)
fffff880`0198b000 fffff880`01996000   mssmbios mssmbios.sys Mon Jul 13 19:31:10 2009 (4A5BC3BE)
fffff880`017e9000 fffff880`017fb000   mup      mup.sys      Mon Jul 13 19:23:45 2009 (4A5BC201)
fffff880`016ef000 fffff880`017e1000   ndis     ndis.sys     Mon Jul 13 19:21:40 2009 (4A5BC184)
fffff880`04564000 fffff880`04570000   ndistapi ndistapi.sys Mon Jul 13 20:10:00 2009 (4A5BCCD8)
fffff880`0393e000 fffff880`03951000   ndisuio  ndisuio.sys  Mon Jul 13 20:09:25 2009 (4A5BCCB5)
fffff880`04570000 fffff880`0459f000   ndiswan  ndiswan.sys  Mon Jul 13 20:10:11 2009 (4A5BCCE3)
fffff880`0428b000 fffff880`042a0000   NDProxy  NDProxy.SYS  Mon Jul 13 20:10:05 2009 (4A5BCCDD)
fffff880`018f0000 fffff880`018ff000   netbios  netbios.sys  Mon Jul 13 20:09:26 2009 (4A5BCCB6)
fffff880`03e6f000 fffff880`03eb4000   netbt    netbt.sys    Mon Jul 13 19:21:28 2009 (4A5BC178)
fffff880`01600000 fffff880`01660000   NETIO    NETIO.SYS    Mon Jul 13 19:21:46 2009 (4A5BC18A)
fffff880`04174000 fffff880`04185000   Npfs     Npfs.SYS     Mon Jul 13 19:19:48 2009 (4A5BC114)
fffff880`0197f000 fffff880`0198b000   nsiproxy nsiproxy.sys Mon Jul 13 19:21:02 2009 (4A5BC15E)
fffff800`03063000 fffff800`0363f000   nt       ntkrnlmp.exe Sat Jun 19 00:16:41 2010 (4C1C44A9)
fffff880`0143a000 fffff880`015dd000   Ntfs     Ntfs.sys     Mon Jul 13 19:20:47 2009 (4A5BC14F)
fffff880`061ef000 fffff880`061fb000   NuidFltr NuidFltr.sys Tue Jun 29 04:54:32 2010 (4C29B4C8)
fffff880`040fb000 fffff880`04104000   Null     Null.SYS     Mon Jul 13 19:19:37 2009 (4A5BC109)
fffff880`053e4000 fffff880`053e5180   nvBridge nvBridge.kmd Sat Oct 16 13:06:16 2010 (4CB9DB88)
fffff880`0480a000 fffff880`053e3a80   nvlddmkm nvlddmkm.sys Sat Oct 16 13:12:46 2010 (4CB9DD0E)
fffff880`038eb000 fffff880`0393e000   nwifi    nwifi.sys    Mon Jul 13 20:07:23 2009 (4A5BCC3B)
fffff880`041d8000 fffff880`041fe000   pacer    pacer.sys    Mon Jul 13 20:09:41 2009 (4A5BCCC5)
fffff880`00fcd000 fffff880`00fe2000   partmgr  partmgr.sys  Mon Jul 13 19:19:58 2009 (4A5BC11E)
fffff880`00f8d000 fffff880`00fc0000   pci      pci.sys      Mon Jul 13 19:19:51 2009 (4A5BC117)
fffff880`016d4000 fffff880`016e5000   pcw      pcw.sys      Mon Jul 13 19:19:27 2009 (4A5BC0FF)
fffff880`06857000 fffff880`068fd000   peauth   peauth.sys   Mon Jul 13 21:01:19 2009 (4A5BD8DF)
fffff880`06014000 fffff880`06051000   portcls  portcls.sys  Mon Jul 13 20:06:27 2009 (4A5BCC03)
fffff880`00d0c000 fffff880`00d20000   PSHED    PSHED.dll    Mon Jul 13 21:32:23 2009 (4A5BE027)
fffff880`0135b000 fffff880`01366e00   PxHlpa64 PxHlpa64.sys Tue Jun 23 19:16:35 2009 (4A416253)
fffff880`04540000 fffff880`04564000   rasl2tp  rasl2tp.sys  Mon Jul 13 20:10:11 2009 (4A5BCCE3)
fffff880`0459f000 fffff880`045ba000   raspppoe raspppoe.sys Mon Jul 13 20:10:17 2009 (4A5BCCE9)
fffff880`045ba000 fffff880`045db000   raspptp  raspptp.sys  Mon Jul 13 20:10:18 2009 (4A5BCCEA)
fffff880`045db000 fffff880`045f5000   rassstp  rassstp.sys  Mon Jul 13 20:10:25 2009 (4A5BCCF1)
fffff880`0192e000 fffff880`0197f000   rdbss    rdbss.sys    Mon Jul 13 19:24:09 2009 (4A5BC219)
fffff880`0414e000 fffff880`04157000   RDPCDD   RDPCDD.sys   Mon Jul 13 20:16:34 2009 (4A5BCE62)
fffff880`04157000 fffff880`04160000   rdpencdd rdpencdd.sys Mon Jul 13 20:16:34 2009 (4A5BCE62)
fffff880`04160000 fffff880`04169000   rdprefmp rdprefmp.sys Mon Jul 13 20:16:35 2009 (4A5BCE63)
fffff880`013c5000 fffff880`013ff000   rdyboost rdyboost.sys Mon Jul 13 19:34:34 2009 (4A5BC48A)
fffff880`045f5000 fffff880`045fcc00   RimSerial_AMD64 RimSerial_AMD64.sys Mon Nov 24 12:01:01 2008 (492ADDCD)
fffff880`04513000 fffff880`0451b000   RootMdm  RootMdm.sys  Mon Jul 13 20:10:47 2009 (4A5BCD07)
fffff880`03951000 fffff880`03969000   rspndr   rspndr.sys   Mon Jul 13 20:08:50 2009 (4A5BCC92)
fffff880`05e12000 fffff880`05ffaf00   RTKVHD64 RTKVHD64.sys Tue Oct 06 06:51:17 2009 (4ACB2125)
fffff880`068fd000 fffff880`06908000   secdrv   secdrv.SYS   Wed Sep 13 09:18:38 2006 (4508052E)
fffff880`017e1000 fffff880`017e9000   spldr    spldr.sys    Mon May 11 12:56:27 2009 (4A0858BB)
fffff880`03800000 fffff880`03871000   spsys    spsys.sys    Mon May 11 13:20:58 2009 (4A085E7A)
fffff880`03969000 fffff880`039ff000   srv      srv.sys      Thu Aug 26 23:38:00 2010 (4C773318)
fffff880`06947000 fffff880`069ae000   srv2     srv2.sys     Thu Aug 26 23:37:46 2010 (4C77330A)
fffff880`06908000 fffff880`06935000   srvnet   srvnet.sys   Thu Aug 26 23:37:24 2010 (4C7732F4)
fffff880`059fd000 fffff880`059fe480   swenum   swenum.sys   Mon Jul 13 20:00:18 2009 (4A5BCA92)
fffff880`02c02000 fffff880`02dff000   tcpip    tcpip.sys    Sun Jun 13 23:39:04 2010 (4C15A458)
fffff880`06935000 fffff880`06947000   tcpipreg tcpipreg.sys Mon Jul 13 20:09:49 2009 (4A5BCCCD)
fffff880`03e44000 fffff880`03e51000   TDI      TDI.SYS      Mon Jul 13 19:21:18 2009 (4A5BC16E)
fffff880`03e51000 fffff880`03e6f000   tdx      tdx.sys      Mon Jul 13 19:21:15 2009 (4A5BC16B)
fffff880`0191a000 fffff880`0192e000   termdd   termdd.sys   Mon Jul 13 20:16:36 2009 (4A5BCE64)
fffff960`00550000 fffff960`0055a000   TSDDD    TSDDD.dll    unavailable (00000000)
fffff880`019d4000 fffff880`019fa000   tunnel   tunnel.sys   Mon Jul 13 20:09:37 2009 (4A5BCCC1)
fffff880`04461000 fffff880`04473000   umbus    umbus.sys    Mon Jul 13 20:06:56 2009 (4A5BCC20)
fffff880`060e7000 fffff880`060e8f00   USBD     USBD.SYS     Mon Jul 13 20:06:23 2009 (4A5BCBFF)
fffff880`04200000 fffff880`04211000   usbehci  usbehci.sys  Mon Jul 13 20:06:30 2009 (4A5BCC06)
fffff880`04473000 fffff880`044cd000   usbhub   usbhub.sys   Mon Jul 13 20:07:09 2009 (4A5BCC2D)
fffff880`04211000 fffff880`04267000   USBPORT  USBPORT.SYS  Mon Jul 13 20:06:31 2009 (4A5BCC07)
fffff880`061bb000 fffff880`061c7000   usbprint usbprint.sys Mon Jul 13 20:38:18 2009 (4A5BD37A)
fffff880`061c7000 fffff880`061e2000   USBSTOR  USBSTOR.SYS  Mon Jul 13 20:06:34 2009 (4A5BCC0A)
fffff880`00fc0000 fffff880`00fcd000   vdrvroot vdrvroot.sys Mon Jul 13 20:01:31 2009 (4A5BCADB)
fffff880`0410b000 fffff880`04119000   vga      vga.sys      Mon Jul 13 19:38:47 2009 (4A5BC587)
fffff880`04119000 fffff880`0413e000   VIDEOPRT VIDEOPRT.SYS Mon Jul 13 19:38:51 2009 (4A5BC58B)
fffff880`00fe2000 fffff880`00ff7000   volmgr   volmgr.sys   Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`00e00000 fffff880`00e5c000   volmgrx  volmgrx.sys  Mon Jul 13 19:20:33 2009 (4A5BC141)
fffff880`01000000 fffff880`0104c000   volsnap  volsnap.sys  Mon Jul 13 19:20:08 2009 (4A5BC128)
fffff880`059e0000 fffff880`059ed000   vwifibus vwifibus.sys Mon Jul 13 20:07:21 2009 (4A5BCC39)
fffff880`018c9000 fffff880`018df000   vwififlt vwififlt.sys Mon Jul 13 20:07:22 2009 (4A5BCC3A)
fffff880`018ff000 fffff880`0191a000   wanarp   wanarp.sys   Mon Jul 13 20:10:21 2009 (4A5BCCED)
fffff880`0413e000 fffff880`0414e000   watchdog watchdog.sys Mon Jul 13 19:37:35 2009 (4A5BC53F)
fffff880`00e70000 fffff880`00f14000   Wdf01000 Wdf01000.sys Mon Jul 13 19:22:07 2009 (4A5BC19F)
fffff880`00f14000 fffff880`00f23000   WDFLDR   WDFLDR.SYS   Mon Jul 13 19:19:54 2009 (4A5BC11A)
fffff880`041cf000 fffff880`041d8000   wfplwf   wfplwf.sys   Mon Jul 13 20:09:26 2009 (4A5BCCB6)
fffff960`000f0000 fffff960`00400000   win32k   win32k.sys   unavailable (00000000)
fffff880`00f7a000 fffff880`00f83000   WMILIB   WMILIB.SYS   Mon Jul 13 19:19:51 2009 (4A5BC117)
fffff880`038b5000 fffff880`038d6000   WudfPf   WudfPf.sys   Mon Jul 13 20:05:37 2009 (4A5BCBD1)
fffff880`06800000 fffff880`06831000   WUDFRd   WUDFRd.sys   Mon Jul 13 20:06:06 2009 (4A5BCBEE)

Unloaded modules:
fffff880`0b8a8000 fffff880`0bab0000   hiber_iaStor
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`0bab0000 fffff880`0bac3000   hiber_dumpfv
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`069ae000 fffff880`069ca000   mfeapfk.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`0b85f000 fffff880`0ba67000   hiber_iaStor
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`0ba67000 fffff880`0ba7a000   hiber_dumpfv
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`06831000 fffff880`0684d000   mfeapfk.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`0b0b0000 fffff880`0b2b8000   hiber_iaStor
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`0b2b8000 fffff880`0b2cb000   hiber_dumpfv
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`069ae000 fffff880`069ca000   mfeapfk.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`0ace0000 fffff880`0aee8000   hiber_iaStor
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`0aee8000 fffff880`0aefb000   hiber_dumpfv
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`06831000 fffff880`0684d000   mfeapfk.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`03800000 fffff880`03871000   spsys.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`069ae000 fffff880`069db000   mfeavfk01.sy
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`01831000 fffff880`0183f000   crashdmp.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`03eb6000 fffff880`040be000   dump_iaStor.
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`040be000 fffff880`040d1000   dump_dumpfve
    Timestamp: unavailable (00000000)
    Checksum:  00000000
My System SpecsSystem Spec
26 Dec 2010   #3

Windows 7 Home Premium 64 bit
 
 

Thanks for your help
My System SpecsSystem Spec
.


26 Dec 2010   #4

Windows 7 Ultimate 32 bit
 
 

You are welcome. Update us and let us know how your system is doing.
My System SpecsSystem Spec
14 Jan 2011   #5

Windows 7 Home Premium 64 bit
 
 

Hi again just an update after a few weeks

My computer is crashing alot less regularly than it was before - there are times I can turn it on, use it for an evening surfing the net or watching a video and not suffer any crashes. However the crashes haven't totally vanished either, i'm still getting them fairly regularly. Can have it happen two or three times in a day.

Again varying bsod messages, sometimes just a straight reboot rather than showing bsod at all. Still not sure if a particular program is causing it - had it happen when listening to music via spotify, possibly itunes once too (although i cant quite remember!) when streaming video online or when just doing some browsing the internet. Even just when i've left the computer on idle (no music or video playing, just my email open in the internet browser) as i go and do something in the kitchen then come back and it has crashed. It is a real mystery - there has definitely been an improvement compared to before though as the computer is mostly useable rather than just a source of frustration!

I've uploaded the more recent dumps, once again thanks for any help
My System SpecsSystem Spec
14 Jan 2011   #6

Windows 7 Ultimate 32 bit
 
 

Hi, Anna. I am glad there is some improvement. Thank you for the update. I looked at your two most recent dumps, both are dated today. One is a Memory management error code and blames a Windows system core file - very unlikely to be the cause. The other dumps blames memory corruption. All of your drivers appear to be up to date.

I suggest you test your RAM with Memtest86. Follow the instructions in this tutorial: RAM - Test with Memtest86+. Run Memtest from a cold boot after your computer has been off for at least an hour. Let Memtest run for at least seven passes; this will take six to eight hours. Errors, if any, will show on your screen in red. If you see errors, you can stop Memtest. Post back with your results.

If you get no errors with Memtest, enable Driver Verifier closely following the instruction in this tutorial: Driver Verifier - Enable and Disable. If Verifier encounters a faulty driver, it will trigger a BSOD. Upload any and all Driver Verifier enabled dumps.
Code:
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`0301a000 PsLoadedModuleList = 0xfffff800`03257e50
Debug session time: Fri Jan 14 09:41:01.595 2011 (GMT-5)
System Uptime: 1 days 11:22:51.124
Loading Kernel Symbols
...............................................................
................................................................
.................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {41287, 58, 0, 0}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+42ba5 )

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

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

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041287, The subtype of the bugcheck.
Arg2: 0000000000000058
Arg3: 0000000000000000
Arg4: 0000000000000000

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


BUGCHECK_STR:  0x1a_41287

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  firefox.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff8800ab63900 -- (.trap 0xfffff8800ab63900)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000040
rdx=fffffa8005537290 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800030a71b5 rsp=fffff8800ab63a90 rbp=fffff8800ab63b40
 r8=fffff8800ab63ba0  r9=fffff6fb40000000 r10=fffff68000000000
r11=fffff6fb40000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
nt!MiCheckVirtualAddress+0x155:
fffff800`030a71b5 483b4118        cmp     rax,qword ptr [rcx+18h] ds:e680:00000000`00000058=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80003036b7a to fffff8000308a740

STACK_TEXT:  
fffff880`0ab63798 fffff800`03036b7a : 00000000`0000001a 00000000`00041287 00000000`00000058 00000000`00000000 : nt!KeBugCheckEx
fffff880`0ab637a0 fffff800`0308882e : 00000000`00000000 00000000`00000000 00000000`00000000 fffff800`030bc82b : nt! ?? ::FNODOBFM::`string'+0x42ba5
fffff880`0ab63900 fffff800`030a71b5 : fffffa80`0b4ab060 ffffffff`ffffffff 00000000`00000000 fffff880`0ab63b40 : nt!KiPageFault+0x16e
fffff880`0ab63a90 fffff800`030a4633 : 00000000`00000000 00000000`00000000 fffff800`03204e80 fffff780`00000320 : nt!MiCheckVirtualAddress+0x155
fffff880`0ab63ac0 fffff800`0308882e : 00000000`00000000 00000000`0440025c 00000000`00000301 00000000`00000020 : nt!MmAccessFault+0x233
fffff880`0ab63c20 00000000`6d765df3 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
00000000`002ee1f8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x6d765df3


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+42ba5
fffff800`03036b7a cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+42ba5

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9

FAILURE_BUCKET_ID:  X64_0x1a_41287_nt!_??_::FNODOBFM::_string_+42ba5

BUCKET_ID:  X64_0x1a_41287_nt!_??_::FNODOBFM::_string_+42ba5

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

Debug session time: Fri Jan 14 11:06:07.670 2011 (GMT-5)
System Uptime: 0 days 1:24:04.200
Loading Kernel Symbols
...............................................................
................................................................
................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff80003188817, fffff88003316838, fffff880033160a0}

Probably caused by : memory_corruption ( nt!MiEmptyPageAccessLog+e7 )

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

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

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80003188817, The address that the exception occurred at
Arg3: fffff88003316838, Exception Record Address
Arg4: fffff880033160a0, Context Record Address

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
nt!MiEmptyPageAccessLog+e7
fffff800`03188817 8b4138          mov     eax,dword ptr [rcx+38h]

EXCEPTION_RECORD:  fffff88003316838 -- (.exr 0xfffff88003316838)
ExceptionAddress: fffff80003188817 (nt!MiEmptyPageAccessLog+0x00000000000000e7)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT:  fffff880033160a0 -- (.cxr 0xfffff880033160a0)
rax=fffff8a0027d9140 rbx=00000000000f2409 rcx=1002026001f00705
rdx=fffff8a005beda30 rsi=fffffa80057b0138 rdi=0000000000000400
rip=fffff80003188817 rsp=fffff88003316a70 rbp=fffffa8005974000
 r8=fffffa800b670009  r9=fffffa80057b0048 r10=fffffa800adae930
r11=fffffa800adad510 r12=0000000000000000 r13=fffffa80057b0000
r14=0000000000000000 r15=0000000000000008
iopl=0         nv up ei ng nz na po nc
cs=0010  ss=0000  ds=002b  es=002b  fs=0053  gs=002b             efl=00010286
nt!MiEmptyPageAccessLog+0xe7:
fffff800`03188817 8b4138          mov     eax,dword ptr [rcx+38h] ds:002b:10020260`01f0073d=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  audiodg.exe

CURRENT_IRQL:  0

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  ffffffffffffffff

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800032ba0e0
 ffffffffffffffff 

FOLLOWUP_IP: 
nt!MiEmptyPageAccessLog+e7
fffff800`03188817 8b4138          mov     eax,dword ptr [rcx+38h]

BUGCHECK_STR:  0x7E

LAST_CONTROL_TRANSFER:  from fffff80003104aac to fffff80003188817

STACK_TEXT:  
fffff880`03316a70 fffff800`03104aac : fffffa80`0b674b30 00000003`00000000 10020260`01f00705 fffff8a0`027d9140 : nt!MiEmptyPageAccessLog+0xe7
fffff880`03316ae0 fffff800`03096ee2 : 00000000`000013b5 00000000`00000000 fffffa80`00000000 00000000`00000006 : nt! ?? ::FNODOBFM::`string'+0x4972b
fffff880`03316b80 fffff800`03097173 : 00000000`00000008 fffff880`03316c10 00000000`00000001 fffffa80`00000000 : nt!MmWorkingSetManager+0x6e
fffff880`03316bd0 fffff800`03326c06 : fffffa80`0552b040 00000000`00000080 fffffa80`055019e0 00000000`00000001 : nt!KeBalanceSetManager+0x1c3
fffff880`03316d40 fffff800`03060c26 : fffff880`009f0180 fffffa80`0552b040 fffff880`009fafc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`03316d80 00000000`00000000 : fffff880`03317000 fffff880`03311000 fffff880`03316820 00000000`00000000 : nt!KxStartSystemThread+0x16


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!MiEmptyPageAccessLog+e7

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9

STACK_COMMAND:  .cxr 0xfffff880033160a0 ; kb

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0x7E_nt!MiEmptyPageAccessLog+e7

BUCKET_ID:  X64_0x7E_nt!MiEmptyPageAccessLog+e7

Followup: MachineOwner
---------
My System SpecsSystem Spec
15 Jan 2011   #7

Windows 7 Home Premium 64 bit
 
 

Hi again

I ran the memtest for about 10 hours / 9 passes (my dad was real pleased with me hogging the computer all day ) and there were no errors reported.

After this i turned on the driver verifier and have since had a couple of crashes - the second time it then crashed/rebooted automatically a couple more times before i got to the log in screen. However i'm not sure where to get the driver verifier enabled dumps - are these included in the perfmon/system health report and windows_nt6_bsod_jcgriff2 files?(If they are then here are the latest two of those) Or are they located elsewhere?

Thanks for your help once again!
My System SpecsSystem Spec
15 Jan 2011   #8

Windows 7 Home Premium 64 bit
 
 
RAM voltage...

Hi Anna X,

Could you verify your RAM voltage settings in BIOS? I just went though the same problem you've described, and I found by adjusting the RAM voltage from the factory Motherboard default of 1.5V up to 1.6V, all BSOD issues disappeared. The RAM I installed stated it should be run at 1.65V, and in retrospect running it at a lower voltage was the issue. If you pull a stick of RAM out, it will say what its nominal voltage should be, albet in small wiriting somewhere on the printed label.

FYI, when you're in BIOS, make sure you dont pick a voltage that is in pink lettering; it is too high for your system.

Good luck!
My System SpecsSystem Spec
17 Jan 2011   #9

Windows 7 Home Premium 64 bit
 
 

Thanks for the tip, will give this a go
My System SpecsSystem Spec
17 Jan 2011   #10

Windows 7 Home Premium 64 bit
 
 

It appears I cannot change the RAM voltage setting, judging by the Dell community support forum apparently Dell have a lockout of this feature on the BIOS.

Would it be the voltage if i had a few months of trouble free computing with thesystem before the bsod problem started? i havent made any hardware changes or added any ram or anything since i bought it.
My System SpecsSystem Spec
Reply

 Computer crashing regular sometimes bsod sometimes straight to reboot




Thread Tools



Similar help and support threads for2: Computer crashing regular sometimes bsod sometimes straight to reboot
Thread Forum
BSOD and computer runs SLOW after reboot from BSOD BSOD Help and Support
Random BSOD With Regular Computer Use BSOD Help and Support
BSOD during regular computer usage, error 0x00000124 BSOD Help and Support
Solved BSOD during Regular and Gamin computer use BSOD Help and Support
BSOD - Computer Reboot Issue BSOD Help and Support
BSOD crashing my computer.. BSOD Help and Support

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 03:37 PM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33