[SOLVED] random BSOD

keristhename · Jun 30, 2013

Hello, I have a few problems lately. I have an HP envy sleekbook 4-1055tx. i5-3317u processor, Intel HD 4000 and AMD radeon HD 7670m vga, 4gig 1600Mhz ddr3 RAM, Hitachi 500gb storage. I am currently running in Windows 8 Pro 64 bit. Original OS was windows 7 Home Premium 64 bit. I have experienced these BSODs with windows 8, I tried reverting back to original OS but still experienced same crashes, so I upgraded again to windows 8 and replaced a new RAM. I still encountered BSODs. I have updated all my drivers from HP website (except for the amd driver which I got from amd support). here is the link to my minidump files.

minidump.rar

Please help I'm kind of desperate here.

Patrick · Jun 30, 2013

Hi,

Various different bugchecks - ATTEMPTED_WRITE_TO_READONLY_MEMORY (be), PAGE_FAULT_IN_NONPAGED_AREA (50), NTFS_FILE_SYSTEM (24). Given the bugchecks I am going to assume for now we have a simple device driver, however with 50 and 24 we have also possibly have a corrupt NTFS volume, etc. In one of the BE bugchecks, we have the following on the stack:

Code:

fffff802`4a03f6b8 fffff880`01c9a808 : 00000001`47e3fd28 00000028`00000006 fffffa80`00000001 00000000`00000000 : tcpip!memset+0x9e
fffff802`4a03f6c0 fffff880`01c9b5a2 : fffffa80`09405550 fffff880`01c09700 fffffa80`06609740 fffffa80`06609740 : tcpip!TlShimDirectClassify+0xe8
fffff802`4a03f830 fffff880`01c8cb88 : fffff802`4a03fa40 fffff802`4aaeee5c fffffa80`06672b00 fffff880`01e38132 : tcpip!WfpTlShimInspectRecvTcpDatagram+0x352
fffff802`4a03fa00 fffff880`01c980d6 : 00000000`00000000 00000000`00000004 00000000`00001000 fffff780`00000320 : tcpip!InetInspectReceiveTcpDatagram+0x408
fffff802`4a03fb30 fffff880`01c988f3 : fffff802`4a0400d8 fffff802`4a040098 fffff802`4a0400b8 00000000`00000000 : tcpip!TcpTcbReceive+0xf6
fffff802`4a03fc90 fffff880`01c92d01 : fffff880`0594a9a2 fffffa80`07ab0000 00000000`00000000 fffffa80`054b9f30 : tcpip!TcpMatchReceive+0x1f3
fffff802`4a03fe10 fffff880`01c76e5f : fffffa80`07a56480 fffff802`4a040119 fffff802`4a0400c8 fffff880`01e385cd : tcpip!TcpPreValidatedReceive+0x381
fffff802`4a03fef0 fffff880`01c762a8 : fffff880`04d69f8c fffffa80`00000000 00000000`00000000 00000000`00000000 : tcpip!IppDeliverListToProtocol+0x4f
fffff802`4a03ffa0 fffff880`01c7bcb1 : fffff880`01d90b90 00000000`00000000 00000000`00000000 fffff802`4a0400b8 : tcpip!IppProcessDeliverList+0x68
fffff802`4a040050 fffff880`01c754c4 : fffffa80`0a6908b0 fffffa80`0637cd00 00000000`00000008 fffff880`01d90b90 : tcpip!IppReceiveHeaderBatch+0x211
fffff802`4a040180 fffff880`01c80b4c : fffffa80`098d2080 00000000`00000000 00000000`00000001 00000000`00000001 : tcpip!IpFlcReceivePackets+0x8d4
fffff802`4a0403a0 fffff880`01c80429 : fffffa80`0989d501 fffff802`00000001 fffff880`01c80470 00000000`00000000 : tcpip!FlpReceiveNonPreValidatedNetBufferListChain+0x29e
fffff802`4a040470 fffff802`4ab39df5 : 00000000`0000003a fffffa80`098967c0 00000000`00000000 00000000`00000001 : tcpip!FlReceiveNetBufferListChainCalloutRoutine+0x119
fffff802`4a040570 fffff802`4ab3ad85 : fffff880`01c80310 fffff802`4a0406e0 fffffa80`09897a10 00000000`00000000 : nt!KeExpandKernelStackAndCalloutInternal+0xe5
fffff802`4a040670 fffff880`01c805fe : 00000000`00000001 00000000`00000000 fffffa80`00000001 00000000`00000000 : nt!KeExpandKernelStackAndCalloutEx+0x25
fffff802`4a0406b0 fffff880`01adde2e : 00000000`00000000 00000000`00000001 00000000`ffffffff fffff802`4a0407a0 : tcpip!FlReceiveNetBufferListChain+0xae
fffff802`4a040730 fffff880`01add750 : 00000000`00000002 fffffa80`09420000 00000000`00000000 00000000`00000001 : ndis!ndisMIndicateNetBufferListsToOpen+0x373
fffff802`4a0407d0 fffff880`01adda05 : fffffa80`0907f1a0 00000000`00000000 00000000`00000001 00000000`00000000 : ndis!ndisInvokeNextReceiveHandler+0x650
fffff802`4a0408a0 fffff880`05740d0f : fffffa80`09288000 fffff802`4a040a20 00000000`00000000 fffffa80`09288610 : ndis!NdisMIndicateReceiveNetBufferLists+0xc5
fffff802`4a040920 fffffa80`09288000 : fffff802`4a040a20 00000000`00000000 fffffa80`09288610 fffff802`00000001 : [COLOR=#ff0000][U][B]Rt630x64+0x1bd0f[/B][/U][/COLOR]
fffff802`4a040928 fffff802`4a040a20 : 00000000`00000000 fffffa80`09288610 fffff802`00000001 00000000`00000008 : 0xfffffa80`09288000
fffff802`4a040930 00000000`00000000 : fffffa80`09288610 fffff802`00000001 00000000`00000008 0000f800`00000900 : 0xfffff802`4a040a20

Rt630 = Rt630x64.sys (Realtek PCI/PCIe Adapters). Ensure your Realtek drivers are up to date - Realtek

If after updating Realtek drivers you're still having issues, enable Driver Verifier:
Driver Verifier:

What is Driver Verifier?
Driver Verifier is included in Windows 7, Windows Server 2008 R2, Windows Vista, Windows Server 2008, Windows 2000, Windows XP, and Windows Server 2003 to promote stability and reliability; you can use this tool to troubleshoot driver issues. Windows kernel-mode components can cause system corruption or system failures as a result of an improperly written driver, such as an earlier version of a Windows Driver Model (WDM) driver.
Essentially, if there's a 3rd party driver believed to be at issue, enabling Driver Verifier will help flush out the rogue driver by flagging it and causing your system to BSOD.
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"
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 (Windows 7)
- Concurrentcy Stress Test (Windows 8)
- DDI compliance checking (Windows 8)
- 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:
- If Driver Verifier finds a violation, the system will BSOD.
- 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 flag it, 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 > type "system restore" without the quotes.
- Choose the restore point you created earlier.
If you did not set up a restore point, do not worry, you can still disable Driver Verifier to get back into normal Windows:
- 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.
How long should I keep Driver Verifier enabled for?
It varies, many experts and analysts have different recommendations. Personally, I recommend keeping it enabled for at least 36-48 hours. If you don't BSOD by then, disable Driver Verifier.
My system BSOD'd, where can I find the crash dumps?
They will be located in C:\Windows\Minidump
Any other questions can most likely be answered by this article:
[url]http://support.microsoft.com/kb/244617[/URL]

Regards,

Patrick

keristhename · Jun 30, 2013

Wow! Thanks for the quick response. I am not very familiar with this Realtek PCI/PCIe adapter, are you perhaps referring to Realtek Card Reader?..It's the only driver in HP website with realtek on it. Sorry. I have already installed the driver when I upgraded to windows 8. I will try to reinstall it again or update it and hope no more BSOD. Thank you again. Very much Appreciated. btw, by saying corrupt NTFS volume are you saying my Hard disk can be failing?

Patrick · Jun 30, 2013

My pleasure : )

