BSODs 0x50 and 0x101 - Windows 7 x64

P

PabloDrummannBase

New member
Joined
Nov 4, 2014
Posts
3
Hello Sysnative Forums,


I have recently upgraded my seven year old computer running XP to Windows 7. I realize that by year five, I should have just bought a new computer but my ignorance about upgrades has lead me here. Though my upgrade experience has thus far been better then expected, I have been dogged by an occurrence of a 0x50 and 0x101 BSOD that crops up once every other day.


Besides help with my upgrade, I added an additional fan to my chassis bringing the total to four fans (90mm side, 120mm, rear, 120mm front and AMD stock CPU fan). I have also beefed my power supply from Logisys PS480D (480W) to a Thermaltake TR2 (600W). This has helped cut down on the frequency of this crash as well as eliminating a 0x101 that I was getting just after the upgrade.


For these errors, I have been running the Kernel Mini Dumps through WinDbg but it only states that it has been unable to identify the driver causing the trouble. I think my drivers have all been updated but maybe I am missing something. I thought that running Driver Verifier while the dumps were occuring would help distinguish the errors but that hasn't worked either.


I have done multiple malware/virus scans utilizing ESET Online Scanner, Malwarebytes and Microsoft Security Essentials. The results were clean.


I have run the suggested hardware tests. For my hard drive I have run chkdsk on more then one occasion and no errors were found. I have also run the Hitachi DFT32 hard drive test and no errors were found for that.


For RAM, I have run memtest86 on both sticks of my 4 gigs of ram collectively and separately on each stick for (8) passes on each test. No errors were found.


Here are answers to the system questions that were posed:


· OS - Windows 8.1, 8, 7, Vista ? Windows 7 Home Premium Edition
· x86 (32-bit) or x64 ? x64
· What was original installed OS on system? XP Home Edition SP-3, x86
· Is the OS an OEM version (came pre-installed on system) or full retail version (YOU purchased it from retailer)? OEM version that I bought.
· Age of system (hardware): seven years
· Age of OS installation - have you re-installed the OS? Clean installation not even a month old.


· CPU - AMD Athlon 64x2 6000+
· Video Card - Geforce 7300 GS
· MotherBoard - ASUS M2V-MX
· Power Supply - brand & wattage (if laptop, skip this one) - Thermaltake TR2 (600W)


· System Manufacturer - Homebrew
· Exact model number (if laptop, check label on bottom) - n/a


· Laptop or Desktop? Desktop


As far as my troubleshooting goes at this point, I am not sure what steps to take next. I appreciate any assistance toward my way.
 

Attachments

Hi,

Can't debug 0x101's without a kernel dump, so I'll just do the 0x50 for now.

PAGE_FAULT_IN_NONPAGED_AREA (50)

This indicates that invalid system memory has been referenced.

Code: 
0: kd> !verifier

Verify Flags Level 0x0000092b

  STANDARD FLAGS:
    [X] (0x00000000) Automatic Checks
    [X] (0x00000001) Special pool
    [X] (0x00000002) Force IRQL checking
    [X] (0x00000008) Pool tracking
    [ ] (0x00000010) I/O verification
    [X] (0x00000020) Deadlock detection
    [ ] (0x00000080) DMA checking
    [X] (0x00000100) Security checks
    [X] (0x00000800) Miscellaneous checks

You have verifier enabled.

