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: Brand new laptop, Win7 Ult x64, BSOD's!!!

26 Jun 2010   #51
CarlTR6

Windows 7 Ultimate 32 bit
 
 

You latest dmps still point to memory and/or hardware problems.

Quote:
STOP 0x0000001E: KMODE_EXCEPTION_NOT_HANDLED

Usual causes: Device driver, hardware, System service, compatibility, Remote control programs, memory, BIOS

STOP 0x00000050: PAGE_FAULT_IN_NONPAGED_AREA

Usual causes: Defective hardware (particularly memory - but not just RAM), Faulty system service, Antivirus, Device driver, NTFS corruption, BIOS

STOP 0x000000BE: ATTEMPTED_WRITE_TO_READONLY_MEMORY

Usual causes: Device driver, Memory
Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Owner\AppData\Local\Temp\Temp1_Minidumps.zip\062610-17721-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02a05000 PsLoadedModuleList = 0xfffff800`02c42e50
Debug session time: Sat Jun 26 16:53:18.960 2010 (GMT-4)
System Uptime: 0 days 0:12:19.911
...............................................................
................................................................
.......................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

BugCheck 1E, {ffffffffc000001d, fffff88007dddf40, 0, 0}

Unable to load image \SystemRoot\System32\DRIVERS\fvevol.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for fvevol.sys
*** ERROR: Module load completed but symbols could not be loaded for fvevol.sys
Probably caused by : msahci.sys ( msahci!GetTag+ec )

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

0: 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: ffffffffc000001d, The exception code that was not handled
Arg2: fffff88007dddf40, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception

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


EXCEPTION_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION}  Illegal Instruction  An attempt was made to execute an illegal instruction.

FAULTING_IP: 
+5c50952f01f3de0c
fffff880`07dddf40 58              pop     rax

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000000

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x1E

PROCESS_NAME:  sidebar.exe

CURRENT_IRQL:  9

EXCEPTION_RECORD:  fffff88007ddee58 -- (.exr 0xfffff88007ddee58)
ExceptionAddress: fffff88000ddb800 (msahci!GetTag+0x00000000000000ec)
   ExceptionCode: c000001d (Illegal instruction)
  ExceptionFlags: 00000000
NumberParameters: 0

TRAP_FRAME:  fffff88007ddef00 -- (.trap 0xfffff88007ddef00)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=000000000000d117 rbx=0000000000000000 rcx=0000000000000020
rdx=0000000000000013 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88000ddb800 rsp=fffff88007ddf098 rbp=0000000000000000
 r8=0000000000000000  r9=0000000000000012 r10=0000000000003480
r11=00000000fffffd00 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
msahci!GetTag+0xec:
fffff880`00ddb800 c3              ret
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002b07b1b to fffff80002a75600

FAILED_INSTRUCTION_ADDRESS: 
+5c50952f01f3de0c
fffff880`07dddf40 58              pop     rax

