Random BSOD

F

Fredsman

New member
Local time
9:06 PM
Messages
19
Is Windows 7 . . .
- x86 (32-bit) or x64 ? x64
- the original installed OS on the system? Vista Ultimate 32bit
- an OEM or full retail version? OEM
- OEM = came pre-installed on system
- Full Retail = you purchased it from retailer

- What is the age of system (hardware)? Since November 2009
- What is the age of OS installation (have you re-installed the OS?) 2 Days ago it was installed

I have recently had troubles installing windows 7 as viewed in the following thread:

http://www.sevenforums.com/installation-setup/145404-troubles-installing-windows-7-a.html

I have now got Windows 7 Home Edition 64Bit to work now but I get random BSOD, when booting up, when opening files, for whatever reason. Im actually surprised im able to make this post. Below I have attached the dump and html file of the report any help will be appreciated.
 

My Computer

OS
Windows 7 Home Premium 64bit
CPU
Intel Q9400 Quad Core
Motherboard
ASUS P5N-D LGA 775 NVIDIA nForce 750i SLI ATX Intel
Memory
2 x Corsair DDR2 2GB
Graphics Card(s)
260GTX Nvidia
Sound Card
N/a
Monitor(s) Displays
LG Flatron W2242S
Hard Drives
500GB WDC WD50000AAKS- 0
PSU
Corsair 750w
Case
Gigabyte Posedon
Cooling
Air cooling
Fredsman said:
Is Windows 7 . . .
- x86 (32-bit) or x64 ? x64
- the original installed OS on the system? Vista Ultimate 32bit
- an OEM or full retail version? OEM
- OEM = came pre-installed on system
- Full Retail = you purchased it from retailer

- What is the age of system (hardware)? Since November 2009
- What is the age of OS installation (have you re-installed the OS?) 2 Days ago it was installed

I have recently had troubles installing windows 7 as viewed in the following thread:

http://www.sevenforums.com/installation-setup/145404-troubles-installing-windows-7-a.html

I have now got Windows 7 Home Edition 64Bit to work now but I get random BSOD, when booting up, when opening files, for whatever reason. Im actually surprised im able to make this post. Below I have attached the dump and html file of the report any help will be appreciated.
Click to expand...


Two problems

14 of 27 caused by your video driver re-install using these.

When upgrading your graphic driver you MUST remove all traces of the current driver. In order to do that we recommend using Guru3D - Driver Sweeper

When it is removed then download and install the fresh copy.


The rest directly or indirectly caused by your Avast. Remove and replace with Microsoft security essentials

http://files.avast.com/files/eng/aswclear5.exe

http://www.microsoft.com/security_essentials/

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\Windows_NT6_BSOD_jcgriff2\022011-18096-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.16695.amd64fre.win7_gdr.101026-1503
Machine Name:
Kernel base = 0xfffff800`02e67000 PsLoadedModuleList = 0xfffff800`030a4e50
Debug session time: Sun Feb 20 13:19:10.894 2011 (GMT-5)
System Uptime: 0 days 0:00:39.110
Loading Kernel Symbols
...............................................................
................................................................
..............
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {5b89a95, 2, 0, fffff8800ff8b530}

Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+116530 )

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

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

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
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 kernel debugger is available get stack backtrace.
Arguments:
Arg1: 0000000005b89a95, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff8800ff8b530, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff8000310f0e0
 0000000005b89a95 

CURRENT_IRQL:  2

FAULTING_IP: 
nvlddmkm+116530
fffff880`0ff8b530 8b9994010000    mov     ebx,dword ptr [rcx+194h]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  System

TRAP_FRAME:  fffff8800439e400 -- (.trap 0xfffff8800439e400)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000005b89901 rbx=0000000000000000 rcx=0000000005b89901
rdx=0000000000000064 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8800ff8b530 rsp=fffff8800439e590 rbp=fffffa8005bad010
 r8=0000000000000000  r9=0000000000000000 r10=0000000000000000
r11=000000000000002a r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
nvlddmkm+0x116530:
fffff880`0ff8b530 8b9994010000    mov     ebx,dword ptr [rcx+194h] ds:8b88:00000000`05b89a95=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002ed6ca9 to fffff80002ed7740

STACK_TEXT:  
fffff880`0439e2b8 fffff800`02ed6ca9 : 00000000`0000000a 00000000`05b89a95 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`0439e2c0 fffff800`02ed5920 : 00000000`00000001 00000000`00000064 00000000`00000000 00000000`80000000 : nt!KiBugCheckDispatch+0x69
fffff880`0439e400 fffff880`0ff8b530 : fffffa80`057c8b88 fffff880`0ff8af43 00000000`00000001 fffffa80`0571e000 : nt!KiPageFault+0x260
fffff880`0439e590 fffffa80`057c8b88 : fffff880`0ff8af43 00000000`00000001 fffffa80`0571e000 00000000`00000000 : nvlddmkm+0x116530
fffff880`0439e598 fffff880`0ff8af43 : 00000000`00000001 fffffa80`0571e000 00000000`00000000 fffffa80`05b84600 : 0xfffffa80`057c8b88
fffff880`0439e5a0 00000000`00000001 : fffffa80`0571e000 00000000`00000000 fffffa80`05b84600 fffffa80`0571e000 : nvlddmkm+0x115f43
fffff880`0439e5a8 fffffa80`0571e000 : 00000000`00000000 fffffa80`05b84600 fffffa80`0571e000 fffff880`0ffa3679 : 0x1
fffff880`0439e5b0 00000000`00000000 : fffffa80`05b84600 fffffa80`0571e000 fffff880`0ffa3679 00000000`00000064 : 0xfffffa80`0571e000


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nvlddmkm+116530
fffff880`0ff8b530 8b9994010000    mov     ebx,dword ptr [rcx+194h]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nvlddmkm+116530

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4d27c6da

