Sign in with
Sign up | Sign in
Your question

It's time to stop these BSOD's NOW!

Tags:
  • Blue Screen
  • Windows 7
  • Ntoskrnl.Exe
Last response: in Windows 7
Share
October 16, 2014 1:50:37 PM

I have had at least 10 BSOD's in the last two weeks, which is unacceptable. I will link the .dmp files, and I will give my knowledge of the issue. I have had the same errors pop up multiple times now, and they consist of; ntoskrnl.exe, vwififlt.sys, and the most recent, atikmdag.sys. ANY help's appreciated as of now, because I need to type up a paper and I don't want it to crash again.

Link to all the .dmp files; I'm working on it.

Computer Specs:
- R9 270x GPU
- 500Watt PSU
- AMD FX 6300 (six cores) 3.50ghz
- One Stick of 8gb low-profile RAM
- A one TB-harddrive
- Windows 7
- Two Monitors

More about : time stop bsod

October 16, 2014 2:06:07 PM

No motherboard info , no PSU brand name, ram details (timings, freq etc)

First thing to do is prepare a usb flash or cd and run memtest86 for 2-3 passes. If you get errors then its ram related. Might be timings, might be bad contact, bad mobo slot, incorrect NB frequency or just bad ram. If memtest passes then its either AMD driver related / motherboard related or gpu related.
m
0
l
a b $ Windows 7
October 16, 2014 2:06:25 PM

Hi,

So you don't have any stop code.

Did you change any hardware recently ?
How old is your PSU and what brand ?
Did you check for malware, what's your antivirus.....

I am suspecting a weak psu, faulty /overheating GPU / or mobo problems.

If you can test with a known working psu / gpu

maybe this thread can help you
http://www.tomshardware.com/answers/id-2046508/bluescre...
http://www.tomshardware.com/answers/id-1656824/atikmdag...

m
0
l
Related resources
October 16, 2014 2:19:40 PM

I have a 970 Pro3 R2.0 Motherboard from ASRock. My PSU is only six months old, the brand is BALLISTIX crucial 8 gb, one stick, low profile. My GPU idles at 40-45 C, I don't know if that's good or bad. When I game, the CPU gets up to around 50C and the GPU to 70-75. It's not when I'm gaming though, only when I leave my computer to do another task, and when I come back, it's often a blue screen.
m
0
l
October 16, 2014 2:22:15 PM

The Bug Check code is: 0x00000050
Parameters are as follow:
1. fffff800`0482c598
2. 00000000`00000000
3. fffff800`038117d0
4. 00000000`00000000

The most recent, and most re-occuring error deals with ntoskrnl.exe, and the second place one is a tie between vwififlt.sys and atikmdag.sys. I know how to look these up and find where they came from, but I don't know what to do from there.
m
0
l
October 16, 2014 2:26:08 PM

Read my post - there is no simple answer - you'll have to do some troubleshooting including memtest86
m
0
l
October 16, 2014 2:39:08 PM

Okay, I understand and I just did some more digging and concluded that the main problem's ntoskrnl.exe, in all the crashes, it has to do with them in one way or another, with that said, what does it affect, if RAM's out of the question, I won't run the test.
m
0
l
October 16, 2014 2:46:00 PM

BSODs are most often related to RAM when no overclocking has been done to the pc
m
0
l
a b $ Windows 7
October 16, 2014 8:26:05 PM

atikmdag.sys is related to an ATI Graphics card - you might want to take a look at this possible solution - http://windows7themes.net/en-us/fix-atikmpag-sys-atikmd...

vwififlt.sys is a Windows Virtual WiFi Filter Driver - so it could be related to a wireless driver.
You might want to try and run the System File Checker (SFC) to check to make sure that driver is ok.
To run SFC do the following:
Click on Start
Type cmd in the search box
Right click on Command Prompt and select Run as an administrator
Once at the command prompt type sfc /scannow and press enter.
m
0
l
October 17, 2014 9:36:31 AM

From the sounds of it you're getting NETBIOS conflicts with something, without the dump files it's nearly impossible to say what.
However, anti virus is a good start, which are you using?

emdea22 said:
BSODs are most often related to RAM when no overclocking has been done to the pc


BSODs aren't related to hardware alone, RAM isn't always the cause, although you do have a point as RAM is the most common hardware component to go faulty and cause BSODs.

To find the dump files then go to

  1. C:\Windows\minidump


Upload all those files by copying (Make sure you copy the files otherwise you will get access denied, even if you're an administrator) them to the desktop and compressing them in a single .zip folder.

Or even better, upload a Kernel memory dump.

Go the Start
Right click My Computer
Select Properties
Click Advanced system settings
Click on the Advanced tab
Select Settings under Startup and Recovery
Then under Write debugging information select Kernel memory dump.

Once a dump is created go to:

  1. C:\Windows\memory.dmp


Copy the file to the desktop, zip it up and upload it to a file sharing site like Onedrive. After the upload is done post the download link in your next reply.
m
0
l
!