Hi,

The attached DMP file is of the SYSTEM_SERVICE_EXCEPTION (3b)bug check.

This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.

This error has been linked to excessive paged pool usage and may occur due to user-mode graphics drivers crossing over and passing bad data to the kernel code.

We have barely any info from the dump itself, so let's go ahead and enable Driver Verifier. Before doing so however, ensure you have the latest video card drivers via the manufacturers website. If you are already on the latest video card drivers, uninstall and install a version or a few versions behind the latest to ensure it's not a latest driver only issue. If you have already experimented with the latest video card driver and many previous versions, please give the beta driver for your card a try.


Driver Verifier:

What is Driver Verifier?

Driver Verifier is included in Windows 8, 7, Windows Server 2008 R2, Windows Vista, Windows Server 2008, Windows 2000, Windows XP, and Windows Server 2003 to promote stability and reliability; you can use this tool to troubleshoot driver issues. Windows kernel-mode components can cause system corruption or system failures as a result of an improperly written driver, such as an earlier version of a Windows Driver Model (WDM) driver.

Essentially, if there's a 3rd party driver believed to be at issue, enabling Driver Verifier will help flush out the rogue driver if it detects a violation.

Before enabling Driver Verifier, it is recommended to create a System Restore Point:

Vista - START | type rstrui - create a restore point
Windows 7 - START | type create | select "Create a Restore Point"
Windows 8 - Restore Point - Create in Windows 8

How to enable Driver Verifier:

Start > type "verifier" without the quotes > Select the following options -

1. Select - "Create custom settings (for code developers)"
2. Select - "Select individual settings from a full list"
3. Check the following boxes -
- Special Pool
- Pool Tracking
- Force IRQL Checking
- Deadlock Detection
- Security Checks (Windows 7 & 8)
- DDI compliance checking (Windows 8)
- Miscellaneous Checks
4. Select - "Select driver names from a list"
5. Click on the "Provider" tab. This will sort all of the drivers by the provider.
6. Check EVERY box that is NOT provided by Microsoft / Microsoft Corporation.
7. Click on Finish.
8. Restart.

Important information regarding Driver Verifier:

- If Driver Verifier finds a violation, the system will BSOD.

- After enabling Driver Verifier and restarting the system, depending on the culprit, if for example the driver is on start-up, you may not be able to get back into normal Windows because Driver Verifier will flag it, and as stated above, that will cause / force a BSOD.

If this happens, do not panic, do the following:

- Boot into Safe Mode by repeatedly tapping the F8 key during boot-up.

- Once in Safe Mode - Start > Search > type "cmd" without the quotes.

- To turn off Driver Verifier, type in cmd "verifier /reset" without the quotes.
・ Restart and boot into normal Windows.

If your OS became corrupt or you cannot boot into Windows after disabling verifier via Safe Mode:

- Boot into Safe Mode by repeatedly tapping the F8 key during boot-up.

- Once in Safe Mode - Start > type "system restore" without the quotes.

- Choose the restore point you created earlier.

How long should I keep Driver Verifier enabled for?

It varies, many experts and analysts have different recommendations. Personally, I recommend keeping it enabled for at least 24 hours. If you don't BSOD by then, disable Driver Verifier.

My system BSOD'd, where can I find the crash dumps?

They will be located in %systemroot%\Minidump

Any other questions can most likely be answered by this article:
Using Driver Verifier to identify issues with Windows drivers for advanced users

Regards,

Patrick

 

i did try the verifier and lol didn't even take me 1 second just restarted then BSOD idk said kernal stack faulty driver something here is the dump file

 

The DMP file is of the DRIVER_VERIFIER_DETECTED_VIOLATION (c4) bug check.

This is the general bug check code for fatal errors found by Driver Verifier.

Despite its name however, we're not getting a device driver detected within violation.
1. Did you follow:

Before doing so however, ensure you have the latest video card drivers via the manufacturers website. If you are already on the latest video card drivers, uninstall and install a version or a few versions behind the latest to ensure it's not a latest driver only issue. If you have already experimented with the latest video card driver and many previous versions, please give the beta driver for your card a try.

?

2. If so, I am noticing you have a Killer Wireless-N 1100 Series LAN device driver listed and loaded. These NIC's can sometimes cause a lot of issues if the drivers aren't up to date, so be sure they are - http://www.bigfootnetworks.com/support/index.php?_m=downloads&_a=view

Regards,

Patrick

 

oh yea i did update nvidia to latest drivers but not killer wireless thats what ill do now if theres something else ill post a replay

 

