random BSOD, used driver verifier and multiple crashes generated

[deowba]

Hello everyone, I am getting lost trying to troubleshoot my BSOD problem myself, I sincerely thank you for your help in advance. All my knowledge is from Google searches, please assume I know nothing regarding IT...

Summary of History:
1) Jan this year: Bought laptop Sager NP7270 with a Samsung 850 EVO M.2 SSD 500GB HDD, chose Windows 7 professional 64bit as my OS installed on above m.2 SSD. For personal use: gaming, websurf, media, email, etc.

2) Started getting random BSOD during normal everyday use, no detectable pattern and times. My then current guesses-- possible sound driver clash w/Sound Blaster Cinema 2 and Realtek audio (since opening laptop I've had unresponsive issues with SB Cinema 2). Tried uninstalling SB Cinema 2 but I'm unable to (error, unable to). Also, issue with losing sound when resuming from hibernate/sleep.

3) March 20th: Decided to clean install with prepackaged drivers and OS disc. Did not install SB Cinama 2. All seemed well, except still getting no sound after resuming from hibernate/sleep-- realized if I go into sleep again and resume, sound will come back.

4) April 8th: hit with first BSOD after clean install, then subsequent random BSOD next few days (see below screenshot of bluescreenview BSOD crashtimes).

5) Sometimes during these few months: Ran SFC config, results normal. I also did run a HDD check (through Windows), and no errors. Also, ran standard Windows Memory Diagnostic, results normal.

6) Yesterday: ran 13hrs (8 passes) of Memtest86, 0 errors. Also ran 1 pass of Memtest86+, 0 errors.

7) Today(4/21): Ran Driver Verifier using this tutorial, and all sorts of problems arose-- Most or all of the logged crashes are from shutting down (improper shutdown) during my restarts, and I wouldn't even get an actual bluescreen (it just resets). Also, while Driver Verifier was on, computer would be very sluggish. Internet connectivity would be very sluggish. Firefox would crash multiple times. My wireless mouse would stop responding suddenly (I'd have to use touchpad).

After each crash I would look at BlueScreenView and try to Google the Bug Check String/stop error code, and also the driver causing issue, but I fail at finding the solution as I don't know how to figure out the pattern. Below is a screenshot of my BlueScreenView:

View attachment 385496



And here is my log file: View attachment 385497

Again, your help is greatly appreciated!

 

[sphenic]

Driver verifier

You are seeing all sorts of different errors, like I was...

Here is what I did on mine to pinpoint the problem.

Ran driver verifier with default settings, on all drivers. rebooted and fired up stuff intil i got a BSOD.
Took the newly created memory.dbg file from c:\windows and loaded it into WinDBG.

It told me what device driver was creating issues.

 

[axe0]

Hi deowba,

Welcome to the 7forums

I strongly recommend that you visit the support page of your laptop manufacturer and install all updated drivers.
There are several different drivers flagged, most of them are outdated.

 

[deowba]

Thank you both for responses. Should I follow through with both your solutions? Perhaps axe0's first, go to Sager support for updated drivers; then follow with sphenic's advice on driver verifier on default and then winDBG...?

 

[axe0]

Driver verifier isn't necessary, the drivers that caused the crashes are already shown in the dumps and I've done the Windbg part for you

 

[deowba]

I see, well thank you very much axe0! To follow up on your instructions:
1) do you have a list of those drivers that are outdated, i.e. are there certain ones I should have more priority in updating?

2) once I've updated, should I run any sort of test to verify stability?

Thank you again (sphenic too), and thanks guys for having me. I'll touch back once I've completed your instructions.

 

[axe0]

1. It is pretty generic, I noticed quite some drivers so I recommend that you go through the list provided by Sager.

2. I prefer to suggest to test under normal circumstances.

 

[deowba]

axe0, I went to Sager's support page and found my laptop's list of updated drivers. After installing the chipset and intel driver, I double checked the driver versions they offer with the ones I'm currently using. It turns out they're the same.

Here is the link for Sager's updated list of drivers for my NP7270 laptop.

All drivers listed are the same versions as mine, except the below few:

Bluetooth (I disabled this device instead as I don't use)
Integrated video camera (I disabled this device as I don't use as well)
Killer Wireless-AC N1535 Wireless LAN (I don't have this in my machine)
Intel WiDi Driver for Windows 7 64 BIT (I don't think this is installed on my machine)

To add, I also discovered in my device manager "Microsoft Virtual WiFi Miniadapter" w/drivers from 2006. As I don't plan on using this service, I disabled as well.


​

My question is does this mean my drivers are actually most up to date with the Manufacturer's? And where do I go from here then?

 

[axe0]

Update and reinstall the drivers, it then appears that some 'up to date' drivers are using a very old driver that caused crashes.
To explain, there are multiple drivers for the same thing, 1 of those drivers is very old while others are up to date, the other drivers is the onces you likely see.

 

[deowba]

Alright, I've reinstalled all the drivers from Sager's list. Only 2 I didn't install are Bluetooth (I couldn't figure out which folder of drivers to choose from- 7265 or 8260) and Integrated Video Camera. I just kept them disabled from my last post above (disabled under device manager).

1) Will this be ok?
2) Now, we wait and see through normal laptop use? When should I check back to mark thread as solved?

Thank you again.

 

[axe0]

1. Let's hope that it is enough

2. Yes. I normally suggest to wait a few days before marking the thread as solved.

 

[deowba]

Unfortunately, got a crash tonight. Was browsing Firefox v46.0 and it crashed all of a sudden, and wouldn't restart (keeps going to the crash window). So I decided to restart the laptop, after waiting a bit longer than usual, the laptop boots and tells me Windows 7 didn't shutdown properly. Looks like it was a BSOD, and again no actual blue screen.

Below is the BlueScreenView error:
View attachment 385731


And here is the log file: View attachment 385732

Thank you again for the help!

 

[axe0]

You don't see the BSOD probably because you haven't set the recovery settings to not reboot when a BSOD occurs, this causes the BSOD to instantly disappear with your SSD as boot device.
I had the same problem a few times when I was booting, this happened a long time ago.
With a SSD you need to uncheck the 'Automatically restart' option in the Startup & Recovery settings to get the BSOD screen visible for you.
http://www.sevenforums.com/tutorials/174459-dump-files-configure-windows-create-bsod.html
View attachment 385738

After you've done that run driver verifier again according to below instructions to see if it flags anything.

Diagnostic Test

 DRIVER VERIFIER

   Warning

Please make a backup of your important files and get your rescue media or create one.
Please create a restore point.

Please follow this tutorial to run driver verifier.

Some windows drivers are blamed in a few crashes, but that usually means that a 3rd party driver is actually the cause.
Driver verifier stresses your drivers and will crash your pc if any driver fails due to a violation.

Driver verifier should be performed for a max of 48 hours, or when you have a bluescreen, whatever comes first.

If driver verifier has found a violation and you can't get back into windows normally, try to boot into safe mode and reset in safe mode driver verifier, or in the troubleshooting options open command prompt and type verifier /reset.

   Note

Your system will act very sluggishly while driver verifier is enabled, this is normal as your drivers will be being subjected to heavy testing in order to make them crash.

 

[deowba]

HELP! Laptop feels bricked. After rebooting to start driver verifier:

1) 1st reboot- hangs at startup; tried again, same.
2) Reboot, this time tried Safe Mode and Safe Mode w/command prompt- now boot hangs at CLASSPNP.SYS. Every single time.

3) Put in my Windows 7 cd to try to system restore-- it hangs at the windows logo screen (4 color windows animation freezes). Every single time. **To note, I can disable UEFI in bios and the windows 7 cd will boot, but when I go to repair, it says "This version of System Recovery Options is not compatible with the version of windows you are trying to repair. Try using a recovery disc that is compatible with this version of windows." So I still can't get to system recovery... Is it because my m.2 SSD (C drive) needs UEFI on?


I am essentially stuck with no way to restore back to Windows 7. Is my only option to reinstall windows 7? (Hopefully it is still possible...)

 

[axe0]

Try first to reset the settings of driver verifier before using the system restore point, you can reset them in some ways which I've mostly included in my post.

 

[deowba]

Axe0, thanks for your continued support.

1) I was able to get into repair mode through my windows7 boot cd by also enabling "Launch CSM" and "Network Stack" under the submenu of "UEFI" being enabled, looks like they were both disabled. (Should these stay enabled?)

