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: BSOD

05 Oct 2010   #1
Hellerup

Windows 7 Enterprise 64 bit
 
 
BSOD

Hi

I have recently purchased a new notebook.

I have installed Windows 7 on the system myself, and used all drivers supplied by the vendor. I experience BSOD with somwhat regualr intervals. Sometimes the system runs all day, and sometimes I get 3-4 crashes within a short time.

It seems as if the BSOd begin to appear after a few days, when I try to reinstall. That is it runs fine for a couple of days and then begin crashing.

I have supplied the files you request and hope someone could take a look (the html is in Danish - I dont know how to change it).

Kind regards

Martin

Is Windows 7 . . . - 64bit
- full retail version?
- What is the age of system (hardware)? CPU - 1 month
Motherboard - Intel(R) 5 Series/3400 Series Chipset 1 month
Graphics card - ATI Radeon Mobility 5650 1 month
HDDs - 1 month
- Fresh win 7 install, and continuous BSOD



My System SpecsSystem Spec
.
05 Oct 2010   #2
CarlTR6

Windows 7 Ultimate 32 bit
 
 

HI, Martin, and welcome to the forum. Sorry you are having problems. I will take a look.
Quote:
Error code A, IRQL_NOT_LESS_OR_EQUAL. Usual causes - Kernel mode driver, System Service, BIOS, Windows, Virus scanner, Backup tool, compatibility.

Error code 50 (2X), PAGE_FAULT_IN_NONPAGED_AREA. Usual causes - Defective hardware (particularly memory - but not just RAM), Faulty system service, Antivirus, Device driver, NTFS corruption, BIOS.
Code:
Kernel base = 0xfffff800`02c66000 PsLoadedModuleList = 0xfffff800`02ea3e50
Debug session time: Sat Oct  2 07:08:32.229 2010 (GMT-4)
System Uptime: 0 days 0:05:32.415
Loading Kernel Symbols
...............................................................
................................................................
........................
Loading User Symbols
Loading unloaded module list
...
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {fffffa0008dc68f8, 2, 0, fffff80002ce0291}

Probably caused by : ntkrnlmp.exe ( nt!KiTimerWaitTest+171 )

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

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

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: fffffa0008dc68f8, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80002ce0291, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002f0e0e0
 fffffa0008dc68f8 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!KiTimerWaitTest+171