the problem that bigfootnetwork doesnt load at all XD cant even download the driver lol

 

nvm went to their facebook page and fount out there website is down but they did post external link for drivers downloading latest one now

 

ok the problem isnt from anything updated drivers everything but then i took a screen shot of the blue screen it said nvlddmkm.sys so i was like still not satisfied so i did verifier again checked everything except Microsoft and nvidia and worked perfectly after no bsods so i think the problem is from Nvdia driver i have the latest one so i really dont know what do..

 

I believe there's a bug with the latest nVidia drivers that rolled out, because there's a huge frequency of nVidia crashes. Is there a beta driver available to download and install for your video card?

Regards,

Patrick

 

yea i did install the beta one and didnt bsod with driver verifer but i guess i should wait atleast 24 hours like u said? so i be certain that it wont crash again thank you i really didnt know what to do without ur help

 

It's my pleasure!

Yes, keep verifier enabled for at least 24 hrs. If you don't crash in that time frame, go ahead and disable it.

Regards,

Patrick

 

oh XD now it came for memory mangement i read memory mangement in ur bsod blog i found out its about usb drivers ill try to find usb driver and then ill see if it will bsod again XD

but the problem i didnt connect any external device XD so i dont think its from usb since i have no external device connection :s ill upload the dump file XD

 

The attached DMP file is of the MEMORY_MANAGEMENT (1a) bug check.

This indicates that a severe memory management error occurred.

BugCheck 1A, {3452, 75672000, fffff700010936e8, 64c00007e5144424}

The 1st parameter of the bug check is 3452 which = OTHER which indicates an unknown memory management error occurred.Can you enable verifier one more time, please? If it shows no driver in violation, we'll begin hardware diagnostics.

Regards,

Patrick

 

ok

 

Great, thanks.

Regards,

Patrick

 

verifier didnt have any problems

 

Keep it enabled for at least 48 hrs.

Regards,

Patrick

 

okay. thanks :smile:

 

My pleasure as always.

Regards,

Patrick

 

its stupid nvidia driver again.. nvldmkm.sys again and while i was typing this driver verifier did it again so i had to disable it idk whats wrong with this laptop its just wierd..

 

I believe there's a bug with nVidia's drivers right now, this is pretty frequent in a few cases. Either that, or you have another underlying hardware issue. We can run a Memtest since we've seen a *1A bug check and see what comes up. Run it for no less than ~8 passes (several hours):

Memtest86+:

Download Memtest86+ here:

Memtest86+ - Advanced Memory Diagnostic Tool

Which should I download?

You can either download the pre-compiled ISO that you would burn to a CD and then boot from the CD, or you can download the auto-installer for the USB key. What this will do is format your USB drive, make it a bootable device, and then install the necessary files. Both do the same job, it's just up to you which you choose, or which you have available (whether it's CD or USB).

How Memtest works:

Memtest86 writes a series of test patterns to most memory addresses, reads back the data written, and compares it for errors.

The default pass does 9 different tests, varying in access patterns and test data. A tenth test, bit fade, is selectable from the menu. It writes all memory with zeroes, then sleeps for 90 minutes before checking to see if bits have changed (perhaps because of refresh problems). This is repeated with all ones for a total time of 3 hours per pass.

Many chipsets can report RAM speeds and timings via SPD (Serial Presence Detect) or EPP (Enhanced Performance Profiles), and some even support changing the expected memory speed. If the expected memory speed is overclocked, Memtest86 can test that memory performance is error-free with these faster settings.

Some hardware is able to report the "PAT status" (PAT: enabled or PAT: disabled). This is a reference to Intel Performance acceleration technology; there may be BIOS settings which affect this aspect of memory timing.

This information, if available to the program, can be displayed via a menu option.

Any other questions, they can most likely be answered by reading this great guide here:

FAQ : please read before posting

Regards,

Patrick

 

ok before i sleep today ill set it on 7 passes then tommorow i should post and tell u the results

 

Great, I look forward to your update.

Regards,

Patrick

 

left it for 8-9 hours it was like on pass 1 again i really dont know how T_T but it said no errors pass complete

 

You left the system on for 8-9 hrs and it was only on Pass #1? What was the walltime (total time of the test), did you get to see?

Regards,

Patrick

 

Could you post the make and model of your laptop, and if you installed drivers from the Nvidia site your liable to have issues, since many laptop makers modify drivers to work with their hardware,I suggest you use the driver from the laptop makers support page for your model.