BSOD

[CMurphy3639]

Thanks in advance to anyone who offers help. I built this computer about 11-12 months ago using a parts list from a pretty reliable friend. Everything went fine and I've really had no problems with it until now. Last week while browsing the web, the video screwed up and blue screened. I tried restarting in safe mode and normal, both times it just bluescreened again. Finally I got to a point where it told me I had windows files corrupt. I formatted and reinstalled, however the problems persist. However it only seems to be now when I'm playing Call of Duty online, I haven't had the graphics issues doing anything else other than the first browsing incident. On restart, the computer doesn't always boot up properly. 75% of the time after a BSOD, I have to reset the CMOS using the jumper or even taking out the battery for a few minutes. Sometimes it takes multiple attempts. I'm not really sure what the issue is all of a sudden and I don't know computers well enough to diagnose it on my own. Attached is the .zip of minidump files. ANY help or advice is appreciated. Thanks again.

 

[zigzag3143]

Thanks in advance to anyone who offers help. I built this computer about 11-12 months ago using a parts list from a pretty reliable friend. Everything went fine and I've really had no problems with it until now. Last week while browsing the web, the video screwed up and blue screened. I tried restarting in safe mode and normal, both times it just bluescreened again. Finally I got to a point where it told me I had windows files corrupt. I formatted and reinstalled, however the problems persist. However it only seems to be now when I'm playing Call of Duty online, I haven't had the graphics issues doing anything else other than the first browsing incident. On restart, the computer doesn't always boot up properly. 75% of the time after a BSOD, I have to reset the CMOS using the jumper or even taking out the battery for a few minutes. Sometimes it takes multiple attempts. I'm not really sure what the issue is all of a sudden and I don't know computers well enough to diagnose it on my own. Attached is the .zip of minidump files. ANY help or advice is appreciated. Thanks again.

You have several DMP's in this upload that have a date back in 2008 so I am just running the current ones now.

 

[ttran]

Hi there, welcome to SF
I think u have problem with drivers
here is the bugcheck for all of your minidump files

BugCheck 1000007E, {ffffffffc0000005, fffff8800459784f, fffff88003cb8638, fffff88003cb7e90}
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_SEGMENT::FlushPendingCPUAccess+57 )
Followup: MachineOwner
---------
BugCheck 1A, {411, fffff6800002cd98, 88500000b63d8884, ff7ff6800002cd99}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+6091 )
Followup: MachineOwner
---------
BugCheck 3B, {c0000005, fffff88002d20f01, fffff88007b12fa0, 0}
Probably caused by : Npfs.SYS ( Npfs!NpReadDataQueue+171 )
Followup: MachineOwner
---------
BugCheck A, {c000010e, 2, 0, fffff80002ad0db0}
Probably caused by : ntkrnlmp.exe ( nt!KiFlushRangeWorker+0 )
Followup: MachineOwner
---------
BugCheck 3B, {c0000005, fffff9600015b51c, fffff88009040f90, 0}
Probably caused by : win32k.sys ( win32k!SleepInputIdle+4 )
Followup: MachineOwner
---------

I checked your drivers, look like they all up to date
First I would do system file check to see if everything is fine, to do that
Go Start-->type cmd in search and run it as administrator--> in cmd window type in sfc /scannow (space between sfc and /)
I would use driver verifier
below is part of a post of Ken, a great expert of 7forum

If your BSODs are 3rd party sofware related, the Driver Verifier will help flush out the rogue driver by flagging it and causing your system to BSOD.


1. Create a Windows System Restore Point -
Vista --> START | type rstrui - create a restore point

Windows 7 --> START | type create | select "Create a Restore Point"

2. Run the Driver Verifier -
DRIVER VERIFIER

START | type verifier | make these selections - 

1. Select 2nd option - "Create custom settings (for code developers)"
2. Select 2nd option - "Select individual settings from a full list"
3. Check these boxes -

• Special Pool • Pool Tracking • Force IRQL checking • Deadlock Detection • Security Checks (Windows 7) • Miscellaneous Checks

4. Select last option - "Select driver names from a list"
5. Click on the Provider heading - sorts list by Provider
6. Check ALL boxes where "Microsoft" IS NOT the Provider
7. Click on Finish 

*** IMPORTANT - PLEASE READ:

- If the Driver Verifier (DV) finds a violation, it will result in a BSOD

- After re-start, you may not be able to log on to normal Windows
... • Boot into SAFEMODE - tap the F8 key repeatedly during boot-up
... • Select "System Restore"
... • Choose the restore point that you created in step #1

- For Driver Verifier status - type verifier /query (in a cmd/DOS screen)
- To turn Driver Verifier off - verifier /reset then re-boot

- The Driver Verifier needs to run as long as possible - even if the status screen appears clear.
- All future BSOD dumps must be VERIFIER_ENABLED_MINIDUMPs - otherwise the dump(s) are of no use

If your system does BSOD while the Driver Verifier is running, please retrieve the dump file from c:\windows\minidump, zip it up & attach to your next post.

 

[CMurphy3639]

Will do.

 

[zigzag3143]

TTran

