I am getting random BSODs out of no where please help

K

KevWestBeats

New Member
You guys were very helpful to me a few months back so I am hoping you will be able to help me out again. Over the weekend I was getting BSODs and something called a bad pool caller or something of that nature. so i googled it found out it had something to do with my intel wifi drivers sucking so i said ok updated the drivers didnt have any issues for 24 hours. then I just a moment ago got a random one as I was doing some work for my business. I am now afraid of going back to it and losing more work. Idk what to do please help. How do I find the problem and eliminate it. I did not get a specific error or anything.
 
Download BlueScreenView
No installation required.
Unzip downloaded file and 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.
 
==================================================
Dump File : 061112-14929-01.dmp
Crash Time : 6/11/2012 6:04:45 PM
Bug Check String :
Bug Check Code : 0x00000109
Parameter 1 : a3a039d8`996df53c
Parameter 2 : 00000000`00000000
Parameter 3 : 89408282`a3219d1d
Parameter 4 : 00000000`00000101
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+7f1c0
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17803 (win7sp1_gdr.120330-1504)
Processor : x64
Crash Address : ntoskrnl.exe+7f1c0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\windows\Minidump\061112-14929-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 7601
Dump File Size : 262,144
==================================================

==================================================
Dump File : 060912-24882-01.dmp
Crash Time : 6/9/2012 6:10:06 PM
Bug Check String : BAD_POOL_CALLER
Bug Check Code : 0x000000c2
Parameter 1 : 00000000`00000007
Parameter 2 : 00000000`0000109b
Parameter 3 : 00000000`00000000
Parameter 4 : fffffa80`08117210
Caused By Driver : fltmgr.sys
Caused By Address : fltmgr.sys+25377
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+7f1c0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\windows\Minidump\060912-24882-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 7601
Dump File Size : 262,144
==================================================

==================================================
Dump File : 060912-20919-01.dmp
Crash Time : 6/9/2012 3:40:10 PM
Bug Check String : BAD_POOL_CALLER
Bug Check Code : 0x000000c2
Parameter 1 : 00000000`00000007
Parameter 2 : 00000000`0000109b
Parameter 3 : 00000000`00000008
Parameter 4 : fffffa80`0b26d210
Caused By Driver : fltmgr.sys
Caused By Address : fltmgr.sys+25377
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+7f1c0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\windows\Minidump\060912-20919-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 7601
Dump File Size : 262,144
==================================================

==================================================
Dump File : 060812-28688-01.dmp
Crash Time : 6/8/2012 7:07:30 PM
Bug Check String : DRIVER_CORRUPTED_EXPOOL
Bug Check Code : 0x000000c5
Parameter 1 : 00000000`00000008
Parameter 2 : 00000000`00000002
Parameter 3 : 00000000`00000000
Parameter 4 : fffff800`033f9b05
Caused By Driver : Ntfs.sys
Caused By Address : Ntfs.sys+d9f4
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+7f1c0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\windows\Minidump\060812-28688-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 7601
Dump File Size : 262,144
==================================================

==================================================
Dump File : 060812-22448-01.dmp
Crash Time : 6/8/2012 6:00:09 PM
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x00000050
Parameter 1 : fffffa7f`ffffffd0
Parameter 2 : 00000000`00000001
Parameter 3 : fffff800`0328c142
Parameter 4 : 00000000`00000007
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+7f1c0
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17803 (win7sp1_gdr.120330-1504)
Processor : x64
Crash Address : ntoskrnl.exe+7f1c0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\windows\Minidump\060812-22448-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 7601
Dump File Size : 262,144
==================================================

==================================================
Dump File : 060412-27721-01.dmp
Crash Time : 6/4/2012 8:41:24 AM
Bug Check String :
Bug Check Code : 0x00000116
Parameter 1 : fffffa80`07b0a010
Parameter 2 : fffff880`01607a2c
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000002
Caused By Driver : dxgkrnl.sys
Caused By Address : dxgkrnl.sys+5d000
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+7f1c0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\windows\Minidump\060412-27721-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 7601
Dump File Size : 262,144
==================================================
 
KevWestBeats said:
That is way over my head
Click to expand...

Memtest draws random patterns in RAM in order to test that each memory cell can read and write properly. You just run it and walk away or something, just let it run. if you see any kind of error message you know there's probably a problem with your memory. if you replace the memory and still have problems, then there is probably something wrong with your motherboard (assuming the new piece is good).
 
Abzu said:
Memtest draws random patterns in RAM in order to test that each memory cell can read and write properly. You just run it and walk away or something, just let it run. if you see any kind of error message you know there's probably a problem with your memory. if you replace the memory and still have problems, then there is probably something wrong with your motherboard (assuming the new piece is good).
Click to expand...

That's not what he meant. He meant he has no idea how to create a bootable CD from an image.

KevWestBeats said:
That is way over my head
Click to expand...

Read carefully. If you still don't understand something, ask.

Download Memtest HERE: http://www.memtest86.com/memtest86-4.0a.iso.zip

Download ImgBurn from HERE: http://www.digital-digest.com/softw...w8EuP&decode=11b793aba0f4a7bc55d18d6e38753aca

Extract the ISO file from the memtest.iso.zip to a location you can find it (such as your desktop)
Install ImgBurn
Launch ImgBurn
Select "Write image file to disc"
Under "Source" click the folder with the magnifying glass. Navigate to the desktop (or wherever you extracted the ISO file to)
Insert a blank CD-R
Click the big "Burn" button at the bottom

Once done, insert the CD and reboot the computer. Go into the BIOS and change the boot order so the CD drive is the first bootable drive. Then just let memtest run. If any red shows up during the test, the you have bad RAM.
 
You must log in or register to reply here.
Back
Top