STACK_TEXT:  
fffff880`07ddde88 fffff800`02b07b1b : 00000000`0000001e ffffffff`c000001d fffff880`07dddf40 00000000`00000000 : nt!KeBugCheckEx
fffff880`07ddde90 fffff800`02ac8770 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000003 : nt!KipFatalFilter+0x1b
fffff880`07ddded0 fffff800`02aa3bdc : fffffa80`05103b60 00000000`00000000 fffffa80`05103c68 fffff800`02a3e417 : nt! ?? ::FNODOBFM::`string'+0x95d
fffff880`07dddf10 fffff800`02a9b2ed : fffff800`02bbd4c4 fffff880`07ddf9b0 00000000`00000000 fffff800`02a05000 : nt!_C_specific_handler+0x8c
fffff880`07dddf80 fffff800`02aa2950 : fffff800`02bbd4c4 fffff880`07dddff8 fffff880`07ddee58 fffff800`02a05000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`07dddfb0 fffff800`02aaf8df : fffff880`07ddee58 fffff880`07dde6c0 fffff880`00000000 fffffa80`042a6c88 : nt!RtlDispatchException+0x410
fffff880`07dde690 fffff800`02a74c42 : fffff880`07ddee58 fffffa80`0469b6a8 fffff880`07ddef00 00000000`00000001 : nt!KiDispatchException+0x16f
fffff880`07dded20 fffff800`02a72d9f : fffff880`07ddef00 00000000`00000009 fffffa80`06ff3800 fffff800`00000000 : nt!KiExceptionDispatch+0xc2
fffff880`07ddef00 fffff880`00ddb800 : fffff880`00dd8501 fffffa80`0469b6a8 00000000`00000001 00000000`00000001 : nt!KiInvalidOpcodeFault+0x11f
fffff880`07ddf098 fffff880`00dd8501 : fffffa80`0469b6a8 00000000`00000001 00000000`00000001 fffff880`009eb180 : msahci!GetTag+0xec
fffff880`07ddf0a0 fffff880`00db8f37 : 00000000`0000003c 00000000`00000001 fffffa80`046bdef0 fffff880`03eb056d : msahci!AhciHwStartIo+0x1b5
fffff880`07ddf0f0 fffff800`02a70e4b : 00000000`0000003c fffff880`00daec74 fffffa80`046bdef0 00000000`00000004 : ataport!IdeStartCrbSynchronized+0x7b
fffff880`07ddf160 fffff880`00db8e7d : 00000000`00000000 fffff880`00db8ebc fffffa80`042a68a0 fffffa80`0469a1a0 : nt!KeSynchronizeExecution+0x3b
fffff880`07ddf1a0 fffff800`02fe562f : 00000000`00000000 fffffa80`042a6940 00000000`00001000 00004036`0000a6c4 : ataport!IdeStartIoCallBack+0x2d5
fffff880`07ddf310 fffff880`00de30d3 : fffffa80`042a68a0 fffff880`00de312c 00000000`00000000 00000000`00000000 : hal!HalBuildScatterGatherList+0x203
fffff880`07ddf380 fffff880`00db8b3b : fffffa80`042a68a0 fffffa80`042a68a0 fffffa80`0469a1a0 00000000`00000000 : PCIIDEX!BmSetup+0x6b
fffff880`07ddf3e0 fffff880`00db77eb : 00000000`00000001 00000000`00000000 00000000`00000000 fffffa80`046e83b0 : ataport!IdeDispatchChannelRequest+0xef
fffff880`07ddf410 fffff880`00db7650 : 00000000`00000001 00000000`00000000 00000000`00000000 00000000`00000000 : ataport!IdeStartChannelRequest+0x113
fffff880`07ddf490 fffff880`00db89e2 : fffffa80`0469a1a0 00000000`00000000 00000000`00000103 00000008`00000000 : ataport!IdeStartDeviceRequest+0x2c4
fffff880`07ddf550 fffff880`00db44ee : 00000000`00000000 fffffa80`042a68a0 00000000`00000001 fffffa80`044074d0 : ataport!IdePortPdoDispatch+0xb6
fffff880`07ddf580 fffff880`0190d445 : 00000000`00000000 00000000`00000001 fffffa80`044074d0 00000000`860e1600 : ataport!IdePortDispatch+0x16
fffff880`07ddf5b0 fffff880`0190d695 : fffffa80`04c50500 fffffa80`046e8060 00000000`00020000 fffff880`00000001 : CLASSPNP!ServiceTransferRequest+0x355
fffff880`07ddf650 fffff880`00fec0af : fffffa80`043b2010 00000000`ffffffff fffffa80`043b2248 00000000`00000001 : CLASSPNP!ClassReadWrite+0xd5
fffff880`07ddf6a0 fffff880`00e1612c : fffffa80`04c55720 fffffa80`043b2010 fffffa80`043b2010 00000000`00ffffff : partmgr!PmGlobalDispatch+0x9f
fffff880`07ddf6d0 fffff880`018bd2bf : 00000000`ffffffff fffffa80`04c56190 fffffa80`043b2010 00000082`00000005 : volmgr!VmReadWrite+0x11c
fffff880`07ddf710 00000000`ffffffff : fffffa80`04c56190 fffffa80`043b2010 00000082`00000005 00000000`00000011 : fvevol+0x12bf
fffff880`07ddf718 fffffa80`04c56190 : fffffa80`043b2010 00000082`00000005 00000000`00000011 00000040`00000016 : 0xffffffff
fffff880`07ddf720 fffffa80`043b2010 : 00000082`00000005 00000000`00000011 00000040`00000016 00000000`00000003 : 0xfffffa80`04c56190
fffff880`07ddf728 00000082`00000005 : 00000000`00000011 00000040`00000016 00000000`00000003 fffff880`018bd53c : 0xfffffa80`043b2010
fffff880`07ddf730 00000000`00000011 : 00000040`00000016 00000000`00000003 fffff880`018bd53c fffffa80`04c56190 : 0x82`00000005
fffff880`07ddf738 00000040`00000016 : 00000000`00000003 fffff880`018bd53c fffffa80`04c56190 00000067`0000001a : 0x11
fffff880`07ddf740 00000000`00000003 : fffff880`018bd53c fffffa80`04c56190 00000067`0000001a 00000000`00000020 : 0x40`00000016
fffff880`07ddf748 fffff880`018bd53c : fffffa80`04c56190 00000067`0000001a 00000000`00000020 00000040`00000020 : 0x3
fffff880`07ddf750 fffffa80`04c56190 : 00000067`0000001a 00000000`00000020 00000040`00000020 00000000`00000000 : fvevol+0x153c
fffff880`07ddf758 00000067`0000001a : 00000000`00000020 00000040`00000020 00000000`00000000 fffffa80`043b22d8 : 0xfffffa80`04c56190
fffff880`07ddf760 00000000`00000020 : 00000040`00000020 00000000`00000000 fffffa80`043b22d8 fffffa80`04c53710 : 0x67`0000001a
fffff880`07ddf768 00000040`00000020 : 00000000`00000000 fffffa80`043b22d8 fffffa80`04c53710 00000000`00000000 : 0x20
fffff880`07ddf770 00000000`00000000 : fffffa80`043b22d8 fffffa80`04c53710 00000000`00000000 00000000`00000003 : 0x40`00000020


