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: BSOD only started recently after changing DVD Drive Model - am lost...


15 Jun 2013   #1

windows 7 Ultimate 64
 
 
BSOD only started recently after changing DVD Drive Model - am lost...

Hi, I am getting a BSOD once per day on average and have read up online, updated all my drivers, changed webcams etc.

I believe it started happening a week after I got my DVD drive replaced. My PC is 5 months old and was running smoothly with no issues up until my dvd drive failed. None of the errors I am receiving state anything wrong with the DVD player so I am not convinced it is related to it but am not sure if the new dvd drive has cuased another issue.

Once crash dump related to the logitech driver and I realised my web cam was not certified on Windows 7 bit so I got a new webcam but the BSOD keeps occurring.

I ran a driver update program and all my drivers are upto date but I still get the BSOD.

Am not lost as to what could be causing it and would really appreciate any help.

many thanks, Brendon.

My System SpecsSystem Spec
.

15 Jun 2013   #2
Arc

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium 64 Bit SP 1
 
 

Disable Driver Verifier.
Code:
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
It may not be needed anymore at once. If it is needed later, we will instruct you accordingly.

The display driver is failing there.
Code:
fffff880`08137e08  fffff880`04a65ec0Unable 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
 nvlddmkm+0x1d8ec0
It is just a few days ago only that I uninstalled the 320.18 WHQL, as it is problematic there; and a lot of other users reported it as problematic. I would suggest you to do the same. Install the 314.22 WHQL only.
  • Uninstall All nvidia items in Control Panel > Programs and features
    • 3D Vision Control Driver
    • 3D Vision Driver
    • Graphics Driver
    • HD Audio Driver
    • PhysX
    • nvidia Update
    (Are you using nvidia chipset drivers? If so, dont uninstall anything other than those are listed).
  • Now follow Drivers - Clean Left over Files after Uninstalling
  • Boot normally now. Go to Drivers - Download NVIDIA Drivers, Download 314.22 WHQL. While installing, Select Custom (Advanced) install. In the next page, follow this settings:

Another most expected thing is, Trend Micro Internet Security.
Code:
fffff880`08137e28  fffff880`03e2786fUnable to load image \SystemRoot\system32\DRIVERS\tmevtmgr.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for tmevtmgr.sys
*** ERROR: Module load completed but symbols could not be loaded for tmevtmgr.sys
 tmevtmgr+0xa86f
Description here: Driver Reference Table - tmevtmgr.sys

I strongly recommend you to Uninstall TrendMicro, using their uninstaller tool. Use Microsoft Security Essentials as your antivirus with windows inbuilt firewall, and free MBAM as the on demand scanner.
Download, install and update those, and then run full system scans with both of them, one by one.

Let us know the results.

P.S. As you vave taken care of the Logitech Webcam, keeping silent on it.
My System SpecsSystem Spec
15 Jun 2013   #3

windows 7 Ultimate 64
 
 

thanks will give this a try, appreciate your help. How from the info I zipped up were you able to determine this? Am keen to learn more.....
My System SpecsSystem Spec
.


16 Jun 2013   #4
Arc

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium 64 Bit SP 1
 
 

Quote   Quote: Originally Posted by badler View Post
thanks will give this a try, appreciate your help. How from the info I zipped up were you able to determine this? Am keen to learn more.....
At first take care of the issue. You will have time to learn Learning is a function of time.
My System SpecsSystem Spec
27 Jun 2013   #5

windows 7 Ultimate 64
 
 

HI, I follwed this (except for Trend Micro) and still getting a BSOD. Can you review the attached updated zip file and let me know next steps please. Have been using trend for months on the PC without any issues so am keen to try and keep it if I can. Also, Logitech MK320 keyboard now behaving weirdly, sometimes you type and nothing happens on the screen then it catches up and shows everything you typed, like there is a delay. Its not all the time. Many thanks.
My System SpecsSystem Spec
27 Jun 2013   #6
Arc

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium 64 Bit SP 1
 
 

