[spellcast]

I have been receiving blue screen, during games, for almost a week now.
Please help i really want this over with...
Attached dmp file.

Windows 7 ultimate
Asus formula V
AMD FX-8350
Sapphire 7970 vapor X
4X4GB RAM Kingston hyper x beast ( 2400Mhz oc )\

Edited by spellcast, 22 August 2013 - 05:59 PM.

[Advertisements]

spellcast and I'm sorry to hear you are having a issue with BSOD's.
Please note that you did not attach the dmp file to your original post. Please do so on your response and I will try to assist you.

[rshaffer61]

spellcast and I'm sorry to hear you are having a issue with BSOD's.
Please note that you did not attach the dmp file to your original post. Please do so on your response and I will try to assist you.

[spellcast]

sorry about that.

it says im unable to upload that kind of file.

[rshaffer61]

Try the following.


Download BlueScreenView
No installation required.
Double click on BlueScreenView.exe file to run the program.
When scanning is done, go Edit>Select All.
Go File>Save Selected Items, and save the report as BSOD.txt.
Open BSOD.txt in Notepad, copy all content, and paste it into your next reply.

Thanks to Broni for the instructions and program

[spellcast]

==================================================
Dump File : 090813-10124-01.dmp
Crash Time : 08/09/2013 3:16:02 PM
Bug Check String : SYSTEM_SERVICE_EXCEPTION
Bug Check Code : 0x0000003b
Parameter 1 : 00000000`c0000005
Parameter 2 : fffff800`034ae29a
Parameter 3 : fffff880`09826e40
Parameter 4 : 00000000`00000000
Caused By Driver : Wdf01000.sys
Caused By Address : Wdf01000.sys+8ebd
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+75b80
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\090813-10124-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 7601
Dump File Size : 276,472
Dump File Time : 08/09/2013 3:16:42 PM
==================================================

==================================================
Dump File : 090213-10296-01.dmp
Crash Time : 02/09/2013 6:45:16 PM
Bug Check String : SYSTEM_SERVICE_EXCEPTION
Bug Check Code : 0x0000003b
Parameter 1 : 00000000`c0000005
Parameter 2 : fffff880`012bd248
Parameter 3 : fffff880`0976fd60
Parameter 4 : 00000000`00000000
Caused By Driver : Ntfs.sys
Caused By Address : Ntfs.sys+ba248
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+75b80
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\090213-10296-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 7601
Dump File Size : 276,416
Dump File Time : 02/09/2013 6:46:25 PM
==================================================


this stupid [bleep] is driving me insane

[rshaffer61]

OK we are getting somewhere now. The driver Wdf01000.sys is part of the Windows system so now we have to determine the origin of the issue.
First do this and then I may have you update a driver or more afterwards.

Download WhoCrashed from the link in my signature below
This program checks for any drivers which may have been causing your computer to crash....

Click on the file you just downloaded and run it.
Put a tick in Accept then click on Next
Put a tick in the Don't create a start menu folder then click Next
Put a tick in Create a Desktop Icon then click on Install and make sure there is a tick in Launch Whocrashed before clicking Finish
Click Analyze
It will want to download the Debugger and install it Say Yes
WhoCrashed will create report but you have to scroll down to see it
Copy and paste it into your next reply

http://www.resplendence.com/downloads

[spellcast]

Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Sun 08/09/2013 7:16:02 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\090813-10124-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B80)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800034AE29A, 0xFFFFF88009826E40, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sun 08/09/2013 7:16:02 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800034AE29A, 0xFFFFF88009826E40, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Mon 02/09/2013 10:45:16 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\090213-10296-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0xBA248)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF880012BD248, 0xFFFFF8800976FD60, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.




--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

3 crash dumps have been found and analyzed. No offending third party drivers have been found. Consider configuring your system to produce a full memory dump for better analysis.


Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.

[rshaffer61]

It may be a case of a corrupted system file within Windows 7 so I'm going to have you run a SFC or System File Check.