STACK_COMMAND:  kb

FOLLOWUP_IP: 
msahci!GetTag+ec
fffff880`00ddb800 c3              ret

SYMBOL_STACK_INDEX:  9

SYMBOL_NAME:  msahci!GetTag+ec

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: msahci

IMAGE_NAME:  msahci.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bcabd

FAILURE_BUCKET_ID:  X64_0x1E_BAD_IP_msahci!GetTag+ec

BUCKET_ID:  X64_0x1E_BAD_IP_msahci!GetTag+ec

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

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


Loading Dump File [C:\Users\Owner\AppData\Local\Temp\Temp1_Minidumps.zip\062610-19078-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*Symbol information
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02a10000 PsLoadedModuleList = 0xfffff800`02c4de50
Debug session time: Sat Jun 26 16:40:26.549 2010 (GMT-4)
System Uptime: 0 days 0:15:50.500
Loading Kernel Symbols
...............................................................
................................................................
.......................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck BE, {fffff8800122fca4, 8000000003ad3121, fffff880083c8950, b}

Probably caused by : win32k.sys ( win32k!NtUserPostMessage+31 )

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

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

ATTEMPTED_WRITE_TO_READONLY_MEMORY (be)
An attempt was made to write to readonly memory.  The guilty driver is on the
stack trace (and is typically the current instruction pointer).
When possible, the guilty driver's name (Unicode string) is printed on
the bugcheck screen and saved in KiBugCheckDriver.
Arguments:
Arg1: fffff8800122fca4, Virtual address for the attempted write.
Arg2: 8000000003ad3121, PTE contents.
Arg3: fffff880083c8950, (reserved)
Arg4: 000000000000000b, (reserved)

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


CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xBE

PROCESS_NAME:  sidebar.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff880083c8950 -- (.trap 0xfffff880083c8950)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000080 rbx=0000000000000000 rcx=fffffa8005cf5d70
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002a8880c rsp=fffff880083c8ae0 rbp=0000000000000001
 r8=0000000000000000  r9=0000000000000000 r10=fffff96000120884
r11=000007fffff94000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up di pl nz na po nc
nt!ExAcquireResourceExclusiveLite+0x9c:
fffff800`02a8880c ff87244b0000    inc     dword ptr [rdi+4B24h] ds:000f:00000000`00004b24=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002b00a22 to fffff80002a80600

STACK_TEXT:  
fffff880`083c87e8 fffff800`02b00a22 : 00000000`000000be fffff880`0122fca4 80000000`03ad3121 fffff880`083c8950 : nt!KeBugCheckEx
fffff880`083c87f0 fffff800`02a7e6ee : 00000000`00000001 fffffa80`05cf5d70 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x423be
fffff880`083c8950 fffff800`02a8880c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
fffff880`083c8ae0 fffff800`02a8c74b : 00000000`03fb4950 fffffa80`072db060 00000000`00000000 fffff800`02d7bdcc : nt!ExAcquireResourceExclusiveLite+0x9c
fffff880`083c8b50 fffff960`001208b5 : fffff880`083c8bb8 00000000`00000000 fffff880`009eb180 fffff880`083c8bf8 : nt!ExEnterPriorityRegionAndAcquireResourceExclusive+0x23
fffff880`083c8b80 fffff800`02a7f853 : fffffa80`072db060 fffff880`083c8c60 00000000`00008002 00000000`00000020 : win32k!NtUserPostMessage+0x31
fffff880`083c8be0 00000000`77a792ca : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`05acf628 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77a792ca


STACK_COMMAND:  kb

FOLLOWUP_IP: 
win32k!NtUserPostMessage+31
fffff960`001208b5 33db            xor     ebx,ebx

SYMBOL_STACK_INDEX:  5

SYMBOL_NAME:  win32k!NtUserPostMessage+31

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: win32k

IMAGE_NAME:  win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4bdc4376

FAILURE_BUCKET_ID:  X64_0xBE_win32k!NtUserPostMessage+31

BUCKET_ID:  X64_0xBE_win32k!NtUserPostMessage+31

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

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


