BSOD loading Netflix/Flash app

[blackwarden999]

So, while I was on wireless, which I think the problem might originate from, I had 3 BSODs within a span of 30 minutes. Two of the BSODs were linked to opening Netflix on Firefox and the other was caused by opening a Flash app on Chrome. If I recall correctly, the last BSOD error was something akin to Driver not less or equal? Regarding the dump files, when I went to double check that a dump file was created upon BSOD, I noticed that the option to have it overwrite was checked, so I'm not sure if the previous two BSOD dump files were recorded. Some of my previous older BSODs (which the issue was solved) were included in the folder, I believe, since the program just captured everything in the minidump folder.

System Specs:

Windows 7 Home Premium 64 bit
CPU: i5 M430
Memory: 4 gb
Video Card: ATI Radeon Mobility 5850
The laptop is roughly 2 years old now

 

[JMH]

The DMP's you submitted were from 2010, thus useless.
Please read carefully below...


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.

 

[blackwarden999]

Yes, I realize they were from 2010. When I checked sysdm.cpl, I noticed that under debugging information, it was set to kernel memory dump and overwrite any existing file was checked. So where exactly would that dump file be? I assumed the dump file would be placed somewhere in the minidump folder anyway, overwriting one of the older dumps and that the program recommended would grab it.

 

[zigzag3143]

Yes, I realize they were from 2010. When I checked sysdm.cpl, I noticed that under debugging information, it was set to kernel memory dump and overwrite any existing file was checked. So where exactly would that dump file be? I assumed the dump file would be placed somewhere in the minidump folder anyway, overwriting one of the older dumps and that the program recommended would grab it.

There are several reasons that may prevent you from having a DMP file in the usual places.

If you control panel is not configured for small dump you probably will then find it in C:\windows and it will be called MEMORY.dmp. It will overwrite every crash.

Other reasons are if you have UAC turned off, if you have a small page file, or a page file on a different HD than the OS.

 

[blackwarden999]

Yes, I realize they were from 2010. When I checked sysdm.cpl, I noticed that under debugging information, it was set to kernel memory dump and overwrite any existing file was checked. So where exactly would that dump file be? I assumed the dump file would be placed somewhere in the minidump folder anyway, overwriting one of the older dumps and that the program recommended would grab it.

There are several reasons that may prevent you from having a DMP file in the usual places.

If you control panel is not configured for small dump you probably will then find it in C:\windows and it will be called MEMORY.dmp. It will overwrite every crash.

Other reasons are if you have UAC turned off, if you have a small page file, or a page file on a different HD than the OS.

Hm, ok. I changed my setting as instructed, restarted, and I duplicated the conditions that caused the BSOD again, yet no new dump was created in the minidump folder. Should I just zip up a copy of my Memory.dmp file or...?

Edit: My Memory.dmp file is showing a last edited date of 2010 as well. Uh, what exactly should I do?

 

[zigzag3143]

There are several reasons that may prevent you from having a DMP file in the usual places.

If you control panel is not configured for small dump you probably will then find it in C:\windows and it will be called MEMORY.dmp. It will overwrite every crash.

Other reasons are if you have UAC turned off, if you have a small page file, or a page file on a different HD than the OS.

 

[blackwarden999]

There are several reasons that may prevent you from having a DMP file in the usual places.

If you control panel is not configured for small dump you probably will then find it in C:\windows and it will be called MEMORY.dmp. It will overwrite every crash.

Other reasons are if you have UAC turned off, if you have a small page file, or a page file on a different HD than the OS.

Ok, can you please clarify? I have UAC turned on and I don't have a different HD. My control panel was configured for a small dump, it's showing that it should be in "%SystemRoot%\Minidump" and the "write an event to the system log" is checked. That would mean that the only issue then is a small page file but I'm not exactly sure what that means and what I can do about it?

 

[zigzag3143]

There are several reasons that may prevent you from having a DMP file in the usual places.

If you control panel is not configured for small dump you probably will then find it in C:\windows and it will be called MEMORY.dmp. It will overwrite every crash.

Other reasons are if you have UAC turned off, if you have a small page file, or a page file on a different HD than the OS.

Ok, can you please clarify? I have UAC turned on and I don't have a different HD. My control panel was configured for a small dump, it's showing that it should be in "%SystemRoot%\Minidump" and the "write an event to the system log" is checked. That would mean that the only issue then is a small page file but I'm not exactly sure what that means and what I can do about it?

In your system control panel there is a place to set your page file. If you haven't touched it, it is probably set to system managed. If that is the case it is set correctly.

There are other reasons that a DMP isnt created but if you still dont have one upload your event viewr logs to us and we can look through them.

Please provide us with your Event Viewer administrative logs by following these steps:


Click Start Menu
Type eventvwr into Search programs and files (do not hit enter)
Right click eventvwr.exe and click Run as administrator
Expand Custom Views
Click Administrative Events
Right click Administrative Events
Save all Events in Custom View As...
Save them in a folder where you will remember which folder and save as Errors.evtx
Go to where you saved Errors.evtx
Right click Errors.evtx -> send to -> compressed (zipped) folder
Upload the .zip file here.

 

[blackwarden999]

Ok, I've uploaded the event viewer logs.

 

[zigzag3143]

Ok, I've uploaded the event viewer logs.

The event viewer logs dont shed any new light on the problem. I would try re-installing silverlight, flash, etc.

 

[blackwarden999]

Ok, I've uploaded the event viewer logs.

The event viewer logs dont shed any new light on the problem. I would try re-installing silverlight, flash, etc.

Would it be possible for the problem to originate from the wireless? I've been trying to duplicate the BSOD on a wired connection but it seems to load fine, without any issues. I do find it weird however that I'd only get a BSOD loading something with Flash/Silverlight on wireless and nothing else.

 

[zigzag3143]

Ok, I've uploaded the event viewer logs.

The event viewer logs dont shed any new light on the problem. I would try re-installing silverlight, flash, etc.

Would it be possible for the problem to originate from the wireless? I've been trying to duplicate the BSOD on a wired connection but it seems to load fine, without any issues. I do find it weird however that I'd only get a BSOD loading something with Flash/Silverlight on wireless and nothing else.

Could be. In your event viewer there were many DHCP/DNS timeouts, but they are somewhat normal in networking. In your case they may not be normal.

If you continue to work on Ethernet, and crash on wifi, you might want to try updating the routers firmware.