Windows 7: Bsod

Boulayman · 08 Sep 2011

Did not have the time to read it and can't even find a minidump folder on my windows (?). Brand new computer, just got the ssd installed ( with great pains) yesterday. I disabled all kind of options in my ssd as outlined here ("I need a New PC!" 2011 Thread of reading the OP. Seriously. |OT2| - NeoGAF)

Those options were:

Quote:

Disable indexing
Description: Indexing creates and maintains a database of file attributes. This can lead to multiple small writes when creating/deleting/modifying files.

Searching for files will still work.
Instructions: Start Menu -> Right-Click Computer -> Manage -> Services and Applications -> Services - > Right-Click Windows Search -> Startup type: Disabled -> OK

Disable defragmentation
Description: Defragmenting a hard disk's used space is only useful on mechanical disks with multi-millisecond latencies. Free-space defragmentation may be useful to SSDs, but this feature is not available in the default Windows Defragmenter.
Instructions: Start Menu -> Right-Click Computer -> Manage -> Services and Applications -> Services - > Right-Click Disk Defragmenter -> Startup type: Disabled -> OK

Disable Write Caching
Description: There is no cache on the SSD, so there are no benefits to write caching. There are conflicting reports on whether this gains speed or not.
Instructions: Start Menu -> Right-Click Computer -> Manage -> Device Manager -> Disk drives -> Right-Click STEC PATA -> Properties -> Policies Tab -> Uncheck Enable write caching -> OK
Free up extra drive space
Disable the Page File
Description: Eliminate writing memory to the SSD, free over 2GB of disk space. Warning - If you run out of memory the program you're using will crash.
Instructions: Start Menu -> Right-Click Computer -> Properties -> Advanced System Settings -> Settings (Performance) -> Advanced Tab -> Change -> Uncheck Automatically manage -> No paging file -> Set -> OK -> Restart your computer
Alternatively, if you want to play it safer, you can set a custom size of 200MB min and max.

Disable System Restore
Description: Don't write backup copies of files when installing new programs or making system changes. Can free up between a few hundred MB to a couple GB. Warning - Although unlikely, if a driver installation corrupts your system, there won't be an automatic way to recover.
Instructions: Start Menu -> Right-Click Computer -> Properties -> Advanced System Settings -> System Protection Tab -> Configure -> Turn off system protection -> Delete -> OK

I was able to get some information from the event viewer though ( it's in french but I would be glad to translate anything if need be)

Quote:

Nom du journal*:System
Source*: Microsoft-Windows-Kernel-Power
Date*: 2011-09-08 13:37:17
ID de l’événement*:41
Catégorie de la tâche*

63)
Niveau*: Critique
Mots clés*: (2)
Utilisateur*: Système
Ordinateur*: Famille-PC
Description*:
Le système a redémarré sans s’arrêter correctement au préalable. Cette erreur peut survenir si le système ne répond plus, s’est bloqué ou n’est plus alimenté de façon inattendue.
XML de l’événement*:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331C3B3A-2005-44C2-AC5E-77220C37D6B4}" />
<EventID>41</EventID>
<Version>2</Version>
<Level>1</Level>
<Task>63</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000002</Keywords>
<TimeCreated SystemTime="2011-09-08T17:37:17.966020100Z" />
<EventRecordID>2550</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="8" />
<Channel>System</Channel>
<Computer>Famille-PC</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="BugcheckCode">0</Data>
<Data Name="BugcheckParameter1">0x0</Data>
<Data Name="BugcheckParameter2">0x0</Data>
<Data Name="BugcheckParameter3">0x0</Data>
<Data Name="BugcheckParameter4">0x0</Data>
<Data Name="SleepInProgress">false</Data>
<Data Name="PowerButtonTimestamp">0</Data>
</EventData>
</Event>

Specs of the computer: Windows 7 64 bits, 8 gb of ram, 120 ggb vertex 3 max iops ssd, 3 regular hard drives, cpu intel i5 2500 k, video card xfx ati radeon hd 5850, sound card xfi prelude 7.1, av installed: avira free

Edit: Also the first time it reboot, it told me that windows couldn't start and that I needed to put a windows installation disk. THen I turned it off and booted it up again and then it was able to start.

