RAM related BSOD

AbsoluteGuardian

Honorable
Jan 29, 2014
132
0
10,680
Hi, I wasn't entirely sure where to post this because I'm not 100% sure about the cause of the BSOD, but today alone I've had 2 bluescreens, which all seemed to happen while I was rendering a video for a college project. I'm quite desparate to fix this as the project needs to be done by Monday and I was hoping you guys could help me out.

I would include the dump files from WhoCrashed but I don't see any way of attaching files.
 

Ota El Proscrito

Reputable
Oct 25, 2014
16
0
4,520
Ok, that could be the RAM or the GPU, can you give me your computer specifications?
If the bluescreen just happens sometimes: Try to buy new ram, if you have 4GB of RAM it shouldn't be expensive for you.
 

AbsoluteGuardian

Honorable
Jan 29, 2014
132
0
10,680


I ran the Windows Memory Diagnostic yesterday and it came up with no errors.

Specs are as follows:

OS: Windows 7 Home-Premium 64-bit
GPU: EVGA Nvidia GeForce GTX550Ti Superclocked
CPU: AMD FX-8120 eight-core
RAM: 16.0GB Dual-Channel DDR3 @ 671MHz (9-9-9-24)
MoBo: Gigabyte Technology Co., Ltd. GA-970A-D3 (Socket M2)

I'm thinking it might be some left over GPU driver since WhoCrashed always seems to hint at it being a driver and not hardware, but is there any way of cleaning out old drivers without deleting the current one? If not, could someone give me a step-by-step on how to do it properly? I like to think I'm quite tech-savvy but I'm slightly paranoid about messing this up.

 
nvlddmkm.sys is causing one of the crashes the video drivers

I would see if there are any updates for your Logitech GamePanel the drivers are 5 yrs old from 2009. And the file belonging to this LGBusEnum.sys can cause the other stop error 0x0000001e

And LGVirHid.sys - Logitech Gamepanel Virtual HID Device Driver can also cause the other 0x1e stop error . The drivers for this are also old / from 2009
 

AbsoluteGuardian

Honorable
Jan 29, 2014
132
0
10,680


I'll have a look into that right now.
 

AbsoluteGuardian

Honorable
Jan 29, 2014
132
0
10,680
Would it be safe to just...Delete those drivers? I've had a look into it and I don't even have anything that uses their GamePanel tech, I have a cheap K200 Keyboard that was never actually advertised for gaming.
 

AbsoluteGuardian

Honorable
Jan 29, 2014
132
0
10,680
I only have entries for Logitech SetPoint and Logitech Gaming Software 8.46

I don't remember installing anything for the K200, I think Windows just pulled the default drivers for it.

Edit: I uninstalled both of the pieces of software, all the drivers that were 'problematic' appear to be gone. If this actually sorts out the BSODs I'll be amazed, although I'll know for sure when I try to render the video again.
 

AbsoluteGuardian

Honorable
Jan 29, 2014
132
0
10,680


I'll mark your post as the solution tomorrow, assuming nothing blows up while I'm rendering the video. Either way, thanks for your help. Even if this wasn't the main culprit then these drivers were causing problems and I'm glad to be rid of them.

 
Are you using a Shock4 controller? I would uninstall these drivers

I think this jswpslwfx.sys belongs to a dlink wireless adapter. See if there are updated drivers for it, these are old / from 2008

I see this file is on your system spfdrv.sys I think it belongs to some softperfect program. Whats the program?
 

AbsoluteGuardian

Honorable
Jan 29, 2014
132
0
10,680


I've deleted jswpslwfx.sys (simply because I don't use a wireless adapter anymore) and spfdrv.sys since it seems very sketchy, I've never used a 3rd party firewall before.

I'm not using a DualShock4 controller but I am using DualShock3, however I've been using it for less than a month and these bluescreens have been happening for considerably longer.

 

AbsoluteGuardian

Honorable
Jan 29, 2014
132
0
10,680
That...Didn't fix things. Now, I don't have a crash dump log for this unfortunately, since it vanished after I did a system restore but while I was RECORDING some footage my PC bluescreened and this time the cause was dxgmms1.sys I suppose this has something to do with my graphics drivers, but they are completely up to date.