Code: 
0: kd> k
Child-SP          RetAddr           Call Site
fffff800`00b9c968 fffff800`02f3e5b3 nt!KeBugCheckEx
fffff800`00b9c970 fffff800`02ebfcee nt! ?? ::FNODOBFM::`string'+0x43801
fffff800`00b9cad0 fffff800`02e0deea nt!KiPageFault+0x16e
fffff800`00b9cc68 fffff800`02e12768 hal!HalpHpetQueryCount+0x1c
fffff800`00b9cc70 fffff800`02eca786 hal!KeQueryPerformanceCounter+0x74
fffff800`00b9cca0 fffff800`02eb989c nt!PoIdle+0x5a7
fffff800`00b9cd80 00000000`00000000 nt!KiIdleLoop+0x2c

Not really much to go on here, pretty barren stack. The only thing that's going on here is processor #0 was idle but then awoke to retrieve the current value and frequency of the performance counter (KeQueryPerformanceCounter routine call). We hit the access violation after attempting to do so.

Code: 
0: kd> .trap 0xfffff80000b9cad0
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffffdffd0b000 rbx=0000000000000000 rcx=0000000280000024
rdx=0000000000bf368a rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002e0deea rsp=fffff80000b9cc68 rbp=0000000000000000
 r8=0000000000000000  r9=0000000000da7a64 r10=000000000006ff30
r11=fffff8000303ce00 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
hal!HalpHpetQueryCount+0x1c:
fffff800`02e0deea 448b80f0000000  [COLOR=#0000ff]mov     [/COLOR][COLOR=#008000]r8d[/COLOR],dword ptr [[COLOR=#800080]rax+0F0h[/COLOR]] ds:fffffffd`ffd0b0f0=????????

We were setting r8d to the value at address rax+0F0. Why did this fail?

Code: 
0: kd> !pte fffffffdffd0b000
                                           VA fffffffdffd0b000
PXE at FFFFF6FB7DBEDFF8    PPE at FFFFF6FB7DBFFFB8    PDE at FFFFF6FB7FFF7FF0    PTE at FFFFF6FFFEFFE858
contains 00000000001EE063  contains 0000000000000000
GetUlongFromAddress: unable to read from fffff800030f95dc
pfn 1ee       ---DA--KWEV  [COLOR=#ff0000]not valid[/COLOR]

rax's contents were invalid.


I'll really need a verifier enabled kernel dump to be definitive, but I'm pretty sure this is a bad CPU.

Can you please find it in C:\Windows labeled MEMORY.DMP, and then upload it 3rd party and paste the link here? I mention 3rd party as it'll be too large to locally upload.

Regards,

Patrick
 
Hi Patrick,

When I supply Driver Verifier Kernel Dumps, do you need dumps that are 3rd party drivers only or do want Driver Verifier Dumps with everything?
 
I'll just paste my DV instructions here for you so there's no confusion:

Driver Verifier:

What is Driver Verifier?

Driver Verifier monitors Windows kernel-mode drivers, graphics drivers, and even 3rd party drivers to detect illegal function calls or actions that might corrupt the system. Driver Verifier can subject the Windows drivers to a variety of stresses and tests to find improper behavior.

Essentially, if there's a 3rd party driver believed to be causing the issues at hand, enabling Driver Verifier will help us see which specific driver is causing the problem.

Before enabling Driver Verifier, it is recommended to create a System Restore Point:

Vista - START | type rstrui - create a restore point
Windows 7 - START | type create | select "Create a Restore Point"
Windows 8/8.1 - Restore Point - Create in Windows 8

How to enable Driver Verifier:

Start > type "verifier" without the quotes > Select the following options -

1. Select - "Create custom settings (for code developers)"
2. Select - "Select individual settings from a full list"
3. Check the following boxes -
- Special Pool
- Pool Tracking
- Force IRQL Checking
- Deadlock Detection
- Security Checks (only on Windows 7 & 8/8.1)
- DDI compliance checking (only on Windows 8/8.1)
- Miscellaneous Checks
4. Select - "Select driver names from a list"
5. Click on the "Provider" tab. This will sort all of the drivers by the provider.
6. Check EVERY box that is NOT provided by Microsoft / Microsoft Corporation.
7. Click on Finish.
8. Restart.

Important information regarding Driver Verifier:

- Perhaps the most important which I will now clarify as this has been misunderstood often, enabling Driver Verifier by itself is not! a solution, but instead a diagnostic utility. It will tell us if a driver is causing your issues, but again it will not outright solve your issues.

- If Driver Verifier finds a violation, the system will BSOD. To expand on this a bit more for the interested, specifically what Driver Verifier actually does is it looks for any driver making illegal function calls, causing memory leaks, etc. When and/if this happens, system corruption occurs if allowed to continue. When Driver Verifier is enabled per my instructions above, it is monitoring all 3rd party drivers (as we have it set that way) and when it catches a driver attempting to do this, it will quickly flag that driver as being a troublemaker, and bring down the system safely before any corruption can occur.

- After enabling Driver Verifier and restarting the system, depending on the culprit, if for example the driver is on start-up, you may not be able to get back into normal Windows because Driver Verifier will detect it in violation almost straight away, and as stated above, that will cause / force a BSOD.

If this happens, do not panic, do the following:

- Boot into Safe Mode by repeatedly tapping the F8 key during boot-up.

- Once in Safe Mode - Start > Search > type "cmd" without the quotes.

- To turn off Driver Verifier, type in cmd "verifier /reset" without the quotes.

- Restart and boot into normal Windows.

If your OS became corrupt or you cannot boot into Windows after disabling verifier via Safe Mode:

- Boot into Safe Mode by repeatedly tapping the F8 key during boot-up.

- Once in Safe Mode - Start > type "system restore" without the quotes.

- Choose the restore point you created earlier.

-- Note that Safe Mode for Windows 8/8.1 is a bit different, and you may need to try different methods: 5 Ways to Boot into Safe Mode in Windows 8 & Windows 8.1

How long should I keep Driver Verifier enabled for?

I recommend keeping it enabled for at least 24 hours. If you don't BSOD by then, disable Driver Verifier. I will usually say whether or not I'd like for you to keep it enabled any longer.

My system BSOD'd with Driver Verifier enabled, where can I find the crash dumps?

- If you have the system set to generate Small Memory Dumps, they will be located in %systemroot%\Minidump.

- If you have the system set to generate Kernel Memory Dumps, it will be located in %systemroot% and labeled MEMORY.DMP.

Any other questions can most likely be answered by this article:

Using Driver Verifier to identify issues with Windows drivers for advanced users

Regards,

Patrick
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top