zigzag3143 · 08 Sep 2011

It may be located in C:\windows and be called MEMORY.DMP. You can also search for *.DMP

Boulayman · 08 Sep 2011

I just looked for both and couldn't find a thing. Neither a memory.dmp nor a single dmp file. In my older hard drive that has win 7 pro 32 bits installed I found a minidump folder but the dmp in it dates back to before today's bsod.

Edit: I figure it might have to do with all that stuff I disabled on the ssd drive %

Boulayman · 08 Sep 2011

Added file with perfmon and that other app as outlined in the forum posting rules

seth500 · 08 Sep 2011

Just reading the thread on how you disabled things on the drive, those in fact wouldn't cause a bsod those a pretty common things to do for an ssd installation so you all right there. With that said we need to get a dump file out of your computer and hopefully we can do that by enabling driver verifier so your computer will bsod:

Dump Files - Configure Windows to Create on BSOD
Driver Verifier - Enable and Disable

The first tutorial will make sure that your computer is setup to write a minidump when it blue screens. The second is to stress out the drivers to find out which driver is causing problems. So try those and see if we can get a minidump file or two.

Regards

Seth

Boulayman · 08 Sep 2011

That worked indeed and gave me the blue screen of death. I booted the computer twice, hence why I have the two dmp files that were created in the Minidump folder that windows created for the occasion. All the dmp files options were already set as the tutorial set somehow but this time it created the dump file. Currently in safe more with network support. Attached are the two dump files.

Edit: one strange thing is that I couldn't get the complete mode despite having more than 8 gb set as pagefile

Edit 2: Also, another thing. I kept hearing a loud screeching sound from my headset as windows was starting right before the bsod

seth500 · 08 Sep 2011

Well it pointing to your usb drivers it seems if you can update those and get back with us on if you have anymore problems I would appreciate it..

Code:

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


