New
#11
It sounds to me like you did it right, now wait and see if you get further BSODs.
OK. If nothing is fixed it should happen within a week. Hopefully not.
Thanks!
Unfortunately, no fix. I just got another BSOD.
==================================================
Dump File : 031313-7566-01.dmp
Crash Time : 13.3.2013. 12:20:28
Bug Check String : DRIVER_POWER_STATE_FAILURE
Bug Check Code : 0x0000009f
Parameter 1 : 00000000`00000003
Parameter 2 : fffffa80`0d2b3a10
Parameter 3 : fffff800`04833748
Parameter 4 : fffffa80`10b59270
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+75c40
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.18044 (win7sp1_gdr.130104-1431)
Processor : x64
Crash Address : ntoskrnl.exe+75c40
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\031313-7566-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 7601
Dump File Size : 1.171.248
==================================================
The interesting thing is, I seem to be getting BSODs more often now, after I have installed the newest NVIDIA drivers.
Any ideas?
SF Diagnostic file attached
Last edited by malus; 13 Mar 2013 at 07:45.
Please run the two following programs to check for root kits and virus infections:
WDO
TDSSKILLER
I highly doubt this is a virus, since I'm rather careful. Also, I got first BSOD the first day I got the laptop. There is little chance I got infected by that point. I will run the 2 programs nonetheless. Not that I have a better idea.
Unfortunately it is beginning to look Like a hardware problem ,But I will see if I can get another set of eyes on the problem.
Also try running through this tutorial: Fix: Nvlddmkm.sys Blue Screen BSOD Error in Windows 7
With the help of some of our other members Iit was pointed out to me thta you have around 24K of this error:
so please also run the following from an elevated command prompt:Code:Event[0]: Log Name: System Source: Disk Date: 2012-12-07T17:37:27.469 Event ID: 51 Task: N/A Level: Warning Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Malus-AsusN76 Description: An error was detected on device \Device\Harddisk2\DR24 during a paging operation.
Code:chkdsk /f /r
I ran WDO and TDSSKILLER scans. No threats found.
I also ran the Nvlddmkm.sys tutroial. Looking at file dates, the one that was in Windows/System32/drivers folder was the same one as from the newest NVIDIA driver package. I did the tutorial anyways.
Regarding this disk issue, I wonder if you read my first post. My system disk is SSD, and I also have internal 750 WD Scorpio Black drive for storage. What does Harddisk2 in \Device\Harddisk2\DR24 apply to? Is it the SSD or HDD?
Also what do you mean by "around 24K of this error"?
I did the chkdsk on both drives. Results are attached in separate txt files titled accordingly.
I have to main suspects:
a) SSD drive (as far as i know, they tend to make trouble like this)
b) RAM incompatilibity (since my Asus laptop officially supports 8GB, and I'm using 16)
Maybe there is a way to test and see if any of those to suspects are the problem!?
To answer your questions as follows, It is hard to tell which hard drive the error is referring to but from what I can gather it is referring to your SSD, by 24k i mean the error occurred around 24,000 times as shown your system event log, the error its self points to either a bad connector bad lead or a bad drive its self.
Now, to test and see if the ram Is causing a problem you can simply remove the extra ram and let it run and see if you still get a blue screen after removing. Also with your hard drives try re-seating them in the laptop, it may just be that they aren't seated quite right.
I just got another BSOD. This means that nothing that I've tried suggested here fixed it. I suspected the SSD or RAM from the start. Is it now safe to exclude the gpu and drivers, even though the dump files blame the gpu?
Is there any way to pinpoint the problem a bit more precise?
If it is the problem with ssd or ram; is there a way to provoke the crash?
I will try next with pulling out one ram module....
PS Since the bsods are now comming daily, it seems that installing the newset nvidia drivers actually worsened it.
Last edited by malus; 15 Mar 2013 at 02:05.