Blue Screen of Death (BSOD)

Unfortunately no DMP's included.
Please try this way.

We do need the DMP file as it contains the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.

If you are overclocking STOP

You may be able to get the DMP files without crashing by booting into safe mode (F8) with networking.

Please follow these instructions to collect data from the crashes and upload them here.

https://www.sysnative.com/forums/sh...indows-8-7-amp-Vista?p=303&viewfull=1#post303

https://www.sysnative.com/0x8/BSOD_Windows7_Vista_v2.64_jcgriff2_.exe


To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.

The procedure:

* Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
* Zip up the contents of that folder

Please upload them to skydrive or a file sharing service and put a link to them in your next post.

Also go to start>search/run>cmd>msinfo32 and include it in the upload.



To ensure minidumps are enabled:

* Go to Start, in the Search Box type: sysdm.cpl, press Enter.
* Under the Advanced tab, click on the Startup and Recovery Settings... button.
* Ensure that Automatically restart is unchecked.
* Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
* Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
* OK your way out.
* Reboot if changes have been made.


https://www.sysnative.com/forums/showthread.php/325-BSODs-but-no-Dump-Files


http://www.osronline.com/article.cfm?article=545
 
Hi,

my C:\Windows\Minidump is empty
i dont have dmp files in that locations.........i made all the changes that you have mentioned in the post
 
IF you have been using a Registry Cleaner that may be the reason no DMP's were produced.


For dumps to be produced. . .

* Page file must be on OS drive

* Page file base allocation size must be > than installed physical RAM

* Windows Error Reporting (WER) system service should be set to MANUAL

* Set page file to system manged on the OS drive.

* Set system crash/recovery options to "kernel Memory Dump"

* User account control must be running.

* Sometimes SSD drives with older firmware don't create DMPS.
 
Last edited:
Hi,

iam sorry but i dont know how to verify this things

* Page file must be on OS drive

* Page file base allocation size must be > than installed physical RAM

* Windows Error Reporting (WER) system service should be set to MANUAL

* Set page file to system manged on the OS drive.

* Set system crash/recovery options to "kernel Memory Dump"

* User account control must be running.

* Sometimes SSD drives with older firmware don't create DMPS.


can u please help me on this

thanks and regards
ranjeet
 
Hi,

Finally i got DMP file,
i am attaching all the files you require (i.e)
1. Windows7_Vista_jcgriff2
2. Perfmon in html format
3. system info
The above three files are zipped in (BSOD(Windows7_Vista_jcgriff2+PERFMON+SYSTEM INFO).zip)
and finally
4. the dmp file (072312-18657-01-DMP.zip)
 

Attachments

Hello jeetv33!

I've taken a look at your attached dump file and it is a standard D1: DRIVER_IRQL_NOT_LESS_OR_EQUAL bugcheck pointing to the driver culprit athr.sys which is the Atheros Extensible Wireless LAN driver for CB42/CB43/MB42/MB43 Network Adapter - D-Link AirPlus DWL-G520 Wireless PCI Adapter(rev.B). I believe it was discontinued in 2008.

Regardless, double check and install the latest version of that driver here: http://www.atheros.cz/

Driver(s) in need of update if available:

VSTCNXT3.SYS - Wed Oct 15 20:29:13 2008 (Conexant SoftK56 Modem Driver). Update if available here.

VSTAZL3.SYS - Wed Oct 15 20:30:03 2008 - Same as above, refer to above.

VSTDPV3.SYS - Wed Oct 15 20:32:04 2008 - Same as above, refer to above.
Click to expand...

Regards,

Patrick
 
As Epeen hinted too, those 56k modem drivers look a little funky. I've often seen 56k modem drivers create resource or other conflicts because they're poorly coded and old, probably due to dialup being obsolete. Unless you still have some need for a 56k modem, you'll want to uninstall the drivers for it.
 
Vir Gnarus said:
probably due to dialup being obsolete
Click to expand...

Unfortunately, dial-up is not obsolete in the U.S. There are indeed many people who are still on dial-up either because broadband isn't available or they cannot afford it. At another forum, members frequently mention going to the local public library in order to download security updates.

As recent as February, 2011, from U.S. Broadband Map Shows Large Uncovered Areas | PCWorld Business Center

The nation's first national broadband map shows that between 5 percent and 10 percent of the U.S. population lacks access to broadband that supports basic applications, including downloading Web pages, photos and video, said the U.S. National Telecommunications and Information Administration (NTIA).
Click to expand...

That appears to be an improvement from 2009, when C|Net reported:

In a survey of more than 100,000 people in more than 50,000 households across the U.S., 40 percent reported no broadband or high-speed access to the Internet, while 30 percent said they have no Internet access at all.
Click to expand...
 
In my experience, old modem drivers do not cause issues with Windows 7. I have seen probably hundreds of users with old laptops that had old modem drivers, and I have yet to see those be culprits in crashes. I have a similar modem on my Toshiba laptop; in fact, many of my drivers have 2007 timestamps. I have never had any crashes with the system.

I have seen quite a few crashes due to USB wireless network adapters, and especially if their drivers are out of date.
 

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

Back
Top