More specifically, Rt630x64.sys is a driver for a Realtek NETWORK adapter. So you're going to want to update your network drivers from HP's website.

And no, no evidence of that yet. If anything we may have to do a chkdsk / SFC if it comes to that, but we don't know if it's even file system related yet. Keeping our eyes on the Realtek network adapter driver for now.

Regards,

Patrick

keristhename · Jun 30, 2013

Ok so it's related to my Network Adapters..I'm going to reinstall and update all my network adapters then. Thank you very much for the help! Btw, I already tried chkdsk few days ago, and rebooted then sfc scan..it said it could not repair some error and will be repaired next time I rebooted. So I did and tried sfc again and no errors were found. Anyway, I'll just update everything for now and post if there is any progress later. Thank you so much!

Patrick · Jun 30, 2013

Great, thanks for the additional information!

I will look forward to your response : )

Regards,

Patrick

keristhename · Jun 30, 2013

Patrick said:
Great, thanks for the additional information!

I will look forward to your response : )

Regards,

Patrick

Hello again..I just experienced several BSODs after reinstalling my Realtek LAN network adapter. I have updated my minidump link but in case you need it here is the new link..

minidump.rar

thanks again!

Patrick · Jun 30, 2013

Okay, I am going to recommend enabling Driver Verifier so we can pinpoint whether or not we have driver causing issues here:

Driver Verifier:

What is Driver Verifier?
Driver Verifier is included in Windows 7, Windows Server 2008 R2, Windows Vista, Windows Server 2008, Windows 2000, Windows XP, and Windows Server 2003 to promote stability and reliability; you can use this tool to troubleshoot driver issues. Windows kernel-mode components can cause system corruption or system failures as a result of an improperly written driver, such as an earlier version of a Windows Driver Model (WDM) driver.
Essentially, if there's a 3rd party driver believed to be at issue, enabling Driver Verifier will help flush out the rogue driver by flagging it and causing your system to BSOD.
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"
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 (Windows 7)
- Concurrentcy Stress Test (Windows 8)
- DDI compliance checking (Windows 8)
- 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:
- If Driver Verifier finds a violation, the system will BSOD.
- 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 flag it, 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 > type "system restore" without the quotes.
- Choose the restore point you created earlier.
If you did not set up a restore point, do not worry, you can still disable Driver Verifier to get back into normal Windows:
- 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.
How long should I keep Driver Verifier enabled for?
It varies, many experts and analysts have different recommendations. Personally, I recommend keeping it enabled for at least 36-48 hours. If you don't BSOD by then, disable Driver Verifier.
My system BSOD'd, where can I find the crash dumps?
They will be located in C:\Windows\Minidump
Any other questions can most likely be answered by this article:
[url]http://support.microsoft.com/kb/244617[/URL]

Please from this point on also only attach the latest dump, and not all of them. Thanks! : )

I am going to bed now, I will check as soon as I wake up.

Regards,

Patrick

keristhename · Jun 30, 2013

2 BSOD again before i could start driver verifier. I have downloaded a program named Whocrashed and showed it was Advance Micro Devices WDDM1.2 for Radeon 7670m which I installed from windows update. I have no idea how to uninstall the program so I just uninstalled my AMD Radeon graphics driver. I am now running driver verifier. If it crashed I will update here. Thank you so much for the help Sir Patrick. I really appreciate it. I do hope it doesn't crash this time. I will keep on updating my network adapters too. Have a good night sir. Thanks!

Patrick · Jun 30, 2013

Great work, keep me updated : )

Regards,

Patrick

keristhename · Jun 30, 2013

Hello, Here are my newest minidumps.

minidump(2).rar

These two crash happened before I could run driver verifier. I recently uninstalled my AMD driver from device manager and Catalyst Control Install Manager from control panel. I have been running driver for 6 hours now and so far no BSOD. Now I don't know if reinstalling and updating my realtek lan network adapter solved the crashes earlier which pointed to realtek as the culprit. Is it possible that I have multiple driver failure? hmm I'll just let driver verifier run a little longer see if it bsod is gone for now as I plan to install amd driver again later and run driver verifier again. Need to go to school now, I hope no bsod when I get back. Thank you for the help!

Patrick · Jun 30, 2013

Hi,

Both attached dumps are verifier enabled, but unfortunately we're not getting a flagged driver.

PAGE_FAULT_IN_NONPAGED_AREA (50)

This indicates that invalid system memory has been referenced.

Usual causes are a bug in a device driver, hardware related memory issues, corrupt NTFS volume, anti-virus software.

IRQL_NOT_LESS_OR_EQUAL (a)

A kernel-mode driver or process attempted to access a protected memory location it does not have permission for, or a kernel interrupt request level (IRQL) attempted to access a memory address that is too high.

This bugcheck usually occurs when a driver uses an incorrect memory address. Other possible causes of this error include: bug in a device driver, system service, the BIOS, an old Anti-virus program or backup tool, or possibly memory issues.

Since we are not catching a driver issue here, I am going to recommend running Memtest to ensure your memory is not the culprit here:

Memtest86+:

Download Memtest86+ here:

[url]http://www.memtest.org/[/URL]

Which should I download?

You can either download the pre-compiled ISO that you would burn to a CD and then boot from the CD, or you can download the auto-installer for the USB key. What this will do is format your USB drive, make it a bootable device, and then install the necessary files. Both do the same job, it's just up to you which you choose, or which you have available (whether it's CD or USB).

How Memtest works:

Memtest86 writes a series of test patterns to most memory addresses, reads back the data written, and compares it for errors.

The default pass does 9 different tests, varying in access patterns and test data. A tenth test, bit fade, is selectable from the menu. It writes all memory with zeroes, then sleeps for 90 minutes before checking to see if bits have changed (perhaps because of refresh problems). This is repeated with all ones for a total time of 3 hours per pass.

Many chipsets can report RAM speeds and timings via SPD (Serial Presence Detect) or EPP (Enhanced Performance Profiles), and some even support changing the expected memory speed. If the expected memory speed is overclocked, Memtest86 can test that memory performance is error-free with these faster settings.

Some hardware is able to report the "PAT status" (PAT: enabled or PAT: disabled). This is a reference to Intel Performance acceleration technology; there may be BIOS settings which affect this aspect of memory timing.

This information, if available to the program, can be displayed via a menu option.

Any other questions, they can most likely be answered by reading this great guide here:

[url]http://forum.canardpc.com/threads/28864-FAQ-please-read-before-posting[/URL]

Regards,

Patrick

keristhename · Jul 1, 2013

Hello, I have new minidumps. What happened last night was like this, I uninstalled AMD driver and AMD catalyst install manager from device manager and control panel. Then I let driver verifier run for the whole night and no BSOD. So earlier this morning I restarted my laptop without installing AMD driver and driver verifier still runnning. Then everytime my laptop would boot I would get a BSODs. I can't get past the BSOD and I can't boot to safe made (I tried everything f8, shift+f8, fn+f8)..then windows 8 offered my to system restore so I did. I updated all my drivers now and so far no BSOD yet. I will try the memtest when I go to sleep. :)

minidump(3).rar

Thanks for the help I hope it's not a hardware problem as I'm out of budget.

Patrick · Jul 1, 2013

Hi,

One dump was successfully salvaged that's verifier enabled, however there's unfortunately not much I can get from it. It's flagging atikmpag.sys which is the ATI/AMD video driver. Keep me updated with how the system performs after the update of all of the drivers, etc.

Regards,

Patrick

keristhename · Jul 1, 2013

Hello, I just had a crash right now. I could upload the minidump if you want or we could wait for the other crashes to occur for comparison. I'm having multiple driver failure..Weird thing though is that after I installed the newest amd driver and updated my intel hd 4000 at device manager, I do not have the "configure switchable graphics" option when I right click at the desktop so I updated my amd driver in device manager and it downloaded but actually reverted back to a lower version. I am installing again the newest driver for now. If all else fails I might try to clean install my laptop for tonight..

keristhename · Jul 1, 2013

Here are the two new minidumps with driver verifier on and all drivers updated. Windows is also updated. I will try to run memtest tonight see if it's bad RAM. Thanks for the help! :)

minidump(4).rar

Patrick · Jul 1, 2013

Hi,

Latest two attached are: PAGE_FAULT_IN_NONPAGED_AREA (50) / IRQL_NOT_LESS_OR_EQUAL (a). I would definitely recommend a Memtest at this point! You can also try a clean install to rule out all software issues, corruption, etc, if you wish.

Regards,

Patrick

keristhename · Jul 2, 2013

Hello! I just did memtest86 for more than 12 hours. Pass: 11 Error: 0..should I try to clean install now? delete all partitions from win7(HP tools and recovery) and just format the drive C or should I delete everything?..

Patrick · Jul 2, 2013

Hi,

If you'd like to do a clean install and reinstall Windows to rule out software that's certainly an option : )

Regards,

Patrick

keristhename · Jul 3, 2013

I just did a clean install. Encountered two BSOD

minidump(5).rar

[SOLVED] random BSOD

Well-known member

Sysnative Staff

Well-known member

Sysnative Staff

Well-known member

Sysnative Staff

Well-known member

Sysnative Staff

Well-known member

Sysnative Staff

Well-known member

Sysnative Staff

Well-known member

Sysnative Staff

Well-known member

Well-known member

Sysnative Staff

Well-known member

Sysnative Staff

Well-known member