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

12 Jun 2010   #1

Windows 7 x64
Windows 7 x64 BSOD


I have problems with my Windows.
I just suddenly shows BSOD. Today it appeared after I started my computer and tried to open Firefox.

System info:
1) OS - Windows 7 x64
2) Computer is new, no previous OS (work on it for 3 days)
3) I have not re-installed OS
4) CPU - Intel Core i3 530
5) Video - Zotac GeForce GT 240
6) MotherBoard - Asus P7H55-M

My System SpecsSystem Spec

12 Jun 2010   #2

win7 ultimate / virtual box

debugger says it cannot identify the faulting driver and the 0x50 error suggests a driver file error. Most likely there is a problem with that file and it needs to be updated or replaced ?

most of your drivers are from july 2009 and your realtek nic driver is from jan 2010 so try updating all your drivers ?

please can you tell us what antivirus and or third party firewall are you using ?
My System SpecsSystem Spec
12 Jun 2010   #3

Windows 7 x64

I'm using Avira, no third-party firewall.
My System SpecsSystem Spec

12 Jun 2010   #4

Windows 7 x64

I had a BSOD again.
After restart I had to Launch Startup Repair, because the computer didn't want to start Windows,
and I got IRQL_NOT_LESS_OR_EQUAL at the end of Launch Startup Repair.

After Windows started I got an DRIVER_IRQL_NOT_LESS_OR_EQUAL.
I've updated drivers for my network adapter.
My System SpecsSystem Spec
12 Jun 2010   #5

win7 ultimate / virtual box

Im seeing Klif.sys and Kl1.sys and other files associated with kapersky , did you use a trial version then unninstall it ?

I suggest you remove all remnants of kasperksy using the removal tool provided here by ice systems

then let us know how you get on
My System SpecsSystem Spec
12 Jun 2010   #6

Windows 7 x64

Thank you.

I don't think it is Kaspersky.
First of all, it all started when I had Avira.
I installed Kaspersky today, after I wrote first post, but before I installed new network adapter driver.
And I'm waiting....
My System SpecsSystem Spec
12 Jun 2010   #7

Windows 7 x64

Crush again.
Uninstalled Kaspersky, installed Microsoft Security Essentials.
My System SpecsSystem Spec
18 Jun 2010   #8

Windows 7 x64

Problem was in RAM.
My System SpecsSystem Spec
18 Jun 2010   #9

Microsoft Window 7 Professional 32 bit

There are two thing that I want to say from the minidump check
First, I would recommend you to remove kapersky antivirus just for testing, because it appear as process during BSODs occur.
One of the minidump check indicate memory corruption, if uninstalling kapersky doens't work, I would suggest to download third party called memtest86, burn it to cd and let it run for at least 7 passes
Here is the bugcheck

BugCheck 50, {ffffd80003250b00, 0, fffff800030c7d97, 7}

Could not read faulting driver name
Probably caused by : ntkrnlmp.exe ( nt!PspReturnQuota+47 )
Followup: MachineOwner
2: kd> !analyze -v
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
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.
Arg1: ffffd80003250b00, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff800030c7d97, If non-zero, the instruction address which referenced the bad memory
Arg4: 0000000000000007, (reserved)
Debugging Details:

Could not read faulting driver name
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800032fa0e0
fffff800`030c7d97 488b5d00        mov     rbx,qword ptr [rbp]
PROCESS_NAME:  avp.exe
BugCheck 50, {ffffda8006c17738, 0, fffff800031c1cbf, 7}

Could not read faulting driver name
Probably caused by : memory_corruption ( nt!MiLogPageAccess+10f )
Followup: MachineOwner
Let us know if you need help

My System SpecsSystem Spec

 Windows 7 x64 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 12:49 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