FAILURE_BUCKET_ID:  X64_0xD1_nvlddmkm+116530

BUCKET_ID:  X64_0xD1_nvlddmkm+116530

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

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

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
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 kernel debugger is available get stack backtrace.
Arguments:
Arg1: 0000000005b89a95, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff8800ff8b530, address which referenced memory

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


READ_ADDRESS:  0000000005b89a95 

CURRENT_IRQL:  2

FAULTING_IP: 
nvlddmkm+116530
fffff880`0ff8b530 8b9994010000    mov     ebx,dword ptr [rcx+194h]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  System

TRAP_FRAME:  fffff8800439e400 -- (.trap 0xfffff8800439e400)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000005b89901 rbx=0000000000000000 rcx=0000000005b89901
rdx=0000000000000064 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8800ff8b530 rsp=fffff8800439e590 rbp=fffffa8005bad010
 r8=0000000000000000  r9=0000000000000000 r10=0000000000000000
r11=000000000000002a r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
nvlddmkm+0x116530:
fffff880`0ff8b530 8b9994010000    mov     ebx,dword ptr [rcx+194h] ds:8b88:00000000`05b89a95=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002ed6ca9 to fffff80002ed7740

STACK_TEXT:  
fffff880`0439e2b8 fffff800`02ed6ca9 : 00000000`0000000a 00000000`05b89a95 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`0439e2c0 fffff800`02ed5920 : 00000000`00000001 00000000`00000064 00000000`00000000 00000000`80000000 : nt!KiBugCheckDispatch+0x69
fffff880`0439e400 fffff880`0ff8b530 : fffffa80`057c8b88 fffff880`0ff8af43 00000000`00000001 fffffa80`0571e000 : nt!KiPageFault+0x260
fffff880`0439e590 fffffa80`057c8b88 : fffff880`0ff8af43 00000000`00000001 fffffa80`0571e000 00000000`00000000 : nvlddmkm+0x116530
fffff880`0439e598 fffff880`0ff8af43 : 00000000`00000001 fffffa80`0571e000 00000000`00000000 fffffa80`05b84600 : 0xfffffa80`057c8b88
fffff880`0439e5a0 00000000`00000001 : fffffa80`0571e000 00000000`00000000 fffffa80`05b84600 fffffa80`0571e000 : nvlddmkm+0x115f43
fffff880`0439e5a8 fffffa80`0571e000 : 00000000`00000000 fffffa80`05b84600 fffffa80`0571e000 fffff880`0ffa3679 : 0x1
fffff880`0439e5b0 00000000`00000000 : fffffa80`05b84600 fffffa80`0571e000 fffff880`0ffa3679 00000000`00000064 : 0xfffffa80`0571e000


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nvlddmkm+116530
fffff880`0ff8b530 8b9994010000    mov     ebx,dword ptr [rcx+194h]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nvlddmkm+116530

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4d27c6da

FAILURE_BUCKET_ID:  X64_0xD1_nvlddmkm+116530

BUCKET_ID:  X64_0xD1_nvlddmkm+116530

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

My Computer

Computer Manufacturer/Model Number
HP Pavillion dv-7 1005 Tx
OS
Win 8 Release candidate 8400
CPU
[email protected]
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
Thanks for the reply, Can this be done in safe mode? I can't seem to log on without having a blue screen :(
 

My Computer

OS
Windows 7 Home Premium 64bit
CPU
Intel Q9400 Quad Core
Motherboard
ASUS P5N-D LGA 775 NVIDIA nForce 750i SLI ATX Intel
Memory
2 x Corsair DDR2 2GB
Graphics Card(s)
260GTX Nvidia
Sound Card
N/a
Monitor(s) Displays
LG Flatron W2242S
Hard Drives
500GB WDC WD50000AAKS- 0
PSU
Corsair 750w
Case
Gigabyte Posedon
Cooling
Air cooling
You must log in or register to reply here.
Back
Top