zigzag3143
New member
- Local time
- 10:17 AM
- Messages
- 27,140
As you suspected booting normally with those options set resulted in a smooth load and no crash, however booting normally with all drivers resulted in a bsod with the dump attached. A sincere thank you to all of those who have helped me so far - far more help here than Cyberpower wants to give me.
Continuing, this one was caused by hardware. Probably a device driver causing a memory exception.
Either the memory caused the hardware or the reverse.
If you havent yet
1-rum memtest
Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Boot from the CD, and leave it running for at least 5 or 6 passes.
Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot. Test the sticks individually, and if you find a good one, test it in all slots.
2-Run a system file check
http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html?ltr=S
3-If you are overclocking stop. If you are running a raid re-install its driver.
Ken
Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\K\Desktop\100910-29484-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*C:\symbols;*http://msdl.microsoft.com/download/symbols/;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is:
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`02c4b000 PsLoadedModuleList = 0xfffff800`02e88e50
Debug session time: Sat Oct 9 17:21:57.755 2010 (GMT-4)
System Uptime: 0 days 0:02:05.471
Loading Kernel Symbols
...............................................................
................................................................
.............
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1E, {ffffffffc0000005, fffff80002fbe007, 1, 79}
Probably caused by : hardware ( nt!NtAllocateVirtualMemory+f27 )
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: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80002fbe007, The address that the exception occurred at
Arg3: 0000000000000001, Parameter 0 of the exception
Arg4: 0000000000000079, 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!NtAllocateVirtualMemory+f27
fffff800`02fbe007 ff4c8b74 dec dword ptr [rbx+rcx*4+74h]
EXCEPTION_PARAMETER1: 0000000000000001
EXCEPTION_PARAMETER2: 0000000000000079
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ef30e0
0000000000000079
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x1E
PROCESS_NAME: explorer.exe
CURRENT_IRQL: 0
EXCEPTION_RECORD: fffff88007793508 -- (.exr 0xfffff88007793508)
ExceptionAddress: fffff80002fbe007 (nt!NtAllocateVirtualMemory+0x0000000000000f27)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000001
Parameter[1]: 0000000000000079
Attempt to write to address 0000000000000079
TRAP_FRAME: fffff880077935b0 -- (.trap 0xfffff880077935b0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002fbe007 rsp=fffff88007793740 rbp=fffff80002fbe260
r8=0000000000000000 r9=0000000000000000 r10=fffffa80039f70c0
r11=fffff88007793660 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc
nt!NtAllocateVirtualMemory+0xf27:
fffff800`02fbe007 ff4c8b74 dec dword ptr [rbx+rcx*4+74h] ds:d540:00000000`00000074=????????
Resetting default scope
MISALIGNED_IP:
nt!NtAllocateVirtualMemory+f27
fffff800`02fbe007 ff4c8b74 dec dword ptr [rbx+rcx*4+74h]
LAST_CONTROL_TRANSFER: from fffff80002cf5a39 to fffff80002cbb740
STACK_TEXT:
fffff880`07792d38 fffff800`02cf5a39 : 00000000`0000001e ffffffff`c0000005 fffff800`02fbe007 00000000`00000001 : nt!KeBugCheckEx
fffff880`07792d40 fffff800`02cbad82 : fffff880`07793508 00000000`00000005 fffff880`077935b0 fffffa80`060814a0 : nt!KiDispatchException+0x1b9
fffff880`077933d0 fffff800`02cb98fa : 00000000`00000001 00000000`00000005 fffff880`0107ea00 00000000`00000000 : nt!KiExceptionDispatch+0xc2
fffff880`077935b0 fffff800`02fbe007 : 00000000`00000005 fffff800`02fbe260 fffffa80`060814a0 00000000`00000000 : nt!KiPageFault+0x23a
fffff880`07793740 fffff880`07793801 : fffffa80`00000040 fffff880`07793a30 fffff880`07793940 fffffa80`060814a0 : nt!NtAllocateVirtualMemory+0xf27
fffff880`077938f0 fffffa80`00000040 : fffff880`07793a30 fffff880`07793940 fffffa80`060814a0 00000000`00000000 : 0xfffff880`07793801
fffff880`077938f8 fffff880`07793a30 : fffff880`07793940 fffffa80`060814a0 00000000`00000000 fffff880`07793928 : 0xfffffa80`00000040
fffff880`07793900 fffff880`07793940 : fffffa80`060814a0 00000000`00000000 fffff880`07793928 fffff801`00000104 : 0xfffff880`07793a30
fffff880`07793908 fffffa80`060814a0 : 00000000`00000000 fffff880`07793928 fffff801`00000104 00000000`00000000 : 0xfffff880`07793940
fffff880`07793910 00000000`00000000 : fffff880`07793928 fffff801`00000104 00000000`00000000 00000000`00000000 : 0xfffffa80`060814a0
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!NtAllocateVirtualMemory+f27
fffff800`02fbe007 ff4c8b74 dec dword ptr [rbx+rcx*4+74h]
SYMBOL_STACK_INDEX: 4
SYMBOL_NAME: nt!NtAllocateVirtualMemory+f27
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: hardware
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MODULE_NAME: hardware
FAILURE_BUCKET_ID: X64_IP_MISALIGNED
BUCKET_ID: X64_IP_MISALIGNED
Followup: MachineOwner
---------
My Computer
- Computer Manufacturer/Model Number
- HP Pavillion dv-7 1005 Tx
- OS
- Win 8 Release candidate 8400
- Memory
- 4 gigs
- Graphics Card(s)
- Nvidia 9600M
- Sound Card
- HD built-in
- Monitor(s) Displays
- 17" Wxga
- Screen Resolution
- 1440x900
- Cooling
- none
- Internet Speed
- 45Mb down 5Mb up