New Custom Build, Fresh Win7 install, BSOD issues ntoskrnl/win32k

Hi 7Forums,


I recently bought a new computer from a pc build website. I installed Win7 HP 64bit and started to instantly experience BSODs. After a bit of diagnostics, memtest told me that one of the RAM sticks was horrifically broken, that has since been sent off for replacement and the system has been 'more' stable with only 8gb. However I have still been experiencing BSODs specifically when the computer isn't doing very much of anything.

I have been trying to play BF4 which as you will probably know is littered with awful programming and has constant crashes, generally though (90% of the time) these are 'soft crashes' and I can ctrl alt delete and end the process. Most of the BSODs seem to not actually be related to the game crashing, though may have come about because I have been trying to update my drivers etc etc to stop the constant game crashes?!?


I have done another fresh install since removing one of the 8gb ram sticks, and did the usual driver installs, updates, and microsoft important updates. I then went through and re-installed all my usual programs - vlc/skype/CCcleaner/malwarebytes/adobe air/flash/postgresql/bbflashback video recorder/MSE.


Since my last fresh install on the 17th November I have had 12 BSODs many of which have come about when the computer is either basically idle, or i'm watching a youtube video or just browsing files in explorer rather than whilst playing bf4 or doing more intense stuff.

9x system service exception
1x kmode exception not handled
1x memory management
1x page fault in nonpaged area

All my drivers are as far as I can see up to date, where possible I auto detect.

Hopefully I have done this properly and included all information required in my pc specs pane and from the SFDTool.

Thanks in advance, this has been a very frustrating and confusing few weeks. The computer can work for hours on end absolutely fine, including to play bf4 at high fps on high settings, then suddenly doing nothing it crashes multiple times.

lsaw2


EDIT-

As per the 2nd post in this thread-
ntoskrnl.exe BSOD randomly


1) As far as I know nothing is OC.
2) I only put MSE on there.
3) I haven't run Chkdsk since this fresh install but had run it previously on my other installs...
4) Similarly I had run SFC before and got no errors

Will check 5-10 now and potentially go back and redo steps 3 and 4.

Hi lsaw2.

Your crash dumps are not showing finite cause, but they are stop 0x3B, usually caused either by RAM or by any driver failure..

Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.
If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

If memtest86+ is free from errors, enable Driver Verifier to monitor the drivers.
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

   Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

   Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

   Tip

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any.

Hi Arc, thanks.

I ran Memtest for 21 hours (10ish passes) zero errors. I then turned on driver verifier and have been using the computer as normal all day. (pic1)


I managed a hard crash ie no blue screen no nothing just the sound glitched out and the screen froze on what it was showing and it had to be turned off at the power with no crash dumps left twice now, once the screen went messy. (pic2 is the bf4 crash which made the screen go funny.) These crashes don't seem to help me with diagnostics though. The main thing that seemed slow to respond/laggier was anykind of streaming video, both just watching it and interacting with it. Pressing play on youtube would mean 2 seconds of nothing then it plays, similarly you hear the sound then 5 seconds later the pictures starts to move (now inline with the sound). Other than that it performed pretty much as normal not even a slight slowdown for bf4.

As per coolkats post in the other thread I link in my OP, I ran tdskiller, eset, run clean installs, crystal disc (pic3), have got open hardware monitor (pic4) no idea what things should be normal though.


I have idea where to go next with regards trying to figure out what is the cause/what can be done. Nothing appears in event viewer around the time of the crashes so i'm lost on what to think.


EDIT
one of the main problems I am having is just web browsers crashing alot, both firefox and chrome which i've never had any problems with are so unstable no matter how little/much I am doing with them.

Thanks in advance for your help.

lsaw2

The second screenshot is whatever a hardware failure. And you can disable driver verifier now, as it did not let you crash.

Memtest detected zero errors. So test the other hardware.

Stress test the Graphics Card using Furmark.
Video Card - Stress Test with Furmark

Stress test the CPU.
Hardware - Stress Test With Prime95

Is the computer hot? Report us the heat of the computer after a couple of hours of your normal usage. Upload a screenshot of the summery tab of Speccy. Alternatively, you can publish a Speccy snapshot too: Speccy - Publish Snapshot of your System Specs .

Check if the Power Supply Unit (PSU) supplying adequate power to the computer or not.
eXtreme Power Supply Calculator
Also let us know what is the wattage of the PSU?

Now that is interesting.

All the hardware are tested to be fine. Temps are also very nice. 650 watts are not bad for a PSU at all.

Go for teh driver verifier option now, as suggested in post #2?

Same issues, it is indicating to display failure, and memory failure.

lsaw2 said:

Does this look like a slight hardware problem, with something like the motherboard being very slightly faulty hence not being a continuous problem? IF so what can I do next to try and diagnose this? send it back to the build company?

As we have checked everything, and all came out to be good, even DV failed to catch any problematic drivers; in this situation only one thing remains there, that is the motherboard. But we cannot test it, specially in remote assistance.

I would suggest you to opt for a clean install in that stage. If it is any issue other than hardware, a clean install is supposed to minimize it.

If the BSODs still continue in the same way, better you plan to RMA the board, if possible.

Best of luck.
Keep us informed about any advancement.