Loading Dump File [C:\Users\Administrator\Downloads\dump\090811-40653-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*F:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Machine Name:
Kernel base = 0xfffff800`02018000 PsLoadedModuleList = 0xfffff800`02255e70
Debug session time: Thu Sep  8 18:03:48.635 2011 (UTC - 6:00)
System Uptime: 0 days 0:01:35.681
Loading Kernel Symbols
...............................................................
................................................................
...................................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D5, {fffff9802718ef10, 0, fffff88003a3b740, 0}

Unable to load image \SystemRoot\System32\drivers\FNETURPX.SYS, Win32 error 0n2
*** WARNING: Unable to verify timestamp for FNETURPX.SYS
*** ERROR: Module load completed but symbols could not be loaded for FNETURPX.SYS

Could not read faulting driver name
Probably caused by : FNETURPX.SYS ( FNETURPX+1740 )

Followup: MachineOwner
---------

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_PAGE_FAULT_IN_FREED_SPECIAL_POOL (d5)
Memory was referenced after it was freed.
This cannot be protected by try-except.
When possible, the guilty driver's name (Unicode string) is printed on
the bugcheck screen and saved in KiBugCheckDriver.
Arguments:
Arg1: fffff9802718ef10, memory referenced
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation
Arg3: fffff88003a3b740, if non-zero, the address which referenced memory.
Arg4: 0000000000000000, (reserved)

Debugging Details:
------------------


Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800022c00e0
 fffff9802718ef10 

FAULTING_IP: 
FNETURPX+1740
fffff880`03a3b740 8b4330          mov     eax,dword ptr [rbx+30h]

MM_INTERNAL_CODE:  0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

BUGCHECK_STR:  0xD5

PROCESS_NAME:  XFastUsb.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff8800f4a27b0 -- (.trap 0xfffff8800f4a27b0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000001 rbx=0000000000000000 rcx=25e56c2e4fc80000
rdx=0000000000000100 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88003a3b740 rsp=fffff8800f4a2940 rbp=0000000000000002
 r8=fffff880009bf180  r9=0000000000000100 r10=0000000000000080
r11=fffff8800f4a2930 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
FNETURPX+0x1740:
fffff880`03a3b740 8b4330          mov     eax,dword ptr [rbx+30h] ds:000e:00000000`00000030=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002108df4 to fffff800020885c0

STACK_TEXT:  
fffff880`0f4a2648 fffff800`02108df4 : 00000000`00000050 fffff980`2718ef10 00000000`00000000 fffff880`0f4a27b0 : nt!KeBugCheckEx
fffff880`0f4a2650 fffff800`020866ae : 00000000`00000000 fffff980`2718eee0 00000000`00000000 fffffa80`0d59e010 : nt! ?? ::FNODOBFM::`string'+0x426f7
fffff880`0f4a27b0 fffff880`03a3b740 : fffff980`2718eee0 00000000`00000002 fffff980`2718eee0 fffffa80`0aef1060 : nt!KiPageFault+0x16e
fffff880`0f4a2940 fffff980`2718eee0 : 00000000`00000002 fffff980`2718eee0 fffffa80`0aef1060 fffffa80`0d9bc260 : FNETURPX+0x1740
fffff880`0f4a2948 00000000`00000002 : fffff980`2718eee0 fffffa80`0aef1060 fffffa80`0d9bc260 fffff800`0252ec16 : 0xfffff980`2718eee0
fffff880`0f4a2950 fffff980`2718eee0 : fffffa80`0aef1060 fffffa80`0d9bc260 fffff800`0252ec16 fffff980`2718eee0 : 0x2
fffff880`0f4a2958 fffffa80`0aef1060 : fffffa80`0d9bc260 fffff800`0252ec16 fffff980`2718eee0 00000000`00000002 : 0xfffff980`2718eee0
fffff880`0f4a2960 fffffa80`0d9bc260 : fffff800`0252ec16 fffff980`2718eee0 00000000`00000002 fffffa80`0d9d5d00 : 0xfffffa80`0aef1060
fffff880`0f4a2968 fffff800`0252ec16 : fffff980`2718eee0 00000000`00000002 fffffa80`0d9d5d00 fffffa80`06ef9b98 : 0xfffffa80`0d9bc260
fffff880`0f4a2970 fffff800`023a0597 : fffffa80`0d9d5d00 fffff880`0f4a2c60 fffffa80`0d9d5d00 fffffa80`0d9bc260 : nt!IovCallDriver+0x566
fffff880`0f4a29d0 fffff800`023a0df6 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!IopXxxControlFile+0x607
fffff880`0f4a2b00 fffff800`02087813 : 00000000`000008be fffff880`0f4a2b88 fffffa80`0d89bb90 0000007f`ffffffff : nt!NtDeviceIoControlFile+0x56
fffff880`0f4a2b70 00000000`74fe2dd9 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0008ebf8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x74fe2dd9


STACK_COMMAND:  kb

FOLLOWUP_IP: 
FNETURPX+1740
fffff880`03a3b740 8b4330          mov     eax,dword ptr [rbx+30h]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  FNETURPX+1740

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: FNETURPX

IMAGE_NAME:  FNETURPX.SYS

DEBUG_FLR_IMAGE_TIMESTAMP:  48e6d476

FAILURE_BUCKET_ID:  X64_0xD5_VRF_FNETURPX+1740

BUCKET_ID:  X64_0xD5_VRF_FNETURPX+1740

Followup: MachineOwner
---------

Thats it for me tonight I'll be back in the morning to catch up with ya.

Regards

Seth

Boulayman · 08 Sep 2011

Thanks a lot for the help. I will look into updating them tonight and rerun the verifier. Good night !

Boulayman · 08 Sep 2011

I updated my bios, and ran verifier and it didnt't fix the problem. ON top of that screeching noise, I did notice one thing: the bsod happens while windows is loading an app that came with my motherboard for the usb: Xfast Usb. That would confirm seth's theory.

seth500 · 09 Sep 2011

Go ahead and open the verifier and delete the settings and reboot the computer if you haven't already done so. I would suggest removing the application to see if the bsod's stop. Then check for driver updates without installing the software that is causing the issue. If your manufacturer of your motherboard has updated software that is current for the xfast usb then you can go ahead and install it.

I would also recommend downloading this little tool that is very easy to use called driveragent.exe what it does it will scan your computer for other hardware drivers that may need updating and will take you to a website where you can see which ones are outdated and it will tell you the name of them which in turn will allow you to google for them and install them..It's attached below.

Windows 7: Bsod

Bsod problems?