SFC /Scannow Win7

Go HERE and read the tutorial that shows how to do SFC or System File Checker and running in a Elevated Command Prompt in Vista and Win7.

[spellcast]

Ok so i ran that.
and it stated there was a corrupted file but was unable to fix them.

Edited by spellcast, 12 September 2013 - 12:04 PM.

[rshaffer61]

OK we can move on to the next step then.

OK the issue seems to be the Win 7 OS itself that is causing your problem so lets do a Repair Installation by following the steps HERE.
Please read and follow all instructions carefully.

[spellcast]

ok so I did that, and have just reformated cause that didnt help, and now it still comes up as corrupted.

[rshaffer61]

Not sure why you formatted and reloaded windows but that tells me now we are dealing with a hardware issue since it is doing it with a fresh install.
Try the following and let me know what the results are.

Run hard drive diagnostics: http://www.tacktech....ay.cfm?ttid=287
Make sure, you select tool, which is appropriate for the brand of your hard drive.
Depending on the program, it'll create bootable floppy, or bootable CD.
If downloaded file is of .iso type, use ImgBurn: http://www.imgburn.com/ to burn .iso file to a CD (chose "Write image file to disc" option), and make the CD bootable.

NOTE. If your hard drive is made by Toshiba, try the Hitachi DFT CD Image version of the software

Thanks to Broni for the instructions



Once done with the above and results are posted and then I respond then you can do the next set of instructions. Do this only if the HD diagnostics does not show anything.







A If you have more than one RAM module installed, try starting computer with one RAM stick at a time.

NOTE Keep in mind, the manual check listed above is always superior to the software check, listed below. DO NOT proceed with memtest, if you can go with option A

B. If you have only one RAM stick installed...
...run memtest...


1. Download - Pre-Compiled Bootable ISO (.zip). If you prefer to use the USB version then use this link USB KEY
2. Unzip downloaded /memtest86+-4.20.iso.zip file.
3. Inside, you'll find /memtest86+-4.20.iso file.
4. Download, and install ImgBurn: http://www.imgburn.com/
5. Insert blank CD into your CD drive.
6. Open ImgBurn, and click on Write image file to disc
7. Click on Browse for a file... icon:



8. Locate memtest86+-4.20.iso file, and click Open button.
9. Click on ImgBurn green arrow to start burning bootable memtest86 CD:



10. Once the CD is created, boot from it, and memtest will automatically start to run. You may have to change the boot sequence in your BIOS to make it work right.

To change Boot Sequence in your BIOS

Reboot the system and at the first post screen (where it is counting up memory) start tapping the DEL button
This will enter you into the Bios\Cmos area.
Find the Advanced area and click Enter
Look for Boot Sequence or Boot Options and highlight that click Enter
Now highlight the first drive and follow the directions on the bottom of the screen on how to modify it and change it to CDrom.
Change the second drive to the C or Main Drive
Once that is done then click F10 to Save and Exit
You will prompted to enter Y to verify Save and Exit. Click Y and the system will now reboot with the new settings.


The running program will look something like this depending on the size and number of ram modules installed:




It's recommended to run 5-6 passes. Each pass contains very same 8 tests.

This will show the progress of the test. It can take a while. Be patient, or leave it running overnight.



The following image is the test results area:



The most important item here is the “errors” line. If you see ANY errors, even one, most likely, you have bad RAM.

[spellcast]

Ummm for the hard drive test I have an ocz solidstate

[rshaffer61]

OK skip that and do the memtest.

[spellcast]

ok so i ran the memtest

#'s - RAM sticks
/ - open
[ ] - slots

Results
[1] [2] [3] [4] Errors
[1] [/] [/] [/] Fine
[/] [2] [/] [/] Fine
[/] [/] [3] [/] Fine
[/] [/] [/] [4] Fine
[1] [/] [2] [/] Fine
[/] [3] [/] [4] Fine
[1] [3] [2] [4] Fine

like What the... is wrong i dont understand whats going on.