Random BSOD's related to Drivers

Sergent

Active member
Joined
Nov 9, 2013
Posts
39
Hello, this is my second time posting here about some problems i've been having with my Computer. The first problem was o fcource, BSOD and i'm back for the same thing. My last problem was with my faulty Graphics Card, after fixing that the BOSD's stopped for a good chunk of time but have recently started up again. This time the reason is driver_irql_not_less_or_equal, from what i know all of my drives are up to date but i still cant figure out why they became a problem again.

View attachment Windows7_Vista_jcgriff2.rar
 
Hi,

All of the DMP files located in your jcgriff2 output folder are from Nov. 2013. If you navigate to C:\Windows\Minidump, is there anything newer that you can manually zip up & attach?

Regards,

Patrick
 
Hi,

All of the DMP files located in your jcgriff2 output folder are from Nov. 2013. If you navigate to C:\Windows\Minidump, is there anything newer that you can manually zip up & attach?

Regards,

Patrick
I recently did a disc cleanup so all of my recent dump files are gone, i'll get back to you at the end of today, it'll prob crash a few times.
 
Hi,

All of the DMP files located in your jcgriff2 output folder are from Nov. 2013. If you navigate to C:\Windows\Minidump, is there anything newer that you can manually zip up & attach?

Regards,

Patrick
Well, i guess my computer decided to be nice and not crash today. Can you go off of anything i provided?
 
It wouldn't be worth looking at (respectfully, of course). That's ~6 months ago, and lots of things have changed since then :grin1:

We can just wait for a crash, it's okay.

Regards,

Patrick
 
It wouldn't be worth looking at (respectfully, of course). That's ~6 months ago, and lots of things have changed since then :grin1:

We can just wait for a crash, it's okay.

Regards,

Patrick
My computer has been crazy nice to me lately but i finally got a crash, the problem is, when i go to MiniDump, the folder is empty. Why?
 
Either the dump process did not complete gracefully due to a complication or there's improper dump settings.

If your computer is not generating .DMP files, please do the following:

1. Start > type %systemroot% which should show the Windows folder, click on it. Once inside that folder, ensure there is a Minidump folder created. If not, CTRL-SHIFT-N to make a New Folder and name it Minidump.

2. Windows key + Pause key. This should bring up System. Click Advanced System Settings on the left > Advanced > Performance > Settings > Advanced > Ensure there's a check-mark for 'Automatically manage paging file size for all drives'.

3. Windows key + Pause key. This should bring up System. Click Advanced System Settings on the left > Advanced > Startup and Recovery > Settings > System Failure > ensure there is a check mark next to 'Write an event to the system log'.

Ensure Small Memory Dump is selected and ensure the path is %systemroot%\Minidump.

4. Double check that the WERS is ENABLED:

Start > Search > type services.msc > Under the name tab, find Windows Error Reporting Service > If the status of the service is not Started then right click it and select Start. Also ensure that under Startup Type it is set to Automatic rather than Manual. You can do this by right clicking it, selecting properties, and under General selecting startup type to 'Automatic', and then click Apply.

Regards,

Patrick
 
Either the dump process did not complete gracefully due to a complication or there's improper dump settings.

If your computer is not generating .DMP files, please do the following:

1. Start > type %systemroot% which should show the Windows folder, click on it. Once inside that folder, ensure there is a Minidump folder created. If not, CTRL-SHIFT-N to make a New Folder and name it Minidump.

2. Windows key + Pause key. This should bring up System. Click Advanced System Settings on the left > Advanced > Performance > Settings > Advanced > Ensure there's a check-mark for 'Automatically manage paging file size for all drives'.

3. Windows key + Pause key. This should bring up System. Click Advanced System Settings on the left > Advanced > Startup and Recovery > Settings > System Failure > ensure there is a check mark next to 'Write an event to the system log'.

Ensure Small Memory Dump is selected and ensure the path is %systemroot%\Minidump.

4. Double check that the WERS is ENABLED:

Start > Search > type services.msc > Under the name tab, find Windows Error Reporting Service > If the status of the service is not Started then right click it and select Start. Also ensure that under Startup Type it is set to Automatic rather than Manual. You can do this by right clicking it, selecting properties, and under General selecting startup type to 'Automatic', and then click Apply.

Regards,

Patrick
Hopefully fixed it, not we await another crash.
 
So, we have a problem. Finally got a crash, but a MiniDump still wasn't created, even after fixing everything you told me to do.
 
Probably faulty hardware.

Can you please run Memtest 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).

Do note that some older generation motherboards do not support USB-based booting, therefore your only option is CD (or Floppy if you really wanted to).

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
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top