Driver irql not less or equal BSOD

driverdj2000

driverdj2000

New Member
So i just got this BSOD on my pc.
the specs are in my sig.
its a D1 stop code.
The strange thing is it happened just as pc was shutting down.
so event viewer didnt log it.
i had two stop f4 errors a few wks ago.
All these since i installed a new 2tb spinpoint in my system.
until then not one problem.
Anyone else have this issue?
cheers
 
No nothing else. Its 3 bsod's in a month or so. So its not very regular.
The first 2 were supposedly a process or thread in windows that terminated unexpectedly.
I did update my sound drivers recently for my mobo and I moved indexing and page file from my ssd to the new drive, so it could be a lot of things.
 
Download BlueScreenView (in Zip file)
No installation required.
Unzip downloaded file and double click on BlueScreenView.exe file to run the program.
When scanning is done, go Edit>Select All.
Go File>Save Selected Items, and save the report as BSOD.txt.
Open BSOD.txt in Notepad, copy all content, and paste it into your next reply.
 
Thanks guys. Unfortunetely there is nothing to scan.
It says windows did not save the error because I've no page file for c drive.
I moved it back to c drive so when it happens again ill run the scan and post results.
 
Also, make sure, your settings are correct...

1. Click Start, point to Settings, and then click Control Panel (Start>Control Panel in Vista).
2. Double-click System.
3. Click (Advanced system settings link in Vista, then --->)the Advanced tab, and then click Settings under Startup and Recovery.
4. Make sure, there is a checkmark in Write an event to the system log.
5. In the Write debugging information list, click Small memory dump (64k) (128K in Windows 7).
 
Broni said:
Also, make sure, your settings are correct...

1. Click Start, point to Settings, and then click Control Panel (Start>Control Panel in Vista).
2. Double-click System.
3. Click (Advanced system settings link in Vista, then --->)the Advanced tab, and then click Settings under Startup and Recovery.
4. Make sure, there is a checkmark in Write an event to the system log.
5. In the Write debugging information list, click Small memory dump (64k) (128K in Windows 7).
Click to expand...

I agree.

You can also put the COMPLETE MEMORY DUMP instead of small if you want.Just in case.The memory dump specifies what type of information Windows should write to the specified dump file.Here is the description of each one of them:

Small Memory Dump records the smallest set of useful information that will help identify why the system stopped unexpectedly. This option requires a paging file of at least 2 MB on the boot volume of your computer and specifies that Windows will create a new file each time the system stops unexpectedly. A history of these files is stored in the directory listed under Small Dump Directory.

Kernel Memory Dump records only kernel memory, which speeds up the process of recording information in a log when the system stops unexpectedly. Depending on the amount of RAM in your computer, you must have from 50 MB to 800 MB available for the paging file on the boot volume.

Complete Memory Dump records the entire contents of system memory when the system stops unexpectedly. If you choose this option you must have a paging file on the boot volume large enough to hold all of the physical RAM plus one megabyte (MB).

Note that you must be logged in as the computer administrator to set the recovery options.





Cheers and have a great day!
 
You must log in or register to reply here.
Back
Top