fffff800`02ce0291 488b6d00        mov     rbp,qword ptr [rbp]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  iexplore.exe

TRAP_FRAME:  fffff80004209600 -- (.trap 0xfffff80004209600)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000008 rbx=0000000000000000 rcx=0000000000000000
rdx=fffffa8008dc6820 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002ce0291 rsp=fffff80004209790 rbp=fffffa0008dc68f8
 r8=fffff80002e53001  r9=0000000000000002 r10=000000000000003c
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe cy
nt!KiTimerWaitTest+0x171:
fffff800`02ce0291 488b6d00        mov     rbp,qword ptr [rbp] ss:fffffa00`08dc68f8=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002cd5ca9 to fffff80002cd6740

STACK_TEXT:  
fffff800`042094b8 fffff800`02cd5ca9 : 00000000`0000000a fffffa00`08dc68f8 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff800`042094c0 fffff800`02cd4920 : 00000000`0000000a fffffa80`08dc6828 fffff800`02e50e80 fffff800`02ce2de0 : nt!KiBugCheckDispatch+0x69
fffff800`04209600 fffff800`02ce0291 : 00000000`00000000 fffff800`02ce0000 fffff800`00000004 00000000`000000ff : nt!KiPageFault+0x260
fffff800`04209790 fffff800`02ce1d7d : fffffa80`08dc6820 fffffa80`08956168 fffffa80`08956168 00000000`00000000 : nt!KiTimerWaitTest+0x171
fffff800`04209810 fffff800`02ce24be : 00000000`c622a12e fffff800`04209e88 00000000`0000533c fffff800`02e53a08 : nt!KiProcessExpiredTimerList+0x6d
fffff800`04209e60 fffff800`02ce1cb7 : fffff800`02e50ec1 fffffa80`0000533c fffffa80`071a1a28 00000000`0000003c : nt!KiTimerExpiration+0x1be
fffff800`04209f00 fffff800`02cdc865 : 00000000`00000000 fffffa80`0415a060 00000000`00000000 fffff880`04791db0 : nt!KiRetireDpcList+0x277
fffff800`04209fb0 fffff800`02cdc67c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxRetireDpcList+0x5
fffff880`09b87be0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchInterruptContinue


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiTimerWaitTest+171
fffff800`02ce0291 488b6d00        mov     rbp,qword ptr [rbp]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!KiTimerWaitTest+171

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9

FAILURE_BUCKET_ID:  X64_0xA_nt!KiTimerWaitTest+171

BUCKET_ID:  X64_0xA_nt!KiTimerWaitTest+171

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

Kernel base = 0xfffff800`02c15000 PsLoadedModuleList = 0xfffff800`02e52e50
Debug session time: Tue Oct  5 13:47:02.418 2010 (GMT-4)
System Uptime: 0 days 0:00:13.589
Loading Kernel Symbols
...............................................................
...............................................................
Loading User Symbols
Loading unloaded module list
...
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff81102cac400, 0, fffff81102cac400, 5}


Could not read faulting driver name
Probably caused by : ksecdd.sys ( ksecdd!KsecFastIoDeviceControl+22 )

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

1: 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: fffff81102cac400, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff81102cac400, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000005, (reserved)

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


Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ebd0e0
 fffff81102cac400 

FAULTING_IP: 
+5c36952f01b3dca4
fffff811`02cac400 ??              ???

MM_INTERNAL_CODE:  5

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  MsMpEng.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff88002b6f820 -- (.trap 0xfffff88002b6f820)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000beeb90 rbx=0000000000000000 rcx=fffffa80084e6b20
rdx=0000000000bef001 rsi=0000000000000000 rdi=0000000000000000
rip=fffff81102cac400 rsp=fffff88002b6f9b8 rbp=0000000000000000
 r8=0000000000beecd0  r9=0000000000000040 r10=0000000000beeb90
r11=0000000000100003 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
fffff811`02cac400 ??              ???
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002d048c1 to fffff80002c85740

FAILED_INSTRUCTION_ADDRESS: 
+5c36952f01b3dca4
fffff811`02cac400 ??              ???