Loading Dump File [C:\Users\Owner\AppData\Local\Temp\Temp1_Minidumps.zip\062610-25459-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*Symbol information
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02a0b000 PsLoadedModuleList = 0xfffff800`02c48e50
Debug session time: Sat Jun 26 18:43:10.133 2010 (GMT-4)
System Uptime: 0 days 1:48:25.084
Loading Kernel Symbols
...............................................................
................................................................
..........................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff8802278d64c, 0, fffff880012de811, 2}


Could not read faulting driver name
Probably caused by : memory_corruption

Followup: memory_corruption
---------

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

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


Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cb30e0
 fffff8802278d64c 

FAULTING_IP: 
Ntfs!NtfsAllocateRecord+21d
fffff880`012de811 448b842484000020 mov     r8d,dword ptr [rsp+20000084h]

MM_INTERNAL_CODE:  2

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

BUGCHECK_STR:  0x50

PROCESS_NAME:  chrome.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff8800278d430 -- (.trap 0xfffff8800278d430)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa8004fb4701 rbx=0000000000000000 rcx=fffffa8004f32180
rdx=fffffa8004d37dc0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880012de811 rsp=fffff8800278d5c8 rbp=fffffa80043b8970
 r8=0000000000008000  r9=fffff8800278d678 r10=0000000000000002
r11=0000000000000001 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
Ntfs!NtfsAllocateRecord+0x21d:
fffff880`012de811 448b842484000020 mov     r8d,dword ptr [rsp+20000084h] ss:0018:fffff880`2278d64c=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002afa832 to fffff80002a7b600

STACK_TEXT:  
fffff880`0278d2c8 fffff800`02afa832 : 00000000`00000050 fffff880`2278d64c 00000000`00000000 fffff880`0278d430 : nt!KeBugCheckEx
fffff880`0278d2d0 fffff800`02a796ee : 00000000`00000000 00000000`00000000 00000000`00000000 fffff8a0`00000000 : nt! ?? ::FNODOBFM::`string'+0x40f00
fffff880`0278d430 fffff880`012de811 : 00000000`00002d33 00000000`00000000 00000000`000302eb 00000000`00001000 : nt!KiPageFault+0x16e
fffff880`0278d5c8 fffffa80`045269a0 : fffff880`012df161 fffffa80`045269a0 fffffa80`04d37f88 fffff880`0278d760 : Ntfs!NtfsAllocateRecord+0x21d
fffff880`0278d708 fffff880`012df161 : fffffa80`045269a0 fffffa80`04d37f88 fffff880`0278d760 fffff8a0`00007000 : 0xfffffa80`045269a0
fffff880`0278d710 fffff880`012dd2b7 : fffffa80`045269a0 fffffa80`04f32180 fffffa80`04206b00 00000000`00000000 : Ntfs!NtfsAllocateMftRecord+0xb1
fffff880`0278d7d0 fffff880`012c4d7f : fffffa80`045269a0 fffffa80`045269a0 fffff8a0`0bc69901 00000000`00000000 : Ntfs!NtfsCreateNewFile+0x3d7
fffff880`0278db10 fffff880`0122dc0d : fffffa80`045269a0 fffffa80`043b8970 fffff880`076c6450 fffffa80`03f8e900 : Ntfs!NtfsCommonCreate+0xecf
fffff880`0278dcf0 fffff800`02a73487 : fffff880`076c63c0 00000000`7efaf000 00000000`00000000 00000000`7368af40 : Ntfs!NtfsCommonCreateCallout+0x1d
fffff880`0278dd20 fffff800`02a73441 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KySwitchKernelStackCallout+0x27
fffff880`076c6290 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSwitchKernelStackContinue


STACK_COMMAND:  kb

CHKIMG_EXTENSION: !chkimg -lo 50 -db !Ntfs
3 errors : !Ntfs (fffff880012de808-fffff880012de818)
fffff880012de800  00  00  49  8b  d6  49  8b  cf *68  33  2d  00  00  88  44  24 ..I..I..h3-...D$
fffff880012de810 *54  44  8b  84  24  84  00  00 *20  ba  01  00  00  00  48  8d TD..$... .....H.

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  STRIDE

FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_STRIDE

BUCKET_ID:  X64_MEMORY_CORRUPTION_STRIDE

Followup: memory_corruption
---------
I will have to review this thread before I can make any suggestions.After reading through this thread, I see that you have tried everything the experts have suggested. I am going to suggest a clean install, Clean Install Windows 7. If your computer is still under warranty, I would pursue getting it checked under warranty.


My System SpecsSystem Spec
.
26 Jun 2010   #52
Casey R

Windows 7 Home Premium 64bit
 
 

Thanks, Carl. I really appreciate it.
My System SpecsSystem Spec
26 Jun 2010   #53
CarlTR6

Windows 7 Ultimate 32 bit
 
 

You are welcome, Casey, I am sorry that we could not solve your problem. Let us know what you do and how it comes out.
My System SpecsSystem Spec
.

27 Jun 2010   #54
Casey R

Windows 7 Home Premium 64bit
 
 

I don't know if this is of any help - but the BSOD's are almost a guarantee when doing something media intensive - ie, streaming video, or playing a video game.
My System SpecsSystem Spec
27 Jun 2010   #55
CarlTR6

Windows 7 Ultimate 32 bit
 
 

Quote   Quote: Originally Posted by Casey R View Post
I don't know if this is of any help - but the BSOD's are almost a guarantee when doing something media intensive - ie, streaming video, or playing a video game.
That would lead me to suspect the video card/driver or the LAN (network) adapter card/driver.
My System SpecsSystem Spec
28 Jun 2010   #56
Casey R

Windows 7 Home Premium 64bit
 
 

Thanks Carl. Any suggestions as to how to track down which it is?

I'm certain it must be a driver issue - I dualbooted my laptop with Ubuntu Linux last night, and everything is working perfectly in Linux.....ie, the same tasks that are guaranteed to cause a BSOD on Win7, like playing YouTube in HD.
My System SpecsSystem Spec
28 Jun 2010   #57
Jonathan_King

Windows 7 Professional x64
 
 

My System SpecsSystem Spec
19 Jul 2010   #58
Casey R

Windows 7 Home Premium 64bit
 
 

Some more BSOD's.

Right now I am trying to edit a video with Windows Live Movie Maker.

Everytime I go to render the video, it begins to render and then BSOD's.

Any thoughts?

Minidumps attached.
My System SpecsSystem Spec
19 Jul 2010   #59
Casey R

Windows 7 Home Premium 64bit
 
 

This Minidump came from Driver Verifier.
My System SpecsSystem Spec
19 Jul 2010   #60
JMH

Win 7 Ultimate 64-bit. SP1.
 
 

Quote   Quote: Originally Posted by Casey R View Post
This Minidump came from Driver Verifier.

Casey R hi and welcome

This crash was caused by memory corruption. If you have not run memtestx86 for at least 6 passes you should do so now.

I see no evidence that driver verifier was enabled at the time of this crash.

I do see that the windows media network service was also involved in the crash.

I would run memtest

Run a system file check (type sfc /scannow)

Let us know if you need further assistance

Jan
My System SpecsSystem Spec
Reply

 Brand new laptop, Win7 Ult x64, BSOD's!!!




Thread Tools




Similar help and support threads
Thread Forum
Brand new Laptop with multiple BSOD
Hi Everyone Apologies for first post being a cry for help, I have just bought a New Samsung Series 7 Gamer and am having a lot of BSOD 4 so far today, my desktops have never given me a problem but this is my first laptop, is possible for someone to help me fix these problems?, I have attached a...
BSOD Help and Support
BSOD On Brand New Dell Laptop.
Good afternoon, A user received a BSOD while shutting down their PC. It is a Dell Lattitude E6520. It is running Windows 7 Pro 64 Bit. 4 GB RAM, 2.5 Ghz i5 Processor. I am including the zipped "Grab All" folder which contains the dmp file from the BSOD event. Any help with this would be...
BSOD Help and Support
BSOD Fresh Win7 Install - Brand new laptop - No AV installed
So I have a Dell XPS 17 laptop that is pretty much brand new (bought in June, pulled out of the box in September). First thing I did was download Windows 7 torrent. Wipe the drives and install it with the intentions of activating it using my OEM key. Everything installed fine all hardware was...
BSOD Help and Support
Constant BSOD, please help brand new laptop
Hey guys, have just recently bought a acer aspire 5740g with windows 7 64bit. Things were running fine for a few weeks, have the latest norton anitvirus and firewall aswell as spybot search and destroy. Both find no viruses or spyware/ However i have to run norton on safe mode all the time or it...
BSOD Help and Support
BSOD on Brand New Laptop. Please help!
I'm not very computer savvy and was hoping someone here can help me out. My Laptop is a brand new Asus G73JW-A1...less than 2 weeks old. I've been getting some random BSODs while just browsing the internet. I believe it may have something to do with my USB slots? I've noticed on 2 occasions...
BSOD Help and Support
BSOD on brand new laptop
hello first of all this is the first time i visit this site, so tell me if i dont include any crucial information. (a) anyway, i bought my laptop from HP (model Pavilion dv6-2165eo Entertainment) just 10 days ago. very soon i started having problems with BSOD. sometimes i get them twice in an...
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 18:34.
Twitter Facebook Google+ Seven Forums iOS App Seven Forums Android App