Care to take the suggestion in total? Then let us know?

You cannot expect desired results with the BSOD causer present in the system.
My System SpecsSystem Spec
04 Jul 2013   #7

windows 7 Ultimate 64
 
 

Hi, I followed everything and got another BSOD today, updated dump files attached, can you please help to work out what is causing it? thanks
My System SpecsSystem Spec
04 Jul 2013   #8
Arc

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium 64 Bit SP 1
 
 

It is a stop 0x51.

According to Carrona.org, STOP 0x00000051: REGISTRY_ERROR
Usual causes: Hardware failure, File system corruption, Security issues

The file system corruption is comparatively easier to recover. A repair install is enough to do it. But we need to take care of the other two probable causes.

Scan the system for possible virus infection with the following programs.
Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.

Stress test the Graphics Card using Furmark.
Video Card - Stress Test with Furmark

Stress test the CPU.
Hardware - Stress Test With Prime95

Let us know the results. If those are all OK, we will decide our next step.
_________________________________________________________
BSOD ANALYSIS:
Code:
.........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 51, {1, fffff8a000024010, 145b000, 374}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::NNGAKEGL::`string'+9dba )

Followup: MachineOwner
---------
My System SpecsSystem Spec
08 Jul 2013   #9

windows 7 Ultimate 64
 
 

Hi,

All suggested tests ran successfully. no errors. Have had a few more BSOD since my last post, updated diagnostics attached. What would you suggest as next steps?

Thanks,

Brendon.
My System SpecsSystem Spec
08 Jul 2013   #10

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium x86 Service Pack 1 - Linux Mint Mate 14 x64
 
 

Welcome to the forums badler,

Code:
BugCheck 1A, {41790, fffffa8001a7b220, ffff, 0}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+35084 )
Code:
Usual causes:  Device driver, memory, kernel
It seems that a page table page has become corrupt, this is a data structure used store mappings between physical and virtual memory addresses.

Code:
1: kd> dt nt!_MMPFN fffffa8001a7b220
   +0x000 u1               : <unnamed-tag>
   +0x008 u2               : <unnamed-tag>
   +0x010 PteAddress       : 0xfffff6fb`40000018 _MMPTE <-- PTE which points to the particular PFN
   +0x010 VolatilePteAddress : 0xfffff6fb`40000018 Void
   +0x010 Lock             : 0n1073741848
   +0x010 PteLong          : 0xfffff6fb`40000018
   +0x018 u3               : <unnamed-tag>
   +0x01c UsedPageTableEntries : 0xffff
   +0x01e VaType           : 0 ''
   +0x01f ViewCount        : 0 ''
   +0x020 OriginalPte      : _MMPTE
   +0x020 AweReferenceCount : 0n128
   +0x028 u4               : <unnamed-tag>
The reference count for the UsedPageTableEntries field seems to be have dropped below zero, this results in a fatal error (BSOD).

Run Driver Verifier to scan for any corrupted drivers which may be causing problems, this program works by running various stress tests on drivers, in order to produce a BSOD which will locate the driver; run for least 24 hours:
information   Information

You may need to enable the Special Pool option too.
My System SpecsSystem Spec
Reply

 BSOD only started recently after changing DVD Drive Model - am lost...




Thread Tools



Similar help and support threads for2: BSOD only started recently after changing DVD Drive Model - am lost...
Thread Forum
Recently started getting random BSODs BSOD Help and Support
PC Crashes while in sleep - Started recently BSOD Help and Support
Got a few BSOD recently without changing anything on my comp. BSOD Help and Support
BSOD Stop: 0x00000124; started recently always crashes without warning BSOD Help and Support
Random BSOD recently started, code1a, 3b and 50 by ntkrnlmp and win32k BSOD Help and Support
BSOD's started recently BSOD Help and Support
Recently started overheating CPU/crashing 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 01:12 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