Excellant analysis. Just an FYI. In three of the below the first parameter indicated a memory exception. (ffffffffc0000005) so I would also suggest downloading a 3rd party app called memtestx86, burn it to CD, and run it for at least 7 passes.

Thanks

Ken

Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Wed Jun  9 01:14:40.524 2010 (GMT-4)
System Uptime: 0 days 0:03:44.897
BugCheck 1000007E, {ffffffffc0000005, fffff8800459784f, fffff88003cb8638, fffff88003cb7e90}
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_SEGMENT::FlushPendingCPUAccess+57 )
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Wed Jun  9 01:37:59.747 2010 (GMT-4)
System Uptime: 0 days 0:10:07.371
BugCheck 1A, {411, fffff6800002cd98, 88500000b63d8884, ff7ff6800002cd99}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+6091 )
BUGCHECK_STR:  0x1a_411
PROCESS_NAME:  vsserv.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Wed Jun  9 01:10:18.384 2010 (GMT-4)
System Uptime: 0 days 8:19:11.007
BugCheck 3B, {c0000005, fffff9600015b51c, fffff88009040f90, 0}
Probably caused by : win32k.sys ( win32k!SleepInputIdle+4 )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  Steam.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Wed Jun  9 02:00:31.189 2010 (GMT-4)
System Uptime: 0 days 0:10:43.812
BugCheck 3B, {c0000005, fffff88002d20f01, fffff88007b12fa0, 0}
Probably caused by : Npfs.SYS ( Npfs!NpReadDataQueue+171 )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  iw4mp.exe

 

[CMurphy3639]

"Windows Resource Protection did not find any integrity violations."

Do you want me to go through the process you quoted from Ken next?

 

[ttran]

yes please, also run memtest86 as Ken suggest also

 

[CMurphy3639]

Ok I opened the verifier and did all the settings in the quote, clicked finished, restarted my computer and the computer blue screened as soon as the desktop tried to load.

 

[CMurphy3639]

Attached is the minidump files from the verifier restart.

Also, in regards to memtextx86, does it matter that I'm using 64 bit?

 

[ttran]

Are you using Bitdefender? Bugcheck indicated bdfm.sys, which is belong to bitdefender product, caused BSOD
Please un-install the Bitdefender if that is the case, then use MSE instead, then tell us how it goes
http://www.microsoft.com/security_essentials/
Here is the bugcheck for the minidump you just uploaded

Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Users\TUANTR~1\AppData\Local\Temp\Rar$DI12.588\061510-19515-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*e:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (3 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02a18000 PsLoadedModuleList = 0xfffff800`02c55e50
Debug session time: Tue Jun 15 14:41:52.764 2010 (UTC + 7:00)
System Uptime: 0 days 0:00:46.153
Loading Kernel Symbols
...............................................................
................................................................
..........................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck C4, {f6, aac, fffffa80069abb30, fffff88007dd4651}
Unable to load image \SystemRoot\system32\DRIVERS\bdfm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for bdfm.sys
*** ERROR: Module load completed but symbols could not be loaded for bdfm.sys
Probably caused by : bdfm.sys ( bdfm+e651 )
Followup: MachineOwner
---------

 

[zigzag3143]

Attached is the minidump files from the verifier restart.

Also, in regards to memtextx86, does it matter that I'm using 64 bit?

Doesnt matter that you are using 64 bit as it is burned to a cd, booted from, and run outside of windows. It is going to take a while but is worth it.


Ken

 

[CMurphy3639]

Ok I'm going to retry the verifier now and then run the memtest86 overnight.

 

[CMurphy3639]

I tried to rerun the verifier. This is what I got from the Windows Boot Manager:

"Windows failed to start. A recent hardware or software change might be the cause. To fix the problem blah blah blah

Status: 0xc000000e

Info: The boot selection failed because a required device is inaccessible."

So what do I do since I can't even get into safe mode now?

 

[CMurphy3639]

Using the Windows CD, I was able to repair the bootup error that was going on. I tried to load the system restore point from before the verifier but it says system restore is turned off and I got an error when I tried to turn it on.

Also, what should I do about the verifier at this point?

 

[ttran]

Hi CMurPhy
thanks for waiting
I just got some advises from Ken (zigzag3143).
Do you have the backup and restore point, if yes, u can boot from DVD and repair. If not, I would suggest to do a clean-install of window 7
Sorry but this is only thing I can think of rightnow

 

[CMurphy3639]

TTran,

Thanks to you and Ken for all your help, I can see you guys are busy on here and I appreciate you just trying to help.

I was able to do the system repair via my disk, but all my system restore points are gone apparently. I'm back on my desktop at least. Is there any data from the verifier I can get to try and help diagnose what happened or should I just go ahead and do the memory scan overnight and come back tomorrow with the results?

 

[ttran]

Go ahead and do memory scan overnight, it might give us interesting results:sarc:

 

[CMurphy3639]

Ok, I'll run it overnight and post results tomorrow. I'm curious, what about that verifier would have totally prevented the start up from happening? I thought the verifier just scans?

 

[ttran]

yeah, When that happend, usually we restore the system point in order to bring system back to life

 

[CMurphy3639]

Well I'm guessing because it can't run that there IS DEFINITELY a problem and we can't use the verifier to help us figure out the issue?