STACK_TEXT:  
fffff880`02b6f6b8 fffff800`02d048c1 : 00000000`00000050 fffff811`02cac400 00000000`00000000 fffff880`02b6f820 : nt!KeBugCheckEx
fffff880`02b6f6c0 fffff800`02c8382e : 00000000`00000000 fffffa80`084e6b20 00000000`00881f00 fffff680`00011cb8 : nt! ?? ::FNODOBFM::`string'+0x40e8b
fffff880`02b6f820 fffff811`02cac400 : fffff880`015ca122 fffffa80`084afb00 00000000`00000000 00000000`00390402 : nt!KiPageFault+0x16e
fffff880`02b6f9b8 fffff880`015ca122 : fffffa80`084afb00 00000000`00000000 00000000`00390402 00000000`00000001 : 0xfffff811`02cac400
fffff880`02b6f9c0 fffff800`02fa0473 : fffffa80`084e6b20 fffff880`02b6fca0 00000000`00beeb80 00000000`00000001 : ksecdd!KsecFastIoDeviceControl+0x22
fffff880`02b6fa10 fffff800`02fa0f66 : fffffa80`0849db30 00000000`00000000 00000000`00000000 00000000`00000000 : nt!IopXxxControlFile+0x373
fffff880`02b6fb40 fffff800`02c84993 : 00000000`00000534 fffffa80`084afb60 00000000`00bef268 fffff800`00000008 : nt!NtDeviceIoControlFile+0x56
fffff880`02b6fbb0 00000000`7768fdca : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`00beeb28 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7768fdca


STACK_COMMAND:  kb

FOLLOWUP_IP: 
ksecdd!KsecFastIoDeviceControl+22
fffff880`015ca122 483b05dfe40000  cmp     rax,qword ptr [ksecdd!KsecLsaProcess (fffff880`015d8608)]

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  ksecdd!KsecFastIoDeviceControl+22

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: ksecdd

IMAGE_NAME:  ksecdd.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc156

FAILURE_BUCKET_ID:  X64_0x50_CODE_AV_BAD_IP_ksecdd!KsecFastIoDeviceControl+22

BUCKET_ID:  X64_0x50_CODE_AV_BAD_IP_ksecdd!KsecFastIoDeviceControl+22

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

1: kd> lmtsmn
start             end                 module name
fffff880`00ed7000 fffff880`00f2e000   ACPI     ACPI.sys     Mon Jul 13 19:19:34 2009 (4A5BC106)
fffff880`04547000 fffff880`045d1000   afd      afd.sys      Mon Jul 13 19:21:40 2009 (4A5BC184)
fffff880`051d4000 fffff880`051ea000   AgileVpn AgileVpn.sys Mon Jul 13 20:10:24 2009 (4A5BCCF0)
fffff880`0134f000 fffff880`0135a000   amdxata  amdxata.sys  Tue May 19 13:56:59 2009 (4A12F2EB)
fffff880`01301000 fffff880`0130a000   atapi    atapi.sys    Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`0130a000 fffff880`01334000   ataport  ataport.SYS  Mon Jul 13 19:19:52 2009 (4A5BC118)
fffff880`052b3000 fffff880`052d6000   AtiHdmi  AtiHdmi.sys  Thu Apr 08 03:42:30 2010 (4BBD88E6)
fffff880`04acd000 fffff880`05177000   atikmdag atikmdag.sys Thu May 06 11:32:10 2010 (4BE2E0FA)
fffff880`02e00000 fffff880`02e36000   atikmpag atikmpag.sys Thu May 06 11:06:24 2010 (4BE2DAF0)
fffff880`00f9f000 fffff880`00fab000   BATTC    BATTC.SYS    Mon Jul 13 19:31:01 2009 (4A5BC3B5)
fffff880`0449b000 fffff880`044a2000   Beep     Beep.SYS     Mon Jul 13 20:00:13 2009 (4A5BCA8D)
fffff880`02fae000 fffff880`02fbf000   blbdrive blbdrive.sys Mon Jul 13 19:35:59 2009 (4A5BC4DF)
fffff960`007d0000 fffff960`007f7000   cdd      cdd.dll      unavailable (00000000)
fffff880`0443b000 fffff880`04465000   cdrom    cdrom.sys    Mon Jul 13 19:19:54 2009 (4A5BC11A)
fffff880`00d30000 fffff880`00df0000   CI       CI.dll       Mon Jul 13 21:32:13 2009 (4A5BE01D)
fffff880`01b99000 fffff880`01bc9000   CLASSPNP CLASSPNP.SYS Mon Jul 13 19:19:58 2009 (4A5BC11E)
fffff880`00cd2000 fffff880`00d30000   CLFS     CLFS.SYS     Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`02fe5000 fffff880`02fe9500   CmBatt   CmBatt.sys   Mon Jul 13 19:31:03 2009 (4A5BC3B7)
fffff880`0105e000 fffff880`010d1000   cng      cng.sys      Mon Jul 13 19:49:40 2009 (4A5BC814)
fffff880`00f96000 fffff880`00f9f000   compbatt compbatt.sys Mon Jul 13 19:31:02 2009 (4A5BC3B6)
fffff880`051c4000 fffff880`051d4000   CompositeBus CompositeBus.sys Mon Jul 13 20:00:33 2009 (4A5BCAA1)
fffff880`086b4000 fffff880`086c2000   crashdmp crashdmp.sys Mon Jul 13 20:01:01 2009 (4A5BCABD)
fffff880`02f0d000 fffff880`02f90000   csc      csc.sys      Mon Jul 13 19:24:26 2009 (4A5BC22A)
fffff880`02f90000 fffff880`02fae000   dfsc     dfsc.sys     Mon Jul 13 19:23:44 2009 (4A5BC200)
fffff880`02efe000 fffff880`02f0d000   discache discache.sys Mon Jul 13 19:37:18 2009 (4A5BC52E)
fffff880`01b83000 fffff880`01b99000   disk     disk.sys     Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`05313000 fffff880`05335000   drmk     drmk.sys     Mon Jul 13 21:01:25 2009 (4A5BD8E5)
fffff880`086c2000 fffff880`086d5000   dump_dumpfve dump_dumpfve.sys Mon Jul 13 19:21:51 2009 (4A5BC18F)
fffff880`0420f000 fffff880`04419000   dump_iaStor dump_iaStor.sys Wed Mar 03 21:51:31 2010 (4B8F2033)
fffff880`086a8000 fffff880`086b4000   Dxapi    Dxapi.sys    Mon Jul 13 19:38:28 2009 (4A5BC574)
fffff880`046a7000 fffff880`0479b000   dxgkrnl  dxgkrnl.sys  Thu Oct 01 21:00:14 2009 (4AC5509E)
fffff880`0479b000 fffff880`047e1000   dxgmms1  dxgmms1.sys  Mon Jul 13 19:38:32 2009 (4A5BC578)
fffff880`013a6000 fffff880`013ba000   fileinfo fileinfo.sys Mon Jul 13 19:34:25 2009 (4A5BC481)
fffff880`0135a000 fffff880`013a6000   fltmgr   fltmgr.sys   Mon Jul 13 19:19:59 2009 (4A5BC11F)
fffff880`015f4000 fffff880`015fe000   Fs_Rec   Fs_Rec.sys   Mon Jul 13 19:19:45 2009 (4A5BC111)
fffff880`01b49000 fffff880`01b83000   fvevol   fvevol.sys   Fri Sep 25 22:34:26 2009 (4ABD7DB2)
fffff880`01a46000 fffff880`01a90000   fwpkclnt fwpkclnt.sys Mon Jul 13 19:21:08 2009 (4A5BC164)
fffff800`031f1000 fffff800`0323a000   hal      hal.dll      Mon Jul 13 21:27:36 2009 (4A5BDF08)
fffff880`04600000 fffff880`04624000   HDAudBus HDAudBus.sys Mon Jul 13 20:06:13 2009 (4A5BCBF5)
fffff880`01b40000 fffff880`01b49000   hwpolicy hwpolicy.sys Mon Jul 13 19:19:22 2009 (4A5BC0FA)
fffff880`05852000 fffff880`05870000   i8042prt i8042prt.sys Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`010f7000 fffff880`01301000   iaStor   iaStor.sys   Wed Mar 03 21:51:31 2010 (4B8F2033)
fffff880`047e1000 fffff880`047f7000   intelppm intelppm.sys Mon Jul 13 19:19:25 2009 (4A5BC0FD)
fffff880`05870000 fffff880`0587f000   kbdclass kbdclass.sys Mon Jul 13 19:19:50 2009 (4A5BC116)
fffff800`00bbc000 fffff800`00bc6000   kdcom    kdcom.dll    Mon Jul 13 21:31:07 2009 (4A5BDFDB)
fffff880`02e36000 fffff880`02e79000   ks       ks.sys       Wed Mar 03 23:32:25 2010 (4B8F37D9)
fffff880`015c9000 fffff880`015e3000   ksecdd   ksecdd.sys   Mon Jul 13 19:20:54 2009 (4A5BC156)
fffff880`01660000 fffff880`0168b000   ksecpkg  ksecpkg.sys  Fri Dec 11 01:03:32 2009 (4B21E0B4)
fffff880`04abc000 fffff880`04ac1200   ksthunk  ksthunk.sys  Mon Jul 13 20:00:19 2009 (4A5BCA93)
fffff880`086e3000 fffff880`08706000   luafv    luafv.sys    Mon Jul 13 19:26:13 2009 (4A5BC295)
fffff880`00c7a000 fffff880`00cbe000   mcupdate_GenuineIntel mcupdate_GenuineIntel.dll Mon Jul 13 21:29:10 2009 (4A5BDF66)
fffff880`086d5000 fffff880`086e3000   monitor  monitor.sys  Mon Jul 13 19:38:52 2009 (4A5BC58C)
fffff880`05fed000 fffff880`05ffc000   mouclass mouclass.sys Mon Jul 13 19:19:50 2009 (4A5BC116)
fffff880`00fc0000 fffff880`00fda000   mountmgr mountmgr.sys Mon Jul 13 19:19:54 2009 (4A5BC11A)
fffff880`04465000 fffff880`04492000   MpFilter MpFilter.sys Sat Mar 20 01:58:08 2010 (4BA463F0)
fffff880`01334000 fffff880`0133f000   msahci   msahci.sys   Thu Oct 08 23:24:39 2009 (4ACEACF7)
fffff880`04500000 fffff880`0450b000   Msfs     Msfs.SYS     Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`00f37000 fffff880`00f41000   msisadrv msisadrv.sys Mon Jul 13 19:19:26 2009 (4A5BC0FE)
fffff880`01000000 fffff880`0105e000   msrpc    msrpc.sys    Mon Jul 13 19:21:32 2009 (4A5BC17C)
fffff880`02ef3000 fffff880`02efe000   mssmbios mssmbios.sys Mon Jul 13 19:31:10 2009 (4A5BC3BE)
fffff880`01b2e000 fffff880`01b40000   mup      mup.sys      Mon Jul 13 19:23:45 2009 (4A5BC201)
fffff880`016ce000 fffff880`017c0000   ndis     ndis.sys     Mon Jul 13 19:21:40 2009 (4A5BC184)
fffff880`0469a000 fffff880`046a6000   ndistapi ndistapi.sys Mon Jul 13 20:10:00 2009 (4A5BCCD8)
fffff880`04a24000 fffff880`04a53000   ndiswan  ndiswan.sys  Mon Jul 13 20:10:11 2009 (4A5BCCE3)
fffff880`0529e000 fffff880`052b3000   NDProxy  NDProxy.SYS  Mon Jul 13 20:10:05 2009 (4A5BCCDD)
fffff880`04200000 fffff880`0420f000   netbios  netbios.sys  Mon Jul 13 20:09:26 2009 (4A5BCCB6)
fffff880`01a00000 fffff880`01a45000   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`0587f000 fffff880`05fde000   NETw5s64 NETw5s64.sys Wed Jan 13 11:37:13 2010 (4B4DF6B9)
fffff880`0450b000 fffff880`0451c000   Npfs     Npfs.SYS     Mon Jul 13 19:19:48 2009 (4A5BC114)
fffff880`02ee7000 fffff880`02ef3000   nsiproxy nsiproxy.sys Mon Jul 13 19:21:02 2009 (4A5BC15E)
fffff800`02c15000 fffff800`031f1000   nt       ntkrnlmp.exe Sat Jun 19 00:16:41 2010 (4C1C44A9)
fffff880`01426000 fffff880`015c9000   Ntfs     Ntfs.sys     Mon Jul 13 19:20:47 2009 (4A5BC14F)
fffff880`04492000 fffff880`0449b000   Null     Null.SYS     Mon Jul 13 19:19:37 2009 (4A5BC109)
fffff880`045da000 fffff880`04600000   pacer    pacer.sys    Mon Jul 13 20:09:41 2009 (4A5BCCC5)
fffff880`00f81000 fffff880`00f96000   partmgr  partmgr.sys  Mon Jul 13 19:19:58 2009 (4A5BC11E)
fffff880`00f41000 fffff880`00f74000   pci      pci.sys      Mon Jul 13 19:19:51 2009 (4A5BC117)
fffff880`0133f000 fffff880`0134f000   PCIIDEX  PCIIDEX.SYS  Mon Jul 13 19:19:48 2009 (4A5BC114)
fffff880`015e3000 fffff880`015f4000   pcw      pcw.sys      Mon Jul 13 19:19:27 2009 (4A5BC0FF)
fffff880`052d6000 fffff880`05313000   portcls  portcls.sys  Mon Jul 13 20:06:27 2009 (4A5BCC03)
fffff880`0442d000 fffff880`0443b000   psd      psd.sys      Sun Jul 19 16:17:45 2009 (4A637F69)
fffff880`00cbe000 fffff880`00cd2000   PSHED    PSHED.dll    Mon Jul 13 21:32:23 2009 (4A5BE027)
fffff880`04a00000 fffff880`04a24000   rasl2tp  rasl2tp.sys  Mon Jul 13 20:10:11 2009 (4A5BCCE3)
fffff880`04a53000 fffff880`04a6e000   raspppoe raspppoe.sys Mon Jul 13 20:10:17 2009 (4A5BCCE9)
fffff880`04a6e000 fffff880`04a8f000   raspptp  raspptp.sys  Mon Jul 13 20:10:18 2009 (4A5BCCEA)
fffff880`04a8f000 fffff880`04aa9000   rassstp  rassstp.sys  Mon Jul 13 20:10:25 2009 (4A5BCCF1)
fffff880`02e96000 fffff880`02ee7000   rdbss    rdbss.sys    Mon Jul 13 19:24:09 2009 (4A5BC219)
fffff880`04aa9000 fffff880`04ab4000   rdpbus   rdpbus.sys   Mon Jul 13 20:17:46 2009 (4A5BCEAA)
fffff880`044e5000 fffff880`044ee000   RDPCDD   RDPCDD.sys   Mon Jul 13 20:16:34 2009 (4A5BCE62)
fffff880`044ee000 fffff880`044f7000   rdpencdd rdpencdd.sys Mon Jul 13 20:16:34 2009 (4A5BCE62)
fffff880`044f7000 fffff880`04500000   rdprefmp rdprefmp.sys Mon Jul 13 20:16:35 2009 (4A5BCE63)
fffff880`01af4000 fffff880`01b2e000   rdyboost rdyboost.sys Mon Jul 13 19:34:34 2009 (4A5BC48A)
fffff880`05800000 fffff880`05852000   Rt64win7 Rt64win7.sys Mon Feb 08 22:42:09 2010 (4B70D991)
fffff880`0846a000 fffff880`086a7900   RTKVHD64 RTKVHD64.sys Fri Apr 23 04:29:09 2010 (4BD15A55)
fffff880`04ab4000 fffff880`04abc000   serscan  serscan.sys  Mon Jul 13 20:35:32 2009 (4A5BD2D4)
fffff880`01aec000 fffff880`01af4000   spldr    spldr.sys    Mon May 11 12:56:27 2009 (4A0858BB)
fffff880`05ffc000 fffff880`05ffd480   swenum   swenum.sys   Mon Jul 13 20:00:18 2009 (4A5BCA92)
fffff880`05177000 fffff880`051c4000   SynTP    SynTP.sys    Thu Aug 27 22:00:37 2009 (4A973A45)
fffff880`01801000 fffff880`019fe000   tcpip    tcpip.sys    Sun Jun 13 23:39:04 2010 (4C15A458)
fffff880`0453a000 fffff880`04547000   TDI      TDI.SYS      Mon Jul 13 19:21:18 2009 (4A5BC16E)
fffff880`0451c000 fffff880`0453a000   tdx      tdx.sys      Mon Jul 13 19:21:15 2009 (4A5BC16B)
fffff880`016a6000 fffff880`016ba000   termdd   termdd.sys   Mon Jul 13 20:16:36 2009 (4A5BCE64)
fffff880`0468b000 fffff880`0469a000   tpm      tpm.sys      Mon Jul 13 19:21:48 2009 (4A5BC18C)
fffff960`005d0000 fffff960`005da000   TSDDD    TSDDD.dll    Mon Jul 13 20:16:34 2009 (4A5BCE62)
fffff880`02fbf000 fffff880`02fe5000   tunnel   tunnel.sys   Mon Jul 13 20:09:37 2009 (4A5BCCC1)
fffff880`051ea000 fffff880`051fc000   umbus    umbus.sys    Mon Jul 13 20:06:56 2009 (4A5BCC20)
fffff880`05feb000 fffff880`05fecf00   USBD     USBD.SYS     Mon Jul 13 20:06:23 2009 (4A5BCBFF)
fffff880`04624000 fffff880`04635000   usbehci  usbehci.sys  Fri Dec 04 02:26:02 2009 (4B18B98A)
fffff880`05244000 fffff880`0529e000   usbhub   usbhub.sys   Fri Dec 04 02:26:39 2009 (4B18B9AF)
fffff880`04635000 fffff880`0468b000   USBPORT  USBPORT.SYS  Mon Jul 13 20:06:31 2009 (4A5BCC07)
fffff880`00f74000 fffff880`00f81000   vdrvroot vdrvroot.sys Mon Jul 13 20:01:31 2009 (4A5BCADB)
fffff880`044a2000 fffff880`044b0000   vga      vga.sys      Mon Jul 13 19:38:47 2009 (4A5BC587)
fffff880`044b0000 fffff880`044d5000   VIDEOPRT VIDEOPRT.SYS Mon Jul 13 19:38:51 2009 (4A5BC58B)
fffff880`01a90000 fffff880`01aa0000   vmstorfl vmstorfl.sys Mon Jul 13 19:42:54 2009 (4A5BC67E)
fffff880`00fab000 fffff880`00fc0000   volmgr   volmgr.sys   Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`00c00000 fffff880`00c5c000   volmgrx  volmgrx.sys  Mon Jul 13 19:20:33 2009 (4A5BC141)
fffff880`01aa0000 fffff880`01aec000   volsnap  volsnap.sys  Mon Jul 13 19:20:08 2009 (4A5BC128)
fffff880`05fde000 fffff880`05feb000   vwifibus vwifibus.sys Mon Jul 13 20:07:21 2009 (4A5BCC39)
fffff880`01bd7000 fffff880`01bed000   vwififlt vwififlt.sys Mon Jul 13 20:07:22 2009 (4A5BCC3A)
fffff880`0168b000 fffff880`016a6000   wanarp   wanarp.sys   Mon Jul 13 20:10:21 2009 (4A5BCCED)
fffff880`044d5000 fffff880`044e5000   watchdog watchdog.sys Mon Jul 13 19:37:35 2009 (4A5BC53F)
fffff880`00e24000 fffff880`00ec8000   Wdf01000 Wdf01000.sys Mon Jul 13 19:22:07 2009 (4A5BC19F)
fffff880`00ec8000 fffff880`00ed7000   WDFLDR   WDFLDR.SYS   Mon Jul 13 19:19:54 2009 (4A5BC11A)
fffff880`045d1000 fffff880`045da000   wfplwf   wfplwf.sys   Mon Jul 13 20:09:26 2009 (4A5BCCB6)
fffff960`00020000 fffff960`0032f000   win32k   win32k.sys   Sat Jun 19 00:31:59 2010 (4C1C483F)
fffff880`047f7000 fffff880`04800000   wmiacpi  wmiacpi.sys  Mon Jul 13 19:31:02 2009 (4A5BC3B6)
fffff880`00f2e000 fffff880`00f37000   WMILIB   WMILIB.SYS   Mon Jul 13 19:19:51 2009 (4A5BC117)

Unloaded modules:
fffff880`01bc9000 fffff880`01bd7000   crashdmp.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`04210000 fffff880`0441a000   dump_iaStor.
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`0441a000 fffff880`0442d000   dump_dumpfve
    Timestamp: unavailable (00000000)
    Checksum:  00000000
This is a hardware/hardware related problem. The dumps do not point to a specific cause; so we will have to troubleshoot.

Test your RAM using Memtest86. Follow the instructions in this tutorial: RAM - Test with Memtest86+. Post your results.

If you get no memory errors, please enable Driver Verifier following the instructions in this tutorial. Upload any dumps generated by Driver Verifier.
Driver Verifier - Enable and Disable
My System SpecsSystem Spec
05 Oct 2010   #3
Lemur

Systems 1 and 2: Windows 7 Enterprise x64, Win 8 Developer
 
 

Are you using NVidia RAID? It's May 20, 2009. Please update.
My System SpecsSystem Spec
.

05 Oct 2010   #4
Lemur

Systems 1 and 2: Windows 7 Enterprise x64, Win 8 Developer
 
 

Det forstår jeg ikke. Under system information, there is nothing listed for netwerk. What is your network device?
My System SpecsSystem Spec
05 Oct 2010   #5
Hellerup

Windows 7 Enterprise 64 bit
 
 

Hi

I am not using Raid. My network device is a REalTek PCIe GBE Family Controller and Intel Wifi Link 1000 BGN.

I have already tested my memory with no errors.

I will try to start Verifier and up0load the results.

Regards Martin
My System SpecsSystem Spec
05 Oct 2010   #6
CarlTR6

Windows 7 Ultimate 32 bit
 
 

Did you you use Memetest86 and how many passes did your test make? You need to run it for at least seven passes.
My System SpecsSystem Spec
05 Oct 2010   #7
Lemur

Systems 1 and 2: Windows 7 Enterprise x64, Win 8 Developer
 
 

Quote   Quote: Originally Posted by Hellerup View Post
Hi

I am not using Raid. My network device is a REalTek PCIe GBE Family Controller and Intel Wifi Link 1000 BGN.

I have already tested my memory with no errors.

I will try to start Verifier and up0load the results.

Regards Martin
What are the dates on your network devices?
My System SpecsSystem Spec
06 Oct 2010   #8
Hellerup

Windows 7 Enterprise 64 bit
 
 

Hi

First let me say that I am somewhat in awe ovér the response to my post. I was sitting in front of my screen feeling all alone. Thanks guys .

Lemur: When you ask for the dates on my network device, are you referring to the date of the driver?

I ran memmtest86 and let it run standard. I didnt change the standard setting. I will run it again.

I have started Viewer.exe, but I dont know what to do now? Should I wait for BSOD? In that case where does verifier.exe create the logs?

I am beginning to suspect faulty hardware. I have alongside 64 bit windows, tried to install a 32-bit windows 7 Enterprise and yesterday I BSOD'ed there also.

I will try to run the memtest again and let verifier do whatever it is doing.

Regards Martin
My System SpecsSystem Spec
06 Oct 2010   #9
CarlTR6

Windows 7 Ultimate 32 bit
 
 

Let Memtest run for at least seven passes.

Quote:
I have started Viewer.exe, but I dont know what to do now? Should I wait for BSOD? In that case where does verifier.exe create the logs?
Do you mean you mean Event Viewer or are you meaning Driver Verifier? If the latter, let it run for about 36 hours of computer operation while you use your computer as you normally do. If Driver Verifier encounters a faulty driver, it will trigger a BSOD crash and generate a mini dump. Hopefully, that dump will point to the offending driver.
My System SpecsSystem Spec
06 Oct 2010   #10
Hellerup

Windows 7 Enterprise 64 bit
 
 

I am not sure where viwer.exe came from. I meant verify.exe. So when I catch a crash do I just upload the minidump or do I run the utility as described in posting guidelines?
My System SpecsSystem Spec
Reply

 BSOD




Thread Tools



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 07:40.
Twitter Facebook Google+ Seven Forums iOS App Seven Forums Android App