2) In the windows7 boot disk repair mode, I selected "command prompt" and and chose to use BCDEDIT command to get Safe Mode to boot up. It was successful, but then windows7 would only start in safe mode. I went to MSCONFIG and under the boot tab unchecked "safeboot" while leaving "make all boot settings permanent" unchecked. (Was this the proper way to do it?)

3) I went back to driververifier.exe and reset settings (disabled it).

3) Now that I'm back to normal Windows7, here is the new generated log file: View attachment 385776

 

[axe0]

Update the drivers that your laptop manufacturer should provide, the Realtek audio driver has been flagged in all the crashes.

3: kd> lmvm MBfilt64
Browse full module list
start             end                 module name
fffff880`0a69e000 fffff880`0a6ac000   MBfilt64 T (no symbols)           
    Loaded symbol image file: MBfilt64.sys
    Image path: \SystemRoot\system32\drivers\MBfilt64.sys
    Image name: MBfilt64.sys
    Browse all global symbols  functions  data
    Timestamp:        [COLOR="Red"]Fri Jul 31 05:40:32 2009[/COLOR] (4A7267B0)
    CheckSum:         000185CD
    ImageSize:        0000E000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Your welcome for the support, I'm happy to help

 

[deowba]

Axe0, I am back as I ran into trouble again:

2 days after your post I decided to install Creative Sound Blaster Cinema 2 drivers, because I couldn't find any available Realtek drivers newer than the ones I'm using (I tried Sager and Clevo websites, and Realtek website which only offered a generic driver). Things ran without BSOD's, but just now when booting up before Windows7 started to load it jumped to a checkdisk message, "one of your disks needs to be checked for consistency..."

Below is the WININIT event log of the incident:

Checking file system on C:
The type of the file system is NTFS.


One of your disks needs to be checked for consistency. You
may cancel the disk check, but it is strongly recommended
that you continue.
Windows will now check the disk.

CHKDSK is verifying files (stage 1 of 3)...
207104 file records processed. File verification completed.
678 large file records processed. 0 bad file records processed. 2 EA records processed. 44 reparse records processed. CHKDSK is verifying indexes (stage 2 of 3)...
260544 index entries processed. Index verification completed.
0 unindexed files scanned. 0 unindexed files recovered. CHKDSK is verifying security descriptors (stage 3 of 3)...
207104 file SDs/SIDs processed. Cleaning up 563 unused index entries from index $SII of file 0x9.
Cleaning up 563 unused index entries from index $SDH of file 0x9.
Cleaning up 563 unused security descriptors.
Security descriptor verification completed.
26721 data files processed. CHKDSK is verifying Usn Journal...
34746984 USN bytes processed. Usn Journal verification completed.
CHKDSK discovered free space marked as allocated in the
master file table (MFT) bitmap.
CHKDSK discovered free space marked as allocated in the volume bitmap.
Windows has made corrections to the file system.

487691263 KB total disk space.
76372344 KB in 117828 files.
78844 KB in 26722 indexes.
0 KB in bad sectors.
322919 KB in use by the system.
65536 KB occupied by the log file.
410917156 KB available on disk.

4096 bytes in each allocation unit.
121922815 total allocation units on disk.
102729289 allocation units available on disk.

Internal Info:
00 29 03 00 b1 34 02 00 1d 2b 04 00 00 00 00 00 .)...4...+......
eb 00 00 00 2c 00 00 00 00 00 00 00 00 00 00 00 ....,...........
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................

Windows has finished checking your disk.
Please wait while your computer restarts.


​

After getting back to Windows7, I tried running checkdisk through My Computer>>right-click C drive>>properties>>tool tab>>check now>> "check next time reboot"... ...but after it ran, there was no WININIT log under event viewer(???).

So then I instead went to "search program and files">>chkdsk>>right-click chkdsk.exe and run as administrator. And a WININIT log was generated, and results normal.


Do you think the cause of my BSOD problems are because of a faulty SSD?

 

[axe0]

I don't see any indication that it may be a possibility.

A chkdsk is once in a while required, after almost a year my laptop wanted me to run it again and thus did so by itself.
Chkdsk will change a few things, as it has with your hard drive, but in most of the times there are no real issues.